Due to delivery issues with some of the disks in my array I started my pool with a raidz1 with 3 disks (18TB Seagate Ironwolves). When I received the last 3 disks I extended my vdev 3 times, one for each disk. Each extension was successfull and a scrub was completed after each one. But TrueNAS das…

We have been discussing RAID-Zx expansion in other threads. It appears their are 2 problems with this new feature. The one you list which seems to be a GUI problem. Meaning iX probably can fix that. You might check and see if their is a bug for it already filed. The other seems to be an OpenZFS bu…

[image] Arwen: many people think RAID-Z1, (or RAID-5 for non-ZFS), with disks larger than 2TB is risky I was aware that there were differences in the risk for Z1-Z3, but I did not know that there were also differences when it came to disk size - other than the obvious that we are talking abou…

[image] 24.10 RC2 Raidz expansion caused miscalculated available storage TrueNAS General Seems like a mighty big gotchya with RaidZ expansion. This is the relevant bug report https://ixsystems.atlassian.net/browse/NAS-131728 Basically, the space available is calculated …

I see. I think my best bet to get this resolved is to move the data and recreate the pool.

[image] nicofar: I did not know that there were also differences when it came to disk size - other than the obvious that we are talking about vastly more data with 18TB compared to 2TB. The issue is that their is a chance of an unrecoverable read error, URE, occurring during the disk replacem…

[image] Arwen: Most consumer hard disk drive have specified probably UREs at 2^14, (or was it 10^14?) That is typically given as “less than 1 in 1E14” bits, whatever “less than” may mean. So p ≤ 10^-14. NAS/enterprise HDDs may be rated for “less than 1 in 1E15”, while SSDs are “less than 1 …

[image] Arwen: ANY used failed sector on the source disks can lead to data loss Does that mean that any used failed sector can lead to complete failure of rebuild, or does it mean that any used failed sector can lead to a failure to rebuild the specific file that has the failure?

For classical RAID it would be total array loss. For ZFS it is “only” loss of the specific file, but still an annoyance and something to take into account if you think that raidz1 fully protects against the complete loss of one member drive.

Happy to hear. I’m planning to keep up 1-2-3 for important data, and even then, for family photos missing one or two files will not hurt a lot anyways. The majority of my data is not unique, and I will be able to get it back if I need to. It’s mostly kept locally either as part of a 1-2-3 backup it…

Extended vdev, but no extra space

TrueNAS General

Stux November 13, 2024, 9:42pm 4

Topic		Replies	Views
Starting raidz1 with only 2 disks TrueNAS General SCALE , ZFS	8	3545	December 8, 2024
RAIDZ2 Expansion: Unexplained 10TB Space Loss & 2x Overhead TrueNAS General ZFS , RAID-Zx-expansion	8	377	October 16, 2025
[SOLVED] Planning a SCALE deployment, looking for sanity check on Vdev Structure TrueNAS General SCALE , Hardware , ZFS	21	643	April 21, 2024
Scale v24.04.2 Lost One disk, Unable to import Pool from 2nd one on new H/W TrueNAS General SCALE , ZFS	27	375	August 17, 2024
For Storage Raidz1 or Mirror and rebuild TrueNAS General Hardware , ZFS	6	160	February 25, 2026

Extended vdev, but no extra space

Related topics