This is a discussion on panic[cpu3]/thread=140a000: vfs_mountroot: cannot mount root within the Sun Solaris Administration forums, part of the Solaris Operating System category; --> Hi , I got CPU panic problem on my server. Here is the error message: Rebooting with command: boot ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi , I got CPU panic problem on my server. Here is the error message: Rebooting with command: boot disk6 Boot device: /pci@8,600000/SUNW,qlc@2/fp@0,0/disk@8,0 File and args: | SunOS Release 5.9 Version Generic_118558-11 64-bit Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Cannot mount root on /pseudo/md@0:0,5,blk fstype ufs panic[cpu3]/thread=140a000: vfs_mountroot: cannot mount root 0000000001409970 genunix:vfs_mountroot+70 (0, 0, 0, 200, 1457ef0, 0) %l0-3: 000000000144b800 000000000144b800 0000000000002000 0000000001495a40 %l4-7: 000000000149b800 0000000001411e58 000000000144c000 000000000144f000 0000000001409a20 genunix:main+90 (1409ba0, f0061a30, 1409ec0, 38dc6c, 2000, 500) %l0-3: 0000000000000001 000000000140a000 0000000001413018 00000000 Could anyone told me what happened on my server? Thanks Jason |
| |||
| Jason Wang wrote: > Hi , > > I got CPU panic problem on my server. Here is the error message: > > Rebooting with command: boot disk6 Boot device: > /pci@8,600000/SUNW,qlc@2/fp@0,0/disk@8,0 File and args: | SunOS Release 5.9 > Version Generic_118558-11 64-bit Copyright 1983-2003 Sun Microsystems, Inc. > All rights reserved. Use is subject to license terms. Cannot mount root on > /pseudo/md@0:0,5,blk fstype ufs panic[cpu3]/thread=140a000: vfs_mountroot: > cannot mount root 0000000001409970 genunix:vfs_mountroot+70 (0, 0, 0, 200, > 1457ef0, 0) %l0-3: 000000000144b800 000000000144b800 0000000000002000 > 0000000001495a40 %l4-7: 000000000149b800 0000000001411e58 000000000144c000 > 000000000144f000 0000000001409a20 genunix:main+90 (1409ba0, f0061a30, > 1409ec0, 38dc6c, 2000, 500) %l0-3: 0000000000000001 000000000140a000 > 0000000001413018 00000000 > > Could anyone told me what happened on my server? > > > Thanks > Jason > > > Hi Jason, if possible boot from cdrom or install server and run fsck on boot device disk 6. Last week i had the same problem with a SF2900 and S1 Storage. But from S1 disk results in a CPU Panic. File System has been checked. probe-scsi-all was successfully. The vhdci scsi cable between the S1 and the HBA in E2900 was faulty. After the replacement of the cable the System works fine. HTH Thomas |
| ||||
| > I got CPU panic problem on my server. Here is the error message: > > Rebooting with command: boot disk6 Boot device: > /pci@8,600000/SUNW,qlc@2/fp@0,0/disk@8,0 File and args: | SunOS Release 5.9 > Version Generic_118558-11 64-bit Copyright 1983-2003 Sun Microsystems, Inc. > All rights reserved. Use is subject to license terms. Cannot mount root on > /pseudo/md@0:0,5,blk fstype ufs panic[cpu3]/thread=140a000: vfs_mountroot: > cannot mount root 0000000001409970 genunix:vfs_mountroot+70 (0, 0, 0, 200, > 1457ef0, 0) %l0-3: 000000000144b800 000000000144b800 0000000000002000 > 0000000001495a40 %l4-7: 000000000149b800 0000000001411e58 000000000144c000 > 000000000144f000 0000000001409a20 genunix:main+90 (1409ba0, f0061a30, > 1409ec0, 38dc6c, 2000, 500) %l0-3: 0000000000000001 000000000140a000 > 0000000001413018 00000000 > > Could anyone told me what happened on my server? Is it a Sun Fire V880/V890? From the boot device this would be my best guess. Does it always panic on the same CPU? What happens if you boot single-user mode off a CD-ROM instead of the hard drive? If you can boot up to a command prompt off a CD-ROM I'd say fsck everything and anything and then try to boot up normally and see if that fixes the problem. Should problems happen even while booting off a CD-ROM, then see if you can connect a serial console to the server unless that's what you're already doing. If so, then set diag-level to max and diag-switch? to true and power cycle the machine. With the machine at this level you are more likely to have a CPU or DIMM detected if faulty. There's also a better chance the diagnostics will offline whatever is at fault and at least let you boot up in a degraded state until you can get the machine serviced. Trinean |