warhead

I've been experiencing the same crashes. Same type of error in the syslog just before things start to hang. Same hardware that was running fine on 5.05, once I upgraded to 6.1.3 these crashes tend to happen every couple of weeks. I've got Sabnzbd, sickrage and transmission dockers running. Also running a SAS2LP card in my system, been reading that it might have other issues besides the slow parity check speeds under 6.x, not sure if it's related to this though. Already done several passes of memtest with no errors.

During the early stages of the parity check on my SAS2LP setup (first 10-20% of the array maybe?) the change to nr_requests more than doubled the speed but after that it started tapering off and eventually settled on the old speeds. After the parity check completed, the average speed and duration remained pretty much the same as before with leaving nr_requests as default at 128

Gave those commands a try on my array Unraid 6.1.3 Motherboard - SSD cache, 1.5TB, 3TB, 5TB, SDD cache SAS2LP - 1.5TB, 2TB, 2TB, 5TB, 2TB, 3TB Total 10 drives Before: Elapsed time: 8 minutes Current position: 22.1 GB (0.4 %) Estimated speed: 44.7 MB/sec Estimated finish: 1 day, 6 hours, 54 minutes Disk stats: ~330MB/s After: Elapsed time: 10 minutes Current position: 30.8 GB (0.6 %) Estimated speed: 108.1 MB/sec Estimated finish: 12 hours, 46 minutes Disk stats: ~860MB/s I say the results look pretty good! EDIT: Parity check much further along now and has slowed down a bit. Elapsed time: 4 hours, 28 minutes Current position: 1.38 TB (27.6 %) Estimated speed: 61.7 MB/sec Estimated finish: 16 hours, 18 minutes Disk stats: ~480MB/s

Problem this introduces is complicated bug finding and you make it almost impossible to 'replicate' an install. Eg. I install package XYZ and it works fine on my system and I'm trying to help someone install it 3 months from now but the package version changes at the repo and introduces a small bug. What works on this install might not work next week if there's a broken version uploaded to the repo. I ran into this kind of problem with doing Fedora respins a little while ago. Out of the blue the livecds I make no longer install RAID configurations from the kickstart file and the system would hang part way through the install process. I finally isolated it down to a specific version of udev that got pushed into the repo. I think what might work would be a way for packages to be downloaded straight from repo like you suggested, but also a way for the plugin manifest itself to specify the exact version of a package it requires as a "safe mode install" of sorts.

Silly question but have you noticed a change in the array size? I'm guessing a HD movie collection would be quite large and you'd probably notice the extra free space in the array if the stuff had been deleted or was no longer there. Sent from my iPad using Tapatalk HD

You can just add an echo line to your go file and pipe the line to the sudoers file. Its not recommended to edit this file directly without the syntax checking provided by visudo, but it does work well if you know exactly what you're doing. Alternatively you can edit the sudoers file via visudo and make a copy of it onto your flash drive and then have the go file overwrite the original on reboot. Sent from my Galaxy Nexus using Tapatalk 2

Some motherboards come with 2 different SATA controllers; usually 1 intel one and one from another manufacturer. What PSU do you have? The 2 drives that drop out at the same time, do they happen to be connected with the same molex connector in daisy chain or from a common cable back to the power supply? I suspect that with you having a marked drive as failed and parity correction comes into play, your system can't handle the power load from all drives being active at the same time.

Yes it's meant to be read as a '10' and thus is newer than '8'

Could it be a power supply issue? Parity sync requires all drives to be spun up

Some quick googling showed that that particular DLINK card uses a rebadged Realtek RT8169 chip. Following the advice/help from this thread http://lime-technology.com/forum/index.php?topic=23961.msg210551#msg210551 may help get your card working

There weren't any in my case. Plus the webGUI was still working. I thought that was one of the first things to get killed off in an OOM situation? Sent from my Galaxy Nexus using Tapatalk 2

Do you have a live miniXP cd/usb? I've seen weird issues where devices don't work correctly until you use the Windows drivers to enable that particular feature ( in this case, WOL ). I have a Dell laptop that everytime I turn off bluetooth in linux, I'd have to boot back into windows in order to turn it back on. If you don't have a live windows setup, try plugging in an old hard disk and run a miniXP install off that with the correct driver for your LAN card and enable WOL and disable any type of power management for the card

I had a similar issue the other day using 5rc8a. All my shares ( with the exception of the flash drive ) became inaccessible all of a sudden. Restarting samba via the GUI didn't help and in fact after the restart the share configuration become blank. Checked syslog and all I can see were those "Transport endpoint not connected" errors for each of my shares. I stopped the array and rebooted the machine and it's all normal again.

Have you checked your BIOS version? Try putting the celeron back in and upgrade your BIOS if necessary, clear CMOS and then swap the new CPU in and see if it POSTs Sent from my Galaxy Nexus using Tapatalk 2

Cool idea! Never thought of doing that. Definitely will come in handy when it comes around to trying to get NUT running for my Eaton UPS