March 1, 20251 yr Followed the documented procedure to upgrade a drive - I removed a 1 TB drive, and added in a used (new to me) 3TB. Start the array and get an error, device disabled: I try a few things, run a short smart test, run an extended Smart test - both pass. remove from array, add back to array. Reseat the drive, check the cables. Issue persists. So, I put the 1 TB drive back and Unraid now give me the message: Ideally I get the 3TB drive up and running, but honestly, I just want stability and to get things back and happy. Any suggestions? Thanks. tower-diagnostics-20250228-1905.zip
March 1, 20251 yr Community Expert SAS disks can sometimes be write protected, see if you can confirm that, another option, assuming the old disk is healthy, would be to do a new config, then run a parity check.
March 1, 20251 yr Author Interesting, it's not looking likely though. This is from the manual: https://www.seagate.com/www-content/product-content/constellation-fam/constellation-es/constellation-es-2/en-us/docs/100628615k.pdf and this is the from the log (screenshot posted above) I'll keep looking into it though, see what I might find.
March 2, 20251 yr Community Expert I also didn't see that mentioned, sometimes it's even on SMART, but there are different kinds of protection for SAS disks, and it's strange the disk failing to write at the first sector: Feb 28 11:07:26 Tower kernel: md: disk2 write error, sector=0 Make sure it's not this: https://forums.unraid.net/topic/110835-solved-help-with-a-sas-drive/#findComment-1011689
March 2, 20251 yr Author There is no PSID printed on the drive for me to pass to the SEDUTIL command: All the google results tell me it would be printed in the empty box at the bottom of the label.
March 4, 20251 yr Author I installed Unassigned Devices Plus, and enabled Destructive Mode in the settings. I now have the option to clear the disk. I selected it, typed yes.... and the dialog box said "Success". The UI however, did not change, and this was in the log:
March 4, 20251 yr Community Expert Disk is still not accepting any write requests, possibly there's still some protection, or it's just bad.
March 22, 20251 yr Author I found this reddit post: https://www.reddit.com/r/homelab/comments/jouzh7/truenas_cant_wipe_3tb_seagate_drive/ with my exact HDD Make/Model/Size: SEAGATE DKS2D-H3R0SS Using the suggested command: sg_format --format --size=512 -6 -v -e -v /dev/sdc I then tried to watch the status with the suggested command: scsi_ready /dev/sdc but that actually crashed after some time, and would not work again. I then found and used this command (sg_turs) for a status: https://manpages.ubuntu.com/manpages/xenial/man8/sg_turs.8.html which now successfully gave me a Percentage status on the drive and both commands ran for over 12 hours and then finished. The drive showed in Unraid with an available format option which I tried again. I have the same I/O errors, but now in more than just sector 0. So, I'm in the same state (unable to add to array) despite a more successful format occurring via the sg_format command. I have found other posts with the same issue, with the same drive, but no real answers. I'll keep looking. FYI tower-diagnostics-20250322-1212.zip Edited March 22, 20251 yr by jeradc added link
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.