zach

Still running into issues even after replacing the battery. Going to bite the bullet and replace the motherboard Thanks

Shut it down at night. Booted in the morning and got "CMOS checksum bad." I hit F2 to continue and it continued to boot. I ran a memtest for 6 hours. zero errors. Rebooted again and got the CMOS checksum bad error again. This is new. Never saw a CMOS checksum error until today. Change the battery?

in one file, "first allocation unit is not valid" go ahead and run chkdsk again with the fix option?

Unraid version 4.7 Almost every time I boot unraid, it freezes once, I reboot, and then it boots properly. This morning it froze during "load bzroot." It's never done that before. It usually gets all the way to root login, the screen fills up with code (I dont have a photo) and becomes unresponsive. I ran a memtest and it came out fine. I haven't changed any bios settings or anything on the flash drive in years. syslog-2013-07-19.txt

thank you. that's approximately a 2 year lifespan for a WD20EARS under heavy use, for anyone else wondering. drive is being replaced right now.

Smart test: http://pastebin.com/e8NXzQzE syslog: http://pastebin.com/QEKageQD Unraid 4.7 The first time the drive went red, I ran a smart report and since it looked OK to me, i followed the procedure to rebuild the contents onto the drive. It worked fine for 3 days. I woke up this morning and found my server disabled the drive a second time. Please view my smart report and syslog and offer any advice. I don't really know how to interpret the smart results which is why I ask for help. I checked all cabling both times. Here's another interesting fact: this all happened after I replaced another failed drive last week. I only mention it because it seems like a strange coincidence for two drives to fail so close to each other. Do I go ahead and replace this disk (/dev/sdd) or should I investigate other options first? Thank you.

Thanks for the info Rob. Disk 4 is definitely messed up. The bios loading screen showed the error "4th Slave Hard Disk Error" and I can't run a smart report. Smart report on disk 1 is fine. Can anyone tell me how to force it to re-enable disk 1? If I can't do this, I can't rebuild disk 4. Nightmare situation.

These errors happened at the same time. I booted and Disk 1 has a red ball next to it. Shows "DISK_DSBL" in unmenu Disk 4 has a red ball next to it. Shows "DISK_WRONG" in unmenu (I did not change any disks) Disk 4 is showing a size of 2,147,483,616 even though the size is 976,762,552 Disk 4 is also not showing a temperature I understand that DISK_DSBL means an error occurred during a write. It seems to me that Disk 4 has failed, not Disk 1. Disk 4 is makes many power-cycling noises and also has the strange problems described above. To verify that one drive wasn't interfering with another, I tried unplugging 1 and leaving 4 plugged in, and vice versa. 1 remained as DISK_DSBL, and 4 remained as DISK_WRONG. Can I FORCE unraid to undo DISK_DSBL on disk 1, or in other words, trust that it's fine? If I can do that, then I can replace disk 4 and rebuild it. syslog: http://pastehtml.com/view/1cxc42q.html screenshots: unraid: http://i51.tinypic.com/2f03ggm.jpg unmenu: http://i52.tinypic.com/2ikbgp.jpg

i am in your exact situation right now, with my only EARS drive being the parity disk (no jumper in use). i'm going to wait until 4.7 final before i decide to make any changes. i just want to double check on the process first because i'm only reading about this jumper issue for the first time today. 1. Stop the array 2. unassign the EARS drive (my parity) 3. log in via telnet 4. type the following (from Joe L.) 5. start the array and let it rebuild parity Edited

Thank you everyone. Replacing the drive fixed this. The dead one was definitely blocking the other drive.

When I plug the drive from SATA2 into SATA6 it does not work. This drive DOES work in SATA2 though. If I plug the drive from SATA1 into SATA6 it DOES work. This prove that the port is not broken, but what happened above is still strange. After some experimenting, the drive from SATA6 doesn't work in any port. I think this is the culprit. Joe: How does one disk "block" another?

Unraid says the drives plugged into SATA2 and SATA6 are both "missing." The BIOS does not see the drive in SATA6, but it DOES see SATA2. With SATA6 unplugged, unraid now reads SATA2. (The reverse does not work. if you unplug only SATA2 then both are still missing). The disk controller is on the mobo. Do I need a new motherboard or to just replace disk 6?

i haven't made any hardware changes for months. i'm using the latest unraid version 4.6. the tower was working fine yesterday. i did a clean power down last night and discovered the problem when i turned it on this morning. i inspected all cable connections and everything looks fine. nothing accidentally became loose. the two drives that are "missing" appear to be powered up. syslog attached syslog-2011-01-152.txt

Thanks, Joe. I now understand how this works. Unfortunately though I created the directory, put arial.ttf in there and renamed in subfont.ttf, and still received the same exact error in the debug.log I'll see if I can get some help in the ps3mediaserver thread regarding this.

The following is an excerpt from a log file from ps3mediaserver. I am trying to fix a problem where there program cannot locate the subtitle TTF file, but I am limited by my almost zero knowledge of linux. [Thread-1243] DEBUG 19:01:58.343 New_Face failed. Maybe the font path is wrong. [Thread-1243] DEBUG 19:01:58.343 Please supply the text font file (~/.mplayer/subfont.ttf). I understand that ~ is the home directory. Correct? What is ".mplayer"? is that a directory? I can easily take it from here and put the TTF file where it belongs... if you could just help me understand where that location is Thanks, from a new unraid user and linux noob