Craigb

Thanks LoLight! Will do. All new bits now on order.

Thanks! I'll give this a try. FWIW, that Sony drive has been in service exactly as it is, for years. Can't explain it, but it works. Got the 7.3.1 zip and Rufus. I'll get on it later today.

Update. I've run the the 7.3.1 upgrade several times using three different, new flash drives, both 8 and 32 GB. I used the USB creator tool each time on freshly formatted devices. Tried both GPT and MBR FAT32 formatting before running the creator. No difference. I've intentionally NOT tried to upgrade or reformat the old flash drive, since as LoLight points out, it is very much past it's sell by date! fdisk of /dev/sda (the Sony 4 GB flash disk) shows 3 very clearly incorrect partitions. >>>>>>>>>>> root@NAS1:~# fdisk -l /dev/sda Disk /dev/sda: 3.73 GiB, 4009754624 bytes, 7831552 sectors Disk model: Storage Media Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x0009e87d Device Boot Start End Sectors Size Id Type /dev/sda1 3223366752 3470046675 246679924 117.6G f4 SpeedStor /dev/sda2 378192737 710426324 332233588 158.4G 10 OPUS /dev/sda3 225603442 225603451 10 5K 74 unknown Partition table entries are not in disk order. >>>>>>>>>>>> Absolutely not a clue what those are or where they could've come from... That flash disk has never been used anywhere other than in that server since new. It is FAT32, MBR. I have a clean backup of 7.2.5 just in case... I've now agreed to a full rebuild of that server with finance. New MB, CPU, memory, etc. It's far past time and I'm pretty sure we've got our money's worth from the current hardware. Many thanks to all for the feedback!!

That's correct. The Sony flash drive has been in that server since around 2010. Whilst it seems to be good, my Windows workstation occasionally fails to enumerate it when it's plugged in. Tried upgrading twice more today, no luck. The Sony is MBR FAT32. Double checked the replacement drive and it was GPT. Changed it to MBR, no difference. Copied over the config folder from the good instance and removed the junk from the go file. No difference. Whilst I appreciate the feedback, we're now into the work week here, so I'm done. It stays on 7.2.5.

Thanks for the tip on the go file. The next opportunity to try an upgrade will be Monday AM early CET. This Unraid instance, in various forms, has been running since 2009, so that's too surprising.

Thanks. Ran the create tool 3 times with 7.3.1 on 2 different bootable usb drives. Copied the config folder and it's contents from the backup each time. Same result each time. The most recent 7.3.1 diagnostic file is attached. 7.2.5 works well, is stable and reliable. Colleagues are waiting to get on with their work so at this point, I'm giving up on the upgrade, maybe later. I appreciate the assistance and tips. nas1-diagnostics-20260627-1430.zip

One more data point, after the upgrade, the server will not power down from a command line command. sudo shurdown shuts down the OS but does not power off the server. The front panel power button does not work. A sudo poweroff command also does not power off the machine.

Thanks... Booting after upgrade, the console shows "Unraid Server OS version: 7.3.1" and the login prompt. Ran the diagnostic which returned the following and created a zip. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> root@NAS1:/boot# diagnostics Starting diagnostics collection... sh: line 1: /tmp/servers.conf.txt: No such file or directory done. ZIP file '/boot/logs/nas1-diagnostics-20260627-0944.zip' created. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> One final point, the last line in the boot text before the version line is "sh: -c option requires an argument" I don't recall seeing that booting 7.2.5. nas1-diagnostics-20260627-0944.zip

Thanks! It is booting to unraid. The boot menu is there on startup and it defaults to booting (loading bzimage, bzmodules, etc.) after a few seconds. I'm able to SSH in with the admin credentials but I see a very light Linux instance. df -h shows no data drives. Not sure how to get the diagnostics file from the CLI. I've since had to revert back to 7.2.5 for work and everything is there as expected. I do have syslogs from before and after the upgrade as well as a diagnostic zip from before the upgrade if those are of any value. I must wait until tomorrow morning early to try it again. I'll get the output from a df as well.

Hello, Just ran the upgrade from 7.2.5 to 7.3.1 from the UI. After rebooting, no Unraid UI, no mounted volumes or disks, literally nothing but a command prompt. SSH works in but it's a very thin OS. I have syslogs from before and after. Tried it 3 times, and 3 times, the same result. A very minimal OS and no Unraid. Rolled back to 7.2.5 each time and all is well. Thanks! Craig

File names in the boot drive are now all lower case. Also removed an extraneous comment from a line in GO. All other lines except EMHTTP are now commented out. Settings seemed to be preserved after booting including the host name. Now keeping an eye things. Thanks for the assistance!

Understood - I think. Only change the file name or recreate them from scratch or a template? Presumably do this with the boot drive (USB flash key) out of the server and in my workstation to edit these?

Also... Just noted another setting that's changed on its own. On the SMART settings, I disabled attribute 197 due to issues with the controller on the SSD I use for the cache. 197 is now enabled again.

Attached. One BEFORE changing the server name (from Tower to NAS1) and the other AFTER changing the server name. The SSH setting changing to off is intermittent. Will check that after the next boot. No clue where Tower has come from. It appeared after upgrading to 7.2.x. It's been NAS1 for at least 10 years prior. Thanks! AFTER SERVER NAME CHANGE nas1-diagnostics-20260120-1851.zip BEFORE SETTINGS CHANGE tower-diagnostics-20260120-1848.zip

Hello, After upgrading to 7.2.3 some settings are not retained between boots. Specifically the server name is set and SSH enabled. There may be other affected settings but these two are the most obvious. Both were updated in the UI several times and both have again changed after a reboot. Server name to a very old name and SSH to disabled. Not sure where to look. Thanks!