cdixon

Here you Ok. Thanks. I will definitely look into getting a new controller.

Here you go tower2-diagnostics-20241125-2034.zip

Someone gave me their old media server and I decided recently to turn it into an Unraid server. It has an Supermicro X8DTL-IF motherboard and it so far it seems to work. So I installed Unraid on the system but for whatever reason it is not able to detect the drives. What should I do?

Someone recently gave me a used server and I decided to turn it into an unraid server. It has Windows Server 2008 as it's OS and I don't think it has been used since the early 2010s. I tried installing Unraid on it but whenever I get to the end of the installation process it says the following: IPv4 Not Set IPv6 Not Set What should I do?

So do you think I should replace the psu with one with more wattage?

I have replaced two of my splitter cables. Should I replace the other one? And could this be an issue with my psu? Maybe I have too many drives plugged into it?

It said smartFTP. tower-diagnostics-20241103-0826.zip

I ran a new one on that disk a couple of days ago and these were the results: SmartFTP open device: /dev/sdg failed: INQUIRY failed When it comes to read errors this is what pops up whenever I try streaming something off the disk: Read error, sector=8876464320 However, when I run a parity check after reconfiguring this is what shows up: Ata2: COMRESET failed and then this shows up: disk 1 write error, sector 27927576 I am starting to think that this issue is stemming from the PSU and that I will probably have to get one that can handle more wattage. What do you think I should do?

I notice that when the data rebuild fails. Cpu 3 is at 100%. Could this be the issue?

Greetings: The other day I was running a data rebuild on a drive. The data rebuild failed and my cache drive became disabled at the same time. Now it says that the cache drive is unmountable. What should I do? tower-diagnostics-20241018-0747.zip

Even though the disk is new and it has passed the smart test? Do you you think that this issue might be related to one of the parity drives?

Yes, I did.

Ok, so I ordered new SATA cables for the drive. I replaced the cables and ran a data rebuild but the drive got disabled again. This is what showed up in the log: Oct 15 05:47:21 Tower kernel: sd 10:0:0:0: [sdg] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Oct 15 05:47:21 Tower kernel: sd 10:0:0:0: [sdg] tag#15 CDB: opcode=0x88 88 00 00 00 00 03 a3 81 29 c6 00 00 00 01 00 00 Oct 15 05:47:21 Tower kernel: I/O error, dev sdg, sector 15628052934 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Oct 15 05:47:21 Tower kernel: Buffer I/O error on dev sdg1, logical block 15628052870, async page read What should I do now?

What should I do?

Greetings, everyone: I recently had a drive in my unraid server go bad. I recently replaced the drive and ran a data rebuild on it and for a week the drive was operating normally. But after several days the new drive got disabled and this popped up on the web terminal: Sep 18 08:40:07 Tower kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 0, rd 1655, flush 1, corrupt 0, gen 0 Sep 18 08:40:07 Tower kernel: sd 8:0:0:0: [sdf] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Sep 18 08:40:07 Tower kernel: sd 8:0:0:0: [sdf] tag#20 CDB: opcode=0x28 28 00 05 e4 cc e0 00 00 08 00 Sep 18 08:40:17 Tower kernel: sd 8:0:0:0: [sdf] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s I have looked on the forum for posts dealing with similar problems but the solutions always require for the SATA cables to be replaced. However, I don't think that this necessary because I installed the new drive with new SATA cables. What should I do? ST8000DM004-2U9188_ZR15X21K-20241008-1304.txt tower-diagnostics-20241008-1350.zip

What should I do then? I have already replaced the Data cable.

Do you mean the current diagnostics? Because I was not able to get the diagnostics when the drive failed the second time.

You mean this: unraidlog.txt

Ok, so a couple of months ago, I set spin off delay to never on the drive that was having issues and set it up for a data rebuild. It took about two days to finish and there were not errors along the way. But two months later, I did a parity check and the drive disabled due to write errors. I ran an extended SMART test which came out positive but I am still not sure what is going wrong. Based on the results, what do you think I should do? TOSHIBA_HDWF180_X846Y00IFB6G-20240128-1950.txt unraidlog.txt

Here you go. tower-diagnostics-20231030-1619.zip

Greetings everyone: I recently had a drive in unraid server that got disabled. I replaced the SATA cable and tried to do a data rebuild on it but the drive disabled in the middle of the process. Afterwards, I ran an extended SMART drive test and the results came back positive. Judging from the SMART test results and the error log, what do you think I should do? Thanks in advance. TOSHIBA_HDWF180_X846Y00IFB6G-20231029-2255.txt unraidlog.txt

I have had my Unraid server up and running for over 6 years. Recently, I have had a problem where one of my drives keeps disabling. I particular drive 4 keeps disabling even though it keeps passing the smart tests. Even when I do a data rebuild on the disc it keeps doing this. Judging from the diagnostic results, what should I do? tower-diagnostics-20230313-1741.zip

I already rebooted. What could I do to figure why this happened?

This morning, I checked unraid and I noticed that one of my hard drives was disabled due to 1 read error. After noticing this I restarted the server and put the array in maintenance mode and ran a short smart test. The self test turned out fine and disc 6 is now being rebuilt from the parity. Why did the drive get disabled even though it appears to be healthy? (I included the test results of disc 6 in this post) Thanks in advance! ST8000AS0002-1NA17Z_Z840Q09L-20210902-1243.txt

That's the problem. In the settings, I have Error logging set to Syslog and Output file but I am still unable to find the corrupt files with this option.