> I've got a Sun V240 that crashes every time it tries to fsck /var > (sd0g in my case). > > This happens on more than one of these machines and with more than 1 disk. > > It doesn't matter if I run fsck in read-only mode, whenever it tries > to read from this partition it dumps. > It also happens if I try to use dd to copy the partition elsewhere. > > > ################### > FSCK OUTPUT: > ################### > # fsck -y /dev/sd0g > ** /dev/rsd0g > BAD SUPER BLOCK: MAGIC NUMBER WRONG > > LOOK FOR ALTERNATE SUPERBLOCKS? yes > > sd0(siop0:0:0): Check Condition (error 0x70) on opcode 0x28 > SENSE KEY: Media Error > INFO: 0x22dfdd1 (VALID flag on) > ASC/ASCQ: Unrecovered Read Error > FRU CODE: 0xf > SKSV: Actual Retry Count: 983 > > CANNOT READ: BLK 23984032 > CONTINUE? yes
Yes, your disk is dead. The drive is telling you that quite clearly. The disk tried to re-read that block 983 times in a row, and then it told OpenBSD that the block cannot be read. I don't understand what part of "Media error" it is that people keep not paying attention to. Perhaps we should really add "Your disk is dying".
