oh-tomo

Nov 18 05:48:17 Server2018 kernel: md: sync done. time=98913sec Nov 18 05:48:17 Server2018 kernel: md: recovery thread: exit status: 0 I guess with the rebuild progress frozen in the webGUI, these lines in the syslog indicate that it is done? Usually an email would be sent out when done but I guess that is also frozen.

My waiting for the rebuild to finish is complicated by the fact that the unRAID WebUI is frozen with regards to stating the progress of the disk7 rebuild. So it might be finished or ... ? server2018-diagnostics-20241118-2046.zip

Side question: Why do the smart .txt reports have "2023-12-01" in each of their filenames when the diagnostic report has a datestamp of 20241116/17? What does 2023-12-01 indicate? Also 20 minutes into rebuilding disk7, disk1 disabled and moved its device name from sdj to sdl and appeared in UD. Attempts at running an extended smart test on sdl in the command line (unRAID WebGUI didn't show any response when attempting short tests there, first under the array section as sdj hen when I noticed it was also appearing in the UD section as sdl, so switched to command line) result in "Extended offline Interrupted (host reset)" - two times. I guess I'll wait until disk7 is done rebuilding before running an extended smart test on disk1. 2024-11-17 12:48:17 smartctl -t long /dev/sdl I've been searching online for replacements for my CableCreation Mini SAS (SFF-8643) to 4x SATA Cable, 0.5m but it's hard finding quality brands at such a short length. StarTech does a 1m but 0.5m fits more suitably in my case. Also waiting for rebuilds to finish before attempting to put in a new power supply to see if that helps. server2018-diagnostics-20241117-1545.zip

I may have spoken too soon. During a data rebuild of a new disk6, disk7 went into dsbl state. Even though disk7 is in the new SilverStone cage. (and disk6 and 3 other disks) Running extended smart test on disk7 now.... server2018-diagnostics-20241116-0319.zip

Following up on my issue with Disk6 repeatedly disabling during parity checks, I’ve found a solution by switching to a new drive cage. I replaced my old drive cage, the iStarUSA BPN-DE350SS, with the SilverStone Technology FS305-12G (SST-FS305-12G). Since the swap, I successfully completed rebuilds without any drive issues, which suggests the old cage was… old. Five years old.

Should I switch to a more premium cable? Using this: "CableCreation Internal HD Mini SAS Cable 1.6 Feet/0.5M, Internal HD Mini SAS (SFF-8643 Host) - 4 x SATA (Target) Cable, SFF-8643 to 4 x SATA Cable for Controller, 4 Sata Connect to Hard Drive"

performed an extended offline test after parity check was done, smart for disk 6 seems okay -- was it a controller issue? diagnostics attached server2018-diagnostics-20241017-1400.zip

What happens if you get the settings wrong? Do you get locked out of the dashboard and unable to undo the damage?

Hello again, Thank you for the previous advice regarding the issue with unRAID recognizing two disks with EFI partitions named "EFI," leading to a persistent "Reboot" button. Despite powering off one of the devices to address the duplicate EFI partition names, the "Reboot" button remains for the still-active disk. These disks were formatted on a Big Sur iMac, and I need to keep the EFI partitions as they are to ensure they remain recognizable by the macOS system. My aim is to mount these disks on unRAID and access them remotely from the iMac for backup purposes, keeping the backup drives in a different room away from a crowded workspace. Currently, I am in the middle of a data rebuild and cannot reboot the unRAID system. I have attempted the suggested fixes, including ensuring that the disks are properly unmounted before reinsertion. However, none of these steps have resolved the "Reboot" issue. Could anyone suggest a workaround that does not involve renaming the EFI partitions or rebooting the system? I appreciate any further insights or help. Thank you!

ud_diagnostics posted! ud_diagnostics-20240508-141826.zip

Hi everyone, I'm seeking some guidance with managing an HFS+ formatted drive in unRAID. Here's a breakdown of what happened: Initial Setup: * I had an HFS+ formatted HDD connected to unRAID, appearing as dev 2 in the Unassigned Devices section. * I added a second HDD (formerly a parity drive) as dev 3 with the intention of using it as a backup destination for the HFS+ drive. Formatting and Rebooting: * Seeing no HFS+ formatting options in unRAID, I shut down the drive (dev 3) and formatted it with HFS+ on an iMac. * Upon reconnecting the formatted drive (dev 3) to unRAID, I saw a "reboot" icon next to it. Troubleshooting Attempts: * I performed a full system reboot of unRAID with both drives (in USB 3.0 docks) powered off during the process. * After the unRAID reboot and array mount, I powered on the USB docks one by one. * In the Unassigned Devices GUI, I mounted dev 2 (the HFS+ drive). This resulted in the "reboot" icon reappearing next to dev 3 (the backup drive). Current Situation: * I'm unsure how to proceed with using dev 3 as a backup destination for dev 2 within unRAID. * Does the "reboot" icon next to dev 3 require a system reboot even though it previously had no data on it? Additional Information: * I have both the Unassigned Devices plugin and the Unassigned Devices Plus (UD+) plugin installed. I appreciate any insights and advice you can offer to help me achieve my backup goals. Attached: unRAID Diagnostics Thanks! server2018-diagnostics-20240508-1230.zip

According to Seagate, Instant Secure Erase eliminates the need to physically destroy or overwrite the drive, saving time, money, and resources. Maybe @stereobastler has figured out how to get ISE to work on unRAID in the 3 years since starting this thread:

I would like to use this quick erase functionality on an IronWolf Pro HDD. I downloaded the SeaChest utilities as described in this thread: But I get "RevertSP is not supported on this device" when using that option with Seagate's SeaChest_Erase tool. The SeaChest Erase readme has a section "Enabling TCG Commands In Linux" and the below thread describes how to set libata.allow_tpm to 1 on unRAID, which I did and rebooted. Still "RevertSP is not supported on this device." Then I tried connecting the HDD to a SATA port on the motherboard instead of LSI 9300-8i LBA to see if that made a difference with the libata change. Still "RevertSP is not supported on this device." I don't see anything on Seagate's website saying this model (ST16000NE000-2RW103) is *not* SED. Seagate chat support claimed it is SED and after more questions ended the chat with "The recommendation we could provide is to contact with unRAID to further support." There's a PSID on the label. Why would there be a PSID on the label if it wasn't SED capable?

The Data-Rebuild with the new drive finished so I was able to shut down and connect the old drive directly to SATA data & SATA power with the unRAID PC and on power up it appears in unassigned devices. The old drive is an Iron Wolf Pro and there's a PSID number on the label -- can I use this PSID to do a Instant Secure Erase and save time compared what sounds like a lengthy preclear read/write/read/confirm operation for a 16TB HDD? It would be nice to know if a faster erase for RMA option is possible for this and any future RMAs.

Thanks for your suggestion! I appreciate you taking the time to help. As you mentioned, pre-clear is a valuable tool for checking drive health. However, my primary focus is securely erasing the data on this drive before returning it for RMA. My understanding is that pre-clear focuses on read-modify-write cycles for data integrity, while secure erase specifically overwrites the entire drive with patterns to render data unrecoverable. Perhaps there are specific pre-clear functionalities that you're aware of that might be suitable for secure erase in this case? I'd be happy to learn more if that's the case.