On Sun, Mar 19, 2006 at 11:29:16AM +0000, Wulfy wrote: > Thanks to all who answered. Much appreciated! > > (...) > > > Progress! well, some. > > I did "mkdir /media/card" so that there'd be a directory there to attach to. > > I tried each of the possibilities: > > mount -t vfat /dev/sd[a-d] /media/card > > Mount told me that a, b and d had no media but c gave me an error message: > > >Yewdales-lodge:~# mount -t vfat /dev/sdc /media/card > >mount: wrong fs type, bad option, bad superblock on /dev/sdc, > > missing codepage or other error > > In some cases useful info is found in syslog - try > > dmesg | tail or so > > I looked at dmesg | tail: > > >scsi2: ERROR on channel 0, id 0, lun 2, CDB: Read (10) 00 00 00 00 06 > >00 00 02 00 > >Current sdc: sense key Medium Error > >Additional sense: Unrecovered read error > >end_request: I/O error, dev sdc, sector 6 > >Buffer I/O error on device sdc, logical block 0 > > unable to read partition table > >FAT: bogus number of reserved sectors > >VFS: Can't find a valid FAT filesystem on dev sdc. > >FAT: bogus number of reserved sectors > >VFS: Can't find a valid FAT filesystem on dev sdc. > > I also tried Duncan's suggestion of mounting /dev/sdc1. > > >Yewdales-lodge:~# mount -t vfat /dev/sdc1 /media/card > >mount: special device /dev/sdc1 does not exist > > Two things come to mind. Either the card uses some other fs type or > I've lost all the pictures on it.... :( Of course, I'm not sure what > the dmsg error message means precisely, but "unable to read partition > table" sounds bad. That doesn't depend on the fs, does it?
Is the card reader connected directly to the pc or via a hub? I sometimes had problems when there was a hub (or even a longer cable) but it worked when I plugged it directly into the USB port. HTH -- Joachim Fahnenmüller -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
