Hello Charles On Sun, Apr 24, 2022 at 01:08:03PM -0600, Charles Curley wrote: > I have three hard drives in a RAID 5 array. This morning my motherboard > went wonky and crashed. USB devices on the motherboard are acting up. I > cannot reboot to Debian. I can, however, boot to finnix 120. Using > that, I have fscked all partitions, including the RAID array. I am > running checksums, with no reported errors. So far, so good. > > One drive, /dev/sdd, which has a partition which is a member of the RAID > array, gave me some error messages on the console and copied to dmesg, > reproduced below. It is a SATA drive, masquerading as as SCSI device. I > ran a SMART short test which reported no errors. > > Some quick grepping in syslog and syslog.1 showed no non-routine error > messages for /dev/sdd. > > Would someone who knows SCSI error messages better than I do please let > me know if there are any problems with the drive. > > -------------------------------------------------- > Lines not related to sdd removed. > > [ 1124.317921] sd 3:0:0:0: [sdd] tag#5 FAILED Result: hostbyte=DID_OK > driverbyte=DRIVER_SENSE cmd_age=0s > [ 1124.317925] sd 3:0:0:0: [sdd] tag#5 Sense Key : Illegal Request [current] > [ 1124.317928] sd 3:0:0:0: [sdd] tag#5 Add. Sense: Unaligned write command > [ 1124.317932] sd 3:0:0:0: [sdd] tag#5 CDB: Read(16) 88 00 00 00 00 00 00 04 > 59 80 00 00 00 a0 00 00 > [ 1124.317936] blk_update_request: I/O error, dev sdd, sector 285056 op > 0x0:(READ) flags 0x80700 phys_seg 5 prio class 0 > [ 1124.320088] ata4: EH complete > [ 1150.401439] ata4.00: exception Emask 0x52 SAct 0x180 SErr 0x400c01 action > 0x6 frozen > [ 1150.404656] ata4.00: irq_stat 0x08000008, interface fatal error > [ 1150.407870] ata4: SError: { RecovData Proto HostInt Handshk } > [ 1150.411095] ata4.00: failed command: READ FPDMA QUEUED > [ 1150.414383] ata4.00: cmd 60/40:38:40:54:44/00:00:53:00:00/40 tag 7 ncq dma > 32768 in > res 40/00:40:00:55:44/00:00:53:00:00/40 Emask 0x52 > (ATA bus error) > [ 1150.416190] ata4.00: status: { DRDY } > [ 1150.416967] ata4.00: failed command: READ FPDMA QUEUED > [ 1150.417747] ata4.00: cmd 60/80:40:00:55:44/00:00:53:00:00/40 tag 8 ncq dma > 65536 in > res 40/00:40:00:55:44/00:00:53:00:00/40 Emask 0x52 > (ATA bus error) > [ 1150.419316] ata4.00: status: { DRDY } > [ 1150.420083] ata4: hard resetting link > [ 1150.732231] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > [ 1150.733546] ata4.00: configured for UDMA/133 > -------------------------------------------------- >
This does not look like a happy drive - failed requests, bus error { DRDY } I'd call that dead, particularly since the drive keeps resetting to find the speed. I think it might be a bin it and hope you can find another from somewhere. As others are always fond of telling me: RAID != backup :) All the very best, as ever, Andy Cater > -- > Does anybody read signatures any more? > > https://charlescurley.com > https://charlescurley.com/blog/ >