problem with devices with 2.6.10 kernel

Mr_C · 03-07-2005, 12:34 PM

I've installed my own kernel 2.6.10 on slack10.1 (pat didn't include my sound card in the generic kernel)

Here's my problem when I try to mount a cdrom

Code:

Could not mount device.
The reported error was:
mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

Code:

┌─(clay@SOL:pts/1)─────────────────────────────────────────────────────────────────(~)─┐
└─(1:%)─ ls -l /dev/cdrom
lrwxrwxrwx  1 root root 3 2005-03-07 09:39 /dev/cdrom -> hdc

however if I do the following as root it works with

Code:

root@SOL:~# mount -t 9660 /dev/cdrom/ /mnt/cdrom
mount: unknown filesystem type '9660'
root@SOL:~# modprobe isofs
root@SOL:~# mount -t auto /dev/cdrom /mnt/cdrom
mount: block device /dev/cdrom is write-protected, mounting read-only
root@SOL:~#

(with regards to the modprobe I put cdrom support as a module but didn't enable, but thats no real problem).

here's my fstab

Code:

root@SOL:~# cat /etc/fstab
/dev/hda2        swap             swap        defaults         0   0
/dev/hda1        /                reiserfs    defaults         1   1
/dev/hda3        /mnt/XP          ntfs        ro               1   0
/dev/hda4        /mnt/Data        vfat        defaults,users,umask=0,rw    0   0
/dev/cdrom       /mnt/cdrom       iso9660     noauto,ro,umask=0,users  0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0
/dev/sda1        /mnt/sda1        auto        defaults,user,quiet,umask=0,noauto,rw 0 0
/dev/sdb1        /mnt/sdb1        auto        defaults,user,quiet,umask=0,noauto,rw 0 0
root@SOL:~#

here's my mounts

Code:

root@SOL:~# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / reiserfs rw 0 0
proc /proc proc rw,nodiratime 0 0
sysfs /sys sysfs rw 0 0
none /dev ramfs rw 0 0
/dev/hda3 /mnt/XP ntfs ro,noatime,nodiratime,uid=0,gid=0,fmask=0177,dmask=077,nls=utf8,errors=continue,mft_zone_multiplier=1 0 0
/dev/hda4 /mnt/Data vfat rw,nodiratime,nosuid,nodev,noexec,fmask=0000,dmask=0000 0 0
devpts /dev/pts devpts rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0
/dev/cdrom /mnt/cdrom iso9660 ro 0 0
root@SOL:~#

so why can't I mount my cdrom as a normal user???? --> can't burn cds now of course
Oh and if I pass scsi emulation 'hdc=ide-scsi' to my grub line, hdc dissappears!

also my usb devices sda** have dissappeared

Its a notebook with dvd/cdrw drive

help anyone?!
whats really going on here?

MMYoung · 03-07-2005, 01:48 PM

Quote:

Originally posted by Mr_C
here's my fstab

root@SOL:~# cat /etc/fstab
/dev/hda2 swap swap defaults 0 0
/dev/hda1 / reiserfs defaults 1 1
/dev/hda3 /mnt/XP ntfs ro 1 0
/dev/hda4 /mnt/Data vfat defaults,users,umask=0,rw 0 0
/dev/cdrom /mnt/cdrom iso9660 noauto,ro,umask=0,users 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
/dev/sda1 /mnt/sda1 auto defaults,user,quiet,umask=0,noauto,rw 0 0
/dev/sdb1 /mnt/sdb1 auto defaults,user,quiet,umask=0,noauto,rw 0 0
root@SOL:~#

Change the umask=0 to umask=000. You might also want to also change defaults for /mnt/Data to noauto. This way you can mount/unmount when you want, just a suggestion. BTW, I wouldn't even use the umask for a cdrom, but that's a personal preference. Remove it and you should be able to mount/unmount the cdrom as whomever is logged on at the time. Matter of fact your fstab looks a bit "complicated" to me, as an example here's mine:

/dev/hdb5 swap swap defaults 0 0
/dev/hdb1 / reiserfs defaults 1 1
/dev/hdb6 /boot ext3 defaults 1 2
/dev/hdb7 /var reiserfs defaults 1 2
/dev/hdb8 /home reiserfs defaults 1 2
/dev/hda5 /share vfat noauto,users,rw 1 0
/dev/cdrom /mnt/cdrom iso9660 noauto,users,ro 0 0
/dev/dvd /mnt/dvd iso9660 noauto,users,ro 0 0
/dev/zip /mnt/zip vfat noauto,users,rw 0 0
/dev/jump64 /mnt/jump64 vfat noauto,users,rw 0 0
/dev/jump128 /mnt/jump128 vfat noauto,users,rw 0 0
/dev/usbhd1 /mnt/stuff vfat noauto,users,rw 1 0
/dev/fd0 /mnt/floppy vfat noauto,users,rw 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
none /sys sysfs defaults 0 0

Everything works JUST like I want it to. You might also want to "clean up" your sda* mounts. The way they are set only the user that mounts them can unmount them, and with defaults that might only be root (I'm not sure on that one).

Quote:

Originally posted by Mr_C
Oh and if I pass scsi emulation 'hdc=ide-scsi' to my grub line, hdc dissappears! also my usb devices sda** have dissappeared

While you can use ide-scsi with a 2.6 kernel, the question begs to be asked, "Why?". While the ATAPI driver in the kernel may not be perfect for CD burning right now, it's better than scsi emulation, IMHO. I've been using it since I my first 2.6 compile (2.6.5) and it's worked, barring the 2.6.8 - 2.6.9 thing, like a champ. I'm now using 2.6.11 with no problems. You might also want to look at your kernel config and check out the SCSI and USB section to make sure of your settings. The one thing you DON'T want to use in the USB section is UB, look for this in the USB section:

Quote:

Low Performance USB Block driver

CONFIG_BLK_DEV_UB:

This driver supports certain USB attached storage devices such as flash keys.

Warning: Enabling this cripples the usb-storage driver.

If unsure, say N.

HTH,
MMYoung

Mr_C · 03-07-2005, 01:57 PM

change to umask=000 makes no difference.
Still can't mount cdrom, not even root can 'mount /mnt/cdrom'

MMYoung · 03-07-2005, 02:15 PM

Quote:

Originally posted by Mr_C
change to umask=000 makes no difference.
Still can't mount cdrom, not even root can 'mount /mnt/cdrom'

Looking at your fstab, /mnt/cdrom is "pointing" to /dev/cdrom, which should be a symlink in /dev that points to the actual device node. So there are a couple of things you might want to check.

1.) Make sure you actually have /dev/cdrom.
2.) If you do check to see what it points to by:

