aspik

The third run finished with 0 errors. Attached logs after the check completed. Can I trust the parity? It is safe to do a disk swap, or should I check something else before exchanging the disk? fractal-diagnostics-20240425-0954.zip

Yes, I'm using ECC memory. Ok, then I"ll start a third run. Will report in 24h about the result. Thanks for looking into it!

Hi, I want to replace a smaller disk with a new bigger one. To be sure that everything is OK I started a parity sync (write corrections to parity enabled). The parity sync finished with one error. I then started second run of parity check (also write corrections to parity enabled). After an approximately an hour one error was found/corrected. This second run of the parity check finished with just that one error. How can two parity checks result with one (same?) error? How can I find the root cause? In the past I never had parity errors. Recently I moved the server to a new case, could it be a cable problem? Please find attached diagnostic logs. Thanks in advance for any help. fractal-diagnostics-20240423-2203.zip

Hi, I'm also affected with this bug. For me this is a major issue, in the past I never had issues with unraid. Up times reaching nearly a year. Now I have to reboot the machine just to restore the basic functionality... For me it happens when I delete files over an nfs share mounted to Pop OS. Anything I can provide to help to narrow down the root cause?

Understood. Thank you for the quick responses

Ok, got it, thanks! I stubbed just the tuner [dd01:006] and I see it now in the VM. Do you think it would be better to passthrough the whole PCIe Controller? I read that passing the whole controller is better, or is this only relevant for USB devices?

Hi, I recently build a new server (Asrock C236 WSI with Intel G4560). Now I want passthrough to a win10 VM the PCIe Digital Devices C2 V7 DVB Tuner. I expected to show it up in Other PCI Devices box, unfortunately it's not there. I see it in under System devices: IOMMU group 1: [8086:1901] 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 05) [dd01:0006] 01:00.0 Multimedia controller: Digital Devices GmbH Cine V7 Why it is not possible to select it in the win10 VM settings? How do I passthrough it to my VM?

Hi, I wanted to extend my server. I'm looking for a 4 port SATA controller for my MB SP X7SPA-HF-D525 that can handle sleep S3 and of course WOL. In wiki I see that the Adaptec 1430SA is compatible with unraid. Can someone of you confirm that the controller can properly go sleep and wake up? Compatible with my MB is it, right? Or do you can recommend something else (affordable) ?

+1! For me it is also very important, I know for many of you it is any unnecessary feature, because your running the server 24x7, but if unRAID will compete with the commerce NAS Vendors like qnap or synology it should also natively support S3 (in my opinion). I've already asked, why it is not officially supported and been told that's the reason for that are various hardware dependencies, but I think with a modern hardware it isn't a problem anymore, or knows some of you a motherboard, which doesn't support S3?

OK, I will disable also video and measure it again with disabled IPMI and video. Do you have any other tips what can I also disable (tweak) to get the power draw lower?

Now is my config in my sig:) As you can see there are no power consuming HDDs. For the kill-a-watt meter, i use this version http://www.conrad.com/ce/en/product/125333/Basetech-COST-CONTROL-3000-LCD-000-999999-kWh- I know it isn't high end, but i think i should be enough for me. I have been always wonder how did you get it under 20W, if in this review http://www.servethehome.com/supermicro-x7spehfd525-8gb-ddr3-ipmi-pfsense-freenas-unraid-linux-power-consumption/ it is also closer to my measurement.

No add-in card installed. The PSU is Seasonic 360G http://www.newegg.com/Product/Product.aspx?Item=N82E16817151117. I had the same as you CX430, but I changed it to the seasonic in the hope that it will be more efficient... Unfortunately there is no difference between this two PSUs in consuming power in idle state...

Maybe a try again to connect him to make a respond. I already tried to update to FW, but within IPMIView and that failed, if I correctly recall with an error message "connection refused". There are other options like DOS, but then i have to connect a display and keyboard to the server... Did you update the FW? How did you did that? Yeah, I know that your board draws only 19W (I read a lot here i the forum before I buy this board ) but with my board I was never be able to get under 25W (Idle) don't known why... About the not putting it to sleep, I know that many of your are running their servers 24/7, but for me, as I need it only max 7h a day, against 17h idle means that it would be draw more € in idle than in use, what is in my opinion very unfortunate

Hi gary, I know that you can access the system with IPMI even when it's off, somehow during waking up it's "messing the wake up process... I have to admit that I didn't come alone with the idea to disable IPMI, I found someone that have the same problem and solved it with disabling IPMI: http://forums.gentoo.org/viewtopic-t-954508-start-0.html Unfortunately I didn't become an answer what firmware version he was using.

Hi again, just for Info, if anyone has the same problem, I finally solve this one too! turns out that IPMI caused this issue... after turning it off I can wake up my server. I have also a guess why everyone with this board hadn't this problem, your all bought this board long time before I and have an older IPMI firmware. My is 2.66, on the Supermicro homepage is a new one 2.67, but i didn't check this out. I tried to contact Supermicro support for a changelog, but didn't become a answer. So for everyone who newly bought this board and has WOL problems: make sure your disable the the BMC with the jumper 13!

