Recovering a degraded pool, failed to create mountpoint as filesystem is Readonly

TrueNAS General
,
1

Hello Truenas Community,

I have a pool of RAIDZ1 with 3x drives. one of the drives failed and i want to replace said drive. After restarting the system and plugging in the replacement drive and started the disk replacement, the disk within the pool got exported unexpectedly and couldn’t be imported back to the pool.

image
image1745×874 104 KB

I’ve tried zfs import -fF but it wouldn’t budge. so then I tried zfs import -fFX to rollback and the disks started resilvering until the vdev with 2x disks is recognized again.

image
image822×368 8.71 KB

image
image901×563 23.5 KB

but now I couldn’t get to mount the system and dataset after trying ‘zfs mount -a’ as it output

root@truenas[/]# zfs mount -a
cannot mount ‘/AV-NAS2’: failed to create mountpoint: Read-only file system

here are the output for zpool status -v, zfs list -t all -r AV-NAS2, and zfs get -r readonly AV-NAS2

image
image1115×711 58.4 KB

image
image655×197 16.7 KB

At this point, i’m just trying to access and recover the data off the pool to another drive in my main PC. Any help or ideas to get around this? much appreciated.

EDIT: I’ve already tried to set readonly=off for the 2 mountpoint and then zfs mount -a but it still output the same error above.

Thanks

2

Change your system dataset to your boot-pool. This will remount the .system datasets off your degraded pool and give you a read-write file system to update the mounts DB again.

3

Thanks for the reply Samuel,

the system dataset pool was already set to boot-pool from the start.

image
image824×165 2.35 KB

I guess the error that I have is more related to storage mount itself, as the call error shows below and that there’s no path any whatsoever in the /mnt dropdown.

image
image1071×266 12.4 KB

image
image449×647 12.6 KB

any ideas or more info that I could provide to solving this?

Thanks

4

Please describe your hardware, and double-check all cables and connectors.

5

System:
Truenas SCALE 25.04.1 running on PVE 8.4.0
2 QEMU Virtual Cores ver2.5+
10GB of Memory

Hardware:
Intel n100 Motherboard
16GB DDR4 RAM
128GB SSD

Controller:
m.2 nvme to SATA - ASmedia AS1166 routed directly to Truenas

Disks:
Seagate 4TB ST4000MD004 (x2) connected to ASmedia AS1166

All cables and connectors are connected well.

I haven’t restarted the system after the -fFX rollback, as I wouldn’t want the drive to be exported if were anything to happen during the restart.

6

If I understand your description of your hardware and setup, I think there are a few problems. Advice for ‘production’ (highly recommended) use of virtualizing TrueNAS is in the following article along with blacklisting the ‘controller’ from Proxmox. The other issue may be your M.2 to sata. If I have the correct HD, they are SMR and not CMR types. That is also a problem.

VIRTUAL

Multiply your problems with SATA Port Multipliers and cheap SATA controllers