TOS 5.1.145 (X86) is Released for Update

[Gremlin]

Maybe improper o/s partition sizes if not properly prepared prior to TOS5.1.n. Maybe did not follow outlined upgrade path to get to TOS6.0.n.

[tokingarg]

The exact cause remains unclear. You may consider trying another method to upgrade to the latest TOS6.
Flash the built-in USB drive with the TOS6 version, then install the system directly using the 6.0.770 installation package.
viewtopic.php?t=6433
During installation, you can select the target disk for TOS installation.
(Note: If prompted to “Delete/Create/Format” during installation, stop the operation. You can choose the target disk for TOS installation during setup.)

I followed your instructions. With no drives, TNAS can see it and it loads the TNAS Initialization page. It says No Disk(s) Found. I turn it off and add the nvme. Will not boot and it cannot be found in TNAS.
I plugged in HDMI and keyboard. Attempted to boot from USB, same problem.
It seems that when the nvme is plugged in it just repeats tosdaemon.pid can not be found. I tried both nvmes that I have. In both m.2 slots.
What can I do next?

Gremlin, I appreciate you chiming in but you keep commenting as if I'm not here. I followed all of the instructions when I initially setup the NAS. It ran for 2.5 years with absolutely no problems, going up to 5.0 and then 5.1. The partitions were 8 gb. And I followed the exact upgrade path. 5.1.67-5.1.145-6.0.530-6.077. I waited to update to 6 for nearly a year while the kinks were worked out as I use it for security and back up storage. I have spent many many hours reading the forums over the past 30 months. I'm at a loss and I am asking for help and I am taking suggestions. Maybe you can diagnosis it after it gets running

[TMzethar]

This is the tricky part, as NVMe SSDs do not support hot swapping, and when you have an NVMe SSD connected, it is likely to boot from the old system on the NVMe SSD.
Please refer to the process for handling system partitions on NVMe SSDs.
viewtopic.php?t=7179

[tokingarg]

Thank you. Ill do it a little later. I was hoping that by going through the bios and disabling it as a boot option it would load. Is it possible to load Ubuntu on it and format it that way?

I still dont understand why I was able to get it to 6.0.53 and it was working fine but when I did the auto update through the Control Panel to 6.0.77, that is when it crashed. The nvmes were initialized at 6.0.53. it emailed me to say that it was happening. I let it run, it completed, and then loaded 53 which was running fine.77 is when it stopped working again.

[tokingarg]

Thank you. Ill do it a little later. I was hoping that by going through the bios and disabling it as a boot option it would load. Is it possible to load Ubuntu on it and format it that way?

I still dont understand why I was able to get it to 6.0.53 and it was working fine but when I did the auto update through the Control Panel to 6.0.77, that is when it crashed. The nvmes were initialized at 6.0.53. it emailed me to say that it was happening. I let it run, it completed, and then loaded 53 which was running fine.77 is when it stopped working again.

Update:
Followed the instructions and formatted the nvme with disk genius. Put them back in and it loaded 77. It gave me a notification that it was rebuilding BTRFS TRAID SStorage Pool / volume. I couldnt cancel it. It took about an hour. Sent me an email that it finished. I was worried it did the same thing again and when I restarted. Same error, cant find TOSDaemon.pid.

What should I do now?
Thanks

[TMzethar]

It's possible that some individual drives have issues. You can reinstall TOS on each drive separately. Observe the performance of each drive. Additionally, have you already burned the initboot USB specifically for TOS6?

[tokingarg]

This is what I have done since yesterday.

I completely wiped the NVME. All partitions, low level format.

Didn't even bother with disk genius, just used easeus partition manager, because when I used disk genius to format the 8 gb partition, it still ended in the same way. The low level format seems to work.

I used the latest bootloader that you referred to. It's the same way that I have been using.
I put in the nvme. Turned it on. It initialized the drive and loaded 6.0.77.
Detached the USB and restarted. TOS loaded perfectly. It didn't try to rebuild anything. Just worked.
Wiped the other NVME. Installed it. Turned it on and again it didn't try to rebuild traid/btrfs. It showed it as a storage pool that I could create.
Again, wonderful.

Now when I plugged in the HDD array (4 drives) and restarted it, I watched it go through it's startup script on the monitor and got stuck with the same error, can't find tosdaemon. pid.
Turned it off. Pulled power. Removed the 4 drives. Only the nvme with tos. Restarted and the same issue. It's stuck on tosdaemon. It seems as though anything that I don't format completely messes up the whole system and attempts to load the corrupted version.

This is extremely frustrating. How does the array, which has never been used as an os drive, corrupt everything? I would love to hear your input. Don't you want log files? What is happening?

Thanks

[TMzethar]

If your HDDs were previously used with TOS5, they were likely automatically synchronized by TOS5 to the system partition (containing the old system).
When you boot with all disks connected, the old TOS5 system will boot first from HDDs. Then TOS6 will be resynchronized to the old TOS5.
For your situation, we recommend the following steps:
Reinstall TOS6 on the M.2 SSD.
Connect the HDDs to F4-423 only when TOS6 is running.(Please do not start F4-423 with the HDDs in.)
Open Terminal and use the following command to wipe the old systems from all 4 HDDs:

Code: Select all

mdadm --zero-superblock /dev/sda3
mdadm --zero-superblock /dev/sdb3
mdadm --zero-superblock /dev/sdc3
mdadm --zero-superblock /dev/sdd3
mdadm --zero-superblock /dev/sda2
mdadm --zero-superblock /dev/sdb2
mdadm --zero-superblock /dev/sdc2
mdadm --zero-superblock /dev/sdd2
/etc/tos/scripts/mntdata

Afterwards, even if you start the NAS with the HDDs inside, it will be fine.

[tokingarg]

Thank you soooo much zethar. The superblock seemed to do it. Everything is up and running.

One last question. I have a folder on my Volume2 (raid) that was the public folder in the last system that was a shared folder. It has the little lock on it and it doesn't show up anywhere in the os but I can see it in terminal. I'm guessing it was encrypted but I have no idea. Is there a place where the keys are stored, how to unlock it? Was it locked in tos5? Can I just move it in command line? I don't want to delete in shared folders because I think it deletes the whole thing and it doesn't show up when I setup tnas smb.

Is the key stored on my pc?

Thanks again!