blu3_v2

I have a HP N40L Microserver running 6.7.2 with no issues. After installing the 6.8.0 Update via Update OS and rebooting, my Array Devices in the Unraid GUI are all missing/blank - even my boot USB. Strangely the GUI reported Configuration Valid, however, instead of attempting to Start the Array I captured Diagnositics and downgraded back to 6.7.2 until this Issue can be explained/resolved. Daignostics Diagnostics.zip Before After This is the first time I have had an unsuccessful Update using Unraid, and would like to update to the current stable version rather than remain on a deprecated release. Could someone please take a look and provide some advice.

After blowing apart the server again, rechecking and re-seating all drives and connections I sat down and read through any logs from the Diagnostics.zip that I could decipher. I could not find any errors in SMART reports etc. and the syslog captured showed no errors, and the server had started up successfully and was ready to start with a Valid Array prior to logging in via Telnet and issuing the Poweroff command. I then set about troubleshooting any other potential issues and thought I would try reboot my Modem/Router, and all wireless iOS devices that I use to access the server on my LAN. After booting up the server (again) I was able to access the GUI, Start the Array, and access all Dockers etc. (all using my original Cache Drive so all Dockers and Data were preserved including in-progress downloads). So it appears that it was simply a LAN issue (IP conflict, hardware issue with Router???).

Firstly a little about my setup: - HP N40L Microserver running unRAID 6.7.2 with 6 Data Drives (8Tb Parity, 1 x 8Tb Data + 4 4Tb Data) and 1 Cache Drive (500Gb) - System is used simply to download and store media files on my local network, and is attached to APC UPS and hardwired directly to Wi-Fi Modem/Router, otherwise all access is via Wi-Fi via various devices (iOS) - Dockers: just the basics - Plex Media Server (LimeTech), ruTorrent (Linuxserver.io) and Sickbeard (all up to date with latest versions) - Uptime prior to Crash was 52 Days, and Parity was last checked only 2 Days ago, with 0 errors. System has been rock-solid and I have never encountered any major problems. The Incident: Last night I arrived home from work, opened up ruTorrent and added a couple of magnet links. After adding the links ruTorrent became unresponsive. Seeing that there have been issues with various versions having 100% CPU usage and I often see the docket reboot itself I was not too concerned. I waited a couple of minutes and tried again but could not reach ruTorrent so I tried unRAID Home with the same result - no GUI access. I fired up Termius and logged in via Telnet successfully, so issued the 'Poweroff' command so shut down the server (stupidly forgetting to save a Syslog or Diagnostics as I did not initially think much of the freeze). On reboot I was able to access the GUI, the Array was valid and all Array Drives present but I noticed that my Cache drive was missing from list of available Drives. I initially thought that maybe my old spinning rust disk had died, being the cause of the crash. I tried opening the syslog from the GUI but it had become unresponsive again. I figured that the 'dead' disk was causing slow reads/errors so logged in again via Telnet successfully and shut down again. I opened up my server and replaced the Cache Drive with a (Brand) New SSD I had in the cupboard and booted back up. When I first booted I opened the GUI successfully but noticed multiple Array Drives missing. I quickly shut the server down (via GUI), opened it backup and checked/re-seated all connections. On rebooting I was sucessfully able to access the GUI and confirm that all Disks were present, Array was valid, and new Cache Drive detected. I assigned the new Cache Drive and clicked Start to start the Array but the GUI did not respond. At this point I was becoming seriously concerned. I thought maybe my motherboard had grenaded and was dropping disks, so tried to connect via Telnet but this did not respond initially either. After trying again I was able to access the server via Telnet and confirm that all Disks were present and detected using the ls -l /dev/disk/by-id command. I then shut down again, and did some research online about what steps to take. I rebooted the server (again) and this time was unable to access the GUI at all (previous times I had been able to load the unRAID Home page, but it had not responded to commands), but could still Telnet in. I saved a copy of the Syslog and Diagnostics, which I have attached to this post (Note: on issuing the Diagnostics command I received a few lines of errors referencing missing info and giving line references to dynamix files etc, but the command completed successfully). I am seeking the help of the unRAID community in diagnosing/fixing this issue. I have always found the community super-helpful and have been able to resolve any minor issues I have had in the past. At this point I am not sure what hardware is to blame (Mobo, RAM, USB/Boot Drive), or if it could be a Software issue with a corrupt file(s). Could someone more knowledgeable than me take a look at the attached Diagnostics, help diagnose the cause(s) and/or let me know if there are any other steps I should take. syslog.txt watchtower-diagnostics-20190820-2108.zip

