This content has been marked as final. Show 16 replies
Sadly, this did not work :-(. Any other suggestions? Here is what my current /etc/vfstab looks like
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/dsk/c6t20000011C63FE713d0s1 - - swap - no -
/dev/dsk/c6t20000011C63FE713d0s0 /dev/rdsk/c6t20000011C63FE713d0s0 / ufs 1 no -
/dev/dsk/c6t20000011C63FE713d0s3 /dev/rdsk/c6t20000011C63FE713d0s3 /usr ufs 1 no -
/dev/dsk/c6t20000011C63FE713d0s4 /dev/rdsk/c6t20000011C63FE713d0s4 /var ufs 1 no -
#/dev/dsk/c6t20000011C63FE713d0s6 /dev/rdsk/c6t20000011C63FE713d0s6 /export ufs 2 yes -
#/dev/dsk/c6t20000011C63FE713d0s5 /dev/rdsk/c6t20000011C63FE713d0s5 /opt ufs 2 yes -
/devices - /devices devfs - no -
ctfs - /system/contract ctfs - no -
objfs - /system/object objfs - no -
swap - /tmp tmpfs - yes -
#/dev/dsk/c6t600A0B800029E1D6000003F446A0C1B8d0s0 /dev/rdsk/c6t600A0B800029E1D6000003F446A0C1B8d0s0 /u01 ufs 2 yes -
#/dev/dsk/c6t600A0B800029E1D6000003F446A0C1B8d0s1 /dev/rdsk/c6t600A0B800029E1D6000003F446A0C1B8d0s1 /u02 ufs 2 yes -
#/dev/dsk/c6t600A0B800029E1D6000003F446A0C1B8d0s2 /dev/rdsk/c6t600A0B800029E1D6000003F446A0C1B8d0s2 /u03 ufs 2 yes -
#/dev/dsk/c6t600A0B800074F6C1000003504D8C6524d0s2 /dev/rdsk/c6t600A0B800074F6C1000003504D8C6524d0s2 /u01 ufs 2 yes -
#/dev/dsk/c6t600A0B800074F6C1000003524D8C656Bd0s2 /dev/rdsk/c6t600A0B800074F6C1000003524D8C656Bd0s2 /u02 ufs 2 yes -
#/dev/dsk/c6t600A0B800075F200000003864D8C6521d0s2 /dev/rdsk/c6t600A0B800075F200000003864D8C6521d0s2 /u03 ufs 2 yes -
sharefs - /etc/dfs/sharetab sharefs - no -
I believe we have a Sun StorEdge T3 and that's what the disks are running on.
As far as what kind of disks we are booting off, I'm not sure what your question is by that? What do you mean?
Thanks for all your help. I owe you big time.
Edit: I don't know if this will help but this is what happens when it boots
Rebooting with command: boot
Boot device: /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w21000011c63fe713,0:a File and args:
SunOS Release 5.10 Version Generic_147440-12 64-bit
Copyright (c) 1983, 2012, Oracle and/or its affiliates. All rights reserved.
Not sure if that's helpful.
Edited by: melman101 on May 9, 2012 3:38 PM
Nope I don't see it.
I made a /a directory and tried to mount. Couldn't find device /dev/dsk/c6t20000011C63FE713d0s0
In /dev/dsk I only see
# cd dsk
c0t0d0s0 c1t203700A0B875F200d1s6 c2t203600A0B875F200d1s4
c0t0d0s1 c1t203700A0B875F200d1s7 c2t203600A0B875F200d1s5
c0t0d0s2 c1t203700A0B875F200d2s0 c2t203600A0B875F200d1s6
c0t0d0s3 c1t203700A0B875F200d2s1 c2t203600A0B875F200d1s7
c0t0d0s4 c1t203700A0B875F200d2s2 c2t203600A0B875F200d2s0
c0t0d0s5 c1t203700A0B875F200d2s3 c2t203600A0B875F200d2s1
c0t0d0s6 c1t203700A0B875F200d2s4 c2t203600A0B875F200d2s2
c0t0d0s7 c1t203700A0B875F200d2s5 c2t203600A0B875F200d2s3
c1t203700A0B875F200d0s0 c1t203700A0B875F200d2s6 c2t203600A0B875F200d2s4
c1t203700A0B875F200d0s1 c1t203700A0B875F200d2s7 c2t203600A0B875F200d2s5
c1t203700A0B875F200d0s2 c2t203600A0B875F200d0s0 c2t203600A0B875F200d2s6
c1t203700A0B875F200d0s3 c2t203600A0B875F200d0s1 c2t203600A0B875F200d2s7
c1t203700A0B875F200d0s4 c2t203600A0B875F200d0s2 c3t0d0s0
c1t203700A0B875F200d0s5 c2t203600A0B875F200d0s3 c3t0d0s1
c1t203700A0B875F200d0s6 c2t203600A0B875F200d0s4 c3t0d0s2
c1t203700A0B875F200d0s7 c2t203600A0B875F200d0s5 c3t0d0s3
c1t203700A0B875F200d1s0 c2t203600A0B875F200d0s6 c3t0d0s4
c1t203700A0B875F200d1s1 c2t203600A0B875F200d0s7 c3t0d0s5
c1t203700A0B875F200d1s2 c2t203600A0B875F200d1s0 c3t0d0s6
c1t203700A0B875F200d1s3 c2t203600A0B875F200d1s1 c3t0d0s7
Unfortunately, your OS is on your storage array and the device tree is different when you boot off DVD vs normal. Do you have internal drives in your system? Maybe you could use liveupgrade to migrate your OS to an internal drive and upgrade that way? That's the only advice I can give you at this point...
Wow those paths that are in your vfstab don't look like internal disks in a v440. When you boot with the IBM array disconnected does your vfstab look any different? What does "luxadm display all" show?
Edit- I just realized we haven't discussed what kind of hardware it is. Somehow I thought it was a v440 but obviously it is not. What is the hardware involved here?
Edited by: bobthesungeek76036 on May 10, 2012 12:46 PM
We have a Sun v490.
When we unplug the IBM array, we can boot still boot. Our /etc/vfstab looks the same.
Our df -h looks the same
bash-3.00# df -h
Filesystem size used avail capacity Mounted on
15G 578M 15G 4% /
bash-3.00# luxadm display all
Error: Invalid pathname (all)
bash-3.00# luxadm display /dev/rdsk/c6t20000011C63FE713d0s0
DEVICE PROPERTIES for disk: /dev/rdsk/c6t20000011C63FE713d0s0
Status(Port A): O.K.
Product ID: ST3146807FC
WWN(Port A): 21000011c63fe713
Serial Num: 3HYX1MVQ00007429Q8ND
Unformatted capacity: 140014.406 MBytes
Write Cache: Enabled
Read Cache: Enabled
Minimum prefetch: 0x0
Maximum prefetch: 0xffff
Device Type: Disk device
Device Address 21000011c63fe713,0
Host controller port WWN 210000144f4ae1f0
Ahhhh! The dreaded V490. Now I know what is going on here. For some reason, your internal drive got Ledville-style names (they are FC disks). Meaining c6t20000011C63FE713d0s0 booting from disk is equal to c3t0d0s0 when booting from DVD. I bet if you boot off the DVD single-user and mount /dev/dsk/c3t0d0s0 to /mnt (it might be c1t0d0s0 if you have the external array pulled) you will see your OS root partition. At that point, you could probably edit the vfstab file (make a backup!) and make the devices match the DVD-booted names. Then start the installer and I bet the upgrade option will show up.