Skip to contentSkip to conversation

error message interpretation help?

DISCUSSION James Miller 2 participants 3 messages Feb 2, 2004 – Feb 3, 2004

lore
Share & tools
lore
#0 lore raw

I recently made some kernel changes and was fiddling with lilo.conf on a Debian Sid system. Of course I had to run "lilo" to get the changes to take effect. When I did, I got an error message that I'm not quite sure how to interpret. I'd like to ask some input here on what it means and on what I need to do to correct the problem. Here's what I got when I ran the command "lilo" from an xterm as root:

--------------------------------------------------------
[03:43:15]root@debian-sid root$ lilo
Warning: '/proc/partitions' does not match '/dev' directory structure.

    Name change: '/dev/ide/host0/bus1/target0/lun0/disc' -> '/dev/hdc'

Warning: /dev/hda is not on the first disk
Added Linux-2.4.24 *
Added Linux-2.2.20
---------------------------------------------------------

I should mention that I had some problems mounting the CD drive on this machine initially. To make the CD drive mountable/accessible, I changed an fstab entry that pointed to the CD device. Here's my current fstab:

-------------------------------------------------------------------
[03:43:28]root@debian-sid root$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump>
<pass>

/dev/hda1       /               ext2    errors=remount-ro       0       1
/dev/hdd2       none            swap    sw                      0       0
proc            /proc           proc    defaults                0       0
/dev/fd0        /floppy         auto    user,noauto             0       0
/dev/hdb        /cdrom          iso9660 ro,user,noauto          0       0
/dev/hdc1       /home   ext2    defaults                        0       2
/dev/hdd1       /usr    ext2    defaults

-----------------------------------------------------------------

I believe I changed the entry that now reads "/dev/hdb /cdrom . . ." from something that was more like "/dev/cdrom /cdrom . . ." Could that be what's causing the inconsistency between /proc/partitions and the /dev directory structure? In general, I do not really understand the /dev/cdrom as opposed to /dev/hdx entry in fstab. I've seen it before, but I really can't conjecture what's going on with it, and why a CD drive wouldn't just be labelled the same way as an IDE disk. In any case, without changing the entry from /dev/cdrom to /dev/hdb, I was unable to access the drive (unable to mount it when it had a CD in it). Can someone please help clarify for me 1) whether the /proc/partitions and /dev directory structure inconsistency could be related to renaming the fstab entry for the CD drive and 2) why CD drives get device names on some (newer?) systems like /dev/cdrom instead of /dev/hdx?

Thanks, James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#1 lore raw
Quoted 7 lines · James Miller

I recently made some kernel changes and was fiddling with lilo.conf on a Debian Sid system. Of course I had to run "lilo" to get the changes to take effect. When I did, I got an error message that I'm not quite sure how to interpret. I'd like to ask some input here on what it means and on what I need to do to correct the problem. Here's what I got when I ran the command "lilo" from an xterm as root:

Quoted 9 lines

--------------------------------------------------------
[03:43:15]root@debian-sid root$ lilo
Warning: '/proc/partitions' does not match '/dev' directory structure.

    Name change: '/dev/ide/host0/bus1/target0/lun0/disc' -> '/dev/hdc'

Warning: /dev/hda is not on the first disk
Added Linux-2.4.24 *
Added Linux-2.2.20
---------------------------------------------------------

Looks like a warning, not an error. Lilo seems to have completed
successfully. <obligatory disclaimer> I don't use devfs, YMMV :) </>

Quoted 7 lines

Can someone
please help clarify for me 1) whether the /proc/partitions and /dev directory structure inconsistency could be related to renaming the fstab entry for the CD drive and 2) why CD drives get device names on some (newer?) systems like /dev/cdrom instead of /dev/hdx?

Thanks, James

I imagine that fstab will never be taken into account when
/proc/partitions and /dev are compared. I would not be surprised if it's purely an artefact of using devfs, or perhaps you are supposed to _not_ use /dev/hdc with devfs.

As to naming the cdrom, /dev/cdrom will usually be a symlink to another
device (e.g. hdc or perhaps scd0 if your distro uses scsi emulation for read and write). If you are using the ide driver, /dev/hdc or whichever won't cause you problems. Distros usually get these things right, but maybe you compiled your own kernel and used different options. Since /dev/cdrom no longer works for you, where is it pointing (or, exceptionally, which are the device major / minor numbers, and is it char or block - I'm only asking so you can understand why it no longer works :) ?

Ken

Signature · 8 lines
Brighton tops UK Jedi league
http://www.theregister.co.uk/content/28/35186.html

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
#2 lore raw
Quoted 9 lines · Ken Moffat

As to naming the cdrom, /dev/cdrom will usually be a symlink to another
device (e.g. hdc or perhaps scd0 if your distro uses scsi emulation for read and write). If you are using the ide driver, /dev/hdc or whichever won't cause you problems. Distros usually get these things right, but maybe you compiled your own kernel and used different options. Since /dev/cdrom no longer works for you, where is it pointing (or, exceptionally, which are the device major / minor numbers, and is it char or block - I'm only asking so you can understand why it no longer works :) ?

Thanks for your response, Ken, which only marginally makes sense to me (not a criticism of you, but a statement of my poor grasp of things). I've made a mental note of "devfs" and will try to be aware of how it may apply to this matter. This is *not* a hand-compiled kernel (not by my hand, anyway), but the latest 2.4.x kernel from Debian (apt-get install kernel-image-2.4-686). /dev/cdrom is a symlink pointing at /dev/cdrom0. /dev/cdrom0 is, in turn, a symlink pointing at /dev/hdb (which is the device I manually entered into fstab to get it mountable). This is totally baffling to me: a symlink pointing at a symlink? The logic escapes me. What am I missing? Perhaps more importantly, what is the *right* way to work with the cdrom on this machine? I should make the disclaimer that the original fstab entry may have been /dev/cdrom0, rather than /dev/cdrom - I just don't remember for sure. I still can't see why a symlink should be needed for a CD drive, much less a symlink to a symlink:
is this for the benefit of the user, the OS creator/compiler, the computer itself?

Thanks, James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs