From: Steve Camp (steve@aslan.camp.com)
Date: Sat May 18 2002 - 12:18:14 EDT
Hi,
A friend of mine cannot boot his Netra t1-105. I do not know all the details
of how he installed the OS on this t1, but he may have done something along
the lines of cloning a hard drive or OS image from an * Netra X1 *.
The boot is failing thusly:
ok boot -v
Boot device: /pci@1f,0/pci@1,1/scsi@2/disk@0,0 File and args: -v
Size: 338336+89970+75914 Bytes
SunOS Release 5.8 Version Generic_108528-13 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
Ethernet address = 8:0:20:xx:yy:zz
mem = 524288K (0x20000000)
avail mem = 509575168
root nexus = Netra t1 (UltraSPARC-IIi 360MHz)
pcipsy0 at root: UPA 0x1f 0x0
pcipsy0 is /pci@1f,0
PCI-device: pci@1,1, simba0
simba0 is /pci@1f,0/pci@1,1
PCI-device: pci@1, simba1
simba1 is /pci@1f,0/pci@1
Cannot assemble drivers for root /pci@1f,0/pci@1,1/scsi@2/disk@0,0:a
Cannot mount root on /pci@1f,0/pci@1,1/scsi@2/disk@0,0:a fstype ufs
panic[cpu0]/thread=10408000: vfs_mountroot: cannot mount root
0000000010407970 genunix:vfs_mountroot+70 (10435800, 0, 0, 10410918, 10, 14)
%l0-3: 0000000010435c00 0000000010439110 000000003b000000 0000000010435cf8
%l4-7: 0000000000000000 00000000104136b0 00000000000b7798 0000000000001798
0000000010407a20 genunix:main+94 (10410160, 2000, 10407ec0, 10408030, fff2, 1004ec8c)
%l0-3: 0000000000000001 0000000000000001 0000000000000015 0000000000000e9a
%l4-7: 0000000010428c18 0000000010462120 00000000000cd4c0 0000000000000540
skipping system dump - no dump device configured
rebooting...
Resetting ...
I have researched the "vfs_mountroot: cannot mount root" panic's, and past messages
seem to indicate this is a missing driver issue in the OS image that is loading.
Question is: which driver(s), and proper way to fix? Has anyone run into this
problem before on Netra t1's?
The following have been tried to no avail:
ok boot net -s
# mount /dev/dsk/c0t0d0s0 /a
# add_drv -b /a "SUNW,fas"
(SUNW,fas) already in use as a driver or alias.
# devlinks -r /a
# umount /a
# reboot -- -r
< subsequent reboot failed as above >
ok boot net -s
# mount /dev/dsk/c0t0d0s0 /a
# (cd /;tar cf - dev devices) | (cd /a; tar xfBp -)
# reboot -- -r
syncing file systems... done
rebooting...
Resetting ...
< subsequent reboot failed as above >
ok., Try 3...
replaced /dev/ and /devices
then...
1: removed path_to_inst
2: "boot -ar", accepting all the defaults and answering yes to recreate
/etc/path_to_inst.
Executing last command: boot -ar
Boot device: /pci@1f,0/pci@1,1/scsi@2/disk@0,0 File and args: -ar
Enter filename [kernel/sparcv9/unix]:
Enter default directory for modules [/platform/sun4u/kernel /kernel /usr/kernel]:
Name of system file [etc/system]:
SunOS Release 5.8 Version Generic_108528-13 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
\
The /etc/path_to_inst on your system does not exist or is empty.
Do you want to rebuild this file [n]? y
root filesystem type [ufs]:
Enter physical name of root device
[/pci@1f,0/pci@1,1/scsi@2/disk@0,0:a]:
Cannot assemble drivers for root /pci@1f,0/pci@1,1/scsi@2/disk@0,0:a
Cannot mount root on /pci@1f,0/pci@1,1/scsi@2/disk@0,0:a fstype ufs
panic[cpu0]/thread=10408000: vfs_mountroot: cannot mount root
0000000010407970 genunix:vfs_mountroot+70 (10435800, 0, 0, 10410918, 10, 14)
%l0-3: 0000000010435c00 0000000010439110 000000003b000000 0000000010435cf8
%l4-7: 0000000000000000 00000000104136b0 00000000000b7798 0000000000001798
0000000010407a20 genunix:main+94 (10410160, 2000, 10407ec0, 10408030, fff2, 1004ec8c)
%l0-3: 0000000000000001 0000000000000001 0000000000000015 0000000000000e9a
%l4-7: 0000000010428c18 0000000010462120 00000000000cd4c0 0000000000000540
skipping system dump - no dump device configured
rebooting...
Resetting ...
Thanks in advance.
-- Steve Camp Camp Technologies, LLC steve@camp.com _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:21 EDT