Page 10 of 11

Re: TOS 6.0.460 (X86) Beta is Released for Update

Posted: 18 Sep 2024, 22:30
by DCCentR
bonerserk wrote: 11 Sep 2024, 17:59
TMzethar wrote: 10 Sep 2024, 19:12
DCCentR wrote: 10 Sep 2024, 16:53
We observed the screenshots you provided and the system report in your mailbox. Unfortunately, they were not enough to pinpoint the cause of the problem. Please continue to communicate with the technical support e-mail address to schedule a time for an engineer to investigate the issue remotely.
I've been dealing with this exact problem for a while. I reported it and sent a log report, and I've already tried what the TM engineers suggested (changing disk slots, reinstalling TOS, recreating the RAID), but with no result.

After many tests, I believe that TOS has some incompatibility with the sleep disk status of Seagate disks. I also have Seagate disks ST8000VN004, which should be fully compatible with TOS according to the official pages. When the disks go to sleep and something tries to write or read, sometimes these disks can't wake up, and TOS thinks the RAID is corrupted.

I was able to replicate this issue many times: I have installed Immich (a photo manager) on a server, which has its photo library on my RAID. When all disks are sleeping, if I take a photo with my phone, the Immich app will upload the photo, and the Immich server tries to write it directly to the folder on the RAID. As soon as it tries to write the photo, the RAID enters degraded mode. Less frequently, this also happens when trying to read a file, like a film.

When this happens, I can hear the NAS beeping, and soon after, I can hear the disks starting their reading and wake-up noises. I had installed TOS only on an SSD NVMe disk.

Now, I have reinstalled TOS on the problematic Seagate disk instead of the SSD disk, and it’s been three days without this problem occurring. However, I think that installing TOS on the RAID disks prevents them from going to sleep. I can always hear disk noises, and files are always available with no waiting time, unlike when the disks are really asleep.

When the degraded RAID status occurs, if I shut down the NAS and then start it again, everything works correctly as if nothing happened. This method (shutting down) prevents the RAID rebuilding process, unlike what happens with a reboot.

I want to ask @crisisacting if you want to reinstall TOS on the disks to verify if the problem persists.

I also noticed that this issue is not only related to RAID but also to single disk configuration. I put one of my Seagate disks as a single disk, and the problem is the same. TOS can't wake up the disk, and I can't access files.

I am available to provide any information and support to the TM team to help find and solve this problem.

Thanks.
Hey, this is interesting observation. I think it also can be and my case.
On the day I first encountered the RAID corruption problem, it seems the disks had low activity and may have gone to sleep. I have a default configuration for Disk Sleep - 30 minutes. When I encountered this problem for the second time, my torrent client was turned off (it has half a hundred active torrents) - and it is probably the only regular user of my HDDs right now. Oh, and I also have removed my system partitions from HDDs (system only on NVME)

Re: TOS 6.0.460 (X86) Beta is Released for Update

Posted: 23 Sep 2024, 20:57
by bonerserk
Gremlin wrote: 18 Sep 2024, 21:29
bonerserk wrote: 18 Sep 2024, 20:49
OK. Which "installer" did you use?
With "installer" I mean the web interface provided by TOS on my TNAS ip url. I didn't use some other external installer.

Re: TOS 6.0.460 (X86) Beta is Released for Update

Posted: 23 Sep 2024, 21:02
by bonerserk
DCCentR wrote: 18 Sep 2024, 22:30
bonerserk wrote: 11 Sep 2024, 17:59
TMzethar wrote: 10 Sep 2024, 19:12
We observed the screenshots you provided and the system report in your mailbox. Unfortunately, they were not enough to pinpoint the cause of the problem. Please continue to communicate with the technical support e-mail address to schedule a time for an engineer to investigate the issue remotely.
I've been dealing with this exact problem for a while. I reported it and sent a log report, and I've already tried what the TM engineers suggested (changing disk slots, reinstalling TOS, recreating the RAID), but with no result.

After many tests, I believe that TOS has some incompatibility with the sleep disk status of Seagate disks. I also have Seagate disks ST8000VN004, which should be fully compatible with TOS according to the official pages. When the disks go to sleep and something tries to write or read, sometimes these disks can't wake up, and TOS thinks the RAID is corrupted.

