Hi there,

I just finished my third server mainly for downloads and Adguard/Unbound:

 

- ASRock J5040

- 2 x 8GB Ram

- 1 x 1TB WD SSD for cache -> ZFS

- 1 x 1TB WD SSD for Array drive -> XFS

- no parity drive

 

I learned that the Trim command is not working (yet) for SSDs in the Array.

Should I reformat the Array disk to ZFS?

Is 16GB Ram enough?

 

 

Thank you.

11 hours ago, Civic1201 said:

Should I reformat the Array disk to ZFS?

You can but trim still won't work, recommend assign both as pools, you can use an old flash drive for the array.

Ok I used a cheap 4GB stick for the array, but after reboot I receive the message:

Quote

Disk 1Generic_Flash_Disk_95B550AC-0:0 - 4 GB (sdb)*0.0 B/s0.0 B/s0xfsUnmountable: Unsupported or no file system

After clicking formating the drive is fine. This is normal? I choosed xfs format.

Yes when you first add a Disk to the Array it needs to be formatted by unraid to initialize it, unless you importing in an existing array or pool

Yes I know, but this i sgoing to happen after every reboot. Not a big deal, just asking.

One more question. Sleep time is set to the minimum -> 15 minutes. This means the stick is "sleeping":

 

Now that it is part of the array it should not need formatting on restart. should just be in the array when you start it.

If you mean Spin down delay 15 minutes then after no accessing of the drive for that time the Green dot will go grey and put the drive in a low power state, not sure if those states work on USB flash drives though. You can also click on the green dot and see if it goes grey.

I may found the reason for this bahaviour, please let me know what you think about it.

I am using this adapter for the unraid stick + the stick for the array -> both are connected to this adapter:

 

 

I just ordered a new adapter just for the array stick, maybe this will help:

 

okay, adapter arrived and I installed it. So Unraid drive is directly connected to the motherboard and the array drive is connected to the USB2.0 port -> IO shield.

After reboot the array drive needs stil to be reformated. Any ideas?

2 hours ago, Civic1201 said:

After reboot the array drive needs stil to be reformated. Any ideas?

Was it already formatted once?

Yes to xfs. This happens after every reboot and I have to reformat the drive again.

Format the device, reboot , and post new diags after array start.

3 minutes ago, JorgeB said:

Format the device, reboot , and post new diags after array start.

It is running now in xfs, should I stop the array and format it again or just reboot?

Just

41 minutes ago, Civic1201 said:

reboot , and post new diags after array start.

 

Here you go. 

 

 

tower-diagnostics-20240327-1411.zip

Edited March 27, 20242 yr by Civic1201

XFS is detecting metadata corruption:

 

Mar 27 14:09:02 Tower kernel: XFS (md1p1): Corruption warning: Metadata has LSN (1:23) ahead of current LSN (1:0). Please unmount and run xfs_repair (>= v4.3) to resolve.
Mar 27 14:09:02 Tower kernel: XFS (md1p1): log mount/recovery failed: error -22

 

Suggest trying with a different flash drive

 

 

Yes. that did the trick! Had some issues with cheap stick without SN (warning in Unraid) and an unstable 64GB USB3 stick. Finally a 4GB USB2 drive is running and no issues after reboots.

 

So this problem is solved. Still problems with Unraid Connect backup (coruppted). Maybe you have an idea:

Thanks again for your help.

 

Sorry, can't help with the other issue, someone from Connect support should get back to you in that thread.