Rakrul
Dabbler
- Joined
- Dec 27, 2021
- Messages
- 17
Damn.You can add a larger disk but only the size of the smallest disk in the RAIDZ vdev will be used.
Thanks for clarifying though.
Damn.You can add a larger disk but only the size of the smallest disk in the RAIDZ vdev will be used.
Actually, they're probably fine. "all disks have to be of the same size or the smallest one will determine the space used on all of them" - this characteristic of a vDev isn't mentioned in the current TN13 manual. It was in TN11's manual but didn't make it into this one that I (or a pdf search tool) can find.Apparently my reading abilities are non-existent. :)
.1 now. What's next .2 .3??? :(Save your settings under System->General->Download Config. After the reinstall with 12.0-U8.1, restore your settings under System->General->Upload Config. Remember to save secrets with the config to preserve passwords.
As for functionality bugs on .0 releases, this is par for the course in the entire software industry. TrueNAS isn't an especially egregious offender here. The Release Notes for 13 don't recommend using 13.0 for critical deployments until 13.0-U2 or later.
You did read the release notes, didn't you? If not, then you're guilty of installing under false assumptions, and you should learn from this experience for next time you deal with server software.
Obviously... (Severus Snape). And no it still doesn't work for me which is the entire reason i posted I updated to the latest version before trying to replace the disk.The GUI should be working since U1... have you tried it?
What's not obvious at all is that you tried that at the GUI...Obviously...
uname -a
(or similar) not matching that version on your system (seems you're on U2).zpool status -v
shows your pool has a strange status now for that disk.Well I am running the latest version and it didn't work for me so clearly hasn't been fixed otherwise I wouldn't have bothered coming here right?What's not obvious at all is that you tried that at the GUI...
I can see just fine that you tried running the script (according to the provided instructions for 13.0, hence using a script intended only for 13.0), but that script fails due to a check ofuname -a
(or similar) not matching that version on your system (seems you're on U2).
What I'm asking is that you stop using the script on versions after 13.0 (U1 and U2) and use the GUI (and nothing else).
The issue with the GUI is documented on the release notes page you linked as being fixed in U1 (https://ixsystems.atlassian.net/browse/NAS-116217)
I imagine thatzpool status -v
shows your pool has a strange status now for that disk.
You still haven't addressed the first question I asked you with a clear response.Well I am running the latest version and it didn't work for me so clearly hasn't been fixed otherwise I wouldn't have bothered coming here right?
If you're using SMR drives, you're not going to be happy in the long term, particularly at your next resilver or scrub when zfs starts marking those drives as faulted because they can't keep up.it's some junk smr seagate drives
The GUI isn't working that's painfully obvious considering if it was i wouldn't be here right?You still haven't addressed the first question I asked you with a clear response.
The script is meant only for people running 13.0 (not 13.0-U1 or 13.0-U2 as you currently are). So to reiterate, you should not be using that script.
In order to replace a disk in 13.0-U2, you should use the GUI... again, you showed no evidence that you even tried that, so I'm not clear when you say "it's not working" if you mean the GUI process or the script (which is expected to not work on the version you're using).
You posted an example CLI that is not correct form and proposed it as a solution that others might like to follow (I suggest that they should not).
If you're using SMR drives, you're not going to be happy in the long term, particularly at your next resilver or scrub when zfs starts marking those drives as faulted because they can't keep up.
It seems to me like there's not much point continuing this discussion further. I wish you luck with your resilver and the safety of your pool data (as good design won't save you if you're using SMR disks).
I have no idea why you're here... you have provided evidence that a script doesn't work on a version it's not supposed to work on, some incorrect advice to others, a generally unsatisfied tone and nothing else to help us to help you.The GUI isn't working that's painfully obvious considering if it was i wouldn't be here right?
There is no error in the GUI you click replace disk the big blue button and nothing happens using the latest version, i already have replaced my disk manually as you know since I don't want to put that copy of my data at risk for the sake of troubleshooting and waiting around for a better solution and I don't think anyone would either if their data was at risk and it was their only copy and they had to replace a drive immediately and not wait for a fix and community support to eventually start their resilver I think would you've done the same here.I have no idea why you're here... you have provided evidence that a script doesn't work on a version it's not supposed to work on, some incorrect advice to others, a generally unsatisfied tone and nothing else to help us to help you.
If the GUI wasn't working, it would have helped to share the details provided by the GUI, not the script.
I suspect the GUI is fine as I see evidence from others in the forum that it works, although I haven't yet had occasion to test it myself, so I assume either you're doing something wrong when using the GUI or there's some issue with your install.
I've already advised you to think about your use of SMR (and I suggest you stop it if you care about your data), so I have nothing more to offer you unless you want to document your problem with the GUI.
I'm not sure how you can understand SMR and elect to use it on purpose with ZFS, but it's your own (data's) funeral, so have at it. It's not about the (too long) resilver times (although that's reason enough on its own to not want SMR), the drives will be marked as faulted if they can't respond fast enough and you'll lose your pool if too many of them are faulted.I'm aware how SMR drives work and the resilver time to expect
OK, well I did just that... I've now tested on a fresh install of 13.0-U2 and the GUI replace works exactly as expected. No issues.As for what to look for if you're curious i'm sure you can test everything yourself and if it's working and it's only my installation that's fkd up then no problem at least most people won't face this even though i've done nothing but install truenas 13.0 when it was the latest and click update using the GUI and then try to replace the disk after a reboot that's literally all you'd have to do to replicate my installation, fresh install did absolutely nothing it's not like there's an RNG in place to decide if the installation is gonna be glitchy or work as expected right? :)
Maybe you haven't refreshed the cache on your browser since the update and you're still running parts of the GUI from 13.0 as a result even with the new backend. Try a SHIFT + Refresh in your browser and see if that helps.i've done nothing but install truenas 13.0 when it was the latest and click update using the GUI and then try to replace the disk after a reboot that's literally all you'd have to do to replicate my installation, fresh install did absolutely nothing it's not like there's an RNG in place to decide if the installation is gonna be glitchy or work as expected right? :)