Code:

ls -l /dev/cdrom

Also, could you post the output of lsmod?

Thanks,
MMYoung

keefaz · 03-07-2005, 02:24 PM

Only root can set the type of fs and choose devices when mounting, eg

mount -t iso9660 /dev/cdrom /mnt/cdrom <-- only root can do this
mount /dev/cdrom /mnt/cdrom <-- only root can do this

mount /mnt/cdrom <-- ok for users from your /etc/fstab settings

Working fstab line should be:

Code:

/dev/cdrom       /mnt/cdrom       iso9660     noauto,ro,users  0   0

Mr_C · 03-07-2005, 04:19 PM

Ya I know that only root can interact with /dev.

Code:

┌─(clay@SOL:pts/1)─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────(~)─┐
└─(%)─ cat /etc/fstab | grep cdrom
/dev/cdrom       /mnt/cdrom       iso9660     noauto,ro,umask=000,users  0   0
┌─(clay@SOL:pts/1)─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────(~)─┐
└─(%)─ ls -l /dev/cdrom
lrwxrwxrwx  1 root root 3 2005-03-07 13:40 /dev/cdrom -> hdc

actually by removing the umask option, eveything has returned to normal (hmm I didn't have to recomiple my kernel again....) -- keefaz

K3b refused to see the cdrom, so I deleted my user settings and lauched it again and it found my burner.

Also discovered that usb drives are now called uba.

Thanks for the help.
You're right simple is good. --mmyoung

MMYoung · 03-07-2005, 05:50 PM

Quote:

Originally posted by Mr_C
Also discovered that usb drives are now called uba.

That means you are using the CONFIG_BLOCK_DEV_UB and your usb-storage is "crippled". You should disable that and recompile your kernel. I mistakenly said it was in the USB section, when actually it's in the Block Devices section. See above post.

Quote:

Originally posted by Mr_C
Thanks for the help.
You're right simple is good. --mmyoung

You're welcome. The simpler the better I always say.

Glad I could help,
MMYoung

Mr_C · 03-07-2005, 08:51 PM

Uba. Is this bad? I mean I plugged in a usb external harddrive and it was recognized. What do you mean it cripples usb-storage?

MMYoung · 03-07-2005, 09:18 PM

Quote:

Originally posted by Mr_C
Uba. Is this bad? I mean I plugged in a usb external harddrive and it was recognized. What do you mean it cripples usb-storage?

The "quote" that I have in post number 2 of this thread is a quote from the CONFIG_BLOCK_DEV_UB help file. Matter of fact it states, "If unsure say NO" in the help file.

UB is a "low performance" USB block driver and not really suitable for the "high performance" USB external HD's. I've not read much about UB, but all that I've read about was bad. Well, bad is such a "bad" word, I shoud say all that I've read about UB is "not good". You might want to check out the help file for UB and see what you think. I did find this, usb-storage and the ub device and 2.6.9 may want to give it a read.

Quote:

from the article
So, it is better for certain things and worse for others. In 2.6.10
there are much larger warnings to Distros not to enable it, as it's not
ready yet. The problem is that if you compile your kernel with
CONFIG_BLK_DEV_UB then the devices it believes it can handle (a subset
of the usb-storage devices), then usb-storage will *not* bind to those
devices even if the ub driver is not loaded. Note though that you can
have one device bound to ub and another to usb-storage on the same
machine without problems as long as ub doesn't believe it should have
that 2nd device.

Thus the warning about "crippling" usb-storage.

HTH,
MMYoung

Mr_C · 03-07-2005, 09:33 PM

ok thanks again for the heads up.

Mr_C · 03-22-2005, 04:20 PM

actually its compiled as a module..........
and thus not active, but avaliable, so.....????

saxophobe · 04-06-2005, 07:45 AM

Hi all!

I am having the same problem as described in this thread, but I don't have a umask set in my /etc/fstab:

Code:

/dev/hda2        swap             swap        defaults         0   0
/dev/hda1        /                reiserfs    defaults         1   1
/dev/cdrom       /mnt/cdrom       iso9660     noauto,owner,ro  0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults

Also, here are my mounts:

Code:

rootfs / rootfs rw 0 0
/dev/root / reiserfs rw 0 0
proc /proc proc rw,nodiratime 0 0
sysfs /sys sysfs rw 0 0
none /dev ramfs rw 0 0
devpts /dev/pts devpts rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0

When I try to mount the cdrom drive, I get the following error:

Quote:

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

And when I run dmesg | tail, I get the following:

Code:

hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x50 { LastFailedSense=0x05 }
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 64
isofs_fill_super: bread failed, dev=hdc, iso_blknum=16, block=16
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x50 { LastFailedSense=0x05 }
ide: failed opcode was: unknown
end_request: I/O error, dev hdc, sector 64
isofs_fill_super: bread failed, dev=hdc, iso_blknum=16, block=16

The maker of my distro believes that this may be a kernel bug in isofs. Does anyone here have any ideas about this issue?

Thanks in advance for your time!

sax

Mr_C · 04-06-2005, 10:08 PM

fixed

saxophobe · 04-07-2005, 03:26 PM

Would you mind sharing how this got fixed, Mr_C?!?!?

mdarby · 04-07-2005, 03:39 PM

And what did you do to your .bashrc to make you prompt look like

Code:

┌─(clay@SOL:pts/1)─────────────────────────────────────────────────────────────────(~)─┐
└─(1:%)─ ls -l /dev/cdrom
lrwxrwxrwx  1 root root 3 2005-03-07 09:39 /dev/cdrom -> hdc

???