Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #247491 > unrolled thread
| Started by | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| First post | 2022-04-24 21:10 +0200 |
| Last post | 2022-04-27 04:10 +0200 |
| Articles | 12 — 3 participants |
Back to article view | Back to linux.debian.user
Do I need a new hard drive? Charles Curley <charlescurley@charlescurley.com> - 2022-04-24 21:10 +0200
Re: Do I need a new hard drive? "Andrew M.A. Cater" <amacater@einval.com> - 2022-04-24 21:30 +0200
Re: Do I need a new hard drive? David Christensen <dpchrist@holgerdanske.com> - 2022-04-24 23:10 +0200
Re: Do I need a new hard drive? Charles Curley <charlescurley@charlescurley.com> - 2022-04-25 00:40 +0200
Re: Do I need a new hard drive? David Christensen <dpchrist@holgerdanske.com> - 2022-04-25 07:50 +0200
Re: Do I need a new hard drive? Charles Curley <charlescurley@charlescurley.com> - 2022-04-25 17:40 +0200
Re: Do I need a new hard drive? Charles Curley <charlescurley@charlescurley.com> - 2022-04-25 02:20 +0200
Re: Do I need a new hard drive? David Christensen <dpchrist@holgerdanske.com> - 2022-04-25 08:00 +0200
Re: Do I need a new hard drive? Charles Curley <charlescurley@charlescurley.com> - 2022-04-25 16:20 +0200
Re: Do I need a new hard drive? David Christensen <dpchrist@holgerdanske.com> - 2022-04-26 00:00 +0200
Re: Do I need a new hard drive? Charles Curley <charlescurley@charlescurley.com> - 2022-04-27 00:10 +0200
Re: Do I need a new hard drive? David Christensen <dpchrist@holgerdanske.com> - 2022-04-27 04:10 +0200
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2022-04-24 21:10 +0200 |
| Subject | Do I need a new hard drive? |
| Message-ID | <EfPMm-aVIr-9@gated-at.bofh.it> |
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.
...
[ 2.075895] sd 3:0:0:0: [sdd] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[ 2.075897] sd 3:0:0:0: [sdd] 4096-byte physical blocks
[ 2.075904] sd 3:0:0:0: [sdd] Write Protect is off
[ 2.075906] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[ 2.075921] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.152206] sdd: sdd1
[ 2.152720] sd 3:0:0:0: [sdd] Attached SCSI disk
[ 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
[ 1150.733557] sd 3:0:0:0: [sdd] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
[ 1150.733560] sd 3:0:0:0: [sdd] tag#7 Sense Key : Illegal Request [current]
[ 1150.733562] sd 3:0:0:0: [sdd] tag#7 Add. Sense: Unaligned write command
[ 1150.733565] sd 3:0:0:0: [sdd] tag#7 CDB: Read(16) 88 00 00 00 00 00 53 44 54 40 00 00 00 40 00 00
[ 1150.733567] blk_update_request: I/O error, dev sdd, sector 1396986944 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 1150.735120] sd 3:0:0:0: [sdd] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
[ 1150.735122] sd 3:0:0:0: [sdd] tag#8 Sense Key : Illegal Request [current]
[ 1150.735123] sd 3:0:0:0: [sdd] tag#8 Add. Sense: Unaligned write command
[ 1150.735125] sd 3:0:0:0: [sdd] tag#8 CDB: Read(16) 88 00 00 00 00 00 53 44 55 00 00 00 00 80 00 00
[ 1150.735127] blk_update_request: I/O error, dev sdd, sector 1396987136 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 1150.736651] ata4: EH complete
[ 1155.401430] ata4.00: exception Emask 0x52 SAct 0x80800000 SErr 0x400c01 action 0x6 frozen
[ 1155.404486] ata4.00: irq_stat 0x08000000, interface fatal error
[ 1155.407528] ata4: SError: { RecovData Proto HostInt Handshk }
[ 1155.410548] ata4.00: failed command: READ FPDMA QUEUED
[ 1155.411882] ata4.00: cmd 60/40:b8:40:55:e4/00:00:66:00:00/40 tag 23 ncq dma 32768 in
res 40/00:f8:00:56:e4/00:00:66:00:00/40 Emask 0x52 (ATA bus error)
[ 1155.414526] ata4.00: status: { DRDY }
[ 1155.415848] ata4.00: failed command: READ FPDMA QUEUED
[ 1155.417185] ata4.00: cmd 60/80:f8:00:56:e4/00:00:66:00:00/40 tag 31 ncq dma 65536 in
res 40/00:f8:00:56:e4/00:00:66:00:00/40 Emask 0x52 (ATA bus error)
[ 1155.419904] ata4.00: status: { DRDY }
[ 1155.421265] ata4: hard resetting link
[ 1155.736222] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1155.737557] ata4.00: configured for UDMA/133
[ 1155.737569] sd 3:0:0:0: [sdd] tag#23 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
[ 1155.737571] sd 3:0:0:0: [sdd] tag#23 Sense Key : Illegal Request [current]
[ 1155.737574] sd 3:0:0:0: [sdd] tag#23 Add. Sense: Unaligned write command
[ 1155.737577] sd 3:0:0:0: [sdd] tag#23 CDB: Read(16) 88 00 00 00 00 00 66 e4 55 40 00 00 00 40 00 00
[ 1155.737580] blk_update_request: I/O error, dev sdd, sector 1726240064 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
[ 1155.739201] sd 3:0:0:0: [sdd] tag#31 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
[ 1155.739202] sd 3:0:0:0: [sdd] tag#31 Sense Key : Illegal Request [current]
[ 1155.739204] sd 3:0:0:0: [sdd] tag#31 Add. Sense: Unaligned write command
[ 1155.739205] sd 3:0:0:0: [sdd] tag#31 CDB: Read(16) 88 00 00 00 00 00 66 e4 56 00 00 00 00 80 00 00
[ 1155.739207] blk_update_request: I/O error, dev sdd, sector 1726240256 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 1155.740801] ata4: EH complete
[ 1155.825384] ata4: limiting SATA link speed to 3.0 Gbps
[ 1155.825388] ata4.00: exception Emask 0x52 SAct 0x300000 SErr 0xc00 action 0x6 frozen
[ 1155.827501] ata4.00: irq_stat 0x08000000, interface fatal error
[ 1155.829637] ata4: SError: { Proto HostInt }
[ 1155.829640] ata4.00: failed command: READ FPDMA QUEUED
[ 1155.829645] ata4.00: cmd 60/40:a0:40:54:24/00:00:67:00:00/40 tag 20 ncq dma 32768 in
res 40/00:a8:00:55:24/00:00:67:00:00/40 Emask 0x52 (ATA bus error)
[ 1155.829646] ata4.00: status: { DRDY }
[ 1155.829648] ata4.00: failed command: READ FPDMA QUEUED
[ 1155.829652] ata4.00: cmd 60/80:a8:00:55:24/00:00:67:00:00/40 tag 21 ncq dma 65536 in
res 40/00:a8:00:55:24/00:00:67:00:00/40 Emask 0x52 (ATA bus error)
[ 1155.829653] ata4.00: status: { DRDY }
[ 1155.829656] ata4: hard resetting link
[ 1156.144287] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 1156.145684] ata4.00: configured for UDMA/133
[ 1156.145695] sd 3:0:0:0: [sdd] tag#20 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
[ 1156.145698] sd 3:0:0:0: [sdd] tag#20 Sense Key : Illegal Request [current]
[ 1156.145700] sd 3:0:0:0: [sdd] tag#20 Add. Sense: Unaligned write command
[ 1156.145702] sd 3:0:0:0: [sdd] tag#20 CDB: Read(16) 88 00 00 00 00 00 67 24 54 40 00 00 00 40 00 00
[ 1156.145705] blk_update_request: I/O error, dev sdd, sector 1730434112 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 1156.147784] sd 3:0:0:0: [sdd] tag#21 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
[ 1156.147785] sd 3:0:0:0: [sdd] tag#21 Sense Key : Illegal Request [current]
[ 1156.147787] sd 3:0:0:0: [sdd] tag#21 Add. Sense: Unaligned write command
[ 1156.147789] sd 3:0:0:0: [sdd] tag#21 CDB: Read(16) 88 00 00 00 00 00 67 24 55 00 00 00 00 80 00 00
[ 1156.147791] blk_update_request: I/O error, dev sdd, sector 1730434304 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 1156.149854] ata4: EH complete
--------------------------------------------------
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
[toc] | [next] | [standalone]
| From | "Andrew M.A. Cater" <amacater@einval.com> |
|---|---|
| Date | 2022-04-24 21:30 +0200 |
| Message-ID | <EfQ5H-aVOu-5@gated-at.bofh.it> |
| In reply to | #247491 |
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/
>
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2022-04-24 23:10 +0200 |
| Message-ID | <EfREt-aWUt-7@gated-at.bofh.it> |
| In reply to | #247491 |
On 4/24/22 12:08, 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.
> ...
> [ 2.075895] sd 3:0:0:0: [sdd] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
> [ 2.075897] sd 3:0:0:0: [sdd] 4096-byte physical blocks
> [ 2.075904] sd 3:0:0:0: [sdd] Write Protect is off
> [ 2.075906] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
> [ 2.075921] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
>
> [ 2.152206] sdd: sdd1
> [ 2.152720] sd 3:0:0:0: [sdd] Attached SCSI disk
>
> [ 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
> [ 1150.733557] sd 3:0:0:0: [sdd] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
> [ 1150.733560] sd 3:0:0:0: [sdd] tag#7 Sense Key : Illegal Request [current]
> [ 1150.733562] sd 3:0:0:0: [sdd] tag#7 Add. Sense: Unaligned write command
> [ 1150.733565] sd 3:0:0:0: [sdd] tag#7 CDB: Read(16) 88 00 00 00 00 00 53 44 54 40 00 00 00 40 00 00
> [ 1150.733567] blk_update_request: I/O error, dev sdd, sector 1396986944 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
> [ 1150.735120] sd 3:0:0:0: [sdd] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
> [ 1150.735122] sd 3:0:0:0: [sdd] tag#8 Sense Key : Illegal Request [current]
> [ 1150.735123] sd 3:0:0:0: [sdd] tag#8 Add. Sense: Unaligned write command
> [ 1150.735125] sd 3:0:0:0: [sdd] tag#8 CDB: Read(16) 88 00 00 00 00 00 53 44 55 00 00 00 00 80 00 00
> [ 1150.735127] blk_update_request: I/O error, dev sdd, sector 1396987136 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
> [ 1150.736651] ata4: EH complete
> [ 1155.401430] ata4.00: exception Emask 0x52 SAct 0x80800000 SErr 0x400c01 action 0x6 frozen
> [ 1155.404486] ata4.00: irq_stat 0x08000000, interface fatal error
> [ 1155.407528] ata4: SError: { RecovData Proto HostInt Handshk }
> [ 1155.410548] ata4.00: failed command: READ FPDMA QUEUED
> [ 1155.411882] ata4.00: cmd 60/40:b8:40:55:e4/00:00:66:00:00/40 tag 23 ncq dma 32768 in
> res 40/00:f8:00:56:e4/00:00:66:00:00/40 Emask 0x52 (ATA bus error)
> [ 1155.414526] ata4.00: status: { DRDY }
> [ 1155.415848] ata4.00: failed command: READ FPDMA QUEUED
> [ 1155.417185] ata4.00: cmd 60/80:f8:00:56:e4/00:00:66:00:00/40 tag 31 ncq dma 65536 in
> res 40/00:f8:00:56:e4/00:00:66:00:00/40 Emask 0x52 (ATA bus error)
> [ 1155.419904] ata4.00: status: { DRDY }
> [ 1155.421265] ata4: hard resetting link
> [ 1155.736222] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
> [ 1155.737557] ata4.00: configured for UDMA/133
> [ 1155.737569] sd 3:0:0:0: [sdd] tag#23 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
> [ 1155.737571] sd 3:0:0:0: [sdd] tag#23 Sense Key : Illegal Request [current]
> [ 1155.737574] sd 3:0:0:0: [sdd] tag#23 Add. Sense: Unaligned write command
> [ 1155.737577] sd 3:0:0:0: [sdd] tag#23 CDB: Read(16) 88 00 00 00 00 00 66 e4 55 40 00 00 00 40 00 00
> [ 1155.737580] blk_update_request: I/O error, dev sdd, sector 1726240064 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
> [ 1155.739201] sd 3:0:0:0: [sdd] tag#31 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
> [ 1155.739202] sd 3:0:0:0: [sdd] tag#31 Sense Key : Illegal Request [current]
> [ 1155.739204] sd 3:0:0:0: [sdd] tag#31 Add. Sense: Unaligned write command
> [ 1155.739205] sd 3:0:0:0: [sdd] tag#31 CDB: Read(16) 88 00 00 00 00 00 66 e4 56 00 00 00 00 80 00 00
> [ 1155.739207] blk_update_request: I/O error, dev sdd, sector 1726240256 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
> [ 1155.740801] ata4: EH complete
> [ 1155.825384] ata4: limiting SATA link speed to 3.0 Gbps
> [ 1155.825388] ata4.00: exception Emask 0x52 SAct 0x300000 SErr 0xc00 action 0x6 frozen
> [ 1155.827501] ata4.00: irq_stat 0x08000000, interface fatal error
> [ 1155.829637] ata4: SError: { Proto HostInt }
> [ 1155.829640] ata4.00: failed command: READ FPDMA QUEUED
> [ 1155.829645] ata4.00: cmd 60/40:a0:40:54:24/00:00:67:00:00/40 tag 20 ncq dma 32768 in
> res 40/00:a8:00:55:24/00:00:67:00:00/40 Emask 0x52 (ATA bus error)
> [ 1155.829646] ata4.00: status: { DRDY }
> [ 1155.829648] ata4.00: failed command: READ FPDMA QUEUED
> [ 1155.829652] ata4.00: cmd 60/80:a8:00:55:24/00:00:67:00:00/40 tag 21 ncq dma 65536 in
> res 40/00:a8:00:55:24/00:00:67:00:00/40 Emask 0x52 (ATA bus error)
> [ 1155.829653] ata4.00: status: { DRDY }
> [ 1155.829656] ata4: hard resetting link
> [ 1156.144287] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
> [ 1156.145684] ata4.00: configured for UDMA/133
> [ 1156.145695] sd 3:0:0:0: [sdd] tag#20 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
> [ 1156.145698] sd 3:0:0:0: [sdd] tag#20 Sense Key : Illegal Request [current]
> [ 1156.145700] sd 3:0:0:0: [sdd] tag#20 Add. Sense: Unaligned write command
> [ 1156.145702] sd 3:0:0:0: [sdd] tag#20 CDB: Read(16) 88 00 00 00 00 00 67 24 54 40 00 00 00 40 00 00
> [ 1156.145705] blk_update_request: I/O error, dev sdd, sector 1730434112 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
> [ 1156.147784] sd 3:0:0:0: [sdd] tag#21 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
> [ 1156.147785] sd 3:0:0:0: [sdd] tag#21 Sense Key : Illegal Request [current]
> [ 1156.147787] sd 3:0:0:0: [sdd] tag#21 Add. Sense: Unaligned write command
> [ 1156.147789] sd 3:0:0:0: [sdd] tag#21 CDB: Read(16) 88 00 00 00 00 00 67 24 55 00 00 00 00 80 00 00
> [ 1156.147791] blk_update_request: I/O error, dev sdd, sector 1730434304 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
> [ 1156.149854] ata4: EH complete
> --------------------------------------------------
What is the make and model of your motherboard? RAID HDD's?
How is the motherboard connected to the HDD's?
Please post the output of (redact serial number, etc., as desired):
# smartctl -x /dev/sdd
David
[toc] | [prev] | [next] | [standalone]
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2022-04-25 00:40 +0200 |
| Message-ID | <EfT3z-aXDi-7@gated-at.bofh.it> |
| In reply to | #247496 |
On Sun, 24 Apr 2022 14:07:14 -0700
David Christensen <dpchrist@holgerdanske.com> wrote:
> On 4/24/22 12:08, Charles Curley wrote:
> > I have three hard drives in a RAID 5 array.
>
>
> What is the make and model of your motherboard? RAID HDD's?
ASUS H97M-E
>
>
> How is the motherboard connected to the HDD's?
SATA. All hdds are on the motherboard, and the DVD drive is connected
via an expansion card:
04:00.0 SATA controller: JMicron Technology Corp. Device 0585 (prog-if 01 [AHCI 1.0])
Subsystem: JMicron Technology Corp. Device 0000
Flags: bus master, fast devsel, latency 0, IRQ 31
I/O ports at d200 [size=128]
I/O ports at d180 [size=128]
I/O ports at d100 [size=128]
I/O ports at d080 [size=128]
I/O ports at d000 [size=128]
Memory at f7c10000 (32-bit, non-prefetchable) [size=8K]
Expansion ROM at f7c00000 [disabled] [size=64K]
Capabilities: [80] Power Management version 3
Capabilities: [90] MSI: Enable+ Count=1/8 Maskable- 64bit+
Capabilities: [c0] Express Legacy Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [160] Power Budgeting <?>
Capabilities: [1b8] Latency Tolerance Reporting
Capabilities: [300] Secondary PCI Express
Capabilities: [900] L1 PM Substates
Kernel driver in use: ahci
Kernel modules: ahci
>
>
> Please post the output of (redact serial number, etc., as desired):
>
> # smartctl -x /dev/sdd
I did the short test at 12651 hours today after the error messages I
gave in the last email.
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.7.0-2-amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD40EFRX-68N32N0
Serial Number: WD-<redacted>
LU WWN Device Id: 5 0014ee 2bda92107
Firmware Version: 82.00A82
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun Apr 24 22:08:57 2022 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, frozen [SEC2]
Wt Cache Reorder: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (43680) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 463) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x303d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-K 200 200 051 - 0
3 Spin_Up_Time POS--K 168 166 021 - 6583
4 Start_Stop_Count -O--CK 100 100 000 - 41
5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
7 Seek_Error_Rate -OSR-K 100 253 000 - 0
9 Power_On_Hours -O--CK 083 083 000 - 12653
10 Spin_Retry_Count -O--CK 100 253 000 - 0
11 Calibration_Retry_Count -O--CK 100 253 000 - 0
12 Power_Cycle_Count -O--CK 100 100 000 - 41
192 Power-Off_Retract_Count -O--CK 200 200 000 - 13
193 Load_Cycle_Count -O--CK 198 198 000 - 7905
194 Temperature_Celsius -O---K 125 108 000 - 25
196 Reallocated_Event_Count -O--CK 200 200 000 - 0
197 Current_Pending_Sector -O--CK 200 200 000 - 0
198 Offline_Uncorrectable ----CK 200 200 000 - 0
199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0
200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 5 Comprehensive SMART error log
0x03 GPL R/O 6 Ext. Comprehensive SMART error log
0x04 GPL,SL R/O 8 Device Statistics log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa0-0xa7 GPL,SL VS 16 Device vendor specific log
0xa8-0xb6 GPL,SL VS 1 Device vendor specific log
0xb7 GPL,SL VS 56 Device vendor specific log
0xbd GPL,SL VS 1 Device vendor specific log
0xc0 GPL,SL VS 1 Device vendor specific log
0xc1 GPL VS 93 Device vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer
SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
No Errors Logged
SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 12651 -
# 2 Extended offline Completed without error 00% 10026 -
# 3 Extended offline Completed without error 00% 7 -
# 4 Short offline Completed without error 00% 0 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
SCT Status Version: 3
SCT Version (vendor specific): 258 (0x0102)
Device State: Active (0)
Current Temperature: 25 Celsius
Power Cycle Min/Max Temperature: 22/25 Celsius
Lifetime Min/Max Temperature: 19/42 Celsius
Under/Over Temperature Limit Count: 0/0
Vendor specific:
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 1 minute
Min/Max recommended Temperature: 0/65 Celsius
Min/Max Temperature Limit: -41/85 Celsius
Temperature History Size (Index): 478 (47)
Index Estimated Time Temperature Celsius
48 2022-04-24 14:11 36 *****************
... ..( 13 skipped). .. *****************
62 2022-04-24 14:25 36 *****************
63 2022-04-24 14:26 35 ****************
... ..( 11 skipped). .. ****************
75 2022-04-24 14:38 35 ****************
76 2022-04-24 14:39 34 ***************
... ..( 17 skipped). .. ***************
94 2022-04-24 14:57 34 ***************
95 2022-04-24 14:58 33 **************
... ..( 10 skipped). .. **************
106 2022-04-24 15:09 33 **************
107 2022-04-24 15:10 ? -
108 2022-04-24 15:11 22 ***
... ..( 2 skipped). .. ***
111 2022-04-24 15:14 22 ***
112 2022-04-24 15:15 23 ****
113 2022-04-24 15:16 23 ****
114 2022-04-24 15:17 23 ****
115 2022-04-24 15:18 24 *****
116 2022-04-24 15:19 24 *****
117 2022-04-24 15:20 24 *****
118 2022-04-24 15:21 25 ******
119 2022-04-24 15:22 25 ******
120 2022-04-24 15:23 30 ***********
... ..(130 skipped). .. ***********
251 2022-04-24 17:34 30 ***********
252 2022-04-24 17:35 31 ************
... ..( 21 skipped). .. ************
274 2022-04-24 17:57 31 ************
275 2022-04-24 17:58 32 *************
... ..( 15 skipped). .. *************
291 2022-04-24 18:14 32 *************
292 2022-04-24 18:15 33 **************
... ..( 32 skipped). .. **************
325 2022-04-24 18:48 33 **************
326 2022-04-24 18:49 32 *************
... ..( 12 skipped). .. *************
339 2022-04-24 19:02 32 *************
340 2022-04-24 19:03 33 **************
... ..( 7 skipped). .. **************
348 2022-04-24 19:11 33 **************
349 2022-04-24 19:12 32 *************
... ..( 29 skipped). .. *************
379 2022-04-24 19:42 32 *************
380 2022-04-24 19:43 31 ************
... ..( 19 skipped). .. ************
400 2022-04-24 20:03 31 ************
401 2022-04-24 20:04 32 *************
402 2022-04-24 20:05 ? -
403 2022-04-24 20:06 32 *************
... ..( 8 skipped). .. *************
412 2022-04-24 20:15 32 *************
413 2022-04-24 20:16 33 **************
414 2022-04-24 20:17 33 **************
415 2022-04-24 20:18 ? -
416 2022-04-24 20:19 31 ************
417 2022-04-24 20:20 31 ************
418 2022-04-24 20:21 31 ************
419 2022-04-24 20:22 ? -
420 2022-04-24 20:23 29 **********
421 2022-04-24 20:24 ? -
422 2022-04-24 20:25 29 **********
... ..( 4 skipped). .. **********
427 2022-04-24 20:30 29 **********
428 2022-04-24 20:31 30 ***********
... ..( 7 skipped). .. ***********
436 2022-04-24 20:39 30 ***********
437 2022-04-24 20:40 31 ************
... ..( 3 skipped). .. ************
441 2022-04-24 20:44 31 ************
442 2022-04-24 20:45 32 *************
... ..( 5 skipped). .. *************
448 2022-04-24 20:51 32 *************
449 2022-04-24 20:52 33 **************
... ..( 43 skipped). .. **************
15 2022-04-24 21:36 33 **************
16 2022-04-24 21:37 34 ***************
... ..( 16 skipped). .. ***************
33 2022-04-24 21:54 34 ***************
34 2022-04-24 21:55 35 ****************
... ..( 8 skipped). .. ****************
43 2022-04-24 22:04 35 ****************
44 2022-04-24 22:05 36 *****************
... ..( 2 skipped). .. *****************
47 2022-04-24 22:08 36 *****************
SCT Error Recovery Control:
Read: 70 (7.0 seconds)
Write: 70 (7.0 seconds)
Device Statistics (GP Log 0x04)
Page Offset Size Value Flags Description
0x01 ===== = = === == General Statistics (rev 1) ==
0x01 0x008 4 41 --- Lifetime Power-On Resets
0x01 0x010 4 12653 --- Power-on Hours
0x01 0x018 6 55709780708 --- Logical Sectors Written
0x01 0x020 6 103013781 --- Number of Write Commands
0x01 0x028 6 232196296506 --- Logical Sectors Read
0x01 0x030 6 1070400071 --- Number of Read Commands
0x01 0x038 6 2601127040 --- Date and Time TimeStamp
0x03 ===== = = === == Rotating Media Statistics (rev 1) ==
0x03 0x008 4 12634 --- Spindle Motor Power-on Hours
0x03 0x010 4 2345 --- Head Flying Hours
0x03 0x018 4 7919 --- Head Load Events
0x03 0x020 4 0 --- Number of Reallocated Logical Sectors
0x03 0x028 4 1 --- Read Recovery Attempts
0x03 0x030 4 0 --- Number of Mechanical Start Failures
0x03 0x038 4 0 --- Number of Realloc. Candidate Logical Sectors
0x03 0x040 4 13 --- Number of High Priority Unload Events
0x04 ===== = = === == General Errors Statistics (rev 1) ==
0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors
0x04 0x010 4 7 --- Resets Between Cmd Acceptance and Completion
0x05 ===== = = === == Temperature Statistics (rev 1) ==
0x05 0x008 1 25 --- Current Temperature
0x05 0x010 1 31 --- Average Short Term Temperature
0x05 0x018 1 31 --- Average Long Term Temperature
0x05 0x020 1 42 --- Highest Temperature
0x05 0x028 1 23 --- Lowest Temperature
0x05 0x030 1 38 --- Highest Average Short Term Temperature
0x05 0x038 1 27 --- Lowest Average Short Term Temperature
0x05 0x040 1 34 --- Highest Average Long Term Temperature
0x05 0x048 1 28 --- Lowest Average Long Term Temperature
0x05 0x050 4 0 --- Time in Over-Temperature
0x05 0x058 1 65 --- Specified Maximum Operating Temperature
0x05 0x060 4 0 --- Time in Under-Temperature
0x05 0x068 1 0 --- Specified Minimum Operating Temperature
0x06 ===== = = === == Transport Statistics (rev 1) ==
0x06 0x008 4 271 --- Number of Hardware Resets
0x06 0x010 4 138 --- Number of ASR Events
0x06 0x018 4 0 --- Number of Interface CRC Errors
|||_ C monitored condition met
||__ D supports DSN
|___ N normalized value
Pending Defects log (GP Log 0x0c) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 2 0 Command failed due to ICRC error
0x0002 2 0 R_ERR response for data FIS
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0005 2 0 R_ERR response for non-data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS
0x0008 2 0 Device-to-host non-data FIS retries
0x0009 2 3 Transition from drive PhyRdy to drive PhyNRdy
0x000a 2 4 Device-to-host register FISes sent due to a COMRESET
0x000b 2 0 CRC errors within host-to-device FIS
0x000d 2 0 Non-CRC errors within host-to-device FIS
0x000f 2 0 R_ERR response for host-to-device data FIS, CRC
0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC
0x8000 4 706 Vendor specific
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2022-04-25 07:50 +0200 |
| Message-ID | <EfZLH-b1Hi-7@gated-at.bofh.it> |
| In reply to | #247499 |
On 4/24/22 15:37, Charles Curley wrote: > On Sun, 24 Apr 2022 14:07:14 -0700 > David Christensen <dpchrist@holgerdanske.com> wrote: > >> On 4/24/22 12:08, Charles Curley wrote: >>> I have three hard drives in a RAID 5 array. >> >> >> What is the make and model of your motherboard? > > ASUS H97M-E I'd call that a multimedia desktop board: https://www.asus.com/us/supportonly/H97M-E/HelpDesk_Manual/ My experience with ASUS motherboards is limited to one, and it died sometime after I shorted the power supply with a 2.5" IDE HDD cable adapter. (So, the motherboard death was likely to be related.) >> RAID HDD's? I will assume all three HDD's are the same make and model, per smartctl(8) report below. >> How is the motherboard connected to the HDD's? > > SATA. All hdds are on the motherboard, What is on the other ports -- /dev/sda is optical? /dev/sdb and /dev/sdc are other two HDD's? SATA cables -- Color? Locking or non-locking connectors? Came with motherboard or aftermarket? If the latter, make and model? > and the DVD drive is connected via an expansion card: Okay. >> Please post the output of (redact serial number, etc., as desired): >> >> # smartctl -x /dev/sdd > > I did the short test at 12651 hours today after the error messages I > gave in the last email. > > > smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.7.0-2-amd64] (local build) > Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org > > === START OF INFORMATION SECTION === > Model Family: Western Digital Red > Device Model: WDC WD40EFRX-68N32N0 Western Digital Red Plus NAS hard drive: https://www.westerndigital.com/products/internal-drives/wd-red-plus-sata-3-5-hdd#WD10EFRX > SMART Extended Self-test Log Version: 1 (1 sectors) > Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error > # 1 Short offline Completed without error 00% 12651 - > # 2 Extended offline Completed without error 00% 10026 - You ran a short test two hours ago. You ran a long test 3 to 4 months ago. Please save all current SMART report(s). Please run long tests now on all three drives. Save all of the reports. Post the report(s) for any drive(s) with SMART failures and/or dmesg(1) errors. On 4/24/22 12:08, 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. What were the symptoms? Any more clues since then? So, Debian on the RAID 5? Anything in the M.2 socket? Do you have a power supply tester? If so, does the PSU test okay? If not, get one -- bad PSU's can cause all kinds of malfunctions, and can destroy hardware. Have you run memtest86+? David
[toc] | [prev] | [next] | [standalone]
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2022-04-25 17:40 +0200 |
| Message-ID | <Eg8YF-b7Bm-9@gated-at.bofh.it> |
| In reply to | #247509 |
On Sun, 24 Apr 2022 22:47:50 -0700
David Christensen <dpchrist@holgerdanske.com> wrote:
> I will assume all three HDD's are the same make and model, per
> smartctl(8) report below.
Nope. Two WD Reds, as the report indicates, but not bought at the same
time so likely to be different in detail. One Seagate Ironwolf.
> >> How is the motherboard connected to the HDD's?
> >
> > SATA. All hdds are on the motherboard,
>
>
> What is on the other ports -- /dev/sda is optical? /dev/sdb and
> /dev/sdc are other two HDD's?
Debian and finnix see things differently. On both. sdc and sdd are part
of the RAID array. On Debian, sda is the system drive: /, /home, /etc,
swap, /boot, etc.. sdb is part of the RAID array. Finnix swaps those
two.
>
>
> SATA cables -- Color? Locking or non-locking connectors? Came
> with motherboard or aftermarket? If the latter, make and model?
All black, two red. The black ones came with the computer. The red ones
are aftermarket, Alchemy SATA3 30 cm. BFA-MSC-SATA330RK-RP. All lock.
> Please run long tests now on all three drives. Save all of the
> reports. Post the report(s) for any drive(s) with SMART failures
> and/or dmesg(1) errors.
Long tests run about 10 hours. I did one overnight on sdd, and it
reported no errors. No dmesg errors sine the ones I reported in the
original email.
--------------------------------------------------
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.7.0-2-amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD40EFRX-68N32N0
Serial Number: WD-<redacted>
LU WWN Device Id: 5 0014ee 2bda92107
Firmware Version: 82.00A82
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Mon Apr 25 15:02:26 2022 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (43680) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 463) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x303d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 168 166 021 Pre-fail Always - 6583
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 41
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 083 083 000 Old_age Always - 12670
10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 41
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 13
193 Load_Cycle_Count 0x0032 198 198 000 Old_age Always - 7908
194 Temperature_Celsius 0x0022 119 108 000 Old_age Always - 31
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 12661 -
# 2 Short offline Completed without error 00% 12651 -
# 3 Extended offline Completed without error 00% 10026 -
# 4 Extended offline Completed without error 00% 7 -
# 5 Short offline Completed without error 00% 0 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
--------------------------------------------------
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
[toc] | [prev] | [next] | [standalone]
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2022-04-25 02:20 +0200 |
| Message-ID | <EfUCl-aYEy-3@gated-at.bofh.it> |
| In reply to | #247491 |
On Sun, 24 Apr 2022 13:08:03 -0600
Charles Curley <charlescurley@charlescurley.com> wrote:
> I have three hard drives in a RAID 5 array.
RAID has not yet failed the errant drive. Just now, via ssh into finnix:
root@0:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
md127 : active (auto-read-only) raid5 sda1[3] sdc1[0] sdd1[1]
7813768832 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU]
bitmap: 0/30 pages [0KB], 65536KB chunk
unused devices: <none>
root@0:~#
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2022-04-25 08:00 +0200 |
| Message-ID | <EfZVn-b1Kn-1@gated-at.bofh.it> |
| In reply to | #247501 |
On 4/24/22 17:10, Charles Curley wrote: > On Sun, 24 Apr 2022 13:08:03 -0600 > Charles Curley <charlescurley@charlescurley.com> wrote: > >> I have three hard drives in a RAID 5 array. > > RAID has not yet failed the errant drive. Just now, via ssh into finnix: > > root@0:~# cat /proc/mdstat > Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10] > md127 : active (auto-read-only) raid5 sda1[3] sdc1[0] sdd1[1] > 7813768832 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU] > bitmap: 0/30 pages [0KB], 65536KB chunk > > unused devices: <none> Okay. So, RAID 5 HDD's are sda, sdc, and sdd, and optical is sdb? You do have a backup of your Debian system configuration files and your data, right? David
[toc] | [prev] | [next] | [standalone]
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2022-04-25 16:20 +0200 |
| Message-ID | <Eg7Jf-b6TA-9@gated-at.bofh.it> |
| In reply to | #247510 |
On Sun, 24 Apr 2022 22:52:15 -0700 David Christensen <dpchrist@holgerdanske.com> wrote: > So, RAID 5 HDD's are sda, sdc, and sdd, and optical is sdb? Optical is sr0. sda is an SSD with all the system, /home, etc. md0 is mounted at /crc. > > > You do have a backup of your Debian system configuration files and > your data, right? Lots of them. https://charlescurley.com/blog/posts/2019/Nov/02/backups-on-linux/ -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2022-04-26 00:00 +0200 |
| Message-ID | <EgeUp-bb7O-9@gated-at.bofh.it> |
| In reply to | #247519 |
On 4/25/22 07:18, Charles Curley wrote:
> On Sun, 24 Apr 2022 22:52:15 -0700
> David Christensen <dpchrist@holgerdanske.com> wrote:
>
>> So, RAID 5 HDD's are sda, sdc, and sdd, and optical is sdb?
>
> Optical is sr0.
Interesting. (Must be the SATA controller expansion card?)
> sda is an SSD with all the system, /home, etc.
Good.
I would run a long SMART test on it now.
> md0 is
> mounted at /crc.
Okay.
>> You do have a backup of your Debian system configuration files and
>> your data, right?
>
> Lots of them.
> https://charlescurley.com/blog/posts/2019/Nov/02/backups-on-linux/
Good.
On 4/25/22 08:33, Charles Curley wrote:
> On Sun, 24 Apr 2022 22:47:50 -0700
> David Christensen <dpchrist@holgerdanske.com> wrote:
>
>> I will assume all three HDD's are the same make and model, per
>> smartctl(8) report below.
>
> Nope. Two WD Reds, as the report indicates, but not bought at the same
> time so likely to be different in detail. One Seagate Ironwolf.
Okay.
>>>> How is the motherboard connected to the HDD's?
> Debian and finnix see things differently. On both. sdc and sdd are part
> of the RAID array. On Debian, sda is the system drive: /, /home, /etc,
> swap, /boot, etc.. sdb is part of the RAID array. Finnix swaps those
> two.
Okay.
Rather than a Live Linux distribution for troubleshooting, I install
Debian onto a USB flash drive (SanDisk Ultra Fit USB 3.0 16 GB). I
keep it updated/ upgraded, and install whatever tools I want. You might
want to make one that matches your Debian instance -- that should
eliminate the device enumeration differences.
>> SATA cables -- Color? Locking or non-locking connectors? Came
>> with motherboard or aftermarket? If the latter, make and model?
>
> All black, two red. The black ones came with the computer. The red ones
> are aftermarket, Alchemy SATA3 30 cm. BFA-MSC-SATA330RK-RP. All lock.
https://www.frozencpu.com/products/14060/cab-572/Bitfenix_Alchemy_Multisleeve_SATA_30_Cable_-_30cm_-_Red_BFA-MSC-SATA330RK-RP.html
Those Alchemy SATA cables look good. Assuming you like them, I would
replace the factory cables with new Alchemy cables.
>> Please run long tests now on all three drives. Save all of the
>> reports. Post the report(s) for any drive(s) with SMART failures
>> and/or dmesg(1) errors.
>
> Long tests run about 10 hours. I did one overnight on sdd, and it
> reported no errors. No dmesg errors sine the ones I reported in the
> original email.
I launch SMART tests on all of the drives at the same time. The
microcontroller in each drive runs the test for that drive
independently, so it is okay to run all the tests concurrently.
> smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.7.0-2-amd64] (local build)
> Copyright (C) 2002-19, Bruce Allen, Christian Franke,
www.smartmontools.org
>
> === START OF INFORMATION SECTION ===
> Model Family: Western Digital Red
> Device Model: WDC WD40EFRX-68N32N0
> Serial Number: WD-<redacted>
> LU WWN Device Id: 5 0014ee 2bda92107
> Firmware Version: 82.00A82
> User Capacity: 4,000,787,030,016 bytes [4.00 TB]
> Sector Sizes: 512 bytes logical, 4096 bytes physical
> Rotation Rate: 5400 rpm
> Form Factor: 3.5 inches
> Device is: In smartctl database [for details use: -P show]
> ATA Version is: ACS-3 T13/2161-D revision 5
> SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
> Local Time is: Mon Apr 25 15:02:26 2022 UTC
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
>
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED
>
> General SMART Values:
> Offline data collection status: (0x82) Offline data collection activity
> was completed without error.
> Auto Offline Data Collection: Enabled.
> Self-test execution status: ( 0) The previous self-test
routine completed
> without error or no self-test has ever
> been run.
> Total time to complete Offline
> data collection: (43680) seconds.
> Offline data collection
> capabilities: (0x7b) SMART execute Offline immediate.
> Auto Offline data collection on/off support.
> Suspend Offline collection upon new
> command.
> Offline surface scan supported.
> Self-test supported.
> Conveyance Self-test supported.
> Selective Self-test supported.
> SMART capabilities: (0x0003) Saves SMART data before entering
> power-saving mode.
> Supports SMART auto save timer.
> Error logging capability: (0x01) Error logging supported.
> General Purpose Logging supported.
> Short self-test routine
> recommended polling time: ( 2) minutes.
> Extended self-test routine
> recommended polling time: ( 463) minutes.
> Conveyance self-test routine
> recommended polling time: ( 5) minutes.
> SCT capabilities: (0x303d) SCT Status supported.
> SCT Error Recovery Control supported.
> SCT Feature Control supported.
> SCT Data Table supported.
>
> SMART Attributes Data Structure revision number: 16
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE
> 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail
Always - 0
> 3 Spin_Up_Time 0x0027 168 166 021 Pre-fail
Always - 6583
> 4 Start_Stop_Count 0x0032 100 100 000 Old_age
Always - 41
> 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail
Always - 0
> 7 Seek_Error_Rate 0x002e 200 200 000 Old_age
Always - 0
> 9 Power_On_Hours 0x0032 083 083 000 Old_age
Always - 12670
> 10 Spin_Retry_Count 0x0032 100 253 000 Old_age
Always - 0
> 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age
Always - 0
> 12 Power_Cycle_Count 0x0032 100 100 000 Old_age
Always - 41
> 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age
Always - 13
> 193 Load_Cycle_Count 0x0032 198 198 000 Old_age
Always - 7908
> 194 Temperature_Celsius 0x0022 119 108 000 Old_age
Always - 31
> 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age
Always - 0
> 197 Current_Pending_Sector 0x0032 200 200 000 Old_age
Always - 0
> 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age
Offline - 0
> 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age
Always - 0
> 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age
Offline - 0
>
> SMART Error Log Version: 1
> No Errors Logged
>
> SMART Self-test log structure revision number 1
> Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
> # 1 Extended offline Completed without error 00% 12661
-
> # 2 Short offline Completed without error 00% 12651
-
> # 3 Extended offline Completed without error 00% 10026
-
> # 4 Extended offline Completed without error 00% 7
-
> # 5 Short offline Completed without error 00% 0
-
>
> SMART Selective self-test log data structure revision number 1
> SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
> 1 0 0 Not_testing
> 2 0 0 Not_testing
> 3 0 0 Not_testing
> 4 0 0 Not_testing
> 5 0 0 Not_testing
> Selective self-test flags (0x0):
> After scanning selected spans, do NOT read-scan remainder of disk.
> If Selective self-test is pending on power-up, resume after 0 minute
delay.
That drive looks good to me.
I still don't see the source of the original dmesg(1) errors. I would:
1. Power down and vacuum the inside of the case.
2. Carefully wiggle and then disconnect all PSU cables and connectors.
Feel for any poor connections.
3. Carefully wiggle and then disconnect all SATA cables and connectors,
as above.
4. Test the PSU with a hardware tester.
5. Vacuum some more.
6. Reconnect the PSU and SATA cables. Wiggle each connection, as
above. Dress cables.
7. Boot memtest86+ and run overnight or longer.
If and when you have convinced yourself that all of the hardware is
good, then software is what remains.
Did you figure out what was preventing Debian from booting? Is the
Debian instance fixed?
David
[toc] | [prev] | [next] | [standalone]
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2022-04-27 00:10 +0200 |
| Message-ID | <EgBxD-bpts-7@gated-at.bofh.it> |
| In reply to | #247551 |
Update. I had a friend with a power supply checker check the power supply. The +12 volt line is running at 11.5v, barely within spec. Fishy, but livable for the nonce. I had been running Finnix as Debian wouldn't boot. I pulled all the external USB lines except for a 3.5" external floppy disk drive. The USB problem that started all this went away, i.e. I stopped getting error messages in dmesg. I rebooted Finnix, and did not see the error message. Also, the boot speed was back to normal. An hour and a half ago I booted to the installed Debian system, and that now runs fine. I see no error messages for USB or for any of the drives. RAID looks nominal. I will monitor. The next step will be to add back external USB lines, one at a time, and see if the problem re-appears. It may have been something as simple as mild corrosion on a connector. Meanwhile, I did long tests on the hard drives and SSD; all passed. I've seen no hard drive error messages all day. On Mon, 25 Apr 2022 14:56:50 -0700 David Christensen <dpchrist@holgerdanske.com> wrote: > On 4/25/22 07:18, Charles Curley wrote: > > On Sun, 24 Apr 2022 22:52:15 -0700 > > David Christensen <dpchrist@holgerdanske.com> wrote: > > > >> So, RAID 5 HDD's are sda, sdc, and sdd, and optical is sdb? > > > > Optical is sr0. > > > Interesting. (Must be the SATA controller expansion card?) Yup. > > > Debian and finnix see things differently. On both. sdc and sdd are > > part of the RAID array. On Debian, sda is the system drive: /, > > /home, /etc, swap, /boot, etc.. sdb is part of the RAID array. > > Finnix swaps those two. > > > Okay. > > > Rather than a Live Linux distribution for troubleshooting, I install > Debian onto a USB flash drive (SanDisk Ultra Fit USB 3.0 16 GB). I > keep it updated/ upgraded, and install whatever tools I want. You > might want to make one that matches your Debian instance -- that > should eliminate the device enumeration differences. Would that have solved this transposition? I suspect that Linux sets up the boot drive as sda regardless of how the firmware sees things. But otherwise a good idea, if a bit of work. > > > >> SATA cables -- Color? Locking or non-locking connectors? Came > >> with motherboard or aftermarket? If the latter, make and model? > > > > All black, two red. The black ones came with the computer. The red > > ones are aftermarket, Alchemy SATA3 30 cm. BFA-MSC-SATA330RK-RP. > > All lock. > > > https://www.frozencpu.com/products/14060/cab-572/Bitfenix_Alchemy_Multisleeve_SATA_30_Cable_-_30cm_-_Red_BFA-MSC-SATA330RK-RP.html > > > Those Alchemy SATA cables look good. Assuming you like them, I would > replace the factory cables with new Alchemy cables. I'll keep that in mind. I have one spare, so I can swap that in in pretty quick order if need be. > > > >> Please run long tests now on all three drives. Save all of the > >> reports. Post the report(s) for any drive(s) with SMART failures > >> and/or dmesg(1) errors. > > > > Long tests run about 10 hours. I did one overnight on sdd, and it > > reported no errors. No dmesg errors sine the ones I reported in the > > original email. > > > I launch SMART tests on all of the drives at the same time. The > microcontroller in each drive runs the test for that drive > independently, so it is okay to run all the tests concurrently. I did figure that out, and tested the three remaining drives. All tested with no errors. > > > I still don't see the source of the original dmesg(1) errors. I > would: I've done some of these. But as I am not seeing any more hard drive issues, I'm not going to spend any more time on the rest. > > 7. Boot memtest86+ and run overnight or longer. Interestingly enough, memtest86 locks up right at the 4096 MB mark. It also completely refuses to run on another system I have here. I'm going to do some further testing, then report what I see in a new thread. > > > If and when you have convinced yourself that all of the hardware is > good, then software is what remains. Yup. > > > Did you figure out what was preventing Debian from booting? Is the > Debian instance fixed? I think so; see above. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2022-04-27 04:10 +0200 |
| Message-ID | <EgFhT-brN1-1@gated-at.bofh.it> |
| In reply to | #247586 |
On 4/26/22 15:04, Charles Curley wrote: <top post moved to bottom> > On Mon, 25 Apr 2022 14:56:50 -0700 David Christensen wrote: >> On 4/25/22 07:18, Charles Curley wrote: >>> On Sun, 24 Apr 2022 22:52:15 -0700 David Christensen wrote: >> Rather than a Live Linux distribution for troubleshooting, I install >> Debian onto a USB flash drive (SanDisk Ultra Fit USB 3.0 16 GB). I >> keep it updated/ upgraded, and install whatever tools I want. You >> might want to make one that matches your Debian instance -- that >> should eliminate the device enumeration differences. > > Would that have solved this transposition? I would expect two matching Debian instances would enumerate the same drives in the same order on the same machine, but... > I suspect that Linux sets up > the boot drive as sda regardless of how the firmware sees things. I have seen examples to the contrary. When installing, I make sure the target device is /dev/sda -- installing to /dev/sdb, etc., is a recipe for future problems. > But otherwise a good idea, if a bit of work. A complete Debian instance on a USB flash drive is an invaluable tool, and well worth the time to create and maintain. >> Those Alchemy SATA cables look good. Assuming you like them, I would >> replace the factory cables with new Alchemy cables. > > I'll keep that in mind. I have one spare, so I can swap that in in > pretty quick order if need be. I would order more and make everything match. > I did figure that out, and tested the three remaining drives. All > tested with no errors. Good. > I've done some of these. But as I am not seeing any more hard drive > issues, I'm not going to spend any more time on the rest. Agreed. >> 7. Boot memtest86+ and run overnight or longer. > > Interestingly enough, memtest86 locks up right at the 4096 MB mark. It > also completely refuses to run on another system I have here. I'm going > to do some further testing, then report what I see in a new thread. If you are certain your memtest86+ tool is good, then that is a significant finding. I would download a current copy, burn it to USB, and try again. >> Did you figure out what was preventing Debian from booting? Is the >> Debian instance fixed? > Update. I had a friend with a power supply checker check the power > supply. The +12 volt line is running at 11.5v, barely within spec. > Fishy, but livable for the nonce. > > I had been running Finnix as Debian wouldn't boot. I pulled all the > external USB lines except for a 3.5" external floppy disk drive. The > USB problem that started all this went away, i.e. I stopped getting > error messages in dmesg. I rebooted Finnix, and did not see the error > message. Also, the boot speed was back to normal. > > An hour and a half ago I booted to the installed Debian system, and > that now runs fine. I see no error messages for USB or for any of the > drives. RAID looks nominal. I will monitor. > > The next step will be to add back external USB lines, one at a time, > and see if the problem re-appears. It may have been something as simple > as mild corrosion on a connector. What is the make and model of the PSU? Have you done a power budget calculation? I wonder if your PC is pushing the PSU to the limit, and the USB devices push it over? A weak PSU could cause memory errors, which will cause strange malfunctions. Beware of chasing misleading symptoms. If you can afford a spare PSU, A/B testing could be revealing. David
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web