runtman

Ahh, that's probably it then. This beast is a bit of a dinosaur AMD Turion™ II Neo N40L Dual-Core @ 1500 MHz Memory: 8 GiB Other Single-bit ECC

Mine appears to be crash looping with this output, not really sure why / what is going on (Pal World) Loading Steam API...dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory OK Connecting anonymously to Steam Public...OK Waiting for client config...OK Waiting for user info...OK Success! App '2394010' already up to date. ---Checking if configuration is in place--- ---Configuration found, continuing...--- ---Checking if PublicIP is in place--- ---PublicIP in PalWorldSettings.ini found: << REDACTED >> ---Prepare Server--- ---Server ready--- ---Start Server--- /opt/scripts/start-server.sh: line 109: 65 Illegal instruction ${SERVER_DIR}/Pal/Binaries/Linux/PalServer-Linux-Test Pal ${GAME_PARAMS} ${GAME_PARAMS_EXTRA}

It's reparing as expected, thank you for all of your help!

You have all been great, thank you very much. I'll report back soon

So it's a case of stopping the array, taking the disk out, applying a new config and starting the array again? Are there any special options I need to click so I don't lose data?

Eeek, so what should I do in this case? I can either fit a replacement drive (1TB) or just remove the bad drive (2TB). I don't have a spare 2TB currently. I have plenty of space in the array for this. Is it just a case of ordering a replacement 2TB and allowing the cluster to be 1 disk down for a time period? Thank you for all of your help

Thanks, seems simple enough I see no mention about the drive being smaller though, trurl mentioned it has to be the same size?

Just a question for when this data copy is finished, I will unmount and remove this disk how do I actually rebuild parity at the moment it just lists this disk at "missing" do I need to make a new config? I'm afraid at losing my data here.

Hey I did that before submitting the ticket and it reported everything was ok

Ah fine, yes I wasn't meaning that I would never have to back up anything more going with that the level of raid would mean this disposable data was more resilience, so that is fine. I am currently running my `cp` command when the array is alive, should i turn this off? - Edit: I took the array offlline, un assigned Disk 1. I have now mounted Disk 1 and am moving the data from that to Disk2. To clarify, when finished I need to: - Shut down - Remove Disk 1 - Rebuild Parity (Not 100% sure how to do that just yet) - Shut down - Add replacement Disk - Start up.

I don't have any backups at present it's just media that I have downloaded. I don't have a spare 2TB disk to replace it with, but I was planning on adding a 1TB disk in it's place. I don't really understand how this raid works if I am required to backup the data, perhaps I am a bit ignorant here. Should I power down and reseat Drive 2? I use a Gen 7 microserver.

First off, sorry if this comes up often however seeing so many threads and information it's coming across to me as very varied in the solution. I have quite a simple unraid setup. 2TB - WD Green (Parity) 2TB - WD Green (Disk 1) 2TB - WD Red (Disk 2) 2TB - WD Red (Disk 3) I originally started out with just the two greens then later added the Red disks as I managed to get them off a friend brand new for free. These are roughly 2 weeks old. As of today I noticed a few notifications about `reallocated sector ct is 160` (Disk 1) I noticed this number is climbing, so I immedaitely started copying data from this drive to another drive (Disk 2). Now I am about 20% through the copy and have noticed that Disk 2 is showing as errors, however smart scans on both drives are passing so I am slightly confused as to what is happening here. My immediate plan is to take data off Disk 1, copy it to Disk 2 and take Disk 1 out of the array. But now seeing errors on disk 2 has got me thinking that this may not be the best plan? I'd love some input here. chipshop-diagnostics-20190320-2121.zip