ref kernel errors on boot up mtab sysfs is already mounted sys failed

[todders]

Dear all in Mepis 7 beta 1 i have managed to get rid of the mount: according to mtab,sysfs is already mounted on /sys failed error messages in the kernel by duplicating the following entries in the mtab file and applying them to the fstab file:-

proc /proc proc rw,noexec,nosuid,nodev 0 0
sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0
procbususb /proc/bus/usb usbfs rw 0 0
devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0

i placed all the above mtab entries into my fstab which now looks like this:-

# Pluggable devices are handled by uDev, they are not in fstab
/dev/sda1 / ext3 defaults,noatime 1 1
/dev/sda2 swap swap sw,pri=1 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
procbususb /proc/bus/usb usbfs rw 0 0
devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec 0 0
/dev/sda3 /home ext3 defaults,noatime 1 2
/dev/sdb3 /mnt/sdb3 ext3 auto,users,exec 0 0
# Dynamic entries below
/dev/sdb1 /mnt/sdb1 ext3 noauto,users,exec 0 0
/dev/sdb2 swap swap sw,pri=1 0 0
/dev/cdrom /media/cdrom udf,iso9660 noauto,users,exec,ro 0 0
/dev/scd0 /media/cdrom udf,iso9660 noauto,users,exec,ro 0 0

my original fstab referenced these entries but with a prefix of none,l*i deleted these*like i say it solved all my kernel error messages,if anyone is willing to try it let me know how you got on.

thanks todders

Originally Posted by todders

proc /proc proc rw,noexec,nosuid,nodev 0 0
sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0
procbususb /proc/bus/usb usbfs rw 0 0
devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0

Looks good; thanks

I tried that here, still got the errors :(

[todders]

hello
iam no way an expert on these things was just fiddling did work for me,just make sure you copy your own mtab file settings to your fstab and not just mine and delete the ones that are referenced none in yout fstab file that match the ones you are replacing..

regards

todders

Yep that helps - thanks.
But Assembling MD arrays still failed on boot messages. Is that harmful?

[todders]

hello
no it is not harmful,i have used this fix of mine to remove the mdadm messages though...

to remove the error message ref md arrays i edited the /etc/default/mdadm file and edited as shown below:-

# INITRDSTART:
# list of arrays (or 'all') to start automatically when the initial ramdisk
# loads. This list *must* include the array holding your root filesystem. Use
# 'none' to prevent any array from being started from the initial ramdisk.
INITRDSTART='none' (I CHANGED THIS TO NONE)

# AUTOSTART:
# should mdadm start arrays listed in /etc/mdadm/mdadm.conf automatically
# during boot?
AUTOSTART=false (I CHANGED THIS TO FALSE)

# AUTOCHECK:
# should mdadm run periodic redundancy checks over your arrays? See
# /etc/cron.d/mdadm.
AUTOCHECK=false (I CHANGED THIS TO FALSE)

everthing else in the files i left as it was,obviously i dont have any disk arrays setup,i also noticed a marked improvement in boot up speed of the system as well.

regards

todders

Works
Thks again
For those intending to install to ext HD had to put in rootdelay=5 in the grub menu.lst line.
Allows 5 sec to probe IDE/SATA to avoid the ide busy message.

Worked for me. Thanks. All I did was edit fstab, replacing each occurence of none with proc, sysfs, procbususb, or devpts.

todders' solution:

proc /proc proc rw,noexec,nosuid,nodev 0 0
procbususb /proc/bus/usb usbfs rw 0 0
devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0
sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0

ralvy's solution:

proc /proc proc defaults 0 0
procbususb /proc/bus/usb usbfs devmode=0666 0 0
devpts /dev/pts devpts mode=0622 0 0
sys /sys sysfs defaults 0 0

Is someone here, who is able to explain the difference?

Originally Posted by bluknight

Yep that helps - thanks.
But Assembling MD arrays still failed on boot messages. Is that harmful?

Just make

dpkg-reconfigure mdadm

and choose "none" each time, if you don't have raid.