Hokie Saiko

Members
  • Posts

    8
  • Joined

  • Last visited

Hokie Saiko's Achievements

Noob

Noob (1/14)

2

Reputation

  1. Has this been further delved into? I looked at my \appdata\terraria-tshock folder and can see a file there called 'tshock_4.5.18' which does look like the latest release of tshock; but the log from starting up the container says the game version is running v1.4.3.6. Opening the game states it is on 1.4.4.7 now Thanks for looking into it~
  2. Update on my missing world from half an hour ago: I had to move the oldest backup file I had into the newly created \\NAME\appdata\valheim\.config\unity3d\IronGate\Valheim\worlds_local folder. Previously I was overwriting the the one in the original 'worlds' folder and found that I kept reconnecting to the new, blank, day 1 world. @aRcaNia have you tried moving a backup to this separate "local" folder?
  3. I think @TimNL81 is right about a necessary update. I logged onto my server today to see it had started a brand new world. Unfortunately I had changed my backups to only two hours worth and the latest one did not get me my world back. I'm pretty new to UnRaid so I'm unsure if the previous backups would've been sent to some sort of recycling bin. Dang, been meaning to raise the backups back to the defualt 24 too. Still a learning experience for me and our trio was planning on moving onto V Rising or Terraria very soon anyway so perhaps I can manage to put the lesson to use on the next template.
  4. Hello, pretty new to Unraid so I want to make sure I don't miss something basic, but: CA Auto Updates ran on my binhex-plexpass container and updated earlier today, I saw the notification later. Just now realizing the container is no longer installed. I can still see /mnt/user/appdata/binhex-plexpass exists with all of its content, I'm just not sure what my next step should be in restoring the app. Am I meant to fully re-install it like new? or is there a spot I should be restoring it from? Thanks!
  5. Okay, doing the long smart test sounds like a quicker safety check, I'll go with that. Checking with another console commands help page, I believe that would just be: smartctl -a -tlong /dev/sdb | todos >/boot/smartsdb.txt Can I run these at the same time for all four drives? Will the results be readable in the terminal or should I expect to have to find each of the reports? I'd rather not lose the third data drive to parity, but I believe I saw typical drives are only rated for 60 degrees C and when I saw the preclear in the first morning I saw the drives were sitting at 65, likely for hours. The data is just going to be media, so not necessarily important but I'd rather not lose it without being able to do a parity rebuild. If I ended up using all the space (tbh not sure how big of an if that is) my plan was to continue expanding later with an LSI SAS 4i card. So for now it'll certainly end up cutting a lot of storage, but maybe if the extended is spotless I'll go back to 3/1.
  6. Fair enough, I suppose I'll be running another round of preclears then. If those pass I'll move onto smart tests to see if I should be worried about the 1 night of overheating - I'm mostly worried now on if I should cut my plans down from 3array/1parity drives to 2/2. Thanks for the input.
  7. The preclears started with the bad RAM, but I'm pretty sure the entire post-Read part was with the good RAM (multiple restarts and eventual hardware swap during zeroing). Yea, just before this I was still running windows on what will end up as a cache drive -- that kept having all sorts of blue-screens which I thought were due to CPU drivers but it looks like the RAM was bad before I started delving into unRaid.
  8. Hey y'all, I'm trying to set up a new server and decided to preclear my new shucked HDDs before making an array. Unfortunately, I wasn't really aware that the preclear would essentially stress test the drives so all four of them ended up overheating on the first night (no airflow). I also learned shortly afterwards that the RAM I had started on was faulty. Lastly, because of the RAM issues, the server was restarted multiple times during the process where the preclear successfully resumed when logged back in. Well, two of the preclears have fully finished now and it looks like the post-read verification failed on both. ############################################################################################################################ # # # unRAID Server Preclear of disk 9MH496UK # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 4 - Zeroing the disk: [23:15:40 @ 167 MB/s] SUCCESS # # Step 2 of 4 - Writing unRAID's Preclear signature: SUCCESS # # Step 3 of 4 - Verifying unRAID's Preclear signature: SUCCESS # # Step 4 of 4 - Post-Read verification: FAIL # # # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 36:38:14 | Total elapsed time: 36:38:14 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status (device type: default) # # # # # # ATTRIBUTE INITIAL STATUS # # Reallocated_Sector_Ct 0 - # # Power_On_Hours 42 - # # Temperature_Celsius 27 - # # Reallocated_Event_Count 0 - # # Current_Pending_Sector 0 - # # Offline_Uncorrectable 0 - # # UDMA_CRC_Error_Count 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ I take it my next steps should be to rerun the entire preclears on all four drives to hopefully get a pass. With airflow, new ram, and no restarts it should work out, eh? Did the overheating for a night permanently damage the drives? Would a short/long smart test be more adequate at this point? Thanks!