sexyj

Perhaps there's some compatibility issue with the board when running on 2 x 2008 controller. Took the Pike 2008 out and plugged in another standalone LSI card, same issue. Ended up taking all the stand alone card out and just plugged in the Pike. No problem with it... Very strange issue.

So I updated both controller's fw. For some reason one controller is no longer detecting the drives. Doing some research on it, it indicate it's the cable (forward/reverse) breakout cable. But the cable was obviously working prior to the upgrade. The controller in question is a PIKE 2008, current status in the Controller BIOS https://prnt.sc/JlKC8xYdfiiL Is there anything you can think of? Edit: Problem solved with the controller not being found. Turns out the sas2flash -listall and the syslog order is reverse. Anyway. The problem with the drive changing name still persists after the FW upgrades. I actually have swapped the cable before... Very weird. Edit 2: Upload the latest diag after fixing the controllers fs1-diagnostics-20221006-1827.zip

Whenver I'm starting a new array, the process is crashing and tells me the drive dev name changed Oct 6 06:14:26 FS1 emhttpd: error: hotplug_devices, 1730: No medium found (123): Error: tagged device WDC_WD40EZAZ-19SF3B0_WD-WX42D51N5035 was (sdi) is now (sdn) Anyway one know if there is some settings I can set? Using 2 x SAS2008 controller fs1-diagnostics-20221006-1032.zip

Lowered the array size from 30 to 15... no error so far.

Had a new array without disk 12 in. Then when I try to stop the array during parity, I'm getting the following sdp is a SMART failed drive connected to the server but not mounted.

So if I don't have both disk 9 and 12 in the array, no read error. Spoke too soon. Now disk 6 is having read error. PSU issue?

- I bought 3 new disks to replace the ones that had smart error. - I have 2 out of 3 new disks in Slot 9 and 12. - Create a new Array under Tools -> New config. - When I go to start the array, in the logs I'm getting the following. and after a hard reboot I would get disk 9 read error. I'm fairly convinced that there is some sort of hardware issue with the controller ? Any thoughts?

Rebuilt the array with a new drive and the drive slot is still disabled. Attached the diag fs1-diagnostics-20220503-1354.zip

So another drive (completely healthy according to SMART) just got disabled... Disk 9 disabled * healthy Going to replace it once more with another disk.

I'm rebuilding the array with a new drive replacing the questionable drive. Will see in a few weeks if it happens again

I am having this issue where one of the drive in the array after a few weeks will get disabled. This can only be fixed by resetting the array config and let unraid rebuild the parity data. I have swapped the raid card, the sata cable that is connected from the backpane to the controller. In the syslog I'm seeing on the disabled drive Mar 26 03:16:33 FS1 kernel: blk_update_request: critical target error, dev sdk, sector 1954442736 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0 Mar 26 03:16:33 FS1 kernel: md: disk11 write error, sector=1954442672 Mar 26 03:16:33 FS1 kernel: blk_update_request: critical target error, dev sdk, sector 3907028992 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Mar 26 03:16:33 FS1 kernel: Buffer I/O error on dev sdk, logical block 488378624, async page read Mar 26 03:16:33 FS1 kernel: blk_update_request: critical target error, dev sdk, sector 1302466384 op 0x1:(WRITE) flags 0x0 phys_seg 12 prio class 0 Mar 26 03:16:33 FS1 kernel: md: disk11 write error, sector=1302466320 Mar 26 03:16:33 FS1 kernel: md: disk11 write error, sector=1302466328 Mar 26 03:16:33 FS1 kernel: md: disk11 write error, sector=1302466336 Mar 26 03:16:33 FS1 kernel: md: disk11 write error, sector=1302466344 Mar 26 03:16:33 FS1 kernel: md: disk11 write error, sector=1302466352 Mar 26 03:16:33 FS1 kernel: md: disk11 write error, sector=1302466360 Mar 26 03:16:33 FS1 kernel: md: disk11 write error, sector=1302466368 Mar 26 03:16:33 FS1 kernel: md: disk11 write error, sector=1302466376 Mar 26 03:16:33 FS1 kernel: md: disk11 write error, sector=1302466384 Mar 26 03:16:33 FS1 kernel: md: disk11 write error, sector=1302466392 Mar 26 03:16:33 FS1 kernel: md: disk11 write error, sector=1302466400 Mar 26 03:16:33 FS1 kernel: md: disk11 write error, sector=1302466408 No smart error on the drive. What is the likely culprit here?

Tried troubleshooting the issue by turning all other dockers and VM off and only PMS on. Seems like the media scanning for plex is killing the server. This is the top at the time of crash.

I can't seem to figure out why the PMS docker is crashing my server when it runs the maintenance task each night. All of my drives are in good condition, swapped out all the bad ones with SMART error. Hoping that would fix the problem, but it continues. I have 4 other docker images running and 2 VM's running on the server. It's only when the "Scheduled Tasks" starts for PMS then the server freeze altogether. PMS stream media without any issue or crashing. Any idea where I should be looking at? Top before the server crashed syslog.txt

Can't seem to figure this out. Thought I bought proper cables. Backplane - 80H103215-013 Card - LSI SAS3041XL-S Bought SFF-8087 forward breakout and no drives are detected. Read this article https://forums.unraid.net/topic/6723-sas-to-sata-cables-forward-or-reverse-which-where-why/ and forward breakout seems like it is what I need. Tried plugging the cable into the motherboards sata port as well. No go.

The only USB plugged in is the unraid usb.