July 26, 20178 yr Hey everyone, So to keep this concise, I went away for the long weekend with my small unraid NAS running at home. I can access plex etc from a far so this is nothing out of the ordinary. Unfortunately since I was camping, I didn't have any access to the server for 3-4 days. When I left, it was running perfectly normal, but when I got back, the server was no longer mounted or accessible from my network. My first thought was that the power went out, but the unit wasn't off downstairs. It was completely unreachable though the webgui, so I restarted it manually. After this the system came back online and I could access the menu, but after pressing start, it tried to mount the drives for over two hours on a frozen screen before I stepped in. I re-powered down and powered up and was able to start the server in Maintenance mode. At this point in time I ran a full parity check, thinking a drive/portion may be corrupt. After 8 hours the parity check found 12 errors that it was able to re-write. I think was able to manually spin up the drives in maintenance mode. I rebooted the server, again in maintenance mode and then stopped it. Without any power down, I then tried to start the server again. Again, it froze on mounting the drives and became completely unresponsive. I'm completely at a loss for what to try next. The circles next to the drives are all green, no indication that there is any hardware failure that I can tell. Software wise, nothing was installed or changed over the weekend since I wasn't even in the same province and my house was empty. This happened about 3 weeks ago now. I have received advice from several people that it sounds like a bad drive. I have wiped and data restored each drive since. I have also looked through the SMART data and their do not appear to be any errors with the drive. Additionally, I reinstalled the entire unRAID OS from scratch and removed all installed programs/dockers etc with no help. I have since purchased a new WD Red drive and a new PCIe sata controller card but have yet to install. tl;dr: unRAID freezes when I press Start and cannt mount drives. Tried parity check, no obvious errors. For reference I am running: Pentium G3258 Gigabyte - GA-H87N-WIFI Mini ITX LGA1150 Motherboard 3 x 3tb WD Red Drives, 1 seagate 2tb drive ADATA - XPG V1.0 8GB EVGA 500W PSU SATA III PCIe 2.0 X 1 Controller Card Unraid version 6.3.3 Honestly, my depth of knowledge in this stuff isn't that great yet, and I would love some advice on how to handle this/troubleshoot it properly. Thanks in advance.
July 26, 20178 yr Community Expert Sound like a corrupt xfs disk, after starting the array type diagnostics in the console/SSH and upload the ZIP.
July 26, 20178 yr Community Expert Please use the forum, in reply to your pm: Quote I really appreciate your response. Is there any chance you could give me a quick rundown of where to enter that diagnostic command? I honestly have never a command through the console before. Thanks Brett You can use the server keyboard/monitor if you have one, if not SSH into the server, the diagnostics will be saved to the Logs folder on the flash drive. https://wiki.lime-technology.com/Terminal_Access
July 27, 20178 yr Author @johnnie.black My apologies for that. I didnt know if it was still part of the same question line. I have attached the zip logs to this post here. tower-diagnostics-20170726-1706.zip
July 27, 20178 yr Community Expert Like I said before you'll need to grab the diags after trying to start the array.
July 30, 20178 yr Author @johnnie.black Sorry I definitely missed that part of the description. Took me a day or two to get the time to tackle this again. I hope this zip file is of more assistance. tower-diagnostics-20170730-1525.zip
July 30, 20178 yr @bplouffe thanks for attaching those diagnostics.... I see two issues, johnnie.black is right that there is corruption. Before we fix that, there maybe somethig simpiler to try first. With your array stopped, click on Disk1 and change the 'File System Type' to XFS (currently you have it set to auto). Your other disks are already set to XFS, for whatever reason your Disk1 is different. Then start your array. Try that and let us know your results.
July 30, 20178 yr Author Thanks for the speedy reply @Lev. I changed disk1 to xfs and tried to start the array with the exact same results, locked on mounting. I gave it about 5 minutes to respond before shutting down. I took another diagnostics report when doing this, and can certainly post if the updated info will help.
July 30, 20178 yr Ok next step... when you get it back up, check the box 'start in maintenance mode' then start the array. nothing will mount, that's expected in this mode. at the command terminal type the following 'xfs_repair -v /dev/md1' if you can save the output and post here that'd be great. once it completes, stop the array and then try to start it again normally.
July 30, 20178 yr Author @Lev I can absolutely do that, will get on it now. Maybe a silly question, but what format will the output be in. Will I just see a string within the terminal that I should manually type over, or will it output a text file to copy. Will start on the first part while waiting to hear back. Thanks!
July 31, 20178 yr use the command: xfs_repair -v /dev/md1 | tee /boot/logs/md1_xfs_repair_log.txt that will save the results into that file onto your usb drive in the logs folder.
July 31, 20178 yr Author When I used the command this is the result. Have no since tried to mount disks.
July 31, 20178 yr You didn't get the nicer message unfortunately... No worries though I've seen that one before and resolved it and everything seemed fine afterwards, however others here are more experienced than I am and you can wait for them to comment if you want to be 100% sure. Might mean a file or two is corrupted, but honestly I don't ever know anyway better solution at this point when you get that message. If you want to move forward add the L to the command: xfs_repair -Lv /dev/md1
July 31, 20178 yr Author Ok, so that command has run. Quite a long output that it went through. This is the final screen though.
July 31, 20178 yr Great, stop the array and then start it in normal mode. See if it works now. If still having issues, attach the diagnostic logs again.
July 31, 20178 yr Author @Lev You are a saint. I just got home and went to start it. Worked perfectly. I really appreciate your help and advice. Made my day. Thank you!
July 31, 20178 yr 1 hour ago, bplouffe said: @Lev You are a saint. I just got home and went to start it. Worked perfectly. I really appreciate your help and advice. Made my day. Thank you! Awesome! Glad to hear you're back online! Cheers!
Archived
This topic is now archived and is closed to further replies.