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.

Was finally able to throw in an extra 5TB and 4TB drive in place of disk1/disk3. Upon doing so, I got the warning that starting the array would wipe out the existing data on parity1/2. No combination of disk juggling would resolve this despite me thinking it would. Does in fact look like data loss, so I went ahead and started the array and pulling whatever data I can to pull over to the new array. I had my appdata/configs saved to my SSD cache drive, which is unaffected. I noticed my docker tab was empty (aren't these stored on the cache drive?) but when reinstalling some docker containers, the app would require setup parameters (edit menu) but would then reuse the appdata info, so this should make rebuild a bit easier. But, why does the docker tab clear out if the docker file is located in cache?

Believe my tentative plan (waiting for 10TB Parity 2 to finish SMART extended) will be to run New Config > Preserve All. Assign the parity1&2 respectively, data respectively except exclude disk1/3 (since disk1 is outdated, disk3 is failed). (So does this mean previous disk2 is now disk1? Or do I leave previous disk2 as new disk2? As in, do I have empty data slots in the new config?) With the 2 parities, I'm hoping the array will start without the 2 other data disks. Do I add the 12TB as an additional disk? If in the event that I have to move forward with rebuilding the entire array, is there any point in pulling the existing data off the existing data drives? It's not mission critical, but would be nice... EDIT: The SMART extended test finished and no errors were found, as expected moving the 12TB to parity 2 and 10TB to disk3 did not prompt an easy 'copy' selection. It's looking like a New Config > Preserve All, then force re-enable Parity 2 and praying it allows me to rebuild by throwing in the 12TB into the data array.

Can I force-enable parity 2, then move forward with rebuilding disk 3? Can I force-enable Unraid to see disk 1 as NOT a new device?

Ah, I understand that one. Say parity 2 is still valid, could I force-enable it, then transfer parity 2 to a 12TB parity (will this play nice if parity 1 is 10TB?) then drop the 10TB from parity 2 to disk 3, keeping disk 1 unassigned? Are there any other alternatives?

No, Unraid is seeing it as new because the array has been started/stopped without it prior. So now replugging it back in, Unraid sees it as new; however the disk still has data and has never been wiped.

Sorry, I meant reboot, start array with it unassigned, then reassign it. Let parity rebuild and the error go away. Parity 2 is not showing any yellow abnormalities for disk attributes. I rebooted before I could find out what the error was on it getting disabled. Disk 1 is showing available (it does power on and read), but it's error is UDMA CRC error count - this was a known issue, I was waiting for me to arrive home (today) to pull the drive. I should have unassigned the drive first and rebuilt the array around it, but alas. Disk 3 isn't powering back up, at all, this seems like a catastrophic failure.

The server was brought down minutes after the drive got disabled, so this sounds like a potential option? I figured a reboot would fix it since I have seen Unraid fail out a drive before, reseated the LSI card and the errors went away. I figured this was similar.

I'm not 100% sold that the parity 2 is truly failing. I do know that disk 3 has failed due to it no longer being recognized. Disk 1 shows bad sectors. I'm hopeful that the second parity isn't actually failed, it still reads and SMART short tests fine, though I know that's mostly useless. I don't see any extreme readings in the disk info section which tells me it should be okay. I'm hoping it only disabled that disk due to a temp power loss (loose connector, etc). Is there any hope of setting a new config to make Unraid unmark that disk as disabled, bring back that second parity just enough to rebuild the array OR transfer the parity bits to a new drive?

Parity: 2x 10TB Data: 4x 4TB, 1x 5TB Server has been remote up until this week, I have physical access for this week only. Disk 1 had been showing bad sector counts, I unassigned but never removed the disk. Parity 2 failed tonight, showed disk disabled. Well, as good as time as ever to remove those drives. Shut down, unplugged the failing data disk 1 and was planning on rebooting with parity 2 still connected to do scans. Disk 3 (4tb Data) never came back online. Tested different connectors, same issue. Starting to look like a complete dead drive. Wanted to start the array with 1 parity 10tb, and unassigned the 2x 4TB drives but it is saying too many wrong/missing drives. Tried assigning the disabled parity 2 drive as a data drive, just so I can get the array to rebuild with the minimal disks, then rebuild array once again with a new parity when I get one- same error. However, I am not trying 'new config' as I feel like I'm going to klutz something, so reaching out for help before I do that. Local Best Buy has 1x 12TB (no 10TBs) and I have it on pickup for tomorrow, but that would need to go in as parity since it's larger since it's a larger disk? If so, can I do so without starting the array as I'm unable to now? Looking for any insight here, lots of data here, thankfully nothing mission critical but would really prefer not to have to rebuild it all.

I've gotta be completely missing something... Where is the openvpn config file? Am I modifying for each location.ovpn? Attaching an image of my dir for /config. This was setup per SpaceInvader's video.