blu3_v2
Members
-
Joined
-
Last visited
Everything posted by blu3_v2
-
Thanks JorgeB, Array rebuilt successfully (taking 1 Day 18 Hours plus). Unraid back up and running
-
That’s what I was hoping for. Will try rebuilding on top of Emulated Disk as per the attached instructions on the weekend and report back.
-
Last night I received a notification on starting my Array that Disk1 had been disabled due to a Read Error. Unfortunately I shutdown first and checked connections before gathering Diagnostics, however, SMART Report and Check Filesystem both passed without errors on restart. I have attached Diagnostics and SMART information for the affected Disk. Could someone please take a look and let me know if the Disk should be replaced, or if it is safe to setup as New Config and the correct steps to do so via Tools > New Config. watchtower-diagnostics-20260415-2029.zip watchtower-smart-20260415-2018.zip
-
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.
-
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.
-
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.
-
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.
-
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.
-
Did you ever get this issue sorted out and your disk recognised? I have a similar problem, having just completed a Parity Disk Upgrade (4 > 8Tb). When I plugged my old Parity Drive in it is not recognised as an Unassigned Device (from the unRAID Main Tab or when using the Unassigned Devices Plugin). It was seen as an output when I ran ls -l /dev/disk/by-id from the terminal and also showed up in the recently updated Preclear Disks Plugin screen (as device sdh), however, there is no drive/model info attached to the drive and when I attempted a Preclear it failed.
