January 2, 200917 yr Just installed a new parity drive a couple days ago, parity sync'd up with 0 errors. Well today I was trying to remotely log onto the tower and it wasn't working. So I rebooted the server. When I checked it, it is not started? I've never seen this before, maybe its something simple, but I don't want to click the wrong thing. I've attached a screenshot. Should I "start" or "restore" - Parity should already be ok, will it recheck it if I start? Any ideas why this can happened? Thanks in advance
January 2, 200917 yr Just installed a new parity drive a couple days ago, parity sync'd up with 0 errors. Well today I was trying to remotely log onto the tower and it wasn't working. So I rebooted the server. When I checked it, it is not started? I've never seen this before, maybe its something simple, but I don't want to click the wrong thing. I've attached a screenshot. Should I "start" or "restore" - Parity should already be ok, will it recheck it if I start? Any ideas why this can happened? Thanks in advance If everything is "blue" it has no knowledge of your array, or parity, as it could not successfully read a valid config/super.dat file on the flash drive when you rebooted. Was the array "stopped" when you rebooted it? It appears as if it cannot read the super.dat file on the flash drive, so it is starting out as if you never built parity or assigned disks to your array. Do NOT press "Restore" Unless you are removing a drive from the array, and not rep[lacing it immediately, it is almost never the right thing to do. (there are a few exceptions, as in the "Trust My Parity" operation as described in the "Wiki" REQUIRING commands be entered BETWEEN pressing "Restore" and subsequently pressing "Start" ) Somehow, unRAID thinks it is starting fresh. If you are certain the parity drive listed is actually the parity drive, and son't mind waiting for parity to be calculated once more, then press "Start" If it shows ANY drive as "unformatted" stop the array and reboot once more, DO NOT press the format button... or you will probably lose data on the disks being formatted. Either way, you will be doing a full parity calc (either because you will be forced to, or you will want to). You might post a copy of your syslog before you do anything (before you reboot). (instructions on how are in the wiki) It might contain clues to what happened. It might turn out the "Trust My Parity" series of commands might be best in your situation... only if ALL the drives are healthy, and all assigned to their correct slots in the array. Are they all present? and in the correct assignments? Joe L.
January 2, 200917 yr Author Thanks for your reply Yes the parity drive is as listed. I'm not 100% that the other drives are, but I haven't moved any of them so it would be weird if they were switched. I will post the syslog before I proceed. I gotta run an errand so it will be a couple hours. Thanks again! Happy new year
Archived
This topic is now archived and is closed to further replies.