Xerol

Thanks for your help. I've ordered a replacement disk just in case, all my disks are pretty old, but it's good to know that it's fine for now.

OK, so something strange is happening with the test on drive 6 (and maybe the others?). I completed a test again on drive 6, but the hours of the tests don't match the current hours of the drive like what @JorgeB showed above. Now it shows these SMART test runs (in the diagnostics I uploaded there are only 2): Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 17504 - # 2 Extended offline Completed without error 00% 17432 - # 3 Short offline Completed without error 00% 7574 - The test says it did complete without error again. So I guess I have 2 questions now, why don't the hours of the tests more closely match the current hours of the drive? And my original question, what do I do about the 7,xxx errors on the drive? Thanks again!

Great, thanks for the info! I looked at all of my drives and it looks like the test only ran completely on 1 of the drives. Not sure why that happened, but I'm going to run them again on the other drives. I tried to run tests on multiple drives at the same time previously, maybe that was the issue. Is there a way to run these in batch or concurrently, or does it have to be done 1 drive at a time? Thanks!

Uh oh, looks like I may have missed one when running all of them and it happens to be the important one! I'm running it now, but can you tell me how you knew when the last test was run? I scanned the output of the test, but don't see a date/time other than the current date/time at the top of the report. I'll post results of the test on disk 6 when it completes. Thanks!

Hi All! I've had an Unraid server up and running for quite a while now, it's been rock solid for years running multiple VMs, Dockers, etc. I recently started thinking of other things I would like to run on my server so I've been looking more into it that admittedly I had in the past... things were working, so I didn't look to far into it. I'm afraid I may have some issues with drives though and would like some help confirming that and order of operations if things are failing so that I don't lose any data. My dashboard page was showing multiple drives with errors; either "Current Pending Sector" or "UDMA CRC error count". I ran an extended SMART test on ALL drives and they all passed. My system also did an automatic parity check this morning which passed with 0 errors. I still show over 7,xxx errors on disk 6 though, how can I correct those, or does the drive need to be replaced? All of my drives are pretty old (the system has been purring along for years!), so it wouldn't surprise me if this (and other) drives are ready to be replaced. I've attached the diagnostics. Please let me know if there is any other data I can provide or questions I can answer. Thank you in advance for your help! media-diagnostics-20210301-1606.zip

Just closing the loop on this in case anyone finds this thread and is in a similar situation. It did turn out to be the NIC that was the issue. I bought a new NIC, installed it and disabled the onboard NIC. After this it booted just fine and I'm able to access all drives and shares just like before the storm .

Thanks for the help! The information you asked for is below. I also forgot to mention that I have already verified the port on my router and cabling are good by connecting another computer to them which was able to get a connection to the internet. ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Half Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: no ifconfig eth0 Link encap:Ethernet HWaddr 00:0c:76:ad:f9:18 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:20 Base address:0xe300 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)

Hello, Last week my neighbors house was struck by lightning, unfortunately my house has suffered some electrical side effects as well with some dead devices; tvs, ps3, etc. My server is connected to a UPS, but I haven't been able to access it since the lightning storm. Through various different fact finding missions, I find myself now attempting to boot a trial version of Unraid just to be sure it will boot! Everything does seem to boot, but I'm still unable to access the server from the Web GUI. My working theory is that the onboard NIC has died (my network switch the server was connected to died in the storm). Can someone who is more familiar with Unraid logs have a look at the attached and see if you can confirm my theory? Thanks in advance! syslog.zip

Hi guys, Thanks for your help! I came home this evening, tried a different SATA cable as I did happen to have one laying around, then RAN a short SMART test. I'm not sure quite how to read it, so I should probably post the whole thing, but this seemed to be the relevant bit to me. SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 10% 8900 19897350 # 2 Extended offline Completed without error 00% 268 - # 3 Short offline Completed without error 00% 263 - I find it a little confusing that it says no errors logged, but then further down it says it had a read failure during the short test. Any help would be appreciated. Thanks!

