23TB free space array is full, some or all files unprotected and mover not moving much

[Arby]

I have some issues with my unraid server, it seems to be full, despite have 23TB free. I suspect it might have something to do with the "Some or all files unprotected" warning next to some of the shares. One of my caches, which is a pool only have 143GB free, and manually clicking the mover isn't doing much.

 

Please could you help me figure out what I need to?

 

 

 

 

servername-diagnostics-20230104-1237.zip

[JorgeB]

You are having issues with Protected_cache1:

 

Jan  1 22:51:25 Arborstone kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 22:51:25 Arborstone kernel: ata2.00: irq_stat 0x40000001
Jan  1 22:51:25 Arborstone kernel: ata2.00: failed command: WRITE DMA EXT
Jan  1 22:51:25 Arborstone kernel: ata2.00: cmd 35/00:08:60:26:71/00:00:69:00:00/e0 tag 7 dma 4096 out
Jan  1 22:51:25 Arborstone kernel:         res 51/04:08:60:26:71/00:00:69:00:00/e0 Emask 0x1 (device error)
Jan  1 22:51:25 Arborstone kernel: ata2.00: status: { DRDY ERR }
Jan  1 22:51:25 Arborstone kernel: ata2.00: error: { ABRT }
Jan  1 22:51:25 Arborstone kernel: ata2.00: supports DRM functions and may not be fully accessible
Jan  1 22:51:25 Arborstone kernel: ata2.00: failed to enable AA (error_mask=0x1)
Jan  1 22:51:25 Arborstone kernel: ata2.00: supports DRM functions and may not be fully accessible
Jan  1 22:51:25 Arborstone kernel: ata2.00: failed to enable AA (error_mask=0x1)
Jan  1 22:51:25 Arborstone kernel: ata2.00: configured for UDMA/133 (device error ignored)
Jan  1 22:51:25 Arborstone kernel: ata2: EH complete
Jan  1 22:51:25 Arborstone kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  1 22:51:25 Arborstone kernel: ata2.00: irq_stat 0x40000001
Jan  1 22:51:25 Arborstone kernel: ata2.00: failed command: WRITE DMA EXT
Jan  1 22:51:25 Arborstone kernel: ata2.00: cmd 35/00:08:60:26:71/00:00:69:00:00/e0 tag 15 dma 4096 out
Jan  1 22:51:25 Arborstone kernel:         res 51/04:08:60:26:71/00:00:69:00:00/e0 Emask 0x1 (device error)
Jan  1 22:51:25 Arborstone kernel: ata2.00: status: { DRDY ERR }
Jan  1 22:51:25 Arborstone kernel: ata2.00: error: { ABRT }

 

Check/replace cables and post new diags after array start.

[Arby]

Could this be related to the 

Reallocated sector yellow warning?

 

Protected_cache 2 has a yellow warning on this with a raw value of 690. I think it has increased over the 1-2 years I've had the server.

 

I think the cables are ok but I have been unlucky with the drive from the start. I am thinking of getting rid of the pool entirely and replacing it with just 1 big SSD - is there any documentation I can read that can show me how to replace a pool with 1 drive?

[JorgeB]

Problem is device1, not device2

[Arby]

20 hours ago, JorgeB said:

Problem is device1, not device2

 

That's strange, here is what the protected cache looks like:

 

I constantly get that error sign for protected_cache 2

 

I have just bought another one of these drives, I am going to replace protected_cache 1 as you have said that's the one with the issue.

 

I am going to have to update to 6.10-rc3 or later and follow your comment here, as I don't really want to go through the manual method - do you think that sounds like a good plan? I am just worried protected_cache 2 will also be problematic...there isn't a way unraid can mix up the device number can it? I can't really see protected cache 1 mentioned in the Diags you quoted

[JorgeB]

24 minutes ago, Arby said:

I constantly get that error sign for protected_cache 2

That device has SMART errors but the one missing is #1, note the missing temp, that's a sign the device is offline, see here for better pool monitoring.

[Arby]

43 minutes ago, JorgeB said:

That device has SMART errors but the one missing is #1, note the missing temp, that's a sign the device is offline, see here for better pool monitoring.

 

Wow...I did not know that, that should be a blaring warning ! thank you so much. I'll get to work when the drive gets here and let you know how I get on.