Neejrow

Members
  • Posts

    53
  • Joined

  • Last visited

Neejrow's Achievements

Rookie

Rookie (2/14)

3

Reputation

  1. tower-diagnostics-20230625-0200.ziptower-smart-20230625-0159.zip Finally finished the SMART extended self test. Looks fine I guess?
  2. So there was a power outage last night while I let the full SMART extended self test run. So my unraid server was shutdown via the UPS. So I will have to do another test. Will update once it's done.
  3. Unraid Version: 6.11.5 Motherboard: MSI B550 Mortar Wifi CPU: AMD Ryzen 3900X MEMORY: 32GB @ 3000mhz (mismatched kits of 2x8) Hello, I noticed this morning some errors were listed when my parity drive span up at 5:00am to run MOVER. Also, then recieved two follow up emails with; Subject: Warning [TOWER] - reallocated sector ct is 216 Description: ST8000VN004-2M2101_WKD0TW3W (sdc) Subject: Warning [TOWER] - reported uncorrect is 2 Description: ST8000VN004-2M2101_WKD0TW3W (sdc) I have had errors on drives before and taken certain measures to fix the issue (replace cables etc) or replace the drive itself, but I have never had any errors show up on the parity drive. So I am wondering if I need to do anything differently in this situation? Also just as a side note, is my spin-down delay of 1 hour on my drives too low? They don't get access too often maybe once or twice a day. I do not want to run the drives 24/7 due to the increased noise and electricity costs. I have uploaded the diagnostics to this post and will await for further instruction, thank you. tower-diagnostics-20230623-1623.zip
  4. Just wanted to post and say I also am getting this error. I have no idea what an 'addons' folder is nor how to even access it. What are you doing to find the folder?
  5. Okay thanks for the suggestions. I will turn the server off tomorrow and check what cable it's on. (Mobo / SAS card) I thought I was being smart last time with putting labels on all my drives. Now I realise I'm an idiot for not labelling which end of the system they go to. Edit: Can see in devices which drives are on LSI card / Motherboard ports.
  6. Unraid 6.11.5 Ryzen 3900X B550M Mortar Wifi Hello, Last night I recieved an email that my server encounter some errors on a disk. This concerned me greatly because just recently (2~ weeks ago) I went through a whole ordeal with a drive seemingly failing, and then the replacement drive I bought failed, so had to buy a 2nd replacement drive to fix. (Context here) Immediately upon seeing this error I began a SMART extended self test on the drive, and it has just completed. It returned without error. I'm attaching the diagnostics to this post. Do I simply disregard this small error of 64 as a one off random thing maybe caused by a memory failure etc, or is this something I should take more seriously? I have had my unRAID server running great for 3 years, up until a couple of weeks ago. The previous incident clearly seemed that the drive itself had failed (under warranty) but now with these errors coming up randomly on a different drive, perhaps something else is also happening that needs to be addressed? I can't really recall ever having errors on drives before outside of a failed drive and faulty SATA cable. What are the next steps I should take? Thanks. tower-diagnostics-20230222-1826.zip
  7. Thank you for the help once again! You're a life saver. I have started the array, things appear to be working fine. I have taken a flash backup and am attaching the diagnostics file. About to start running a non-correcting parity check now also. tower-diagnostics-20230211-1356.zip
  8. I did the new config > Preserve current assignments = All > Apply. Now when I am about to start the array, it is claiming my parity drive will be overwritten (I have selected parity valid box) Is this what it normally says or has something else gone wrong now? I am scared to start the array with that warning message there. As it still stays there even with the parity is valid check mark ticked.
  9. Yes I did the rebuild in maintenance mode. Because I was afraid it might write data from things and screw up the data-rebuild. After it completed I then stopped the array, and restarted the array in normal? mode. Is this the only option?
  10. No I do not have diagnostics from after the rebuild because it all went fine so I didn't see a need to. I haven't touched anything regarding flash drive or anything else. PC Has been on permanently since I did that successful data rebuild onto WP00KDEZ. Then today, I did a proper shutdown from Unraid UI (clicking shutdown button) and now I get this. Is there any way for me to edit the super.dat file to think the correct drive is in (which it...is?) or am I now royally screwed.
  11. Sorry forgot to add the diagnostics. Not sure how much use it will be. tower-diagnostics-20230211-1307.zip
  12. @JorgeB @trurl New issue.... I turned off the PC to load into BIOS to enable CPU Virtualisation so I can run a VM. When I loaded back into unRAID it is claiming my Disk 5 was missing, and the option to select it claims is the incorrect one. It thinks that the correct disk is WP00L646 for Disk 5. Which is that failed new drive I bought last weekend which immediately had errors so I cancelled the rebuild at 19%. The full data rebuild was performed on WP00KDEZ which is the drive I still have in now. How can I get unRAID to recognise this is the correct drive? Or am I now screwed.... I just returned both those 2 failed drives for RMA yesterday.
  13. Great news. Rebuild on the 2nd new drive went off without a hitch. All my data is secure once again! Thanks trurl and JorgeB for the great help! Definitely calmed my nerves when I was panicking.
  14. @trurl New, NEW drive is in. Did a quick 1 min smart-self test and it at least passed that. The previous new drive was failing even those. I decided to keep the drive on my LSI SAS card on a cable I have been using for years, even though I also did recieve brand new sata cables today too. Would rather stick it on a cable I know works fine than risk a new cable that might be faulty and cause the rebuild to fail. Also I understand I'm not in the greatest time-zone (Australia) to be dealing with you, so I'm not expecting immediate responses if something does go wrong again. I'll just post updates as to what is wrong and appreciate any help you can give, when you are able to do so. Thanks! Just started the Data rebuild and will keep you guys updated as to how it goes.
  15. Yeah thanks. Already ordered the new drive so I'll update this thread when that arrives. I have turned off the server completely now because I was unsure what else to do. Is this fine to leave it off for a couple of days?