Hi All, Looking for a little advice on my situation, but I am pretty sure I have a failed parity drive. I noticed a few errors within the past week on my parity drive, so I decided to run a check yesterday. After quite a while, it failed and my parity drive was red. Stupidly, I shut down my server without grabbing a log. Upon my return home last night, I checked all cables and booted the server back up and it said the parity drive was new. I brought the array up instructing it to re-build the parity based on the data on the disks. At some point overnight, it failed again and the parity drive was red again. This time however, I grabbed a log before shutting it down. Here are the relevant parts from when it went down: Feb 14 07:20:55 Media kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Feb 14 07:20:55 Media kernel: ata10.00: failed command: WRITE DMA EXT Feb 14 07:20:55 Media kernel: ata10.00: cmd 35/00:00:c7:df:af/00:04:2e:00:00/e0 tag 0 dma 524288 out Feb 14 07:20:55 Media kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 14 07:20:55 Media kernel: ata10.00: status: { DRDY } Feb 14 07:21:00 Media kernel: ata10: link is slow to respond, please be patient (ready=0) Feb 14 07:21:05 Media kernel: ata10: device not ready (errno=-16), forcing hardreset Feb 14 07:21:05 Media kernel: ata10: soft resetting link Feb 14 07:21:10 Media kernel: ata10: link is slow to respond, please be patient (ready=0) Feb 14 07:21:15 Media kernel: ata10: SRST failed (errno=-16) Feb 14 07:21:15 Media kernel: ata10: soft resetting link Feb 14 07:21:20 Media kernel: ata10: link is slow to respond, please be patient (ready=0) Feb 14 07:21:25 Media kernel: ata10: SRST failed (errno=-16) Feb 14 07:21:25 Media kernel: ata10: soft resetting link Feb 14 07:21:30 Media kernel: ata10: link is slow to respond, please be patient (ready=0) Feb 14 07:22:00 Media kernel: ata10: SRST failed (errno=-16) Feb 14 07:22:00 Media kernel: ata10: soft resetting link Feb 14 07:22:05 Media kernel: ata10: SRST failed (errno=-16) Feb 14 07:22:05 Media kernel: ata10: reset failed, giving up Feb 14 07:22:05 Media kernel: ata10.00: disabled Feb 14 07:22:05 Media kernel: ata10: EH complete Feb 14 07:22:05 Media kernel: sd 10:0:0:0: [sdh] Unhandled error code Feb 14 07:22:05 Media kernel: sd 10:0:0:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00 Feb 14 07:22:05 Media kernel: sd 10:0:0:0: [sdh] CDB: cdb[0]=0x2a: 2a 00 2e af df c7 00 04 00 00 Feb 14 07:22:05 Media kernel: end_request: I/O error, dev sdh, sector 783278023 Feb 14 07:22:05 Media kernel: sd 10:0:0:0: [sdh] Unhandled error code Feb 14 07:22:05 Media kernel: sd 10:0:0:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00 Feb 14 07:22:05 Media kernel: sd 10:0:0:0: [sdh] CDB: cdb[0]=0x2a: 2a 00 2e af e3 c7 00 02 98 00 Feb 14 07:22:05 Media kernel: end_request: I/O error, dev sdh, sector 783279047 Feb 14 07:22:05 Media kernel: sd 10:0:0:0: [sdh] Unhandled error code Feb 14 07:22:05 Media kernel: sd 10:0:0:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00 Feb 14 07:22:05 Media kernel: sd 10:0:0:0: [sdh] CDB: cdb[0]=0x2a: 2a 00 2e af e6 5f 00 02 68 00 Feb 14 07:22:05 Media kernel: end_request: I/O error, dev sdh, sector 783279711 Followed by this error repeating itself hundreds of times: Feb 14 07:22:05 Media kernel: md: disk0 write error Feb 14 07:22:05 Media kernel: handle_stripe write error: 783277960/0, count: 1 Then I get this error repeating itself: Feb 14 07:35:50 Media emhttp: mdcmd: write: Input/output error Feb 14 07:35:50 Media kernel: mdcmd (26): spindown 0 Feb 14 07:35:50 Media kernel: md: disk0: ATA_OP_STANDBYNOW1 ioctl error: -5 I'm pretty sure it is going to result in a failed drive, but is there anything else that I can or should do before purchasing a new drive? Any steps that I am missing? Thanks in advance!

