sreknob

Recommend way is to use the Replace the USB flash device procedure from the guide. When you do this, all of your current settings and shares will be preserved. If you want to start "fresh", then you'd use a brand new flash drive set up as new, boot the fresh drive and then use the "New Config" tool, reassigning all your drives to their proper assignments and selecting the "parity is already valid" checkbox. If you don't select the proper assignments though, there is risk of data loss here. Alternatively, you can set up a new USB drive and just copy the /config folder from your current drive, which should preserve your array and shares configuration as well. I would suggest using the method from the guide - what are you hoping to achieve by "starting fresh"?

Thanks for the information - I was not aware of the overly file system issue. Having said this, I've never had a problem in the past, so perhaps I'm just lucky. It would make sense if this was somehow integrated into the new update workflow in this case. There is no reason to overwrite the "previous" folder file as the intermediate version never was booted, so the previous should say as is. I suppose it could be tracked by comparing the versions between what is loaded and what is in the previous folder before copying over the current files.

Thanks itimpi - I am aware of the manual process, it's just nicer to hit a button 🙂 Maybe more of a suggestion for the new method as it matures further. For now, using the Update Assistant tool seems to work around this issue. Thanks

Hi All - I have one server that I hit the update button on but didn't reboot yet, and now there is a new version. Is there any way with the new upgrade workflow to complete a "double upgrade", meaning skipping an intermediate version if you previously hit upgrade and didn't reboot or if an upgrade came out shortly after starting an upgrade to the previous version? In the past, I could just use the update tool again to get to the current version prior to rebooting, but it appears that there is no easy way to do this "double upgrade" anymore. I now need to reboot to get to the intermediate version, then reboot a second time after updating again to get to latest (save manually doing the upgrade on the flash). Have we lost this ability to do this easily with the new enforced workflow? If so, any chance this could be address in future versions of the new update workflow? Or is this already possible and am I missing something? Thanks! EDIT - Looks like I was able to work around this for now by using the old update method. I use the Update Assistant which checked for a new version as part of it and then click on the banner notification at the top to update the server. Then it used the old update method to successfully complete it. Still, it would be nice to include this ability in the new update workflow instead.

Back to the post thread topic here - Is there any way with the new upgrade workflow to complete a "double upgrade". For example, I have one server that I hit the update button on but didn't reboot yet, and now there is a new version. In the past, I could just use the update tool again to get to the current version prior to rebooting, but it appears that there is no easy way to do this "double upgrade" anymore. I now need to reboot to get to the intermediate version, then reboot again to get to latest (save manually doing the upgrade on the flash). Any insights here or am I missing something? Thanks! Edit - for reference, I was able to get this done by using the old method, triggered by using the Update Assistant Tool, more discussion here. Perhaps this could incorporated into the new update workflow somehow by comparing the version in the previous folder to the running version and allowing a new update without overwriting the previous folder again during the upgrade.

Did this, made no difference. I always check for updates prior to running an update all. Just had another loop of 2 with the full update and then a cycle of restart. Just to mention, in case it's related - anyone else with this issue running the Docker Folder plugin? Only bring this up because I have to refresh my page after the updates to have them show as up to date.

Used to do it twice, just got a persistent loop today. Still an issue 😕 6.11.5

For those that time machine backups are important, it does seem that the TimeMachine docker application works. It's not native and an additional step, but some appear to have found it useful

I just logged onto the forum to get some help with a 12TB drive I was adding to my array that wasn't formatting after pre-clear... If only that upgrade notification came earlier! Will report back if 6.11.3 doesn't solve the problem... Update - Formatting working as expected now. Thanks!

Oops, I guess that's what you get when you have multiple shells open and try in on a server on 6.10 by accident! 🙃

...and if you could add iperf3, that would be amazing as well 🙂

Requesting ddrescue! Thanks for this!

@shawnngtq @myusuf3 @troian @mykal.codes @wunyee @kavinci @cheesemarathon For the minio filesystem error, I resolved this by using directIO rather than shfs, which removes the fuse layer from the equation. The only downside is that you need to use a single disk. Rest of settings are default. /mnt/disk1/minio So far uploaded a couple of GBs without issue

Welcome Eli!

Hard to do much with a 750 with 2GB. Options are something with a small DAG file size (UBIQ) or a coin without a DAG file, like TON. T-rex doesn't support either of those options, however.