Looks like one of my hdd's is dead - it is disabled now and says it had read errors. Checking out logs of the HDD and there are several reading errors.

Trying to figure out if I can safely remove it and install new bigger drive? I've attached the diagnostics archive just in case it is needed.

That actually happened after updating Unraid to the latest version

Thanks

homeserver-diagnostics-20250423-2115.zip

It's logged as a disk problem, but it dropped offline, so there's no SMART, check cables and post new diags after a reboot.

Hi Jorge,

Thank you for your answer.

I've re-checked all the cables - they look good. Restarted the system and now it says the device is not installed. Attaching diagnostics as well, and I cannot check the SMART also.

Definitely dead, right?

In case I need to change it to a bigger drive (not bigger than the parity, ofc) - is it just about replacing the drive, or it's not that simple?

Thanks!

homeserver-diagnostics-20250425-0958.zip

32 minutes ago, OlegBudeanu said:

is it just about replacing the drive, or it's not that simple?

It IS that simple. 

The process is documented here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI.  In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.   The Unraid OS->Manual section covers most aspects of the current Unraid release.

thank you itimpi

sorry to be ignorant, I am relatively new in Unraid setups, but I am happy that it IS that simple! Thanks for the links, I will check them out. I've just seen some forum posts about replacing HDD that they had to follow some procedures - rebuilding and etc. Looks like that's not my case.

22 minutes ago, OlegBudeanu said:

I've just seen some forum posts about replacing HDD that they had to follow some procedures - rebuilding and etc. Looks like that's not my case.

It only gets more complicated if there is some other factor in play such as the failed drive not being emulated correctly or showing as unmountable.

Thank you for the information.

I've removed the faulty drive (and I've found out that the SATA connection was in a very bad shape - it had a crack), and replaced it with a 3TB drive. The device rebuild process is running now. Though the speed is only 16-23 mb/sec, is it supposed to be that slow? It's a WD Red 3TB drive. I believe it's slow because it's copying a lot of small files?

The rebuild process works at the raw sector level and is not aware of the meaning of the contents of those sectors.   The speed is a little low so it could be worth posting the diagnostics taken while experiencing that speed in case it shows up some other issue.

Looks like it ramped up - it's 115 mb/sec at the moment what is pretty good!

Edited April 27, 20251 yr by OlegBudeanu

So the array was rebuilt. It took about 30 hours. But the drive is still offline, and the disk says "uninstalled". The PC BIOS sees the HDD and all the parameters. At this point, I am not sure what is happening.

I assigned the device last time to Disk 3, and it asked to be rebuilt, so I did.

After that, I rebooted Unraid, and it shows again that the disk is not installed.
I've assigned it again, it asks to rebuild again... Doing that again, the speed again is 31 mb/s and it will be rebuilding for 27 hours...

Am I doing something wrong?

I am attaching the Diagnostics.

homeserver-diagnostics-20250428-2134.zip

I am not sure if that is included in Diagnostics, but disk log shows this : 