This appears to have been the issue. For some reason they were disabled under 4.5.3. even though I never unplugged them or moved them or anything. I went and enabled them via the web interface and all is well now. I am running 4.5.3. and all drives are working. Thank you all so much for your help!!

Here is another something interesting... 2 of my drives show up as missing under 4.5.3. To be fair sometimes randomly under 4.3.3. the same two drives would show up as missing, but a reboot would make them appear again. After multiple reboots of 4.5.3. I cannot get them to appear. So I reverted back to 4.3.3. and they showed right up. These two drives are old IDE drives where the rest of my server is hooked up with SATA, could there be something in 4.5.3. where IDE isn't supported anymore? Thanks for your help!

Interestingly enough, this must have been the case. I re-enabled the onboard NIC and it worked fine... for some reason my secondary NIC no longer works with the newer versions. I guess I am lucky that since one must not be supported that at least my other one is Also for anyone who finds this thread the command above should be "ifconfig -a". I had to do some searching on the internet because /all wasn't working, so hopefully this will save someone else some time. Thanks for your help guys!

Hello unraided, Thank you for the response. I tried 4.5.1 a few weeks back and had the same results; at the time I just pushed it aside because I planned on doing an expansion to my server. I will give the commands you mention a shot over the weekend and see what happens. I am not using the onboard LAN on my mobo as it never seemed to work since day one. I built this server from old parts, so it could be bad. Regardless, I have a separate NIC plugged in, how would I find it's name? Would it be eth1? The cabling is all good and my server has a static IP. Thanks again for your help!

Hello everyone, After expanding my server yesterday, I decided as long as I was tinkering with it I would upgrade to the latest version as well. I am currently at 4.3.3. I downloaded the files for 4.5.3 and unzipped them. I then copied the bzroot, bzimage, and memtest files to my flash drive. I made a backup of the current files that would be replaced. After rebooting the server, I was not able to access the web screen. My server runs headless, so I plugged in a monitor and it looks to get to the login prompt. I then reverted back to the backup files and can boot my server again running the old version. I looked at the monitor and it also stops at the login prompt, so I guess this is where it is supposed to stop. Any ideas on why I can't get to the web screen on the newer version? Anything I should try to make it work? I tried to get to it by both the IP address and the server name, but neither worked. Thanks in advance!

Hi Joe, Thanks for the response. I came home and formatted and all is well.

Hi everyone, I have what I hope is a quick question. I apologize for the lack of details in this post, right now I am at work and don't have access to my server. Hopefully they won't be required, but if they are I can post them in a few hours. Last night I added a new drive to my server, something I haven't had to do in a couple of years so I don't remember the exact process. I stopped the server, did a clean powerdown, added my drive, then booted the server back up. Went to the devices page and added my new drive at which time I was prompted to clear it. I let it clear overnight last night because it was taking some time. When I woke this morning I refreshed and it had completed clearing and showed me all of my drives with green orbs next to them except my new drive which had a blue orb and said it was "unformatted". A format button was present, but I did not click it. My question is simply do I need to click the format button to format the new drive? I know that sounds ridiculous, but I am weary of the word format, I don't want to lose all the files on my server. I just want to ensure this is all normal. I was able to use explorer and navigate to my existing shares. I searched my way around the forum and the wiki, but the information I found was a little confusing. Sorry if I overlooked something. Thanks in advance!