Xerol
-
Posts
21 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Xerol
-
-
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!
-
5 hours ago, JorgeB said:
Last extended test on disk6 was many years ago, run a new one, UDMA CRC errors are a connection issue, just acknowledge and make sure it doesn't keep increasing.
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!
-
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!
.
Drive errors; SMART results OK
in General Support
Posted
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.