Apr 28 15:22:37 HomeServer kernel: ata4: SATA max UDMA/133 abar m2048@0xf7c3a000 port 0xf7c3a280 irq 28
Apr 28 15:22:37 HomeServer kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Apr 28 15:22:37 HomeServer kernel: ata4.00: ATA-9: WDC WD30EFRX-68EUZN0, 82.00A82, max UDMA/133
Apr 28 15:22:37 HomeServer kernel: ata4.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Apr 28 15:22:37 HomeServer kernel: ata4.00: configured for UDMA/133
Apr 28 15:22:37 HomeServer kernel: sd 4:0:0:0: [sde] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
Apr 28 15:22:37 HomeServer kernel: sd 4:0:0:0: [sde] 4096-byte physical blocks
Apr 28 15:22:37 HomeServer kernel: sd 4:0:0:0: [sde] Write Protect is off
Apr 28 15:22:37 HomeServer kernel: sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00
Apr 28 15:22:37 HomeServer kernel: sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 28 15:22:37 HomeServer kernel: sd 4:0:0:0: [sde] Preferred minimum I/O size 4096 bytes
Apr 28 15:22:37 HomeServer kernel: sde: sde1
Apr 28 15:22:37 HomeServer kernel: sd 4:0:0:0: [sde] Attached SCSI disk
Apr 28 15:24:45 HomeServer emhttpd: online: WDC_WD30EFRX-68EUZN0_WD-WCC4N2HTSL2N (sde) 512 5860533168
Apr 28 15:24:46 HomeServer emhttpd: read SMART /dev/sde
Apr 28 15:24:55 HomeServer unassigned.devices: Disk with ID 'WDC_WD30EFRX-68EUZN0_WD-WCC4N2HTSL2N (sde)' is not set to auto mount.
Apr 28 21:35:55 HomeServer emhttpd: read SMART /dev/sde
Apr 28 21:36:26 HomeServer kernel: mdcmd (4): import 3 sde 64 2930266532 0 WDC_WD30EFRX-68EUZN0_WD-WCC4N2HTSL2N
Apr 28 21:36:26 HomeServer kernel: md: import disk3: (sde) WDC_WD30EFRX-68EUZN0_WD-WCC4N2HTSL2N size: 2930266532 
Apr 28 21:43:59 HomeServer kernel: ata4.00: exception Emask 0x0 SAct 0x3807fc SErr 0x0 action 0x0
Apr 28 21:43:59 HomeServer kernel: ata4.00: irq_stat 0x40000008
Apr 28 21:43:59 HomeServer kernel: ata4.00: failed command: WRITE FPDMA QUEUED
Apr 28 21:43:59 HomeServer kernel: ata4.00: cmd 61/40:98:80:e2:34/05:00:03:00:00/40 tag 19 ncq dma 688128 out
Apr 28 21:43:59 HomeServer kernel: ata4.00: status: { DRDY ERR }
Apr 28 21:43:59 HomeServer kernel: ata4.00: error: { IDNF }
Apr 28 21:43:59 HomeServer kernel: ata4.00: configured for UDMA/133
Apr 28 21:43:59 HomeServer kernel: ata4: EH complete
Apr 28 21:44:06 HomeServer kernel: ata4.00: exception Emask 0x0 SAct 0x1c00000 SErr 0x0 action 0x0
Apr 28 21:44:06 HomeServer kernel: ata4.00: irq_stat 0x40000008
Apr 28 21:44:06 HomeServer kernel: ata4.00: failed command: WRITE FPDMA QUEUED
Apr 28 21:44:06 HomeServer kernel: ata4.00: cmd 61/40:b0:80:e2:34/05:00:03:00:00/40 tag 22 ncq dma 688128 out
Apr 28 21:44:06 HomeServer kernel: ata4.00: status: { DRDY ERR }
Apr 28 21:44:06 HomeServer kernel: ata4.00: error: { IDNF }
Apr 28 21:44:06 HomeServer kernel: ata4.00: configured for UDMA/133
Apr 28 21:44:06 HomeServer kernel: ata4: EH complete
Apr 28 21:44:13 HomeServer kernel: ata4.00: exception Emask 0x0 SAct 0x3400 SErr 0x0 action 0x0
Apr 28 21:44:13 HomeServer kernel: ata4.00: irq_stat 0x40000008
Apr 28 21:44:13 HomeServer kernel: ata4.00: failed command: WRITE FPDMA QUEUED
Apr 28 21:44:13 HomeServer kernel: ata4.00: cmd 61/40:50:80:e2:34/05:00:03:00:00/40 tag 10 ncq dma 688128 out
Apr 28 21:44:13 HomeServer kernel: ata4.00: status: { DRDY ERR }
Apr 28 21:44:13 HomeServer kernel: ata4.00: error: { IDNF }
Apr 28 21:44:13 HomeServer kernel: ata4.00: configured for UDMA/133
Apr 28 21:44:13 HomeServer kernel: ata4: EH complete
Apr 28 21:44:20 HomeServer kernel: ata4.00: exception Emask 0x0 SAct 0x38000 SErr 0x0 action 0x0
Apr 28 21:44:20 HomeServer kernel: ata4.00: irq_stat 0x40000008
Apr 28 21:44:20 HomeServer kernel: ata4.00: failed command: WRITE FPDMA QUEUED
Apr 28 21:44:20 HomeServer kernel: ata4.00: cmd 61/40:78:80:e2:34/05:00:03:00:00/40 tag 15 ncq dma 688128 out
Apr 28 21:44:20 HomeServer kernel: ata4.00: status: { DRDY ERR }
Apr 28 21:44:20 HomeServer kernel: ata4.00: error: { IDNF }
Apr 28 21:44:20 HomeServer kernel: ata4.00: configured for UDMA/133
Apr 28 21:44:20 HomeServer kernel: ata4: EH complete

 

