Sun Fire v440 Hard disk or controller broken? WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1)


Login or Register for Dates, Times and to Reply

 
Thread Tools Search this Thread
Operating Systems Solaris Sun Fire v440 Hard disk or controller broken? WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1)
# 8  
Sorry about the misleading info from raidctl. The resync was shown because I powered down the system removed one of the disks and powered it back on with a single disk to see whether the error stays. Somehow I was only able to boot when d0 was installed. Pulling d0 the system was not able to boot. I have now replaced the second disk d1 with a fresh disk, the raid seems is rebuilt but still the system shows the same error during boot. Smilie I have now removed d0 again and booted only with the new synced d1 disk but the same error is shown. Is there a possibility that there is a problem with the filesystem itself and this error is now also replicated to the new disk?
# 9  
Well it's complaining about a media error but, sure, it could indeed be a corrupt sector(s) in the middle of a filesystem.

This is, of course, the root filesystem. Is this filesystem UFS or ZFS?

A full filesystem check would be a good idea. Get ready to write down any inode numbers it complains about (it might not come out with actual filenames if the filesystem is corrupt.

Do you have a backup? If not, you should take one because filesystem checking can destroy a filesystem faster than you can blink if there is significant corruption and it tries to correct it.

Of course, you will probably need to boot from DVD media to check a root filesystem.
# 10  
Probably a good idea just to do a root filesystem check with a "no write" flag. That way you get to see what damage there is without the risk that it will try to fix it. It will show you the difference as to whether there is one file corrupt or one million files corrupt.
# 11  
It's a UFS filesystem. I did a file system check and the results don't look good:


Quote:
# fsck -y -F ufs /dev/dsk/c0t0d0s0
** /dev/rdsk/c0t0d0s0 (NO WRITE)
BAD SUPERBLOCK AT BLOCK 16: MAGIC NUMBER WRONG

LOOK FOR ALTERNATE SUPERBLOCKS WITH MKFS? no


LOOK FOR ALTERNATE SUPERBLOCKS WITH NEWFS? no

SEARCH FOR ALTERNATE SUPERBLOCKS FAILED.

USE GENERIC SUPERBLOCK FROM MKFS? no


USE GENERIC SUPERBLOCK FROM NEWFS? no

SEARCH FOR ALTERNATE SUPERBLOCKS FAILED. YOU MUST USE THE -o b OPTION
TO FSCK TO SPECIFY THE LOCATION OF A VALID ALTERNATE SUPERBLOCK TO
SUPPLY NEEDED INFORMATION; SEE fsck(1M).


There is no recent backup available. The project team that is responsible for the server did not regulary backup the machine. This morning I tried to ufsdump the filesystem but this failed with a couple of errors. I do have a ufsdump from 2017. Maybe I try to restore this dump to the new disk just to check whether this works. If it doesn't there must be a hardware fault somewhere in the system as the disk is brand new.
# 12  
That's not too bad on face value.

There's obviously a superblock located at block=16 but the system maintains other copies at other block locations

AFAIR, you should be able to specify an alternative superblock location and get it to fix the superblock (at least).

Google that, I'll look it up too, or probably another Sun expert on here will chip in. Don't do anything rash yet.
# 13  
Yep, there's another copy of the superblock at block=32. (And there will be others).

The search for an alternative superblock failed because you spec'd NO WRITE. So it didn't even try.
# 14  
Use the switch:

Code:
-o b=32

on the command line to use superblock at block=32.
Login or Register for Dates, Times and to Reply

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

Test Your Knowledge in Computers #975
Difficulty: Easy
In July 2009, Alan Cox quit his Linux kernel development role as the TTY layer maintainer after disagreement with Linus Torvalds about who should pay for beers during a trip to Amsterdam.
True or False?

10 More Discussions You Might Find Interesting

1. Solaris

Removing a disk from SUN Fire V440 running Solaris 8

Hi, I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either. Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Discussion started by: Echo68
5 Replies

2. Solaris

Sun-Fire V440 boot disk issue

Hi, I have Sun Fire V440. Boot disks are mirrored. system crashed and it's not coming up. Error message is Insufficient metadevice database replicas located. Use Metadb to delete databases which are broken. Boot disks are mirrored and other disks are ZFS configuration. Please... (2 Replies)
Discussion started by: samnyc
2 Replies

3. Solaris

Sun Fire v440 Over heat Problem.

Dear Team, I need some expert advice to my problem. We have a Sun Fire v440 in our customer Place. Server is working fine and no hardware deviations are found except one problem that processors generating too much heat. I have verified and found that the room temperature was 26-27 degree.... (5 Replies)
Discussion started by: sudhansu
5 Replies

4. Solaris

Firmware password Solaris Sun Fire v440

Hi: I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Discussion started by: mguazzardo
1 Replies

5. AIX

SCSI PCI - X RAID Controller card RAID 5 AIX Disks disappeared

Hello, I have a scsi pci x raid controller card on which I had created a disk array of 3 disks when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk ) suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies

6. Solaris

error messages in Sun Fire V440

Hello, I am seeing error messages in V440 (OS = solaris 8). I have copied here : The system does not reboot constantly and it is up for last 67 days. One more interesting thing I found, I see errors start appearing at 4:52AM last until 6am and again start at 16:52am on same day.. I... (5 Replies)
Discussion started by: upengan78
5 Replies

7. Solaris

Sun Fire v440 hardware problem (can't get ok>)

First of all it's shut down 60 second after power on and write on console : SC Alert: Correct SCC not replaced - shutting managed system down! This is cured by moving out battery from ALOM card. Now server start to loop during the testing. That's on the console: >@(#) Sun Fire V440,Netra... (14 Replies)
Discussion started by: Alisher
14 Replies

8. Solaris

USB Hard Disk Drive Supported by Sun Fire V890

Hi, Can anyone suggest me any USB Hard Disk Drive which I can connect to Sun Fire V890 and take backup at a quick speed. A test with SolidState USB Hard Drive for backup work was taking writing at 2GB per hour for a 75GB backup. Regards, Tushar Kathe (1 Reply)
Discussion started by: tushar_kathe
1 Replies

9. Solaris

Sun Fire v440 keeps shutting down

Hello, I hope you can help me. I am new to Sun servers and we have a Sun Fire v440 server in which one power supply failed, we are waiting for new one. But now our server is shutting down constantly. Is there any setting with which we can prevent this behaviour? (1 Reply)
Discussion started by: Tibor
1 Replies

10. Solaris

Sun Fire V440 and Patch 109147-39

Got an curious issue. I applied 109147-39 to, oh 15 or so various systems all running Jumpstarted Solaris 8. When I hit the first two V440s, they both failed with Return code 139. All non shell commands segfaulted from then on. The patch modified mainly the linker libraries and commands. ... (2 Replies)
Discussion started by: BOFH
2 Replies

Featured Tech Videos