- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- fsck problems
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-14-2005 08:39 AM
01-14-2005 08:39 AM
fsck problems
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".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-14-2005 11:41 AM
01-14-2005 11:41 AM
Re: fsck problems
did you run fsck manually as suggested?
Is there any reason you do not use advfs?
greetings,
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2005 11:16 PM
01-17-2005 11:16 PM
Re: fsck problems
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2005 01:57 AM
01-19-2005 01:57 AM
Re: fsck problems
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2005 02:08 AM
01-19-2005 02:08 AM
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_
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2005 02:23 AM
01-19-2005 02:23 AM
Re: fsck problems
Mohamed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2005 08:32 PM
01-23-2005 08:32 PM
Re: fsck problems
why not checking hardware first and then try to fsck the named filesystems?
There is a troubleshooting section within the admin guide.