[SunHELP] FSCK problem, U30, Solaris 9
Vermette, Matt Spawar (723)
matt.vermette at navy.mil
Tue Oct 5 08:17:24 CDT 2004
When you boot the system off CD, make use of the following to ensure a
successful removal of metadevice root filesystem
A) Execute the following command: boot cdrom -sw
B) fsck the boot drive: fsck /dev/dsk/c0t0d0s0
B) Mount the root filesystem: mount /dev/dsk/c0t0d0s0 /a
C) Move current config files to backup: mv /a/etc/vfstab
/a/etc/vfstab.bak; mv /a/etc/system /a/etc/system.bak
D) Move good config files in place: mv /var/tmp/vfstab /a/etc/vfstab;
mv /var/tmp/system /a/etc/system
NOTE: Verify /var/tmp directory. Booting off of cdrom generates
these files automatically and I am not sure if it's /var/tmp off the top
of my head.
This should get you back to your original logical devices for
troubleshooting and verification. Also, make sure your Electrically
Erasable Programmable Read-Only Memory (EEPROM) is configured properly
for non-interactive boot. Otherwise, execute a stop-a after memory
initialization and manually boot your root device in single-user mode.
Matthew A. Vermette
Honeywell Technology Solutions Inc.
Matt.Vermette at navy.mil
Matthew.Vermette at honeywell-tsi.com
8438138896 at mobile.mycingular.com
From: sunhelp-bounces at sunhelp.org [mailto:sunhelp-bounces at sunhelp.org]
On Behalf Of Phil Stracchino
Sent: Friday, October 01, 2004 8:55 AM
To: SunHELP; Rescue
Subject: [SunHELP] FSCK problem, U30, Solaris 9
I just applied the latest Solaris 9 alert and recommended patch clusters
to an U30 running Solaris 9 4/03. This appears to have caused two
problems: First, one of the patches added mpt to /etc/driver_aliases
and /etc/driver_classes, but not to /etc/name_to_major, giving the
'WARNING: add spec: No major number for mpt' message at boot.
This, I've fixed.
The other problem is more serious. The machine is unable to fsck
/dev/md/dsk/d10, which is a two-way mirror mounted as / on this box. All
the other metadevices can be fsck'd, and /dev/md/dsk/d10 can be booted
from, mounted read-only, etc, etc. However, attempting to fsck it
produces the following:
# fsck -F ufs /dev/md/rdsk/d10
fsck: ioctl _FIOGETSUPERBLOCK error: Inappropriate ioctl for device
I can fsck both of the submirrors fine, and they come up clean. I've
broken the mirror and alternately re-newfs'd and duplicated both
mirrors, so I know the filesystems themselves should be good. They fsck
cleanly. Currently, what's happening is that mount insists the primary
and alternate boot filesystems (the former submirrors) are not ufs. I
cannot get either one mounted read-write except by booting from a CD.
The root filesystem, as /dev/rdsk/c0t0d0s0, can be fsck'd, and mounts
fine read-only, but any attempt to remount it read-write yields:
# mount -F ufs -o rw,remount /dev/dsk/c0t0d0s0
mount: /dev/dsk/c0t0d0s0 is not this fstype
I don't know if I've fully successfully gotten the system to stop trying
to boot from the metadevice (/dev/md/dsk/d10), because I can't get a
booted root filesystem mounted read-write so that I can run metaroot to
properly set the boot.
Any advice on how I can get this problem fixed and get this machine back
in operation? I've been working on this since about 10pm last night and
I'm making very little progress.
========== Fight Back! It may not be just YOUR life at risk.
alaric at caerllewys.net : phil-stracchino at earthlink.net :
phil at novylen.net
phil stracchino : unix ronin : renaissance man : mystic zen biker
2000 CBR929RR, 1991 VFR750F3 (foully murdered), 1986 VF500F (sold)
Linux Now! ...Friends don't let friends use Microsoft.
SunHELP maillist - SunHELP at sunhelp.org
More information about the SunHELP