RockDawg

Yes, I removed the battery. I powered up with only the CPU installed and I also tried booting up the one board outside of the case. Always the same result.

I'll try to keep this short. My computer had been running great since I built it ~8 months ago. Last week we had a power outage in the middle of the night (PC should have been in S3 suspend) and the next day it was powered off. I tried to turn it on, but nothing. Nothing powered up at at all. I ran down to Staples and buy a new power supply and it powers up, but won't boot. Monitor says no signal and I don't get the usual POST beep or any error beeps. I pulled the video card and tried the onboard gpu. I disconnected every drive, and pulled/rotated each stick of RAM... Nothing. I tried the monitor with my laptop and it works so it's fine. I removed the battery and cleared the CMOS on both boards with no luck. I finally conclude I must have lost the motherboard so I order a new one. I put the new one in tonight and it does the same thing! So I'm down to either another bad MB (possible, but hard to believe), the RAM or the CPU. In the past, I've gotten error beeps the couple times I encountered bad or missing RAM or CPU, but maybe that isn't always the case? My problem is that I don't have another system or hardware to switch the RAM or CPU with to test either one. Anyone have any ideas how I can troubleshoot this? I need my desktop back and it's already been a week. CPU: AMD Phenom II X4 965 Black Edition MB (old): ASUS M4A88TD-M/USB3 MB (new): Asus M4A87TD/USB3 RAM: Mushkin Enhanced Blackline 4GB GPU: GIGABYTE GV-N460OC-1GI GeForce GTX 460 PS (new): Antec EarthWatts EA650 650W

I see. Then shouldn't unRaid be saying that parity is not valid? Both the stock GUI and unMenu say parity is valid. EDIT: Should I just let unRaid go ahead and repair these errors?

I just recently (a few days ago) upgraded this server from 4.5 to 5.0b6a. I performed a parity check before upgrading and it returned 0 errors. I have unMenu installed and via unMenut I installed the monthly parity check and have it set to not correct errors. Last night a parity check ran as expected and it found 4 errors (not expected) and unMenu says "Parity updated 4 times to address sync errors.". My questions: 1. Why was parity updated if the monthly parity check package was set to "NOCORRECT"? 2. I'm going to run another parity check shortly, but any ideas or suggestions/ideas what might have caused the errors? I've had no unexpected shutdowns and like I said, parity was good right before the upgrade. 3. On an unrelated note, there a lot of of repeating lines in my log that say: Apr 30 02:08:23 Tower2 unmenu[1641]: bad method - 3664 345504 2792009 56290 9 3 96 100 0 50610 563803664-^M what does it mean? Here is my log: http://pastebin.com/TBvwL9FJ

Of all the things I tried (including rebooting the server several times), I never tried rebooting the client PC. Sure enough, that fixed it. Thanks for the tip! Thanks to everyone else too! I appreciate all the help!

I just went through and set Yes/Public for each drive, share and also in Settings/Samba. Still not working. If I telnet into the server I can access the contents of the "Kevin" share just fine using Midnight Commander so I'm assuming it's a Samba/permissions issue, but I'm at a loss on what to check next.

I know you're talking about a user share as well, but I had similar symptoms with device shares until, clicking on the device in Main, I explicitly applied Export Yes/Security Public. In my case all the drives already showed with those settings but clicking the apply button for each had the desired effect of letting me access them. I seem to remember having a similar problem with a new user share, but that was day one so my memory is fuzzy. You might try going into the share settings and applying Yes/Public even if it already seems to be set that way. Thanks for the help. I just tried that and unfortunately that didn't fix the problem.

The script fixed the above issue, but I have one user share (Kevin) and the flash that are inaccessible. When I try to open either one form my Windows 7 machine. I get the following error that says the location is unavailable. I tried rebooting and the problem persists. Both have SMB export=yes and security=public. Here is my log: http://pastebin.com/d5Uex7dc

Sorry for being so stupid. I missed the one step that said to run that permissions script. i made sure to do the other steps, but somehow I missed that. I should've double-checked everything before posting. I'm also sorry for posting in the wrong forum. I had multiple tabs open and didn't pay attention to which one I had open. Thanks for your help and sorry for this waste of a thread.

I just upgraded from 4.5 and everything seemed to go fine except when I try to access any drives or user shares from my Win7 computer, I get an "access denied" error. The drives and shares show up, but I cant access the contents. SMB is enabled and the dives are all set to export=yes and security=public. I can't think of anything else that would be blocking access. Herre is my log: http://pastebin.com/zvPQtKRS

Thanks! That worked.

