Sponsored Content
Operating Systems Solaris Sun Fire v440 Hard disk or controller broken? WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1) Post 303044077 by oliwei on Thursday 13th of February 2020 12:33:25 PM
Old 02-13-2020
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.
 

10 More Discussions You Might Find Interesting

1. 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

2. 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

3. 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

4. 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

5. 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

6. 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

7. 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

8. 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

9. 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

10. 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
MKFS.MINIX(8)						       System Administration						     MKFS.MINIX(8)

NAME
mkfs.minix - make a Minix filesystem SYNOPSIS
mkfs.minix [options] device [size-in-blocks] DESCRIPTION
mkfs.minix creates a Linux MINIX filesystem on a device (usually a disk partition). The device is usually of the following form: /dev/hda[1-8] (IDE disk 1) /dev/hdb[1-8] (IDE disk 2) /dev/sda[1-8] (SCSI disk 1) /dev/sdb[1-8] (SCSI disk 2) The device may be a block device or a image file of one, but this is not enforced. Expect not much fun on a character device :-). The size-in-blocks parameter is the desired size of the file system, in blocks. It is present only for backwards compatibility. If omit- ted the size will be determined automatically. Only block counts strictly greater than 10 and strictly less than 65536 are allowed. OPTIONS
-c, --check Check the device for bad blocks before creating the filesystem. If any are found, the count is printed. -n, --namelength length Specify the maximum length of filenames. Currently, the only allowable values are 14 and 30 for file system versions 1 and 2. Ver- sion 3 allows only value 60. The default is 30. -i, --inodes number Specify the number of inodes for the filesystem. -l, --badblocks filename Read the list of bad blocks from filename. The file has one bad-block number per line. The count of bad blocks read is printed. -1 Make a Minix version 1 filesystem. This is the default. -2, -v Make a Minix version 2 filesystem. -3 Make a Minix version 3 filesystem. -V, --version Display version information and exit. The long option cannot be combined with other options. -h, --help Display help text and exit. EXIT CODES
The exit code returned by mkfs.minix is one of the following: 0 No errors 8 Operational error 16 Usage or syntax error SEE ALSO
fsck(8), mkfs(8), reboot(8) AVAILABILITY
The mkfs.minix command is part of the util-linux package and is available from https://www.kernel.org/pub/linux/utils/util-linux/. util-linux June 2015 MKFS.MINIX(8)
All times are GMT -4. The time now is 02:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy