MP3 player (USB mass storage) not mountable anymore, no block-oriented device

the who · 09-07-2004, 07:59 AM

I have a MP3 player that worked flawlessly for months with Slackware, now I just tried to mount it again and get this error:

Code:

tom:~ $ mount /dev/sda1
mount: /dev/sda1 ist kein gültiges blockorientiertes Gerät

Which means, translated, that /dev/sda1 is no valid block-oriented device. Same error when logged in as root.

I googled for a solution but could not find anything helpful.

Entry from /etc/fstab:

Code:

/dev/sda1        /mnt/sda1        vfat        rw,user,noauto   0   0

Edit: The MP3 player itself works fine btw; I can listen to and delete mp3's. It also correctly notices when I connect it to the PC.

geomatt · 09-07-2004, 12:51 PM

Did you check to see what device name it is being assigned? Have a look at the latest entries in /var/log/messages. the reason I suggest this is that I have been having issues with usb devices being assigned different names sda1, sda2 or even sdb1 when I plug them in. There must be a solution to this dynamic renaming but I don;t know what it is. I find I have to rewrite the fstab all the time

-geomatt

failure_man · 09-07-2004, 12:53 PM

After connecting the mp3 player what output do you get from "tail /var/log/messages"?

Also, what does "cat /proc/scsi/scsi" show?

Edit: Somebody already got to /var/log/messages it seems.

As for dynamic reassignment, you could try udev if you're using 2.6*. It should be able to do what you want but I've not needed it badly enough to figure the damn thing out yet. Somebody else could probably be more helpful. Might want to search for or start a udev newbie thread.

the who · 09-07-2004, 01:11 PM

Thanks for replying.

/var/log/messages:

Code:

Sep  7 20:02:24 linux kernel: hub.c: new USB device 00:07.2-1, assigned address 13

/proc/scsi/scsi:

Code:

Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: TEAC     Model: CD-W552E         Rev: 1.13
  Type:   CD-ROM                           ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: SigmaTel Model: MSCN             Rev: 0100
  Type:   Direct-Access                    ANSI SCSI revision: 02

I'm not smarter now, does this look ok or not?

Oh, I'm using kernel 2.4.27.

failure_man · 09-07-2004, 01:54 PM

Your mp3 player is showing up as the second device in /proc/scsi/scsi. This means that the system knows it as sdb. If you adjust fstab to reflect this then it should work correctly.

As for what triggered this problem, did you just change the cd drive to scsi emulated? (Google seems to indicate that this is an ide drive. Is that correct?)

geomatt · 09-07-2004, 04:06 PM

Failure man said:

Quote:

As for dynamic reassignment, you could try udev if you're using 2.6*.

What about kernel 2.4.26? udev is included in slack 10.0 (which comes with 2.4.26) but the description of the package claims that it needs 2.6.*. Might the slack packagers just be assuming that everyone would upgrade their kernel if they wanted to use udev instead of devfs?

-geomatt

p.s. This looks like a good link on writing udev rules which I suspect is the way to get device names solidified. Haven't had time to look through it carefully yet or to try it out.

failure_man · 09-07-2004, 04:50 PM

Since 2.6* is an officially supported kernel series for Slackware 10 it makes sense to include support structure for all its features. Devfs is still available under 2.4*, though it's depreciated.

geomatt · 09-07-2004, 04:54 PM

ok. I guess I'll have to switch to 2.6.* in order to try out a udev approach.

Thanks!

-geomatt

the who · 09-07-2004, 05:55 PM

Quote:

Originally posted by failure_man
Your mp3 player is showing up as the second device in /proc/scsi/scsi. This means that the system knows it as sdb. If you adjust fstab to reflect this then it should work correctly.

As for what triggered this problem, did you just change the cd drive to scsi emulated? (Google seems to indicate that this is an ide drive. Is that correct?)

:] You're right about the CD drive part, I just fiddled around with it a few days ago. However, after adjusting /etc/fstab, I still could not mount it, same error, so I wondered what I did since I mounted it the last time, and ta-da, being the genius that I am, I somehow deactivated SCSI disk support the last time I recompiled the kernel.

Just recompiled with SCSI disk support and now it works.

Thanks for the help and sorry for wasting your time.