Cannot boot nor mount root partition after patching

bax · 11-08-2011, 01:28 PM

After applying the latest patchset on a Sun v240 (SPARC, 64b Solaris 10), I got the below error:

Code:

Boot device: disk  File and args: 
|
Evaluating: 
Out of memory
Warning: Fcode sequence resulted in a net stack depth change of 1 
Evaluating: 

Evaluating: 
The file just loaded does not appear to be executable.
{0} ok

Found this article and tried following the directions. Got it booted to single user from the install DVD and am now attempting to mount the root ZFS filesystem.

Cannot mount as seen below and NO ZFS filesystems show up when I run 'zfs list'

Code:

# zfs list
no datasets available
# zfs mount -a
# zfs list
no datasets available
# mount /dev/dsk/c1t0d0s0 /mnt
NOTICE: mount: not a UFS magic number (0x0)
mount: /dev/dsk/c1t0d0s0 is not this fstype

jlliagre · 11-09-2011, 04:57 AM

You need to import the root pool to have the zfs file systems mounted.

Have a look at this link for a similar procedure:
http://www.solarisinternals.com/wiki...imilar_Problem

bax · 11-09-2011, 09:03 AM

Quote:

Originally Posted by jlliagre

You need to import the root pool to have the zfs file systems mounted.

Have a look at this link for a similar procedure:
http://www.solarisinternals.com/wiki...imilar_Problem

Trying so, think I have a bad disk?

Code:

WARNING: /pci@1c,600000/scsi@2/sd@3,0 (sd6):
        Error for Command: read                    Error Level: Retryable
        Requested Block: 288                       Error Block: 288
        Vendor: SEAGATE                            Serial Number: 052431RGDD  
        Sense Key: Unit Attention
        ASC: 0x29 (scsi bus reset occurred), ASCQ: 0x2, FRU: 0x2
cannot mount '/zpool': failed to create mountpoint
cannot mount '/zpool/oracleclone3': failed to create mountpoint
cannot mount '/zpool/snapclone3': failed to create mountpoint

bax · 11-09-2011, 09:44 AM

So, I got the below mounted, I think. I cannot get to the rpool/ROOT partition.

Code:

# zfs list
NAME                       USED  AVAIL  REFER  MOUNTPOINT
rpool                     18.9G  48.0G    94K  /rpool
rpool/ROOT                7.94G  48.0G    18K  legacy
rpool/ROOT/s10s_u7wos_08  7.94G  48.0G  7.94G  /
rpool/dump                1.00G  48.0G  1.00G  -
rpool/export                40K  48.0G    22K  /export
rpool/export/home           18K  48.0G    18K  /export/home
rpool/swap                  10G  58.0G  29.3M  -
# ls /
a            dev          lib          proc         tmp
bin          devices      mnt          reconfigure  usr
boot         etc          opt          sbin         var
cdrom        kernel       platform     system

jlliagre · 11-09-2011, 05:52 PM

I would temporarily change the rpool mount point to make it accessible. Something like:

Code:

zfs set mountpoint=/s10u7 rpool/ROOT/s10s_u7wos_08
zfs mount rpool/ROOT/s10s_u7wos_08
...
fix your file system
...
zfs umount rpool/ROOT/s10s_u7wos_08
zfs set mountpoint=/ rpool/ROOT/s10s_u7wos_08

bax · 11-15-2011, 03:49 PM

So, I had to reinstall the OS and flash server PROM.

Now, I have a new root disk and the still existing RAIDZ array of the three other disks. How do I go about bringing the zpool back up?

jlliagre · 11-15-2011, 04:28 PM

Just import it, likely with the -f option.

Code:

zpool import

will show you its name (eg: myraidz), then run

Code:

zpool import -f myraidz

bax · 11-16-2011, 11:47 AM

Not showing up when running zpool import. This is frustrating.

bax · 11-17-2011, 12:12 PM

So booting in safe mode off of the cdrom shows the zpool just fine. Cannot get it to show the disks containing the RAIDZ zpool set in cfgadm nor format. However, they show up just fine in safe mode.

Right now, I'm going to try tarring the two zones up onto an NFS mount via safe mode and then transferring them and installing them on another box.

I would rather be able to import the zpool on the existing box but the new OS install is not seeing the disks nor the zpool. Would appreciate insight on that.

jlliagre · 11-17-2011, 02:46 PM

If the OS doesn't see the disks, there is no chance for the pool to be visible. How are they attached ?