-
Posts
164 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by cholzer
-
-
Guys, you should really open a new report in the correct subforum because mine is closed.
Hardly anyone from the dev team will read closed reports. -
6 minutes ago, Ver7o said:
TurboWrite doesn't seem to be the reason for this. Spin ups still happen without it.
Tired to unplug the network cable over night and then in the morning reconnect and check the log if spin ups occurred?
That way you can rule out devices on your network causing the drives to wake up.
Just for the record, since I replaced my failing HBA my drives have stopped to spin up randomly. -
20 hours ago, Vr2Io said:
I use SAS3008 HBA and have't disk spin issue on RC2
Yeah mine was broken, I even got random disconnects of entire disks later on. RMA in progress.
In the meantime the SAS2008 is working fine and no more issues. -
21 hours ago, Pillendreher said:
but since my hardware is barely more than a month old
My HBA is 7 months old, and it started to fail shortly after I upgraded to RC2. So just because your hardware is new does not mean that it is okay.
The only way how you can make sure that RC2 is to blame is by downgrading. -
increased CPU load every 10 seconds!?
Intel Xeon E5-2620 v3
my UnRAID is bored 90% of the day.
there are no dockers, no VM's and no one on the LAN accesses the shares.
With 6.8.3, prior to upgrading to RC2, the CPU load was mostly at 0-1%, sometimes there was a spike to 5% on a core.
Now with RC2 I see multiple CPU cores spike to to 15% every 10 seconds..... (all array disks spun down, no one using it for anything). -
2 hours ago, Pillendreher said:
Since I don't use any such controller and have only experienced this with the RC2, this is software related.
If the issue goes away when you downgrade to the latest stable, then yeah - it would appear that RC2 is the problem.
But just because you don't use the same HBA as I do does not mean that it is software related. In my case the HBA began to die, that is what caused my issue. Your onboard SATA controller can malfunction just as my HBA did.
So unless downgrading Unraid to the latest stable fixes your issue, you can not rule out a hardware fault. In my case the issue started after the upgrade, which is why I first also thought that RC2 was to blame, while it was the HBA. -
On 1/19/2021 at 10:59 PM, mdoom said:
I just happened to stumble onto this thread...
..I've been having this problem forever! Admittedly, I never dug into it much, but was always annoyed that my disks were always spun up. Even if i forced to spin down, they always seemed to come back up. I finally checked logs today and I'm seeing it frequently always reading SMART on all drives. Trying to figure out what is triggering the reading of the SMART stats though.
I will say though, I am using LSI 2008 HBA for my controllers.
EDIT: I also am on RC2. I can't say specifically if this is unique to RC2 or not, however I am on that currently, and currently see logs showing this. I cannot speak to why i previously had issues with disks always spun up. (prior to RC2).
In my case it was caused by the LSI 3008 controller which began to act up in other ways as well. This issue was in my case just one more symptom of the HBA failing.
If you use plugins, VM's or dockers then you should try to disable all of them and see if the disks stay spun down. -
Changed Status to Closed
I am nolonger able to reproduce the issue since I replaced my potentially failing LSI 3008 with an LSI 2008. -
I had to replace my LSI 3008 HBA with an LSI 2008 HBA because I suspected that the 3008 was failing.
Since I did that I can nolonger reproduce this issue.
Disks remain spun down now! -
3 hours ago, SimonF said:
Do you get the entries when connecting usb devices?
I have not tried that.
I only have my Array disks, cache SS and one disk I share through unassigned devices for backups.
That entry in the log just keeps showing up throughout the day. -
Anyone else gets this error in their log?
-
After the update to RC2 everything seemed fine but then I started to notice that Unraid would wake up disks even when data was copied to the *cache* not the array.
I also noticed that throughout the day some disks get spun up for no apparent reason - at times where everyone is asleep - there are no VM's nor dockers, Unraid is used as a plain NAS
-
3 hours ago, Marzel said:
How did you set your spin down? For every disk or in the disk settings for all?
I just have the spindown delay set to 30minutes. That works fine for me using an LSI SAS 2008 in IT-Mode
-
Upgraded my Unraid Server (which runs inside ESXi) to RC2 about a day ago.
Everything is working nicely so far!
Including spin down/up of disks.
(note I do not use any dockers nor Vm's in UNRAID, it is a pretty simple setup with an LSI 2008 in IT mode, 5x 8TB HDD's Array, 1x 500GB cache SSD and 1x 6TB share unassigned devices)
no notification when metadata corruption occurs
in Stable Releases
Posted
Well that is certainly not good for a file server, is it?
I suppose I have to make a feature request for this then?
I am stunned that there is no alert for filesystem issues.....