Jeff in Indy

I was out of town a few days, and returned to "Your server has run out of memory, and processes (potentially required) are being killed off. You should post your diagnostics and ask for assistance on the Unraid forums." So here I am, and here are my diagnostics. Any advice would be helpful. kaokulk-diagnostics-20231218-2013.zip

I royally screwed up and reformatted one of my hard drives, but I didn't see any other option. Let me walk through what happened and set me straight on where I went wrong (besides, obviously, reformatting). I had a SATA card go belly up. It resulted in one of my drives getting out of sync. After I replaced the card (thanks for the day delay, Amazon), I did the whole stop/start/stop/start the array to get it to rebuild the drive. The server faithfully rebuilt my drive, which took a day plus. I came home tonight, and it was completed. The drive had a green dot, the array said it was good. But my drive did not have the Browse option, and on the right side, it said the drive was not formatted. but otherwise, it all looked good. It wasn't emulating the contents, etc. Not seeing any other option, and the drive telling me it didn't have a format on it, I ignored the "Don't format a drive when rebuilding!" warning, and faithfully destroyed 12TB of my data. So a few questions: - Why did it spend 2 days rebuilding when it said there wasn't a proper format on the drive? - What would the right option have been when it said that? - Is there any tool to periodically get a list of the contents of each drive, so I would at least know what was missing? - Can Unraid change the warning message to "Hey! Jeff! Don't be an idiot! I don't care WHAT the message is! DON'T reformat the drive!" Thanks all.

Trying to access my server by its IP address produced no results (the server was headless), I told it to reboot. A few hours later, it did the same thing again. I plugged in a monitor, and it is not displaying anything. I'm going to reboot it again. If I understand correctly, the logs that would help me troubleshoot the issue gets erased when it restarts, yes? If so, is there a way to record the log in a way that it won't be lost when it restarts?

My Plex server was not responding well (I could browse, but nothing was streaming) - I was on 6.11.1 (I upgraded to .3 soon after). I went to Processes, and saw this: I paused, then stopped the nzbget docker. Even after stopping it, the process still remained (unless it somehow doesn't update). So a couple of questions: 1) Is there a way to sort the processes by CPU usage? Or is there a better plug-in to use? 2) Why would the process continue, even after stopping the docker?

So I’m using the steps on the website to back up the cache to the array. I changed the shares to Yes where appropriate and started the Mover. It took the cache from 600+GB to 483GB used. it hasn’t moved in the past couple of hours. The mover is still running, but nothing is happening. How can I see what’s happening, and why it’s stopped moving?

I restored from a quite old copy of Plex, seems to work OK. The rebuild should be complete late tonight, but I won't have time to work on the pool til probably Monday. I'll update when I get to it.

The pool or the entire thing?

Yeah, back in May I had a bad memory stick and replaced the memory.

Yes. I copied a file from my desktop's Downloads folder to my Data share. Probably.

The database isn't corrupt, that's why I restored from a backup that worked. But when I restored it, now I'm being told that it's read only.

It's "temp". I'm not sure why it's there, but it's emply.

This CAME from a backup. Then I tried it again. Same message.

So now I'm back to this non-stop message: Starting Plex Media Server. Error: Unable to set up server: sqlite3_statement_backend::loadOne: attempt to write a readonly database (N4soci10soci_errorE) Stopping Plex Media Server. kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

OK, I tried the Maxell cards, no difference. I then pulled every drive out, and reset all the cables. I think there was a MOLEX splitter that had come loose. Now all drives are showing up, and my disc 7 and parity 2 are being rebuilt, and I have the non-Maxell cards in and running. So after ALL that, I'm back to square one: My Plex database won't run because of a read only error. I'm going to set a Minimum Free Space for my cache when my rebuild is complete. Squid asked if my cache is read only. I never got an answer to that since my system went belly up. Does anyone see anything of interest here? kaokulk-diagnostics-20220630-2322.zip

I reset the cards, no luck. Later today, I'll try seeing if Maxell cards fix it, if not, I'll recheck all the cables.

Diags included. Also a screenshot during boot, showing "SATA link down". Not sure why it's showing that. kaokulk-diagnostics-20220630-0831.zip

So frustrated right now… so I get 2 new SATA cards (mentioned above). Take the old Maxell cards out, put new ones in, hook everything up. Start it up, and the 2 drives that were out of sync don’t show up at all, as well as a third drive. Shut down, replace the SATA cables for those 3 drives. Start it back up, now FOUR drives are missing. They don’t seem to be on the same card, ones even in the motherboard. Aaaaack…

By the way, here's what I got: FebSmart PCIE3.0 to 4-Ports 6Gbps SATA 3.0 Expansion Card for PCs, Servers, NAS, MAC Pros-Plug and Play on Windows, MAC OS, Linux System-ASMedia ASM1064 Non-Raid PCIE 3.0 SATA Controller (FS-S4-Pro) https://www.amazon.com/gp/product/B097R6MQBT/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1

Well, I wondered, since only 1 of those drives use the Marvell card. The other is on the motherboard directly (disc 7, the first one to get out of sync). I figured that maybe the Marvell cards were somehow screwing up other SATA connections, since I didn't know anything about the Marvell problem, and was too much in a panic to do so. I'll wait until the card comes in and replace it, then rebuild disc 7 and Parity 2 from the working parity drive.

I've ordered a new card, and it will be here tomorrow. I had (as far as I know) a working Disc 7 that I was rebuilding when my second parity disc went down. Do I assume that Disc 7 is trash, and rebuild it from my working parity, or should I assume disc 7 is OK, and rebuild parity from that? My guess is the safer bet is to rebuild 7 from the working parity drive.

So I should shut down the server, and order a new controller?

I'm now flying without a net, and I'm not sure what to do next. I have 2 drives that are out of sync. Any help would be greatly appreciated.

I was looking for that setting, when my server became unresponsive on my desktop. My phone was still showing it working, so I rebooted my desktop. Now one of my parity drives is showing it's invalid, and my rebuild of disc 7 has changed to a Read-Check, and has paused. Where do I go from here? Now I'm afraid to do anything. kaokulk-diagnostics-20220628-1600.zip

Well Squid, you tell me. (After moving some files from the cache, I rebooted, and disc 7 came up as invalid. I stopped the array, "removed" disc 7, restarted, stopped, "re-added" disc 7, and it is rebuilding as we speak. So you'll see disc 7 as Invalid in the log.) kaokulk-diagnostics-20220628-1402.zip

I overflowed my cache yesterday, and once again, the Plex database got corrupted. At least I'm getting good at restoring from an old database. So I copied over an older copy, but the UI wouldn't load. I go into the Log, and see these lines over and over... Starting Plex Media Server. Error: Unable to set up server: sqlite3_statement_backend::loadOne: attempt to write a readonly database (N4soci10soci_errorE) Stopping Plex Media Server. kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] How do I enable writing to the database? I hadn't come across this before...