I was able to replicate this issue many times: I have installed Immich (a photo manager) on a server, which has its photo library on my RAID. When all disks are sleeping, if I take a photo with my phone, the Immich app will upload the photo, and the Immich server tries to write it directly to the folder on the RAID. As soon as it tries to write the photo, the RAID enters degraded mode. Less frequently, this also happens when trying to read a file, like a film.

When this happens, I can hear the NAS beeping, and soon after, I can hear the disks starting their reading and wake-up noises. I had installed TOS only on an SSD NVMe disk.

Now, I have reinstalled TOS on the problematic Seagate disk instead of the SSD disk, and it’s been three days without this problem occurring. However, I think that installing TOS on the RAID disks prevents them from going to sleep. I can always hear disk noises, and files are always available with no waiting time, unlike when the disks are really asleep.

When the degraded RAID status occurs, if I shut down the NAS and then start it again, everything works correctly as if nothing happened. This method (shutting down) prevents the RAID rebuilding process, unlike what happens with a reboot.

I want to ask @crisisacting if you want to reinstall TOS on the disks to verify if the problem persists.

I also noticed that this issue is not only related to RAID but also to single disk configuration. I put one of my Seagate disks as a single disk, and the problem is the same. TOS can't wake up the disk, and I can't access files.

I am available to provide any information and support to the TM team to help find and solve this problem.

Thanks.
Hey, this is interesting observation. I think it also can be and my case.
On the day I first encountered the RAID corruption problem, it seems the disks had low activity and may have gone to sleep. I have a default configuration for Disk Sleep - 30 minutes. When I encountered this problem for the second time, my torrent client was turned off (it has half a hundred active torrents) - and it is probably the only regular user of my HDDs right now. Oh, and I also have removed my system partitions from HDDs (system only on NVME)
I can confirm that after a week I moved TOS from NVME to my 2 Seagate disks, my raid is still working with no cases of corruption.

Re: TOS 6.0.460 (X86) Beta is Released for Update

Posted: 24 Sep 2024, 01:35
by DCCentR
bonerserk wrote: 23 Sep 2024, 21:02
DCCentR wrote: 18 Sep 2024, 22:30
bonerserk wrote: 11 Sep 2024, 17:59

I've been dealing with this exact problem for a while. I reported it and sent a log report, and I've already tried what the TM engineers suggested (changing disk slots, reinstalling TOS, recreating the RAID), but with no result.

After many tests, I believe that TOS has some incompatibility with the sleep disk status of Seagate disks. I also have Seagate disks ST8000VN004, which should be fully compatible with TOS according to the official pages. When the disks go to sleep and something tries to write or read, sometimes these disks can't wake up, and TOS thinks the RAID is corrupted.

I was able to replicate this issue many times: I have installed Immich (a photo manager) on a server, which has its photo library on my RAID. When all disks are sleeping, if I take a photo with my phone, the Immich app will upload the photo, and the Immich server tries to write it directly to the folder on the RAID. As soon as it tries to write the photo, the RAID enters degraded mode. Less frequently, this also happens when trying to read a file, like a film.

When this happens, I can hear the NAS beeping, and soon after, I can hear the disks starting their reading and wake-up noises. I had installed TOS only on an SSD NVMe disk.

Now, I have reinstalled TOS on the problematic Seagate disk instead of the SSD disk, and it’s been three days without this problem occurring. However, I think that installing TOS on the RAID disks prevents them from going to sleep. I can always hear disk noises, and files are always available with no waiting time, unlike when the disks are really asleep.

When the degraded RAID status occurs, if I shut down the NAS and then start it again, everything works correctly as if nothing happened. This method (shutting down) prevents the RAID rebuilding process, unlike what happens with a reboot.

I want to ask @crisisacting if you want to reinstall TOS on the disks to verify if the problem persists.

I also noticed that this issue is not only related to RAID but also to single disk configuration. I put one of my Seagate disks as a single disk, and the problem is the same. TOS can't wake up the disk, and I can't access files.

I am available to provide any information and support to the TM team to help find and solve this problem.

