I do have the same issue when boot from i386 desktop CD and try to install
Feisty into a SanDisk Cruzer Crossfire 4GB flash disk.
During the installation, there would be some writing errors and rejecting I/O to dead device
message in dmesg. The first boot of this flash disk would end up with a corrupted filesystem.
The USB host on my motherboard is Intel based.
If I put the udev rule mentioned above in the installing system and target system, the error
messages were not in the dmesg, but a no-access or insufficient permission show in the booting
of the new installed system when the udev rule was executed. Of course, the USB flash disk booting was failed also.
I do have the same issue when boot from i386 desktop CD and try to install
Feisty into a SanDisk Cruzer Crossfire 4GB flash disk.
During the installation, there would be some writing errors and rejecting I/O to dead device
message in dmesg. The first boot of this flash disk would end up with a corrupted filesystem.
The USB host on my motherboard is Intel based.
If I put the udev rule mentioned above in the installing system and target system, the error
messages were not in the dmesg, but a no-access or insufficient permission show in the booting
of the new installed system when the udev rule was executed. Of course, the USB flash disk booting was failed also.
Hope the extra information could help a little.
djhuang