A lot of errors and I am not sure what they mean. This HDD is faulty as well?

Why did you use a 9 year old disk for the replacement?

 

Check connections, then run an extended self-test on that disk.

This HDD was working on an old NAS, but for the last couple of years, it was just turned off.

Doing it now, the short test showed no errors.

Unrelated, your "default shares" would be better if they were all on cache and configured to stay on cache:

https://docs.unraid.net/unraid-os/manual/shares/user-shares/#default-shares

 

And 100G docker.img is probably many times larger than needed.

 

We can work on those when your array is stable again.

 

13 minutes ago, OlegBudeanu said:

This HDD was working on an old NAS, but for the last couple of years, it was just turned off.

The 9 years I was talking about was Power On Hours, so the "turned off" years were not counted.

 

I would really just recommend a newer drive. You have 12TB parity so you could go larger than that old 3TB. And newer larger disks are faster than older smaller disks simply due to data density.

Thanks, I will definitely replace it a bit later, it's just that now I don't have any more options.

Can you please elaborate on the previous post? there is 100gb docker image ?!

5 hours ago, OlegBudeanu said:

I will definitely replace it a bit later, it's just that now I don't have any more options

So you still have a disabled disk according to those last diagnostics. Which means you currently have no further protection from parity.

 

19 hours ago, trurl said:

We can work on those when your array is stable again.

In the meantime, I recommend going to Settings - Docker and disable

Sorry for not updating - the last diagnostics report was done during the re-building process.

Now it finished and the array is green, looks like everything is OK

https://docs.unraid.net/unraid-os/manual/shares/user-shares/#default-shares

 

Ideally, the "default shares" should have all files on cache or other pool, with no files on the array, so Docker/VM performance will not be impacted by slower array reads and especially writes, and so array disks can spin down since these files are always open.

 

Your domains, isos, and system shares are all on the array. Normally, the system share only has 2 files in it, but your system share is on 3 different array disks. appdata is all on cache so that's OK.

 

Do you have any VMs?

 

 

Thanks for the info. I think I will need to buy bigger cache disk, at least 1TB to handle all the shares.

There are no VM's for now.

You should reduce docker.img to about 40G, that will save some space.

 

5 minutes ago, OlegBudeanu said:

at least 1TB to handle all the shares

What do you get from command line with this? (may take a while to complete)

du -h -d 1 /mnt/user

 

17 minutes ago, OlegBudeanu said:

Sorry for not updating - the last diagnostics report was done during the re-building process.

Now it finished and the array is green, looks like everything is OK

Post new diagnostics so I can see the result of that extended self-test

Attached the diagnostics, the command is still gathering the info.

I've just noticed that there are read errors... Looks like I still have to buy a new drive to be on the safe side.

homeserver-diagnostics-20250429-1812.zip

Definitely a failed disk

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%     11649         21530816
# 2  Extended offline    Completed: read failure       90%     11647         21530816

Replace immediately

thanks, will do that asap

btw this is the result of the command 

984G    /mnt/user/Family
12K     /mnt/user/.bzvol
9.5T    /mnt/user/work
99G     /mnt/user/system
72G     /mnt/user/Media
31G     /mnt/user/music
24G     /mnt/user/backup
1.4T    /mnt/user/data
525G    /mnt/user/Photos
4.0K    /mnt/user/FilerunData
0       /mnt/user/SHARE
28K     /mnt/user/Downloads
1.3G    /mnt/user/domains
0       /mnt/user/Speed Test
0       /mnt/user/isos
0       /mnt/user/mysql
48K     /mnt/user/Personal Data
4.0K    /mnt/user/dashy
11G     /mnt/user/appdata
13T     /mnt/user