Ha ha I did the exact same thing before with a zaurus .. I formatted the cf 
card .... ( mk2fs /dev/hde  ) and wondered why the z didn't recognise it :-)

--B

On Monday 30 December 2002 02:15, Gareth Williams wrote:
> On Monday 30 December 2002 11:55, you wrote:
> > Ok, now we're getting somewhere!! I unplugged the device AGAIN and
> > rebooted. Went through the steps again and this time it created the
> > devfs entry...but with errors in the log:
> >
> > Dec 30 11:27:17 localhost kernel: hub.c: new USB device 00:04.2-1,
> > assigned address 2
> > Dec 30 11:27:17 localhost kernel: usb.c: USB device 2 (vend/prod
> > 0xd7d/0x240) is not claimed by any active driver.
> > Dec 30 11:27:21 localhost /etc/hotplug/usb.agent: Setup usb-storage for
> > USB product d7d/240/100
> > Dec 30 11:27:21 localhost kernel: Initializing USB Mass Storage driver...
> > Dec 30 11:27:21 localhost kernel: usb.c: registered new driver
> > usb-storage Dec 30 11:27:21 localhost kernel: scsi1 : SCSI emulation for
> > USB Mass Storage devices
> > Dec 30 11:27:21 localhost kernel:   Vendor:           Model: USB Card
> > Reader   Rev: 1.06
> > Dec 30 11:27:21 localhost kernel:   Type:
> > Direct-Access                      ANSI SCSI revision: 02
> > Dec 30 11:27:21 localhost kernel: USB Mass Storage support registered.
> > Dec 30 11:27:26 localhost kernel: Attached scsi removable disk sda at
> > scsi1, channel 0, id 0, lun 0
> > Dec 30 11:27:26 localhost kernel: sda : READ CAPACITY failed.
> > Dec 30 11:27:26 localhost kernel: sda : status = 1, message = 00, host =
> > 0, driver = 08
> > Dec 30 11:27:26 localhost kernel: Current sd00:00: sense key Not Ready
> > Dec 30 11:27:26 localhost kernel: Additional sense indicates Medium not
> > present
> > Dec 30 11:27:26 localhost kernel: sda : block size assumed to be 512
> > bytes, disk size 1GB.
> > Dec 30 11:27:26 localhost kernel:  /dev/scsi/host1/bus0/target0/lun0:
> > I/O error: dev 08:00, sector 0
> > Dec 30 11:27:26 localhost kernel:  I/O error: dev 08:00, sector 0
> > Dec 30 11:27:26 localhost kernel:  I/O error: dev 08:00, sector 2097144
> > Dec 30 11:27:26 localhost kernel:  I/O error: dev 08:00, sector 2097144
> > Dec 30 11:27:26 localhost kernel:  I/O error: dev 08:00, sector 0
> > Dec 30 11:27:26 localhost kernel:  I/O error: dev 08:00, sector 0
> > Dec 30 11:27:26 localhost kernel: ldm_validate_partition_table(): Disk
> > read failed.
> > Dec 30 11:27:26 localhost kernel:  I/O error: dev 08:00, sector 0
> > Dec 30 11:27:26 localhost kernel:  I/O error: dev 08:00, sector 2
> > Dec 30 11:27:26 localhost kernel:  unable to read partition table
> >
> > Weird is says medium not present since I had a SM card in the reader
> > when I mounted it!! I had to do the sd_mod straight away or the usb
> > would time out. Anyway, once I did this I tried to mount it:
> >
> > [root@localhost jason]# modprobe sd_mod
> > [root@localhost jason]# mount /dev/sda /mnt/cf
> > /dev/sda: Input/output error
> > mount: you must specify the filesystem type
> >
> > So I tried several ways:
> > [root@localhost jason]# mount -t vfat /dev/sda /mnt/cf
> > mount: wrong fs type, bad option, bad superblock on /dev/sda,
> >        or too many mounted file systems
> > [root@localhost jason]# mount -t auto /dev/sda /mnt/cf
> > /dev/sda: Input/output error
> > mount: you must specify the filesystem type
> > [root@localhost jason]#
> >
> > I used vfat cause I know these crap readers use fat by default.
> >
> > Why can't I mount the bugger!!?!@#$%^ =)
> >
> > Cheers
> >
> > Jason
>
> I don't know a lot about these, not owning one myself, but with a regular
> HD you have to address a specific partition, such as /dev/hda1 (with the
> number), which in turn contains the filesystem. I don't think you can have
> a filesystem just on straight /dev/hda, can you? (or can you?..) Would it
> be the same with this?
> my 2c - I have a feeling I'm way off, but I can't think of anything else at
> the moment...
>
> Cheers,
>   Gareth

-- 
-- Bryan Hunt

Freedom is nothing else but the chance to do better.
-- Camus

Reply via email to