saber-raider

Finally! So happy that this has been fixed. Just don't know why it took so long. Hope something fundamenal like that doesn't break again anytime soon.

I am on 7.2.3 . This would be a downgrade over multiple versions, right? Isn't this a risky endeavor?

Same issue here. Very annoyed Lifetime customer. This broke my whole multistep backup strategy. I refuse to use the docker-based workaround given it makes things more complicated and rely on third-party software. TBH I expect the unraid team to fix this e. g. by downgrading Samba and do a bugfix release or find another solution, because this broke existing functionality without any warning.

I can confirm that the update + initial reboot worked fine.

Unraid 7 has now been officially released. I have no system to easily test if the workaround survives the update. I skimmed through the changelog at https://docs.unraid.net/unraid-os/release-notes/7.0.0/ and i don't see a reason it wouldn't work, but OTOH the boot mechanism in 6.x is quite dated compared to other Linux distros and I don't known much about 7.x yet (never used it). Short question: Did anyone who uses the workaround already tried an upgrade?

I can confirm that this workaround works. Thank you so much for taking the time and effort to address this issue; I really appreciate it. I've also opened a ticket with TerraMaster support and made them aware of this thread and the workaround. Hopefully, a long-term solution will be found soon. I'm new to Unraid and was wondering if there's a risk that a future update could modify the first line in `/boot/syslinux/syslinux.cfg`, potentially preventing the system from automatically booting into the OS after an upgrade/reboot cycle?