Today morning during start the server I became an error (see screenshot). It stopped with this message. I've done a reset and the second start was successful, the server started. Can someone tell me what does it mean? Is something wrong with the server? Thanks in Advance.

FYI: if anyone else stumble here with similar problems, I solved it finally. Turns out it was bad cable management and not the right cables. I used the straight/straight SATA cables, after closing the side panel the cables were too squeezed and I was getting the errors. When I left the case open (without the side panel) the errors where gone. A solution for the problem is to buy the down/straight cables and do a better cable management...

Thanks for the replay snowboardjoe. As I said before, it occurs only on the wd re4 disks. I have 2 of them in my array. Yes, indeed, it happens when the disk was spun down and I started to play a file on the htpc. This is what worries me, an physicial drive issue:( I already done a long smart test from the web-gui, the result was without errors.

Unfortunately the error still occurs. What I've done already: - resetet power and data cables: no effect - removed the disks from the backplate and inserted it again: no effect - changed the data cables to other new ones: no effect. Currently I have 5 Disks (with parity) in the array and the errors occurs only on those RE4 disks. Attached syslog and smart report for disk1. Anyone have an Idea? syslog.txt smart_disk1.txt

This is strange.. I use brand new Delock straight/straigh 30cm cables (Item No. 82676). The PSU is also a new Corsair CX430M. Everything is in the Q25 case from Lian Li. Could it be something in the HDD cage from the case? As the cables are not directly connected to the disk, but to the HDD cage.

Thanks for the link! Which error do you mean? Because the log say: Jan 30 20:27:50 Tower kernel: ata3.00: cmd 25/00:08:40:00:0c/00:00:6e:00:00/e0 tag 0 dma 4096 in Jan 30 20:27:50 Tower kernel: res 51/40:08:40:00:0c/00:00:6e:00:00/e0 Emask 0x9 (media error) Jan 30 20:27:50 Tower kernel: ata3.00: status: { DRDY ERR } Jan 30 20:27:50 Tower kernel: ata3.00: error: { UNC } And this looks like a Drive media issue #1, which is not good at all…

Hi dirtysanchez, I disconnected and connected the power and sata cables, but unfortunately I still get this error. I have in my array 4 disks: 2x WD Red 3TB and 2x old RE4-GP 2TB, the error occurs only on those RE4 disks. Sometimes only 1 read error and sometimes even 150! I'm really afraid, that something might go wrong on both disks and I loose the data on both disks... I've attached syslog, do you have any other ideas, what's wrong? syslog.txt

Hi Joe, Thank you for the latest check on my drivers. Now I have precleared my WD AV-GP 2TB disk and have a question about ATA Errors. I guess the smart attributes looks OK? There are no pending sectors to be re-allocated. But the preclear start and finish reports have ATA Errors. As far I could find out, these are cable problems, right? Both Errors occurred on 159 day of use, the disk has currently power on of 408 days, which would mean that the errors occurred quite time ago (where the disk was used in my htpc). What I don’t understand is: SMART Error Log Version: 1 ATA Error Count: 2 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 2 occurred at disk power-on lifetime: 3834 hours (159 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 a0 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- b0 d6 01 e0 4f c2 a0 00 00:22:17.056 SMART WRITE LOG ec 00 00 00 00 00 a0 00 00:22:17.054 IDENTIFY DEVICE ef 02 00 00 00 00 00 00 00:22:16.633 SET FEATURES [Enable write cache] ec 00 00 00 00 00 a0 00 00:22:16.630 IDENTIFY DEVICE b0 d6 01 e0 4f c2 a0 00 00:22:06.756 SMART WRITE LOG Error 1 occurred at disk power-on lifetime: 3834 hours (159 days + 18 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 a0 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- b0 d6 01 e0 4f c2 a0 00 00:22:06.756 SMART WRITE LOG ec 00 00 00 00 00 a0 00 00:22:06.752 IDENTIFY DEVICE ef 02 00 00 00 00 00 00 00:22:06.722 SET FEATURES [Enable write cache] ec 00 00 00 00 00 a0 00 00:22:06.719 IDENTIFY DEVICE ec 00 00 00 00 00 a0 00 00:21:35.933 IDENTIFY DEVICE What does mean: Error: ABRT? Attached start, finish and rpt files. Thanks! WD_AV-GP_2TB.zip

OK, this is indeed a reason.

Yeah, I know that and I wonder why it is not officially supported, is there any particular reason? I thought unraid is mainly designed as a data storage for home users. Why should it be 24h on, when I use it only 6h a day? Good that the S3 script from you has an option to power-down instead of sleep, with SMCIPMITool I can turn on my server with a command also from G2 (S5) state.