Got the dreaded Red Cross on a drive today.  Here is my diagnostics report I grabbed before I rebooted.  I've read that this is typically a cable error, so I swapped cables on this drive but the red X is still there.  Any pointers?

hyrule-diagnostics-20220627-1046.zip

I also tried swapping SATA ports with a drive that was working.  It still has a Red Cross.

On mobile now so can't look at Diagnostics yet. 

 

The drive will stay disabled until rebuilt because it is not in sync with the array 

Ah, got it.  Ok.  Hopefully the diags help then.  I searched through them for "disk5" (the disk with the issue), and ERROR, and couldn't find much.  There are some memory errors I've had for a while and just never got around to fixing, but im fairly certain its unrelated.

36 minutes ago, Linkshot said:

memory errors I've had for a while and just never got around to fixing

You shouldn't even attempt to run any computer unless the RAM is working perfectly. Everything goes through RAM, all OS and other executable code, your data, everything. The CPU can't even do anything with anything until it is loaded into RAM.

 

Builtin memtest won't work with ECC memory, you will have to download the official memtest86.

 

Do this before anything else.

Also, those memory issues have spammed syslog, nothing in diagnostics from before that, so can't really see what happened to disable the disk.

 

Disabled/emulated disk5 was sde but disconnected and reconnected as sdl. SMART report for sdl looks OK, and emulated disk5 is mounted. So you should be good to rebuild the disk to itself after fixing your memory issue, and checking all connections.

 

 

Thanks.  I'll just find the fault RAM and remove it for now.  I can always add more later.  Would you recommend running an extended SMART test first before rebuilding the disk?  Any other ways to see why it might have disconnected?

1 hour ago, Linkshot said:

running an extended SMART test first before rebuilding the disk?

Couldn't hurt