I'm trying to mount a drive from a Windows 7 system that died so I can recover some files. I followed each step in the wiki and something indeed was mounted to /mnt/old_data, but the contents are not all correct. After installing the drive it was assigned slot "sdc" so I used the following command: My problem is that the contents that show up are: root@Tower1:~# cd /mnt/old_data root@Tower1:/mnt/old_data# dir BOOTSECT.BAK Boot/ System\ Volume\ Information/ bootmgr root@Tower1:/mnt/old_data# cd /mnt/old_data/Boot root@Tower1:/mnt/old_data/Boot# dir BCD BCD.LOG1 BOOTSTAT.DAT cs-CZ/ de-DE/ en-US/ fi-FI/ hu-HU/ ja-JP/ memtest.exe nl-NL/ pt-BR/ ru-RU/ tr-TR/ zh-HK/ BCD.LOG BCD.LOG2 Fonts/ da-DK/ el-GR/ es-ES/ fr-FR/ it-IT/ ko-KR/ nb-NO/ pl-PL/ pt-PT/ sv-SE/ zh-CN/ zh-TW/ Anybody have any idea what's up? I see some Windows stuff, but I never had memtest on there. That looks unRaid related. Maybe the drive got trashed when the computer died? It just doesn't seem right. Liek the wiki instructed I never assigned the drive to my array. I only stopped the array so I could see the drop down box on the Devices screen to see which slot it was assigned and then I restarted the array.

Thanks. Yah, I need updated it and unmenu. Which reminds me, thanks for your great contributions to unraid!

I just ran a preclear cycle on a drive that's been in my array for ~18 months. I did this because it showed disabled in my array after a power outage. Here are the results: =========================================================================== = unRAID server Pre-Clear disk /dev/sdi = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Elapsed Time: 14:46:22 ============================================================================ == == Disk /dev/sdi has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 50c50 < 1 Raw_Read_Error_Rate 0x000f 103 093 006 Pre-fail Always - 55633165 --- > 1 Raw_Read_Error_Rate 0x000f 103 093 006 Pre-fail Always - 0 54c54 < 7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always - 136059092 --- > 7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always - 140644518 58,60c58,60 < 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 15391 < 190 Airflow_Temperature_Cel 0x0022 076 051 045 Old_age Always - 24 (Lifetime Min/Max 21/24) < 195 Hardware_ECC_Recovered 0x001a 056 052 000 Old_age Always --- > 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 22207 > 190 Airflow_Temperature_Cel 0x0022 070 051 045 Old_age Always - 30 (Lifetime Min/Max 21/31) > 195 Hardware_ECC_Recovered 0x001a 070 052 000 Old_age Always ============================================================================ Anything to be worried about there?

Gotcha! I'll do that. Thanks!

OK. So I should stop the array, unassign the drive, reboot, preclear the drive, add it back to the array, restart and rebuild the data?

I can understand that for a new drive, but hasn't my drive already been stressed (formatted once and written to many, many times)? Could my current SMART report possibly be less indicative than one returned after a preclear on said drive?

What would a preclear benefit it? I ask because I don't know.

I don't have a spare drive right now. This server is for my movies and TV shows so if it's down for a few it won't bother me that much. What further test would you perform on that drive and I can I perform them with it still in the server?

Attached is the SMART report for that drive. Again, I don't understand much of it, but it seems fine, no? Is it safe for me to perform the "Trust My Array" procedure? smart.txt

We had a power outage in the middle of the night last night and today I notice that my array was started and running but one of my drives was showing a red indicator. I have the server connected to a APS UPS with apcupsd and the powerdown script running to allow a proper shutdown when the battery gets low. It's been quite sometime since I tested it, but I assumed it worked as expected since the array was back up and running without my intervention and no parity check was performed. I now have a drive showing a red indicator. I checked the log and nothing jumps out at me, but I can't claim to understand most of it. I have stopped/restarted and rebooted the array mulitple times and this drive always shows red. I've attached a copy of my log. Is my drive bad or is there something I can do? syslog.txt

Thanks for the feedback guys. I thought I remembered unRaid formatting the drive even before an upgrade, but it's been so long since I've done one, I must be mistaken. It makes sense that a rebuild would copy over the file system thereby 'formatting' the drive. I never thought of it like that before. I did the preclear primarily to test the drive (nice utility Joe L.!).

I recently purchased a Seagate 750G drive and rand preclear on it. Once with a single pass and again with a double pass. I was adding it to my unraid tower as a replacement to a smaller existing drive. After the preclear I powered down the server and removed the smaller drive and installed the new "precleared" Seagate. When I powered up I went under devices and assigned the new drive to the disk number (disk9) of the old (now missing) drive. When I went back to the main page it showed a blue dot next to the new drive and presented me with the option to "upgrade disk and rebuild data" (or something like that) or "restore". I chose "upgrade disk" and expected it to then format the drive, but it never said that it did. It just proceeded to start the rebuild. Why didn't it say anything about formatting the drive?

I see. Don't bother yourself with it then. I've never done any scripting or created a batch file and I don't want people to have to research it for me. I just thought it might be easy enought that someone would know off hand how to do it. Thanks anyway.

RobJ - not exactly sure how to run that.