Hi,

Hope you all can help. I have been trying to get my server running again after the motherboard battery went out. The BIOS was reset and I was able to boot the system again, but now the Parity drive is not properly recognized. The parity drive is loaded internally in the CPU, while "Drive 1" is external. 

 

Not sure if it is same or similar issue as:

 

 

Attached are the logs.

 

Any help is appreciated. Thanks!

papsh-diagnostics-20200518-1215.zip

Gigabyte boards are known to create HPA partitions by default.

 

Also, you should change the SATA controller to AHCI/SATA and update Unraid to latest.

Hi Johnnie,

Thanks for the help. I updated Unraid and AHCI/SATA in the BIOS. Attached are the logs. Please let me know what else I might try. Seems that the Parity (internal) is showing up slightly smaller. Both the internal and external are the exact same make and model. Not sure if I could swap the internal and external to solve the issue since the BIOS is reading the size differently. Not sure if that would do the trick.

Thanks!

papsh-diagnostics-20200522-0717.zip

25 minutes ago, abeg29 said:

Seems that the Parity (internal) is showing up slightly smaller.

It is because the board created the HPA, it's all explained in the link above, including how to remove it.

Hi Johnnie, 

I was able to get HPA removed on that drive. I used the command line method...
hdparm -N p7814037168 /dev/sdc

and this `hdparm -N /dev/sdc` returned `7814037168/7814037168, HPA is disabled`

 

Now I get error `Stopped. Replacement disk is too small.` Any ideas?

Thanks

papsh-diagnostics-20200522-1208.zip

I have tried to start the array since everything looks good, but stops in error due to the `disk is too small` error. I don't see any option to fix the issue.

Thankspapsh-diagnostics-20200522-1241.zip

HPA is also enable on disk1.

 

P.S: 2 SATA ports are still in IDE mode, these AMD controllers have separate settings, usually ports 1 to 4 and ports 5/6.

 

 

Sorry, I was following the recommendation in the blog only to change it on the parity (wrong) drive. I have updated both and now get "Start will start Parity-Sync and/or Data-Rebuild.". I assume I should go ahead and run that? I have a backup of the main drive just in case. If it is successful will by data still be there or will I need to start from scratch?

Thankspapsh-diagnostics-20200523-1217.zip

14 hours ago, abeg29 said:

I should go ahead and run that?

If you currently start the array it will rebuild disk1 from parity, is that what you want?

I just want my server back to normal. 😁 Is this the best option? 

The original problem wouldn't disable disk1, that was something else you did, I'd suggest at least start with disk1 unassigned to make sure the emulated disk1 is mounting and showing the expected data, if yes then re-assign it to rebuild.

Thank again for the help. I am so close! I tried starting the array with Disk 1 unassigned to only start the Parity drive and it is stuck at  "Array Starting•Mounting disks..." It has been like this for about an hour now. I tried t stop the array to retry, but that is no working either. Should I force a hard restart?

Edited May 25, 20206 yr by abeg29
Adding sentence

That suggests fs corruption, see if you can get the diags on the console by typing "diagnostics", then type "reboot" and if it doesn't do it after 5 minutes you'll need to force it.

Ok thanks. I had to force a shutdown. I went ahead and updated a couple of old Plugins to get rid of the additional errors after restart. I was able to start it in Maintenance mode, then stopped the array, then started it normally and it finally mounted. Everything looks good, so I'm going to go ahead and attempt the rebuild/parity check. Thanks again for all your help!

papsh-diagnostics-20200525-1114.zip