After the 24.10.0.1 update, my storage pool disappears. All the standard zpool commands show that it is gone. But if I run:
zpool import -a -d /dev/disk/by-id
it becomes accessible. But after I do that, I still can’t mount it. I get read-only filesystem error.
So I did a clean reinstall of TrueNAS. When I boot 24.10.0, I can mount the pool and start the Samba server and all is good. But when I boot 24.10.0.1 and start the Samba server, then reboot, the same thing happens again. Is this a known issue with 24.10.0.1?
HP Z230 Core I5
8 GB RAM
Root is on an SSD and storage is on 2 X 2 TB spinning disks mirrored
Maybe I jumped the gun; but considering he mentioned it happened when SMB is started I’m assuming there is correlation; some folks mentioning full out server hangs into insta-reboots - so I’m guessing that pools being dropped is more of the same flavour.
It happens, I suspect the OP’s issues stem from a different cause.
There have been a few reports of pools being left exported at boot but I am not experienced enough to say why that might be. Perhaps something in the boot log can provide a hint?
I think it’s different as well. I’m also not entirely sure that stating Samba is related, but i have rebooted it before starting Samba and it did not happen, but the last time it happened, I had just started Samba before rebooting. But I also made a user, changed the IP, etc., so I can’t be entirely sure it is related to Samba directly.
Yes, I’ve seen what you are describing about pools being exported at boot. But in that case, I think that the pool is still visible and mountable, but some timing problem causes it not to get mounted.
Yep, I’ll give it a try tomorrow and report back. This did remind me of another detail. In one instance with 24.10.0.1, I turned the Samba server on, went and did something else and when I came back, it was off. So I have some hope that this will fix it.
Ok, gave it a try. It’s broken the same with 24.10.0.2 as with 24.10.0.1. BUT if I reinstall clean with 24.10.0.2, I can just import the pool and everything works. Si it appears to be a problem with the upgrade process.
Holy sh. I solved it. Posting the cause for posterity.
TLDR: It had nothing to do with TrueNAS.
I was installing Kubuntu unto a different machine and I got an error message I had never seen with the installer saying that it couldn’t find a writable something on the filesystem. And of course, I thought back to the issues I was having with TrueNAS after updating where I couldn’t mount the pool because it complained that the filesystem location was read-only. And I realized that the only difference between this Kubuntu installation and the many I had done before was that I was using a different thumb drive than I usually use. So I burned the Kubuntu ISO onto the thumb drive I normally use and tried installing again on the same machine. It worked fine. So I burned 24.10.0 onto that same thumb drive and clean installed in on my NAS. I then configured everything, started the Samba server, etc, rebooted it and then went into updates under system and updated to 24.10.0.2 and guess what. It worked!
So somehow, anything I installed from that thumb drive was broken. Bad thumb drive I guess. What a fing waste of time. Any way, thank you for your help. How random.
