November 1Nov 1 I ran into a similar issue as another user after upgrading to 7.3.4 and am wondering if someone can make sense of my diagnostic logs to see if I can resolve it the same way.https://forums.unraid.net/topic/201111-system-issue-after-upgrade-to-734I'm currently booted into a default, unlicensed configuration of my NAS.I have a backup of my flash but I worry it's quite outdated (i.e. from a version even earlier than 7.3.2) so I'm hesitant to use it.Thanks in advance! tower-diagnostics-20261101-0103.zip
November 1Nov 1 Solution Your diagnostics show the filesystem on the boot flash was badly damaged. There are 87 FSCK000x.REC files on the flash. These are the pieces left when a filesystem check repairs damaged files. Almost the whole config folder was lost, including the license key file, the disk assignments (super.dat), the pool and share settings, and the Docker and VM settings.That is why the server booted with a default, unregistered configuration.The flash is also still damaged. During boot, Linux found another filesystem error and set the flash to read-only, so no settings can be saved to it now. Your disks are not affected by this. The array and pool data are still on them. Until the configuration is restored, do not start the array, do not create a New Config, and do not format anything. Your backup is still useful, even if it is older than 7.3.2. A config folder from an older release works with 7.3.4. It brings back the license key, disk assignments, pools, shares, and Docker and VM settings. You only lose the changes made after the backup was taken. 1. Shut down the server and connect the flash drive to a PC. Copy everything on it to a folder on the PC, including the FSCK files, before you change anything.2. If you had Unraid Connect flash backup enabled, look for a backup there first. It may be newer than your local one.3. Recreate the flash with the USB Creator using 7.3.4. Then copy the config folder from your backup to the flash, replacing the one that is there. I recommend you use a new good-quality USB 2.0 flash drive for this, because Ultra Fit drives have a history of failing. If you reuse the current drive, the USB Creator formats it, which also removes the filesystem damage. But if this happens again on that drive, replace it.4. Boot the server. On the Main page, before you start the array, confirm that the assigned disks are the ones you have now. If you changed, added, or replaced any disk since the backup, or are unsure about any assignment, do not start the array. Post new diagnostics first.5. If you used a new flash drive, go to Tools > Registration and transfer the license to it.6. If the assignments are correct, start the array. Then check what changed after the backup: new shares will show with default settings, and any containers added after the backup may need to be added again from Apps > Previous Apps. When everything works, make a new flash backup, and make one again after any configuration change.
November 1Nov 1 Author Thanks for the quick reply! I connected the flash drive to my PC, backed up all the files, ran a scandisk operation to fix the errors, then restored my old config folder. My license was a trial in the backup, but I was able to restore it from the website.I was able to get my shares up and running again but my docker settings were out of date so I'm trying to get my Plex server up and running again. I think my host paths are misconfigured but I think I can figure that out.Thanks again!
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.