Problems with fsck on root disk (non lvm) in muli-user mode?

[Mike Nemeth]

Another Sys-adm here crashed a non lvm root disk by
pulling the power. It fsck on reboot, found and fixed errors.
To be sure it was ok, he fscked it after it came up into
multiuser mode. Eorrors occurred, were fixed and a reboot -n was done. When it rebooted it fscked found errors, correct them.
He repeated the above a second time!
After that he had no confendance in the system , so rebuilt it.

Ok I know he should have been in single user mode,
but was the fact he was in multi-user mode causing
the errors?

[Darrel Louis]

Hi,

When running a fsck on the disk it shouldn't matter if it is in Single or Multi usermode.
As long as the disk is not mounted.

[Cheryl Griffin]

A utility as important as fsck should be run in singler user mode, not multi-user mode.

There are several reported accounts that fsck in multiuser mode caused further corruption.

You want the system as quiet as possible. With single user mode, that is guaranteed.

[Devbinder Singh Marway]

Have a look at the following link , regarding fsck and probable causes . The other thing is , it is recommended to unmount filesystem before running fsck hence in single user mode, but if a no system filesystem did you umount it when in multi-user mode and run the fsck , if not then it could be certain processes were running on the filesystem , and when you ran fsck in multi user modem reported errors. Also you could have ran a fsck sanity check ( -m ) option and it would have reported if filesystem was suitable for mounting, whether ti needs further checking or whether it was badly damaged).

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90672/B2355-90672_top.html&con=/hpux/onlinedocs/B2355-90672/00/00/45-con.html&toc=/hpux/onlinedocs/B2355-90672/00/00/45-toc.html&searchterms=fsck&queryid=20001207-044502

[Hamdy Al-Sebaey]

Hi Mike,
I agree with cheryl,it'is better to run fsck in a singel user mode just to avoid any problem.
Anyhow here you
've the steps maybe it'll help you to repair a FS, just try the follow steps:
unmount the file system
#Fsck -F vxfs /dev/vg##/lvol#
if this option does not work, just try this;
#FullFsck: -F vxfs -o full /dev/vg##/lvol#
#vgchange -a y
#mount -a
to check that every FS is mount, type in
#pg /etc/fstab

Goodluck