Hey, newbie to UnRaid and spent the last few weeks setting up my Dell RX730d and learning. Got all the Arrs and things seemed to be settling in nicely. Wanted to get more insight to the system and installed Scrutiny. Immediately lost both parity drives, tried to uninstall Scrutiny but it gave an execution error. I thought restarting docker would fix this but Docker would not restart saying missing path and yes, the mnt/user/appdata is missing as well as my media share. All the drives are not showing any activity although I can still SSH to them and read the data. 

 

Worried about rebooting and maybe losing another drive and then really stuffed with Parity disks working. I'd like to be able to stop the array and restart without a massive parity disk rebuild. Would rather not reboot as the last few times I've had random failed drives. I remove and add them back into the array and they rebuild without error but still.

 

Just came across a post saying Tools - New config - preserve configuration might help but NOT doing that until I know more. I appreciate any help, will try and attach logs and screenshot.

tower-diagnostics-20230915-2304.zip

03:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID SAS-3 3108 [Invader] [1000:005d] (rev 02)
	DeviceName: Integrated RAID
	Subsystem: Dell PERC H730 Mini [1028:1f49]
	Kernel driver in use: megaraid_sas
	Kernel modules: megaraid_sas

RAID controllers NOT recommended with Unraid for many reasons

 

https://forums.unraid.net/topic/102010-recommended-controllers-for-unraid/

 

Quote

Note: RAID controllers are not recommended for Unraid, this includes all LSI MegaRAID models, doesn't mean they cannot be used but there could be various issues because of that, like no SMART info and/or temps being displayed, disks not being recognized by Unraid if the controller is replaced with a different model, and in some cases the partitions can become invalid, requiring rebuilding all the disks.

 

5 hours ago, trurl said:

03:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID SAS-3 3108 [Invader] [1000:005d] (rev 02)
	DeviceName: Integrated RAID
	Subsystem: Dell PERC H730 Mini [1028:1f49]
	Kernel driver in use: megaraid_sas
	Kernel modules: megaraid_sas

RAID controllers NOT recommended with Unraid for many reasons

 

https://forums.unraid.net/topic/102010-recommended-controllers-for-unraid/

 

 

Ah nuts. Thought it would be enough to put it into HBA mode. Looking now for an LSI card that will suit. In the meantime, any advice on what to do to recover my /mnt/user/media file path? It has disappeared along with the contents of my my docker path /var/lib/docker

 

Can I use preserve configuration to avoid a long parity rebuild?

8 hours ago, modality1972 said:

Hey, newbie to UnRaid and spent the last few weeks setting up my Dell RX730d and learning.

I wish I could spend a few weeks setting up, "my Dell RX730d."

 

You'll get it. Bummer you can't blame the hardware.

 

MrGrey.

 

4 hours ago, modality1972 said:

any advice on what to do to recover my /mnt/user/media file path?

A reboot should bring it back, if there are no more disk errors due to the controller crashing:

 

Sep 15 21:17:44 Tower kernel: megaraid_sas 0000:03:00.0: 31068 (748124264s/0x0020/DEAD) - Fatal firmware error: Line 977 in ../../dm/src/dm.c
Sep 15 21:17:44 Tower kernel: 
Sep 15 21:17:44 Tower kernel: megaraid_sas 0000:03:00.0: megasas_disable_intr_fusion is called outbound_intr_mask:0x40000009
Sep 15 21:17:44 Tower kernel: megaraid_sas 0000:03:00.0: FW in FAULT state Fault code:0x10000 subcode:0x0 func:megasas_wait_for_outstanding_fusion
Sep 15 21:17:44 Tower kernel: megaraid_sas 0000:03:00.0: resetting fusion adapter scsi1.
Sep 15 21:17:44 Tower kernel: megaraid_sas 0000:03:00.0: Outstanding fastpath IOs: 1
Sep 15 21:17:44 Tower kernel: megaraid_sas 0000:03:00.0: Reset not supported, killing adapter scsi1.

 

Avoid high i/o for now

2 hours ago, MrGrey said:

I wish I could spend a few weeks setting up, "my Dell RX730d."

 

You'll get it. Bummer you can't blame the hardware.

 

MrGrey.

 

Well I got a great deal off eBay including 8tb drives and then spent time evenings and weekends, which is why it took a few weeks. Hardware does seem to be part of the issue, the LSI Megaraid card is not supported so might be why I keep having issues.

8 minutes ago, JorgeB said:

A reboot should bring it back, if there are no more disk errors due to the controller crashing:

 

Sep 15 21:17:44 Tower kernel: megaraid_sas 0000:03:00.0: 31068 (748124264s/0x0020/DEAD) - Fatal firmware error: Line 977 in ../../dm/src/dm.c
Sep 15 21:17:44 Tower kernel: 
Sep 15 21:17:44 Tower kernel: megaraid_sas 0000:03:00.0: megasas_disable_intr_fusion is called outbound_intr_mask:0x40000009
Sep 15 21:17:44 Tower kernel: megaraid_sas 0000:03:00.0: FW in FAULT state Fault code:0x10000 subcode:0x0 func:megasas_wait_for_outstanding_fusion
Sep 15 21:17:44 Tower kernel: megaraid_sas 0000:03:00.0: resetting fusion adapter scsi1.
Sep 15 21:17:44 Tower kernel: megaraid_sas 0000:03:00.0: Outstanding fastpath IOs: 1
Sep 15 21:17:44 Tower kernel: megaraid_sas 0000:03:00.0: Reset not supported, killing adapter scsi1.

 

Avoid high i/o for now

I will try the reboot option later. Decided to stop the array and now I cannot assign any drives to the array. I read up on what would happen with Tools - New config - preserve configuration and ran that. This is the result (see screenshot). Tried mounting one of the drives but it changed from mount to UDEV, this seems to be a fix here -

 

https://forums.serverbuilds.net/t/guide-unraid-udev-rules-updates-for-white-label-drives/8918

 

Will end up rebooting but any thoughts on fixing the UDEV issue?

 

7 minutes ago, modality1972 said:

I will try the reboot option later.

You shoudl reboot now, the controller crashed, so the the devices are in an unknown state, a simple reboot should bring the data devices back.

Reboot fixed it and no data lost, thank you. I had a different issue where my drives were spinning down (to save power) and when Plex did it's nightly thing, it was causing disk errors and parity rebuilds. I think this is probably down to not having a recommended HBA card. Keeping my drives active fixed that problem for now, but that will be another post for the future. Thanks to everyone who pitched in with advice.