gday,

I've just bought an iriver T30 UMS an can't seem to access it in linux. Because it's the UMS version i though this wouldn't be a problem and it should mount in the usual way. Any ideas anyone?

I have tried updating the firmware to v1.50 and iriver plus2 to the latest version, then formatting the T30 with iriver plus2, but no luck. I'm just in the process of getting the latest linux kernel. Maybe the latest usb mass storage drivers will make a difference. Any help is very much appreciated. Here's some info:


"dmesg" when i plugged it in:

hub.c: new USB device 00:1d.7-5, assigned address 2
usb.c: USB device 2 (vend/prod 0x4102/0x1019) is not claimed by any active driver.
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: iriver Model: T30 Pure Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
SCSI device sda: 1017856 512-byte hdwr sectors (521 MB)
sda: Write Protect is off
sda: sda1 sda2 sda3 sda4
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.


"mount -t vfat /dev/sda1 /mnt/iriver":

mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

"dmesg" gave:

I/O error: dev 08:01, sector 0
FAT: unable to read boot sector

ok, here is what happened.

I installed the latest kernel 2.6.14.2 (i was running slackware 10.1 with 2.4.29). Then I was able to mount the filesystem with "mount -t vfat /dev/sda /mnt/iriver". I rebooted back to my original kernel and tried the same mount command, which to my supprise worked (i thought that i had previously tried this).