[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Sandisk reader problems... Same symptom as firewire?



In reference to the previous message regarding lockup at checking hardware and enabling swap errors. I have the same problem with the sandisk reader that went bad. The reader failed at the same time I was trying to hotplug the scanner from earlier postings.

With a (CF) card in the reader, it will lockup at checking hardware. If you disable kudzu, you can get the computer to boot into a normal state, even with the card reader messed up.
I'm not sure if this lockup state is similar to firewire or not. This computer does not have firewire ports.


Anyway, if no CF card is in the reader port, I am able to get the computer to boot with kudzu enabled. The green light for the CF card flashes off and on continuously. Once booted, dmesg gives me this excerpt. I added the "options scsi_mod max_luns=8" to modprobe.conf. This did not solve the problem. I guess the card reader really failed. Checking with FC1 and XP neither were able to do any better. FC1 would lockup with a CF card as FC2 does. XP recognized a usb mass storage device, but did not go any further.

Jim


sdb : READ CAPACITY failed.
sdb : status=1, message=00, host=0, driver=08
Current sd: sense key Not Ready
Additional sense: Logical unit is in process of becoming ready
sdb: assuming Write Enabled
sdb: assuming drive cache: write through
Device not ready. Make sure there is a disc in the drive.
sdb: Spinning up disk................................................................................................not responding...
sdb : READ CAPACITY failed.
sdb : status=1, message=00, host=0, driver=08
Current sd: sense key Not Ready
Additional sense: Logical unit is in process of becoming ready
sdb: assuming Write Enabled
sdb: assuming drive cache: write through
sdb:<3>Buffer I/O error on device sdb, logical block 0
Buffer I/O error on device sdb, logical block 0
Buffer I/O error on device sdb, logical block 262143
Buffer I/O error on device sdb, logical block 262143
Buffer I/O error on device sdb, logical block 0
unable to read partition table
sdb:<3>Buffer I/O error on device sdb, logical block 0
Buffer I/O error on device sdb, logical block 262143
Buffer I/O error on device sdb, logical block 0
unable to read partition table
Device not ready. Make sure there is a disc in the drive.
Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0
sdb: Spinning up disk...<7>USB Mass Storage device found at 6
.............................................................................................not responding...
sdb : READ CAPACITY failed.
sdb : status=1, message=00, host=0, driver=08
Current sd: sense key Not Ready
Additional sense: Logical unit is in process of becoming ready
sdb: assuming Write Enabled
sdb: assuming drive cache: write through
Device not ready. Make sure there is a disc in the drive.
sdb: Spinning up disk.................................



-----------------------


Referenced message.
> For me, the problem was caused by my "Sandisk ImageMate 6 in 1"
flash
> card reader. I had to disable kudzu in runlevel 1, then run the below
> command to get runlevel 5 or 3 to boot past the checking hardware prompt.

options scsi_mod max_luns=8

Try a line like this in your /etc/modprobe.conf.  Try different numbers
like "6" too.  If this seems to solve your problem, then you need to

submit information about your device ... uh... somewhere... in order to
add to a whitelist of some sort.  Reply to this list, CC me and
davej redhat com if the above suggestion seems to help.

Warren



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]