January 9, 20242 yr I have running 6.11.5 and finally decided to take the plunge and upgrade to 6.12.6. All went well, until after a day or so of uptime, the server started to hang. It would come back up after a reboot, but I decided to downgrade again. That seemed to go fine, but I was having issues with my dockers not all starting up as they should so I rebooted and that is where my problems start. I cannot get the server to come back online again. I have tried several different flash drive backups I made before upgrading etc and nothing is helping. The thing that is confusing me is I was looking in the zip file for one of the flash backups I made and I checked the disk_assignments.txt file and noticed it is labelled as "Disk Assignments as of Mon, 13 Aug 2018 03:00:24 +0100". and looking at the disk assignments in this text file, I can see a number of drives that have been removed and upgraded and changed out, second parity added since 2018 etc. I understood the disk assignments file showed literally the disk assignments at the time of the backup, but I have checked all the flash drive backups I have made and they all have the same disk assignments file in them. Is this file redundant now and the disk assignments are held somewhere else or is there some issue with my flash backups? The backups are made from the GUI>main>flash>backup flash drive. thanks in advance
January 9, 20242 yr Community Expert Solution The disk assignments have always been held in the super.dat file in the backup. This is a binary file and thus not human readable. Not sure when/how the disk_assignments .txt file gets created.
January 9, 20242 yr Author 4 minutes ago, itimpi said: The disk assignments have always been held in the super.dat file in the backup. This is a binary file and thus not human readable. Not sure when/how the disk_assignments .txt file gets created. That makes me feel a lot better now then! Thanks for that - time to keep exploring other options for getting the server back online...
January 9, 20242 yr Community Expert Be careful using old backups. Some have used an old backup that still had a disk assigned as parity but had been re-used as data. So booting the old backup proceeded to write parity to that data disk. At the very least, edit config/disk.cfg and disable autostart so you can check your disk assignments before starting the array.
January 9, 20242 yr Author 32 minutes ago, trurl said: Be careful using old backups. Some have used an old backup that still had a disk assigned as parity but had been re-used as data. So booting the old backup proceeded to write parity to that data disk. At the very least, edit config/disk.cfg and disable autostart so you can check your disk assignments before starting the array. The backup I was using was from Saturday 6th January 2024, before I looked at upgrading the OS, but thanks for the tip!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.