Crashed again this morning, this time it took down Disk 1. Is there information somewhere that can tell me why the disk was disabled?

It's the second time this has happened to that disk since I replaced it. I tried running an extended self-test, but it stops before completing without errors

birdskeep-diagnostics-20241023-0900.zip

Edited October 23, 20241 yr by TheBird956

I just tried running a sort self-test and it stopped. Now the attributes page just says this

This might have something to do with it...

 

Oct 23 09:04:16 BirdsKeep kernel: ata4: SATA link down (SStatus 0 SControl 300)
Oct 23 09:04:17 BirdsKeep kernel: ata4: SATA link down (SStatus 0 SControl 300)
Oct 23 09:04:17 BirdsKeep kernel: ata4: limiting SATA link speed to <unknown>
Oct 23 09:04:20 BirdsKeep kernel: ata4: SATA link down (SStatus 0 SControl 3F0)
Oct 23 09:04:20 BirdsKeep kernel: ata4.00: disable device
Oct 23 09:04:20 BirdsKeep kernel: usb 1-2.3: USB disconnect, device number 78
Oct 23 09:04:20 BirdsKeep kernel: usb 1-2.3: new low-speed USB device number 79 using xhci_hcd
Oct 23 09:04:21 BirdsKeep kernel: hid-generic 0003:09AE:2012.0137: hiddev96,hidraw1: USB HID v1.10 Device [Tripp Lite  Tripp Lite UPS ] on usb-0000:00:14.0-2.3/input0
Oct 23 09:04:21 BirdsKeep kernel: ata4: SATA link down (SStatus 0 SControl 300)
Oct 23 09:04:21 BirdsKeep kernel: ata4.00: detaching (SCSI 4:0:0:0)
Oct 23 09:04:21 BirdsKeep kernel: sd 4:0:0:0: [sde] Synchronizing SCSI cache
Oct 23 09:04:21 BirdsKeep kernel: sd 4:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK
Oct 23 09:04:22 BirdsKeep kernel: ata4: limiting SATA link speed to 1.5 Gbps
Oct 23 09:04:27 BirdsKeep kernel: ata4: link is slow to respond, please be patient (ready=0)
Oct 23 09:04:28 BirdsKeep kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Oct 23 09:04:28 BirdsKeep kernel: ata4.00: ATA-10: WDC WD80EFPX-68C4ZN0, 81.00A81, max UDMA/133
Oct 23 09:04:28 BirdsKeep kernel: ata4.00: 15628053168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Oct 23 09:04:28 BirdsKeep kernel: ata4.00: Features: NCQ-prio
Oct 23 09:04:28 BirdsKeep kernel: ata4.00: configured for UDMA/133
Oct 23 09:04:28 BirdsKeep kernel: scsi 4:0:0:0: Direct-Access     ATA      WDC WD80EFPX-68C 0A81 PQ: 0 ANSI: 5
Oct 23 09:04:28 BirdsKeep kernel: sd 4:0:0:0: Attached scsi generic sg4 type 0
Oct 23 09:04:28 BirdsKeep kernel: sd 4:0:0:0: [sdk] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
Oct 23 09:04:28 BirdsKeep kernel: sd 4:0:0:0: [sdk] 4096-byte physical blocks
Oct 23 09:04:28 BirdsKeep kernel: sd 4:0:0:0: [sdk] Write Protect is off
Oct 23 09:04:28 BirdsKeep kernel: sd 4:0:0:0: [sdk] Mode Sense: 00 3a 00 00
Oct 23 09:04:28 BirdsKeep kernel: sd 4:0:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct 23 09:04:28 BirdsKeep kernel: sd 4:0:0:0: [sdk] Preferred minimum I/O size 4096 bytes
Oct 23 09:04:28 BirdsKeep kernel: sdk: sdk1
Oct 23 09:04:28 BirdsKeep kernel: sd 4:0:0:0: [sdk] Attached SCSI disk
Oct 23 09:04:29 BirdsKeep unassigned.devices: Disk with ID 'WDC_WD80EFPX-68C4ZN0_WD-RD04BPDE (dev1)' is not set to auto mount.

 

That's not in the diags, but it looks like a power/connection issue.

Yeah it happened after I generated the file

Here's a new one

birdskeep-diagnostics-20241023-0911.zip

Could this issue cause/contribute to the crashes I am seeing?

Extremely unlikely that a disk dropping would cause Unraid to crash

Someone on the LTT forums suggested removing one of the RAM stick and see what happens.

 

The first RAM made it crash 3 times in 6 hours. With the second, only 1 crash since the 26th.

 

I'll continue testing that for a few more days and do a few more swaps to confirm.

So here's a final update.

 

All my issues were caused by a failing PSU. The server crashed in the same way as before, but that time it did not boot back up. The fans would "twitch" when powering on (had to toggle the PSU switch before) but nothing else. I was able to use a spare PSU to confirm that was the issue before buying a new power supply.

 

It has now been almost 20 days since the last crash, with no sign of issues.

 

Thank you all for your help resolving this!

I'm running into the same general symptoms and issue (random crashing without anything useful in the syslogs - could be hours apart, days, or weeks)... Started happening out of the blue again about a week or two ago. I had added a new docker and turned off another, but other than that very few changes. Of course I tried disabling the new docker but that didn't make a difference.

I already replaced the PSU and it made no difference. About a year ago, I was having the same issue, which is when I replaced the PSU but since that wasn't it, I also tweaked some BIOS settings to force the AMD CPU to not have c-states, or power idle issues, etc. I also updated the BIOS, and put in another fan for the room to pull in some cooler air. The issue went away after a number of changes but I know it crashed after the PSU swap.