steve1977

Thanks. As I cannot mount the disk, I don't have sdc1. See below. Any thoughts? root@Tower:~# xfs_repair -v /dev/sdc1 /dev/sdc1: No such file or directory /dev/sdc1: No such file or directory fatal error -- couldn't initialize XFS library

Other disks work in this slot, so very unlikely a cable issue. Still any hope to add the disk to the array with "new config" and run some of the check things from the link above (https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/file-systems/#checking-a-file-system). Or already reached the stage where I need to move on?

The "fallen" disk was not part of the array, but UD. The linked guide asked me to run the array in maintenance mode. Shall I add the disk to the array as "new config" and then start in maintenance mode? Don't want to make things worse, so checking with you first. Thanks for your help!

Tried the repair. Got error below: root@Tower:~# xfs_repair -v /dev/sdc Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error

I checked and cannot run SMART. The log gives me below. I will try "check file system" next. === START OF READ SMART DATA SECTION === Read SMART Log Directory failed: scsi error data protection error Read SMART Error Log failed: scsi error data protection error

Unfortunately, I moved it from the original disk (not copied) :-( I can plug it in. When connected in usb enclosure, it shows properly, but cannot mount (though "mount button" shows up). When I put it inside the actual server case, it also shows, but doesn't allow to mount, but gives me the option to "format" it. I can try to get a SMART report later (once back home).

What a drama... I copied things from the disk and succeeded to recover 99% of all files. But you won't believe what happened then... I dropped the new disk with all the recovered content from around 1m to the floor. And now this disk no longer mounts (for obvious reasons). Any idea whether something can be rescued now beyond spending a fortune on some forensics company?

Thanks for your help. I replaced the disk and now things are working.

No. At least not yet... I have stopped parity built and now trying to copy the files out. Fingers crossed that this allows me to save some of the data. After this is done, I will do a thorough smart check on all disks. And once completed, I will rebuild parity. This may well take a few days. Fingers crossed! Shows the risk of building parity "fresh". I downsized one disk from 28TB to this faulty 16TB drive. Thought the quickest way to do this was to rebuild the parity from scratch. Should have looked for other ways.

Would you suggest I stop parity and try to copy the files over to another disk? Or let it finish first?

I have set up a new Unraid array. I am now building parity. While parity is still building, disk 3 shows errors. Building parity continues. Attaching diagnostics. Is the disk faulty? If so, what's the best way to replace it? tower-diagnostics-20260219-0823.zip

I cannot rule it out, but I don't think it is the 3.3V issue. I have other disks (same model), which don't face the issue. I also tried to use the "unidentified" disk in other slots, but without success either. I mounted the "unidentified" disk as UD (which works). I ran an "extended smart" check, but it doesn't complete (stuck at 10%). Also noticed an "UDMA CRC error count", but remember seeing somewhere that this should typically not be an issue? See more details below. Any other ideas what I can try? Error 54 occurred at disk power-on lifetime: 24570 hours (1023 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 53 00 00 00 00 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- b0 d5 07 04 4f c2 00 00 03:29:56.984 SMART READ LOG b0 d5 01 04 4f c2 00 00 03:29:56.945 SMART READ LOG b0 d5 01 09 4f c2 00 00 03:29:56.942 SMART READ LOG b0 d5 01 06 4f c2 00 00 03:29:56.940 SMART READ LOG b0 d5 01 01 4f c2 00 00 03:29:56.937 SMART READ LOG

Let me check this out once back home. Thanks for your help!

Oh... Thank you. This is quite likely to explain it. Don't think I have such an adapter, but can look into. Before doing this, maybe worth trying to connect it to a different slot? Either to a controller card rather than mobo. Or a different psu psu rail. It works when in an usb enclosure, so maybe there is a way to also get it to work without adapter. I also need to check, but I believe I have another identical 16TB disk that is working. Disk 3 or disk 4 should be the same disk and is also connected to the mobo? Maybe I swap this disk to see whether this works, which may help to narrow the issue.

Yes, the disk works in an external USB enclosure. Other disks work though in the same disk slot. In the new diagnostic, I plugged in an 28TB disk instead, which is well identified and works well. So, the 16TB disk only works in USB enclosure, but not when attached to the mobo. The 28TB disk works both in USB enclosure and also when attached to the mobo (same slot).

It must be somewhat related to either the disk or to Unraid / settings. I just swapped again the UD and the mobo disk. And all works well. The previously unidentified disk is now UD. I even mounted it. Including diagnostics. tower-diagnostics-20260205-0912.zip

Some disks are on mobo and others are with a controller card. I forgot where this disk is connected to, but it's the same as disk 1. Power should be more than sufficient with a 1650W PSU.

The same as disk 1 (ZXA0Z649)

I am running Unraid headless and cannot access the Bios. I can attach the disk via usb and can see it. The issue is not the sata slot though as other disks can be identified though. Maybe the answer is as easy that the disk is "faulty", but wondering whether there is some easy to way to figure this out?

Attaching the diagnostic log. Please don't worry about the missing disk 2. This has intentionally be removed for now. What's weird is that I have a disk slotted in (16TB), which is not being picked up by Unraid. If I boot with the disk, Unraid doesn't even boot up. If I plugin the disk after Unraid boots, it doesn't show up / identify. Does the diagnostic provide any indication what's going on? tower-diagnostics-20260205-0801.zip

All worked out well, thank you

A bit worried about data loss, so let me double-check with you that I am doing the right steps. Terminology: This Unraid does not have an Unraid Array. I tried to create one with one of the ZFS disks from the ZFS pool, but this did not work. I would now "stop array" (currently enabled for another pool). Then on command line, I'd run "zpool export disk1". Then I add a new ZFS pool. To this pool. I add both of my ZFS disks (order does not matter). And then hopefully my data is back. Is this right?

pool: disk1 state: ONLINE status: Some supported and requested features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: resilvered 15.0T in 1 days 08:07:46 with 0 errors on Fri Jan 16 18:10:47 2026 config: NAME STATE READ WRITE CKSUM disk1 ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 sdb1 ONLINE 0 0 0 sdc1 ONLINE 0 0 0 errors: No known data errors

Thanks, here we go: no pools available to import

Shall I create a zfs pool again and then post this log? At current stage, it’s removed. Shall I recreate it with both disks? Does the order matter?