I also tried downgrading due to the previously mentioned CPU usage issue, however, since doing so my RSS Feeds no longer automatically update and files/folders are no longer automatically moved to their Tagged Directory (ie. TV/Movies) once downloads complete. I can manually Refresh Feed and downloads start fine. I have so far tried restarting the Docker and returned to the latest build and these problems persist. I am guessing it is a permissions issue - could someone please some advice on what to check or how to fix permissions (I thought this was performed automatically on Docker start). Update: Deleted Docker and reloaded from template (Latest) and the issues seem to have been resolved for now.

Another user checking in with unscheduled Parity Checks. Like Harro, KernelG and others I have a custom schedule (Checks scheduled for the first Monday of the month every 3rd month), and since updating to 6.6.1 Parity Checks have commenced EVERY Monday. Tried editing settings and selecting Apply, then Done but settings are ignored. From the 6.6.2 Release Notes this bug does not seem to have been fixed so thought I better post my experiences here

I could not see anything from the Release Notes, but does anyone know if 6.6.2 fixes the issue of Custom Parity Check Schedules being ignored. I have Checks scheduled for the first Monday of the month every 3rd month, and since updating to 6.6.1 Parity Checks have commenced EVERY Monday.

Just wanted to give a huge thanks to johnnie.black for the advice. I ordered a replacement PCIe SATA card (this time using an ASMedia chipset), installed it over the weekend, and now all drives are successfully recognised. I have just completed a Preclear and Parity check successfully, and old Parity has now been added to the Array. Thanks again for the expert advice.

Thanks, that is a relief.

As Drive 5 was not yet part of the Array and still showing as Unassigned, I was able to stop the Array and change Drive 5 to No Device. When I restarted the Array, Parity was still displayed as valid. Hopefully I don't have any Parity issues with the drive removed from the array before being successfully added. On checking the System Log I was getting constant errors as the system tried to spin this drive down. Once it was as Unassigned, it was still throwing errors into the Log. I have been advised by a helpful forum member that the Marvell controller on my SATA card is notorious for dropping disks, and still suspect dodgy cabling, so I have unplugged this drive from my server until I can source and now PCIe SATA card and cable.

Disk 4 has been on the same controller for a few weeks and has undergone a change from ReiserFS to XFS, as well as a complete Parity Check without issues. I set Disk 5 as No Device rather than attempt to add the old Parity back to the Array for now as it was giving errors while trying to Spin Down, and even now when Unassigned. I will unplug it until I can source a new SATA card and/or cabling.

Hi, After successfully upgrading my old and previously healthy 4Tb Parity Disk to a new 8Tb Disk and converting my entire array to XFS, I attempted to add the now Unassigned old 4Tb to the Array as additional storage (after re-checking Parity which showed 0 errors). However, the Process Aborted shortly after starting and now I am left with the old Parity Drive (Drive 5) having a Blue Square beside it. Could someone please take a look at my Diagnostics file(s) and advise me how to proceed to either fix and add the drive to the array or remove it without harming Parity. See link for Diagnostics http://users.on.net/~jilbo/watchtower-diagnostics-20180404-1845.zip (posted from iPad) Background info. The old Parity Disk in question was removed from its original hot-plug bay of my Microserver and reinstalled connected to a PCIe SATA card as part of the upgrade process. The first time I booted with the old Parity connected it was not available as an Unassigned Device (could only be seen by output of ls -l /dev/disk/by-id). It was only after shutting down and re-checking cabling that it appeared as an Unassigned Device. I suspect it may have been due to a loose connection to the PCIe card, as the card is definitely working - with Disk 4 in my array successfully connected to the other port.

Looks like I spoke too soon. Shortly after starting the Clearing process I received Read errors and the Process Aborted. Have posted in General Support section as unrelated to this plugin.

My old Parity Drive was perfectly healthy, and I can now report that it was correctly recognised as an Unassigned Device once I shutdown the server and triple-checked all cabling (turns out it must have a loose/intermittent connection to my PCIe SATA card). It is now undergoing a Preclear just to be safe before being added as an Array Disk.

Thanks for the tip. I just shutdown my server to check that it was not a cabling issue, and now when I boot the drive is not recognised at all. Looks like I will have to shutdown and recheck cabling again or remove the drive and see if I can format it from another system before adding to the array. I find it strange that the drive had previously been functioning perfectly in unRAID as a Parity drive, then when installed back into the same system it is not recognised. Maybe it has to do with the fact the the Parity drive contains data without a file-system or partition structure as such.