[Slow transfer of local files to unraid]

As mentioned, many small files will always be slower, this is normal with any OS, it will be the same if you transfer from one Windows PC to another.

[Native Install of ZFS on Unraid]

21 minutes ago, donglobal said:

but How would l use ZFS for the array and also have an old flash drive in there as well?

If you want to use zfs won the array you don't need the flash drive.

 

21 minutes ago, donglobal said:

Would I get the benefit of speed that a pool of disks formatted in ZFS would get if I do it this way?

Not in the array.

 

22 minutes ago, donglobal said:

Or is it just worth waiting until the next version of Unraid which apparently will have a full implementation of ZFS to do my install?

Nest release will still require an array device assigned, at least that's the last I heard, but you can already do a full zfs implementation, if like mentioned, you use a flash drive to fulfill the array device requirement.

[Native Install of ZFS on Unraid]

51 minutes ago, donglobal said:

it seems that even when using ZFS for all disks, one still needs to maintain a separate drive/disk in the array. Is this correct?

The issue is not using zfs for all, you can also use zfs for the array, but for now, at least one device must be assigned to the array if you want to only use pools, an old flash drive will do it.

[Slow transfer of local files to unraid]

Copying many small files will always be slower than large ones, but you should see a nice boost if you set the share to exclusive mode, or use a disk share.

[Booting into GUI gives blank screen and blinking cursor]

29 minutes ago, Thunderhead said:

I tried the NON-UEFI boot option as described above and got 'This is not a bootable disk.

Run the make_bootable.bat as admin, syslinux is not needed for UEFI boot, but it is for legacy, and make sure the flash drive is still the first boot device.

 

 

[Disk Error - Help needed to understand]

The SMART report for that disk, this part:

 

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%     58305         -

 

[Cache drive unmountable after a server crash]

The pool is using the single profile, i.e., not redundant, and it will only mount if both devices are available, you can convert to raid1 to make it redundant.

[Lost all files in two large shares after failed disk replaced.]

Check filesystem on disk4, run without -n and if it asks for it, use -L.

[Change default XFS format settings to reflink=0]

1 hour ago, Konstellis said:

May it have something to do with the drive being formatted as encrypted xfs? I would like to keep it encrypted...

Yes, if the drive is encrypted, and still in maintenance mode, you need to use: /dev/mapper/mdXp1

[Change default XFS format settings to reflink=0]

13 minutes ago, Konstellis said:

If I try to use makfx.xfs on the disk I get "mkfs.xfs: cannot open /dev/md2p1: Device or resource busy" (also in maintenance mode).

md device should not be busy in maintenance mode, try rebooting

[Cache drive unmountable after a server crash]

Those appear to be the same diags as before, would need current ones, with the pool mounted.

[Mover not moving files because "File exists"]

IMHO it can be considered a bug regarding the errors logged, which are misleading, the behavior itself would be expected, i.e., if the share is set to use one pool, the mover won't move any data from the same share in a different pool.

[Cache drive unmountable after a server crash]

If it's configured as a redundant pool yes, you can post new diags to confirm.

[Cache drive unmountable after a server crash]

Post the output of

btrfs fi show

 

[need help I/O error, dev sdc, sector 64 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2]

Once a disk gets disabled it needs to be rebuilt, but first post new diags to see if the ATA errors are gone.

[Mover not moving files because "File exists"]

Hmm, error may be caused by the file existing in a different pool, media share is set to use the pool "downloads", but those files are in the pool "server", change the share to use the pool server, other settings should remain the same, and run the mover again.

[need help I/O error, dev sdc, sector 64 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2]

For both?

[BTRFS Cache drive failed, how to restore and update to ZFS?]

One of the NVMe devices dropped offline, power cycle the server, don't just reboot, to see if it comes back and post new diags after array start.

[Disk Error - Help needed to understand]

SMART test passed so the disk should be OK for now, keep monitoring, you can also replace/swap cables to rule that out if more errors occur.

[Mover not moving files because "File exists"]

Post the output of

 

find /mnt -name 01\ -\ Cannonball.mp3

 

Search can take some time, wait until you get the cursor back before posting the output

[Random hard crashes]

Server is running out of RAM, see if you can fix that first by limiting the RAM to VMs/containers.

[Two parity check runs, both finished with 1 error.]

One possible explanation would be the first time that bit was wrongly correctly, like from a bit flip, so the second pass would correct it again, but you appear to be using ECC RAM, so that should not happen, possible an issue with one of the devices, run another check when possible to see if more errors are found.

[Pool disk not recognized]

Only one NVMe device is being detected by Linux:

 

21:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808]
    Subsystem: Samsung Electronics Co Ltd SSD 970 EVO/PRO [144d:a801]
    Kernel driver in use: nvme
    Kernel modules: nvme

 

This is not a software issue, try swapping both NVMe devices and see where the problem follows.

[Flash drive failed, how to move to a new one]

You just need to restore the complete /config folder, from a backup or from the old flash if still readable, then transfer the key.

[Pool disk not recognized]

Please post the diagnostics.