• Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About cholzer

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. Hi! One of my Seagate IronWolf 8TB drives shows 14 read errors. But how concerned should I be about that? The drive is 13 months old, I did pre-clear it. Should I replace it and try RMA? ST8000VN004-2M2101_WKD17TMQ-20210301-0717.txt
  3. 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.
  4. 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.
  5. 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.
  6. 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).
  7. 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.
  8. 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.
  9. Changed Status to Closed I am nolonger able to reproduce the issue since I replaced my potentially failing LSI 3008 with an LSI 2008.
  10. 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!
  11. 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.
  12. Anyone else gets this error in their log?
  13. Already changed the HBA and all cables. I still get this error in the log several times throughout the day. I do not recall getting that error prior to the upgrade to 6.9.2 RC2 What does it even mean? What is this task it tries to abort? *edit* Recently replaced the LSI 3008 with a LSI 2008 (including the cables), this error message still shows up. Jan 18 07:23:17 NAS kernel: sd 3:0:4:0: attempting task abort!scmd(0x000000006d823564), outstanding for 15380 ms & timeout 15000 ms Jan 18 07:23:17 NAS kernel: sd 3:0:4:0: [sdf] tag#789 CDB: opcode=0x85 85 06 20 00 00 00 00 00
  14. So if I would get this one then it comes with IT-Mode not IR-Mode?
  15. Ah so if I would not have bought an LSI SAS 3008 and instead went straight for an 9300-8i then I would not have had to flash the IT BIOS? Cool, great to know! So you would still go for an 9300-8i in 2021, right?