rawfuls

Just updated from 6.12.6 to 6.12.8 and can no longer load WebGUI locally nor externally. Logs indicate that webGUI has started and privoxy is listening. Where to start on this guy? Running on proxynet. EDIT: Solved! LAN_NETWORK under Edit was incorrect.

The rebuild was successful and the data seems to be intact, however Docker is unable to start. Service seems to be enabled on the settings side. EDIT: Maybe I jumped the gun here. Disabling Docker then re-enabling seems to have gotten the service to start.

Understood, so bring down the array, rip open and replace cables (as needed) and rebuild parity after I tell UnRAID that the drive is in fine shape. I did use the cheap(er) Amazon splitters from molex -> SATA (not the cheapest ones that cause fires). Any recommendations here for those LSI SAS and power cables? Maybe it's time I fix these bugs once and for all with quality components. Is the absolute latest version firmware for the LSI cards fine, or should I backdate?

Should I still move data, or just shut the server down, check connections, upgrade firmware and let parity emulate data still? If I still rebuild (by taking the drive out, moving contents to disk5), would I run the new permissions on all disks and all shares, or thinking not needed here?

Had a drive fail and get disabled. While I personally think it's probably a cable problem, I've learned to not shut down UnRAID right away and fuddle, as I want to get the data off before the drive and another drive fails with it (happened once.. that sucked..) So now, I'm running here with my diagnostic logs hoping somebody can jump in and see if they can find something I'm not seeing. I'm okay tossing out disk4 in my array, disk5 has lots of open space and I have a 4TB drive that just passed pre clear that I plan on throwing back into the array when this fiasco is resolved. I've also shut down all dockers, and stopped mover and any other auto-run plugins for the time-being as I was getting ready to use unBalance to move all disk4 onto disk5, until the attached message cropped up. "There are some permission issues with the folders/files you want to transfer 331 file(s)/folder(s) with an owner other than 'nobody' 329 file(s)/folder(s) with a group other than 'users' 0 folder(s) with a permission other than 'drwxrwxrwx' 540 files(s) with a permission other than '-rw-rw-rw-' or '-r--r--r--' You can find more details about which files have issues in the log file (/boot/logs/unbalance.log) At this point, you can transfer the folders/files if you want, but be advised that it can cause errors in the operation You are STRONGLY suggested to install the Fix Common Problems plugin, then run the Docker Safe New Permissions command" This is a new one for me so looking for some insight here. Should I go ahead and run the Tools > New Permissions command on all disks and shares, or just disk5? (disk4 doesn't show) Diagnostics attached, drive failed on March 6th at 4:59pm PST hoangserver-diagnostics-20220309-0100.zip

Getting a new error message that the server is outdated. Two of the players on the newer updated Minecraft version are having the issue whereas two players on the older (matching) version are fine. Is there a way to check the docker for updates? I'm on UnRAID 6.9.2 and docker shows the docker was last created 2 days ago (assuming, updated 2 days ago). EDIT: Sigh, should have checked. Docker > Advanced View (top right) > Force Update for docker container. This fixed it; thanks

So unBalance from disk4 to all other disks. New Config, Preserve All; reduce by 1 disk in total # of disk?

Success! Kind of. The drive failed and seems to be (shorting?) out the controller it's connected to. If connected to the LSI card, the whole adapter fails out. If connected to the board, the whole board controller fails out. At this point, the drive has been disconnected and the parity is emulating the contents. Is this where I now go New Config > Preserve All. Do I downsize by one drive or start the array with the same # of drives, but leave disk4 empty?

New card came in and still having the same issue... Appears it's the motherboard/BIOS, as after testing on my desktop, both the old card and new card work... go figure. I've put the new card in, and connected only 4x hard drives (one SAS -> 4 SATA), and it seems to boot without any issues. Once I use both SAS ports on the 9201, it no longer boots and shows the above error message. Seems like with the total of 8x drives, the 9201i card is indicating a failure... what gives? EDIT: okay.. some more info. (1) LSI 9201-8i w/ 2 SAS (8x hard drives via splitters) -> no boot (1) LSI 9201-8i w/ 1 SAS (4x hard drives via splitters) -> successful boot (2) LSI 9201-8i w/ 1 SAS each (4x hard drives via splitters) -> only recognizes (1) LSI 9201-8i card (4x drives) Testing in my own personal desktop: (1) LSI 9201-8i w/ 2 SAS (8x hard drives via splitters) -> successful boot Seems to me like the motherboard isn't able to read all 8 drives anymore, any belief to thinking it's just a BIOS modification?

The card was cooled off and still wouldn't pass the MPT BIOS error message. Unless it's isolated as a motherboard PCI error, it does seem that I could have taken both of these cards out with heat (my previous card was in the same spot, no active cooling). Case is a Rosewill L4500. It's on the side-most PCI slot, so no real cooling going on. I'm seeing quite a few people bolt up 40mm fans to the heatsinks, so that may be in order.

Nope, so now we know it really is the card failing then Saw heatsinks on the cards and figured it would be alright. Looks like I'll be on the market for another card and figure out an active cooling resolution.

Sigh, restarted and now getting an error at start... MPT BIOS Fault 11b encountered at adapter PCI... Firmware Fault Code: 4101h. This happened to my last LSI 9201-8i card, I wonder if the motherboard is eating these or if these cards are actually dying. Tried a different PCI slot to the same issue.

disk4 disabled overnight, log shows tons of errors, UnRAID shows a billion writes with tons of errors. Not totally thinking it's failed, maybe a loose connection; but recently had a similar situation and lost a good chunk of data. Would like some guidance before I move forward, attaching diagnostics below. I believe the plan is to use unBalance to move all data from disk4 and let unBalance throw it onto the rest of the array. Once unBalance is finished, New Config > Retain all config > All > leave disk4 blank, start up the array, let it rebuild. Once rebuilt, stop array, downsize array down to 10 drives (now 11), then move disk5 to disk4, disk6 to disk 5, etc and should be good? diagnostics-20210215-1121.zip

Ah, then the parity-rebuild did in fact work. Thanks a ton for all the help, JorgeB!

I did have those checked and it still prompted those. Although, now that I look at my data, it does look like my Media has more folders now. Starting to believe that the parity-sync was able to move all files back to Disks2/4... love the self doubt at this point.