1827421 Members
3755 Online
109965 Solutions
New Discussion

fsck problems

 
George R. White
Advisor

fsck problems

I need help getting node to boot up, node oges to single user mode due to ufs_fsck failure. Node running Tru64 Unix 5.1B. Any ideas/solutions to this problem?

ATM IP: configured
dsfmgr: NOTE: updating kernel basenames for system at /
scp kevm random urandom dmapi cdrom0 dsk0 dsk1 dsk2 dsk3 dsk4 dsk5 dsk6 dsk7 tape0 dsk10 dsk13
starting LSM in boot mode
dsfmgr: NOTE: updating kernel basenames for system at /
/sbin/ufs_fsck -p /dev/vol/rootdg/rootvol
/dev/rvol/rootdg/rootvol: 645824 DUP I=297955
/dev/rvol/rootdg/rootvol: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Automatic reboot failed. Run fsck manually.
Repair filesystem(s), then reboot (/sbin/reboot).

INIT: SINGLE-USER MODE
Cannot change mode of "/dev/console".
6 REPLIES 6
Michael Schulte zur Sur
Honored Contributor

Re: fsck problems

Hi,

did you run fsck manually as suggested?
Is there any reason you do not use advfs?

greetings,

Michael
Ralf Puchner
Honored Contributor

Re: fsck problems

why not using the commands given in admin guide?

Help() { FirstReadManual(urgently); Go_to_it;; }
Mohamed  K Ahmed
Trusted Contributor

Re: fsck problems

I have the same problem with an AS4100 running Tru64 UNIX V 4.0G with UFS file systems no LSM
If the system crashed for any reason and I try to boot after crash, I get the same message. I end up running fsck manually. So after getting the
INIT: SINGLE-USER MODE
#
Just issue the command fsck or fsck/p
Leave it to run and then reboot

My disks are old and connected through a SWXCR cards, I think I am having these problems because of the configuration.

HTH

Mohamed
Johan Brusche
Honored Contributor

Re: fsck problems


This is inherent to any UFS implementation for the root filesystem, requiring a single-user fsck after an abrupt multiuser stop. (ie non-clean umount of / )

And it's also one of the reasons why log based filesystems like AdvFS are preferred.

__ Johan.

_JB_
Mohamed  K Ahmed
Trusted Contributor

Re: fsck problems

It is not only for the root directory, actually the fsck failes on 4 drives that are connected to the system through a SCSI Card, but not the system disk which is internal.

Mohamed
Ralf Puchner
Honored Contributor

Re: fsck problems

Mohamed,

why not checking hardware first and then try to fsck the named filesystems?

There is a troubleshooting section within the admin guide.
Help() { FirstReadManual(urgently); Go_to_it;; }