kanotix.com

General Support - mtab and fstab?
drb - 09.09.2006, 11:58 Uhr
Titel: mtab and fstab?
During boot I get an error message concerning mtab and /sys. The message also appears at shutdown. My fstab and mtab entries are below. Is there something wrong with these files to cause the error message. Everything appears to 'work'.

drb

fstab :

Code:
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
usbfs  /proc/bus/usb  usbfs  devmode=0666  0  0
/dev/hdb5       /               reiserfs defaults        0       1
/dev/hdb6       /home           ext2    defaults        0       2
/dev/hda1       /media/hda1     vfat    ro,umask=222,shortname=mixed,quiet 0       0
/dev/hda5       /media/hda5     vfat    ro,umask=222,shortname=mixed,quiet 0       0
/dev/hda6       /media/hda6     ntfs    ro,umask=000    0       0
/dev/hda7       /media/hda7     ntfs    ro,umask=000    0       0
/dev/hdb1       /media/hdb1     ntfs    ro,umask=000    0       0
/dev/hdb2       /media/hdb2     ntfs    ro,umask=000    0       0
/dev/hdb3       /media/hdb3     vfat    umask=000,shortname=mixed,quiet 0       0
/dev/hdb7       /media/hdb7     vfat    umask=000,shortname=mixed,quiet 0       0
/dev/hdb8       none            swap    sw              0       0
/tmp/app/1/image /tmp/app/1      cramfs,iso9660 user,noauto,ro,loop,exec 0       0
/tmp/app/2/image /tmp/app/2      cramfs,iso9660 user,noauto,ro,loop,exec 0       0
/tmp/app/3/image /tmp/app/3      cramfs,iso9660 user,noauto,ro,loop,exec 0       0
/tmp/app/4/image /tmp/app/4      cramfs,iso9660 user,noauto,ro,loop,exec 0       0
/tmp/app/5/image /tmp/app/5      cramfs,iso9660 user,noauto,ro,loop,exec 0       0
/tmp/app/6/image /tmp/app/6      cramfs,iso9660 user,noauto,ro,loop,exec 0       0
/tmp/app/7/image /tmp/app/7      cramfs,iso9660 user,noauto,ro,loop,exec 0       0
#/dev/hdc      /media/hdc   udf,iso9660 user,noauto     0       0
#/dev/hdd     /media/hdd  udf,iso9660 user,noauto     0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0
#/dev/sda1   /media/sda1   vfat   umask=000,shortname=mixed,quiet 0       0
none /sys sysfs defaults 0 0


mtab

Code:
/dev/hdb5 / reiserfs rw 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
/sys /sys sysfs rw,noexec,nosuid,nodev 0 0
udev /dev tmpfs rw,mode=0755 0 0
devshm /dev/shm tmpfs rw 0 0
devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0
usbfs /proc/bus/usb usbfs rw,devmode=0666 0 0
/dev/hdb6 /home ext2 rw 0 0
/dev/hda1 /media/hda1 vfat ro,umask=222,shortname=mixed,quiet 0 0
/dev/hda5 /media/hda5 vfat ro,umask=222,shortname=mixed,quiet 0 0
/dev/hda6 /media/hda6 ntfs ro,umask=000 0 0
/dev/hda7 /media/hda7 ntfs ro,umask=000 0 0
/dev/hdb1 /media/hdb1 ntfs ro,umask=000 0 0
/dev/hdb2 /media/hdb2 ntfs ro,umask=000 0 0
/dev/hdb3 /media/hdb3 vfat rw,umask=000,shortname=mixed,quiet 0 0
/dev/hdb7 /media/hdb7 vfat rw,umask=000,shortname=mixed,quiet 0 0
ockham23 - 09.09.2006, 12:10 Uhr
Titel: RE: mtab and fstab?
The fstab entry
Zitat:
none /sys sysfs defaults 0 0
doesn't look right. Do you know where it came from? Try to comment it out by putting "#" in front of it.
drb - 09.09.2006, 14:29 Uhr
Titel:
Thanks. It has been there since the original 2005-04 install. I'm sure I've seen problems booting without it. I'll look back at some old threads first.

drb
ockham23 - 09.09.2006, 14:59 Uhr
Titel:
"none" isn't a mountable device and it has nothing do to with /sys. "none" is a mounting option for swap as in
Code:
/dev/hda6       none            swap    sw              0       0
swap doesn't need a mount point = "none". I think your fstab entries somehow got mixed up.
drb - 09.09.2006, 15:58 Uhr
Titel:
I've found references to the entry with regard to the 2.6 kernel and udev. Things may have moved on.
feffer777 - 10.09.2006, 20:19 Uhr
Titel:
For what it's worth, I get the same failure message at boot time relating to mtab and /sys though I haven't changed either fstab or mtab in a long time. The message seemed to show up after the recent d-u when udev was problematic. I haven't noticed any problems from it though.

Regards,
Ron
datebro - 10.09.2006, 21:06 Uhr
Titel:
the sys-entry in the fstab was necessary, but is obsolet with an actual hal/dbus. sys is now mountet before the fstab is read, and it is safe to comment the entry out with an # .
On the otherside your error-message tells nothing than a mountet filesystem (sys) could not be mounted a second time, its nothing really wrong.

Greetings
Datebro

ps: the mtab is dynamic, do not never ever edit it!
feffer777 - 12.09.2006, 01:17 Uhr
Titel:
Zitat:

ps: the mtab is dynamic, do not never ever edit it!

Good catch! Actually, I never do edit mtab and have no idea why I wrote that!

Yes, tried it and can confirm the /sys fstab entry can be commented out or removed and the "failure" boot message will disappear.

Thanks,
Ron
slh - 12.09.2006, 09:00 Uhr
Titel:
datebro hat folgendes geschrieben::
the sys-entry in the fstab was necessary, but is obsolet with an actual hal/dbus. sys is now mountet before the fstab is read, and it is safe to comment the entry out with an # .
This is mostly correct, just that very recent sysvnit versions mount proc, sys and usbfs on their own, given that it was "always" crucial to mount those pseudo filesystems explicitly and that failing to mount them will break half of the system. I'm very reluctant to do the trivial changes to our fstab generating scripts - keeping it as-is just emits a bogus (in my opinion very useless and overhyped) warning, removing the entries "is supposed to be safe", whatever that means... Right now I prefer staying conservative and ignoring the useless warning.

datebro hat folgendes geschrieben::
ps: the mtab is dynamic, do not never ever edit it!
This can't be repeated often enough, don't touch /etc/mtab manually.
Alle Zeiten sind GMT + 1 Stunde
PNphpBB2 © 2003-2007