V210 hangs after "Hardware Watchdog Enabled" on boot
Hello,
as I wrote in the subject my SUN V210 hangs after "Hardware Watchdog Enabled" on boot. If I want to shutdown the system with the "power button" I am getting the message "WARNING: Failed to shut down the system!"..
This failure occures after I mounted the harddisk in another hardware enviroment.
I am administrating the SUN temporarily over a HyperTerminal connection to the serial management port.
What could the reason of this problem, and did someone know what I could do?
Thanks and Best Regards
[543 byte] By [
NetCohorta] at [2007-11-27 8:26:39]
# 1
what is the schema of mounting - did You mount v210 drive in another machine?
# 2
Yes, I mounted the harddisk with the command "mount -t ufs -o ufstype=sun" in an Linux enviroment...
# 3
Hmm, maybe you should boot your V210 from a cdrom or jumpstart and run fsck -o f on the root device.By curiosity, was the linux box a SPARC or x86 system? Did seem ok on the linux ? .7/M.
# 4
The SUN box is a SPARC system. The linux system where I mounted the harddisk is a x86 system. But I did not boot from the harddisk, but I boot it in an enviroment of a Linux Live CD like Knoppix. It seems definitivly ok on the Linux.
Unfortunately, at time I did not have a Solaris souce neither on CD nor in the network...
Did I have more possibilities within the ok prompt or within the ALOM? To switch to another runlevel does not work due to the hardware watchdog..
Is there a possibility to disable the hardware watchdog?
Rgds
# 5
I don't think the problem here is the hardware watchdog, its merely the last message you see, whatever the system is doing after that fails.
You could try and boot with 'boot -v' to get some verbose output, then you would probably more accurately see where it goes wrong.
Its a bit funny thought, if i recall correctly you can't mount a Solaris/SPARC ufs disk in Solaris/x86, so i'm a bit surprised it works under Linux.
.7/M.
# 6
I got following message:ok boot -vFATAL: /pci@1c,600000/scsi@2: OpenBoot initialization sequence prematurelyterminated.FATAL: system is not bootable, boot command is disabledIt does not look good... Is there any possibility to repair?Rgds
# 7
ummset the 'auto-boot?' to 'false' at the OK prompt, then do a reset-all (or is it reset all?), and then:boot <default boot device> -vfor example, if the boot device (determined by 'printenv boot-device') points to 'disk2':boot disk2 -v
# 8
It was reset-all, but I did not boot explicit from disk:a (my boot device)..
I got following output (after the hardware watchdog):
Hardware watchdog enabled
su0 at ebus0: offset 0,3f8
su0 is /pci@1e,600000/isa@7/serial@0,3f8
su1 at ebus0: offset 0,2e8
su1 is /pci@1e,600000/isa@7/serial@0,2e8
cpu0: UltraSPARC-IIIi (portid 0 impl 0x16 ver 0x34 clock 1336 MHz)
PCI-device: usb@a, ohci0
ohci0 is /pci@1e,600000/usb@a
Afterwards it hangs...
Do you need the whole output?
# 9
Normally I'd reply with this - is it possible that the Linux machine wrote something to the bootblock on the rootdisk? - can you boot to Solaris on some machine media and run installboot just for kicks?But without Solaris media, you may have an issue doing that - jeff
# 10
Hi,
now I booted the system with one Solaris cdrom in the single user mode.
First I try a fsck:
# fsck -F ufs -o b=32 /dev/rdsk/c0t0d0s0
Alternate super block location: 32.
** /dev/rdsk/c0t0d0s0 (NO WRITE)
BAD SUPER BLOCK: MAGIC NUMBER WRONG
USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION;
eg. fsck [-F ufs] -o b=# [special ...]
where # is the alternate super block. SEE fsck_ufs(1M).
So I try to find the next superblock.
# newfs -N /dev/rdsk/c0t0d0s0
mkfs: bad value for size: 640 must be between 1024 and 640
mkfs: size reset to default 640
Warning: inode blocks/cyl group (42) >= data blocks (40) in last
cylinder group. This implies 640 sector(s) cannot be allocated.
/dev/rdsk/c0t0d0s0:0 sectors in 0 cylinders of 1 tracks, 640 sectors
0.0MB in 0 cyl groups (16 c/g, 5.00MB/g, 2432 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
But I did not get an alternative super-block no..
Did I have another chance?
To run installboot just for kicks. What do you mean with this?
To reinstall the bootblock with:
installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t0d0s0
?
Rgds
Message was edited by:
NetCohort
