A couple of weeks ago I shut down to clean the server.  When I turned it back on I had an issue with Disk 2.  The message was: "Unmountable : No file system."  I collected a log then, which I can upload if needed.  I ended up finding in the documentation a way to rebuild the file system and it worked. Everything was functioning normally.  A couple of days ago I was transferring a file to the array and it failed.  When I pulled up the Unraid UI, it now shows: "Device is disabled, contents emulated." I am going to replace all my SATA cables, check my SATA controller is seated, etc.  I am hoping that someone can provide some insight into why this may be happening, and what I might do to fix it.  Also, when I tried to run a parity check (before the drive error messages) it said it will take 200 days and the speed is like 50 kbps.  Any help is greatly appreciated.  Thank you in advance.

 

P.S. - The diagnostics I attached are the most recent, but I have the one from when it had the "Unmountable : No file system." issue.

 

 

croweflix-diagnostics-20241017-1212.zip

Logs are filled with these:

 

Oct 17 07:00:01 CroweFlix kernel: sd 1:0:0:0: [sde] tag#1588 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 bd c0 00 00 00 08 00 00
Oct 17 07:00:01 CroweFlix kernel: critical target error, dev sde, sector 7814036928 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Oct 17 07:00:01 CroweFlix kernel: sd 1:0:0:0: [sde] tag#1589 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Oct 17 07:00:01 CroweFlix kernel: sd 1:0:0:0: [sde] tag#1589 Sense Key : 0x4 [current] 
Oct 17 07:00:01 CroweFlix kernel: sd 1:0:0:0: [sde] tag#1589 ASC=0x44 ASCQ=0x0 
Oct 17 07:00:01 CroweFlix kernel: sd 1:0:0:0: [sde] tag#1589 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 bd c0 00 00 00 01 00 00

 

Since it rotated can't even see which disk it was, if you know, check/replace cables for that disk and post new diags after array start, if you don't reboot to clear the logs and post new diags after array start.

On 10/17/2024 at 12:27 PM, JorgeB said:

Logs are filled with these:

 

Oct 17 07:00:01 CroweFlix kernel: sd 1:0:0:0: [sde] tag#1588 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 bd c0 00 00 00 08 00 00
Oct 17 07:00:01 CroweFlix kernel: critical target error, dev sde, sector 7814036928 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Oct 17 07:00:01 CroweFlix kernel: sd 1:0:0:0: [sde] tag#1589 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Oct 17 07:00:01 CroweFlix kernel: sd 1:0:0:0: [sde] tag#1589 Sense Key : 0x4 [current] 
Oct 17 07:00:01 CroweFlix kernel: sd 1:0:0:0: [sde] tag#1589 ASC=0x44 ASCQ=0x0 
Oct 17 07:00:01 CroweFlix kernel: sd 1:0:0:0: [sde] tag#1589 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 bd c0 00 00 00 01 00 00

 

Since it rotated can't even see which disk it was, if you know, check/replace cables for that disk and post new diags after array start, if you don't reboot to clear the logs and post new diags after array start.

Ok.  It took a couple of days but I was finally able to get to it.  I'm not sure why but only one of my drives was running through the SATA controller.  Now they are all running through the SATA controller.  The drive is no longer "Missing", but it does show "Unmountable: Unsupported or no file system" again.  I need to first rebuild the file system, correct?  Here is the log I collected after moving the other two drives to the SATA Controller.

croweflix-diagnostics-20241020-1306.zip

1 hour ago, Billy Pilgrim said:

I need to first rebuild the file system, correct? 

No - you will need to run a check filesystem to try and repair it.    A rebuild would result in the same corrupt file system.

2 hours ago, itimpi said:

No - you will need to run a check filesystem to try and repair it.    A rebuild would result in the same corrupt file system.

Sorry, I used the wrong terminology, but that's what I meant. The check worked. It is up and running. Now to see if it will run a parity in a reasonable amount of time.