Thanks.
Hey, this is interesting observation. I think it also can be and my case.
On the day I first encountered the RAID corruption problem, it seems the disks had low activity and may have gone to sleep. I have a default configuration for Disk Sleep - 30 minutes. When I encountered this problem for the second time, my torrent client was turned off (it has half a hundred active torrents) - and it is probably the only regular user of my HDDs right now. Oh, and I also have removed my system partitions from HDDs (system only on NVME)
I can confirm that after a week I moved TOS from NVME to my 2 Seagate disks, my raid is still working with no cases of corruption.
Nice to hear!

Did you try setting “Disk Sleep” to never (as I recall there is such an option) before doing this? I think that might also solve the problem.

I will try to corrupt my RAID again later to prove the HDD wakeup problem. I plan to reinstall TOS6 from scratch anyway (when the installation package is available)

Re: TOS 6.0.460 (X86) Beta is Released for Update

Posted: 24 Sep 2024, 05:05
by bonerserk
DCCentR wrote: 24 Sep 2024, 01:35
bonerserk wrote: 23 Sep 2024, 21:02
DCCentR wrote: 18 Sep 2024, 22:30
Hey, this is interesting observation. I think it also can be and my case.
On the day I first encountered the RAID corruption problem, it seems the disks had low activity and may have gone to sleep. I have a default configuration for Disk Sleep - 30 minutes. When I encountered this problem for the second time, my torrent client was turned off (it has half a hundred active torrents) - and it is probably the only regular user of my HDDs right now. Oh, and I also have removed my system partitions from HDDs (system only on NVME)
I can confirm that after a week I moved TOS from NVME to my 2 Seagate disks, my raid is still working with no cases of corruption.
Nice to hear!

Did you try setting “Disk Sleep” to never (as I recall there is such an option) before doing this? I think that might also solve the problem.

I will try to corrupt my RAID again later to prove the HDD wakeup problem. I plan to reinstall TOS6 from scratch anyway (when the installation package is available)
Yes I tried never sleep option but it doesn't work. Disks were going to sleep anyway so it didn't work because my raid got corrupted.

Re: TOS 6.0.460 (X86) Beta is Released for Update

Posted: 24 Sep 2024, 09:29
by TMzethar
bonerserk wrote: 24 Sep 2024, 05:05
DCCentR wrote: 24 Sep 2024, 01:35
Please do not use the “Never Sleep” option in TOS6 Beta version for the time being, it may cause high disk usage. Please wait for the next TOS6 update.

Re: TOS 6.0.460 (X86) Beta is Released for Update

Posted: 26 Sep 2024, 23:00
by bonerserk
TMzethar wrote: 24 Sep 2024, 09:29
bonerserk wrote: 24 Sep 2024, 05:05
DCCentR wrote: 24 Sep 2024, 01:35
Please do not use the “Never Sleep” option in TOS6 Beta version for the time being, it may cause high disk usage. Please wait for the next TOS6 update.
It seems that version 6.0.500 solved sleep problem.
I installed again TOS on nvme only and disks are going to sleep and finally there were no more raid corruptions in 5 days!

Re: TOS 6.0.460 (X86) Beta is Released for Update

Posted: 27 Sep 2024, 16:54
by ColaChen
bonerserk wrote: 26 Sep 2024, 23:00
Thank you for your use and feedback.

Re: TOS 6.0.460 (X86) Beta is Released for Update

Posted: 30 Sep 2024, 18:05
by DCCentR
bonerserk wrote: 26 Sep 2024, 23:00
TMzethar wrote: 24 Sep 2024, 09:29
bonerserk wrote: 24 Sep 2024, 05:05
DCCentR wrote: 24 Sep 2024, 01:35
Please do not use the “Never Sleep” option in TOS6 Beta version for the time being, it may cause high disk usage. Please wait for the next TOS6 update.
It seems that version 6.0.500 solved sleep problem.
I installed again TOS on nvme only and disks are going to sleep and finally there were no more raid corruptions in 5 days!
I haven't had any more RAID corruption on versions 6.0.500 - 6.0.507 either. Let's hope that the problem has been resolved

Re: TOS 6.0.460 (X86) Beta is Released for Update

Posted: 01 Oct 2024, 15:51
by ColaChen
:) thanks!
DCCentR wrote: 30 Sep 2024, 18:05