DonkeyDon

tl:dr; I get strange characters in screenshot on boot. I can login , and do an "ls", and an "ifconfig" but the results are illegible. See screenshot. GUI isn't working, and the IP is not responding to pings. Any suggestions are greatly appreciated. Background: I have an unRaid system that's been running good for years. Its on an old 6.5ish or 6.6ish version, and the upgrade fails, so I was leaving that upgrade until i built out a new server, and a few years have gone by, with that thought. Recently, I just bought a couple 16TB drives, and wanted to preclear them to check them out before the return period passed. So I powered down gracefully, disconnected two drives, since I didn't need the array working during the preclears, and booted up. Because of the old 6.6ish version the precelear app could not be used, and I cant update, so I tried to copy Joe's .sh script to the flash drive from windows(actually first i followed some online instructions at https://github.com/tquizzle/unRAID to wget the script...and when that didn't work i copied from Joe's original thread via windows to /flash/ directory over network. ) The script gave me an error at line 1307 and never even started, so I gave up on this idea, and powered down, and put drives back to the way it was. Now it won't boot. as shown in the screenshot.

Agreed. Iwent looking for somthing like his when i first got on unraid, but didn't find much that would stay sync'd. But I definitely haven't kept current with what tools are available. Can unRaid 6 use an autochecksum file system like you are describing? if not, what tools do you use for checksums?

I actually had been planning to build a version 6 box, separate from this one, after i finished consolidating. I did the same thing when i upgraded from 4.7, i've always felt safer copying files to an up-and-running box, rather than fiddling with the box containing my data, Before correcting parity, I may replace disk2 with a new.blank drive, then reconstruct disk2 data, then compare the reconstructed files to what's currently on the old drive(mounted as a single non-array disk). At least then, i can isolate the "known good" files from the suspect ones. Bad idea?

I did the above and as it started the parity verify , I immediately got 1007 errors, and 106 writes to the array as shown below. These numbers stayed steady for about an hour, before I let the verifying continue while i slept. Now at 49% with 1381 errors. Another oddity, is that there is no syslog except, for one line showing the restart. This is odd, because when I saw the initial errors, I check the syslog last night, and it showed that they happened in the first 1-2 secs of the scan. I check the flash/logs directory, and there is no files there for this restart of the server, based on timestamp of when i know i restarted it also there was one disk error, which I believe happened before this reboot, when the cabling was questionable. This is my backup server, meaning I don't have a backup of it. So is there an easy way to tell which files on disk2 correspond to the parity errors? if not, how should i proceed?

Hi, I found a few posts regarding this subject, highlighting differnces in version 6, and whats different for version 4.7, and earlier. Being between on version 5.0.5 today, I wanted to ask specifically for my situation. My problem started while I was moving my existing drives, one by one into a new 5 in 3 trayless cage, and running a parity verification in between each swap to make sure each drive worked properly, before I got 5 drives jumbled together. After the 3rd swap, I had an issue where the array wouldn't start( drive2 aka sdg was absent, resulting in the red square DISK_DISABLE_NP. So I shut down, and I replaced the cable. Upon power up, got the blue dot and assigned the drive to same array slot. I believe there's no real problem with any of the drives at this point. Now, I want to restart the array, and run parity without corrections, just to make sure I don't have any other problems, before i go writing anything to what should be an error-free array, but my screen only shows Start as "bring array online and Rebuild parity", But I definitely don't want to rebuild parity until I'm double sure I've got all the drives where they belong, and fully operaional. My screen only offers me the options in the screenshot below.. so how can I safely just start the array and only verify parity without writing to the array? Thanks in advance ! Don

I had a similar problem to this unsolved post : http://lime-technology.com/forum/index.php?topic=29368.0 One preclear session was frozen in putty, and not updating. Strangely, this had blocked me from logging into a new session as well. See attached screenshot. After googling for way too long, I stumbled onto this explanation: http://munkymorgy.blogspot.com/2008/07/screen-ctrl-s-bug.html In case, the link dies in the future, it turns out that I had accidentally fat-fingered CTRL-S, instead of CTRL-A. And CTRL-S tells the terminal to stop updating. CTRL-Q restores the updating. So I had updates again!! .... but still couldn't login . I then had to do some "CTRL-A,p" on each putty session, and "exit" each idle background prompt. Do that on each window until you get the blazing inverse ANSI "[glow=green,2,300]No other windows[/glow]" at the bottom of your preclear window. Once I had only my three preclears running in all my Putty sessions, I could once again log in to root , as per normal, in the fourth window. Don't ask me why or how that helped, but it did the trick for me... I figured I'd share, in case someone else runs into similar issues. Cheers, Don

Everything working fine after power cycle and parity check. Thanks for the help, Joe.

Ok i did search, but i dont know what to look for on this. server has been fine for years..but now: I cant access the webpage or the server files, and I can't shut it down. What I've tried... 1) I can ping the IP of the server, however, i can't access webpage...could access shares at first, but not now. 2) tried pressing powerbutton( I believe i have the power down script installed on unread 4.7.?... so this usually inities a safe shutdown with audible beeps and drive activity. Now, though, I get no indication that i even pressed the button. 3) tried telnetting to the unraid box and logging in to root. CD /boot, then I type powerdown or powerdown.sh. Telnet session hangs, but I can open more telnet sessions. Also tried cd /boot, and ls or dir, which both also hangs the telnet session. I'm a linux noob, but this seems bad to me. 4) unplugging and replugging the network cable gets me a low beep, and a high beep, so the DHCP etc is working normally.but still no webpage or shares. 5) I have not seen the flash drive led blink, so I'm suspecting its died. Can I hot unplug/replug the flash drive? or am I better off just hard power cycling? or there a third approach that would be safer? Thanks in advance , Don

AS you can see in the attached syslog, I keep getting these errors "Detected TX Unit Hang". I don't have any idea what that means, but the system recovers each time, and my file transfers all seem to be working while it happens, so its not a catastrophic failure. The unraid box keeps giving a low beep when the it disconnects, and then a higher beep when it reconnects. Which is becoming annoying... hearing the bing-bong every couple minutes. It seems to stop transferring then resume, but I'd rather it just didn't stumble at all. I've tried disabling the PCI LAN chip on the mobo, but that doesn't seem to help. Any ideas on how to prevent this would be greatly appreciated. Thanks in advance, Don syslog-2010-07-20.zip