The_Keymaker

I used the 'Legacy Upgrade' procedure and manually formatted the USB and manually copied the new OS and old config files (sans go file) method. Inserted USB and rebooted. Everything seems to be working OK. Thank you Frank1940 and ChatNoir!

I am finally ready to upgrade to v6 from 5.0.6. However, reading through the pages of this topic indicates it's not so straight forward and I can expect difficulty. Also, the upgrade wiki link (https://wiki.unraid.net/Upgrading_to_UnRAID_v6) no longer works. After 6 years from the OP, what is the best tried and true method to perform this upgrade? I am running a box stock version (no plugins) of 5.0.6 Plus. Thanks.

Hello All, I am suddenly getting the message "Your access to this site is not private" when trying to access my unRAID server via browser (webGUI). See attached screenshot. I never set any passwords for this server or the shares. I can however access the share via windows File Explorer. What would cause this and how do I fix it?

This command: http://tower/main.htm?cmdSpinUpAll=Spin%20up works fine for my OLD version (4.7) of unRAID to spin up all drives. Can someone post the actual HTTP command (similar to form of the above command) for versions 5.0 and above? Thanks The_Keymaker

The issue turned out to be a bad drive. I replaced the drive and the error messages went away.

Here it is. Entire syslog attached. Thanks! SpinDown_Syslog.txt

I just built a new 5 disk server and specified the spindown for all drives at 2 hours. It appears the drives spin down successfully ( as shown by the flashing green dots in the web interface) but I hear the drives spinning up every few minutes. However, when i check the web interface, the drives show the flashing green dots indicating the drives are still spun down. So i checked my syslog and found the following: Mar 20 21:30:59 MediaServer00 kernel: mdcmd (89): spindown 0 Mar 20 21:31:00 MediaServer00 kernel: mdcmd (90): spindown 1 Mar 20 21:31:00 MediaServer00 kernel: mdcmd (91): spindown 2 Mar 20 21:31:01 MediaServer00 kernel: mdcmd (92): spindown 3 Mar 20 21:31:03 MediaServer00 kernel: mdcmd (93): spindown 4 Mar 20 21:35:44 MediaServer00 kernel: ata1: lost interrupt (Status 0x50) Mar 20 21:35:54 MediaServer00 kernel: mdcmd (94): spindown 0 Mar 20 21:37:55 MediaServer00 kernel: ata1: lost interrupt (Status 0x50) Mar 20 21:38:05 MediaServer00 kernel: mdcmd (95): spindown 0 Mar 20 21:40:06 MediaServer00 kernel: ata1: lost interrupt (Status 0x50) Mar 20 21:40:16 MediaServer00 kernel: mdcmd (96): spindown 0 Mar 20 21:42:17 MediaServer00 kernel: ata1: lost interrupt (Status 0x50) Mar 20 21:42:27 MediaServer00 kernel: mdcmd (97): spindown 0 Mar 20 21:44:28 MediaServer00 kernel: ata1: lost interrupt (Status 0x50) Mar 20 21:44:38 MediaServer00 kernel: mdcmd (98): spindown 0 Mar 20 21:46:39 MediaServer00 kernel: ata1: lost interrupt (Status 0x50) Mar 20 21:46:49 MediaServer00 kernel: mdcmd (99): spindown 0 Mar 20 21:48:50 MediaServer00 kernel: ata1: lost interrupt (Status 0x50) Mar 20 21:49:00 MediaServer00 kernel: mdcmd (100): spindown 0 Mar 20 21:51:01 MediaServer00 kernel: ata1: lost interrupt (Status 0x50) I've [posted only a fragment of the entire log as the "lost interrupt" messages go on and on. Can someone explain what is going on here? I fear the drives attempting to start up like this over and over will shorten their life.

Thanks for the extra insight guys. It just seems there should be a simple option/command/operation (like HDAT2) that is part of unRAID or the Linux OS that would clear the HPA area when requested. The_keymaker

Thanks Mazma, I used HDAT2 instead as I was getting nowhere fast using "HDPARM" I'm wondering why preclear just doesn't clear/erase the ENTIRE drive and storage area, including any HPA data. Regards, The_keymaker

I started a 5 disk (all 2TB) unRAID server build with an old Gigabyte board I had laying around. I checked the BIOS and it did not indicate there were any BIOS protection schems or HPA issue. Anyway, to make a long story short...when i went to assign disks in to the array, one of the disk's capacity ended in "492" while all others were "552": an indication of HPA at work. I have since used a new board. My questions is, wht do I need to do to return the affected disk back to normal so its capacity reads "552" like the others? Thanks!