TOS 6 and hybernation issue.

[teddy]

I hope I have better luck writing on this forum because I don't get any help from the support chat
I have a T12-450 enclosure with 12x22TB drives with a Raid 5 created.
Since I upgraded to TOS 6, the HDD never hibernates.
When the TOS boots up, it does so from disks 1 to 9 at the same time.
When the enclosure hibernates after 10 minutes, only disks 10 to 12 that are not marked as "system" and that have not booted the TOS do so.
My question is:
Is it normal that when the TOS boots up, it does so from 9 disks at the same time?
I have read the Hibernation Troubleshooting viewtopic.php?f=75&t=473&sid=927c3dae54 ... c3c4583d71
and I don't have any active processes or apps, not even SMB. To do the tests I have disconnected the enclosure from the network.
Can someone help me with this problem but without risk of losing data? I don't have a backup of them.
Thanks in advance

[Gremlin]

Perhaps you could explain a little more as to how many pools/Volumes you have set up and which file system(s) you are using. It could make a difference. Is your system updated to latest Tos6 (6.0.555)?

It has to be clear that there is no guarantee of protecting your data without a backup.

Even in a clean install of TOS6 the o/s is always written to all the hdd. I am not surprised that the upgrade leaves behind multiple active o/s raid copies. I am not sure that having 12 drives in a raid5 is necessarily the best organisation for your drives, but your eventual usage may determine that. You say you don't have 'any active processes or apps, etc' but, of course, this is linux so something is always going on .
So, is this all for data storage?

{On my small test system I must say that I notice that it takes a while for the desktop to display while it waits for the hdds to spin up even though I have the os and a separate volume for /home + /@apps (and the rest) on Nnme drives.}

You may be faced with a re-install of the os (details of which are posted elsewhere).

[teddy]

Thanks for the replay.

I have only a pool of 12 disks in Raid 5 of
219.99 TB" and a single BTRFS volume of 219.99TB, with
The TOS6 version is 6.0.555 and the BIOS/initBoot version
5.13.
I only have 2 shared folders, the public one and another with all data.

I agree with you that Linux has a lot of processes, but it seems that this activity doing swap or any other process is the one that does not allow those 9 disks to hibernate but the other 3 that have not started the TOS do.

I would understand that when the disks hibernate only the one that starts the TOS does not do it, but I still do not understand that 9 disks of the 12 are continuously active with the activity light when there is no external process.

I also do not understand that a 1GB NVME that has the TOS installed, when I tell it from the BIOS to boot from that NVME it does not do it, and keep booting the TOS all 9 HDDs at the same time.

[Gremlin]

I was not aware you had Nvme as well (never interested in that size unit ). Maybe there is some limiting factor in TOS 5/6 (9HDD+2NVme) as to total possible number of drives in O/S array. @TMSupport

I don't understand the 9/3 split either. I don't think it wise to change BIOS in your circumstances. {There is also a setting in BIOS 'UTOS Boot First' which should be enabled.)

Did you at some time have Hyper-cache installed? I seem to remember this might have been an issue in some circumstances.

It seems to me that you have included your Nvme in your storage pool. But that is not logical for a RAID5 as you describe. TNAS is designed around virtual arrays, so physical disks are not necessarily related to the virtual arrays. The TOS os is a RAID1 (Mirror) This is automatically spread over all drives. In a clean install you can select the ACTIVE members of the array (up to 2 in Tos6) but the inactive members still have an os system installed. In Tos5 all the drives (Theoretically) were active.

Maybe go to Control Panel > Disk > Disk. Expand individual drive details and see how they compare.

[teddy]

The Raid5 configuration is made up of 12 HDDs (the Raid volume does not include any NVME).

I installed an NVME and did a "Reset System" and installed the TOS on the NVME, I accessed the BIOS to boot from NVME but it continues to boot from the HDDs.

Perhaps the solution would be to do a Factory Default and tell it to install the TOS only on the NVME, but before doing so I have to make a backup with the most important data.

To clarify this a bit more, as you can see, disks 1 to 9 are marked as "System" and are the ones that boot the TOS at the same time.

The NVME, despite having the TOS installed, never boots even though I set it as the first boot device from the BIOS.

HDD1 (System Disk)
22.0 TB
Normal
ST22000NT001-3LS101
HDD2 (System Disk)
22.0 TB
Normal
ST22000NT001-3LS101
HDD3 (System Disk)
22.0 TB
Normal
ST22000NT001-3LS101
HDD4 (System Disk)
22.0 TB
Normal
ST22000NT001-3LS101
HDD5 (System Disk)
22.0 TB
Normal
ST22000NT001-3LS101
HDD6 (System Disk)
22.0 TB
Normal
ST22000NT001-3LS101
HDD7 (System Disk)
22.0 TB
Normal
ST22000NT001-3LS101
HDD8 (System Disk)
22.0 TB
Normal
ST22000NT001-3LS101
HDD9 (System Disk)
22.0 TB
Normal
ST22000NT001-3LS101
HDD10
22.0 TB
Normal
ST22000NT001-3LS101
HDD11
22.0 TB
Normal
ST22000NT001-3LS101
HDD12
22.0 TB
Normal
ST22000NT001-3LS101
NVMe Disk1
1.00 TB
Normal
Samsung SSD 980 1TB


NVMe Disk1
1.00 TB
Normal
Samsung SSD 980 1TB
Serial Number
S649NU0WA29817K
Firmware
3B4QFXO7
NVMe version
1.4
Duration of Use
109 h
Disk Temperature
44°C/111°F
Partitions Information
Partitions
File System
Size
sdza1
EXT4
285M
sdza2
RAID member lacking an independent file system
7.6G
sdza3
RAID member lacking an independent file system
1.9G
sdza4
---
921.5G

[RyanYang]

Due to earlier versions of the USB boot process synchronizing all hard drives as system disks during system installation, and not automatically canceling the existing system disks during updates, you will need to reinstall the system to limit the system disk to one or two hard drives. You may try enabling Debug mode in the "Support and Help" section of the TOS desktop, and later download the logs to see which program is writing data to TOS. If it is not immediately clear, you can send the logs to our technical support team for assistance.