rockytt

did that - posted earlier about the upgrade

Very sure - all the "writes" are shown as belonging to the parity disc and disc 1 shows all 2tb free... Like I'd said - it's only data, not the end of the world - and mostly backups for stuff I have anyway.

sorry - in my world the console is the GUI (which is where I did it) - not used to this command line place

did the shutdown from the console - stop>shutdown It said the parity check was being done because of the missing disc

Yup - not so good news. In the process of doing exactly this-the server decided that since drive 1 was missing/unassigned from the array, it was time to conduct/start a parity synch w/o asking for any input first. I've got a few things I'm going to try over the next few days to try and recover the data on that drive- I do appreciate the help though and am confident it will be sorted out in time.

Nope - did everything you suggested, but when I reassigned disk 1 and tried to restart the array I had the same problem- bad disk then??

Thanks for all your help - will give it a go later today and report back- thanks!

attached! smart_report_sdl.txt

I understand-i was abbreviating it in my post ran it and the results are (as stated in a previous post) too long for me to see on my screen I don't know how to capture it for you and the highest line I can read is the same as in a previous post: 40 51 08 00 00 00 e0 Error: UNC 8 sectors at LBA = 0x00000000 = 0

your patience is much appreciated- not sure what to do after running cmartctl- doesn't show up in syslog and I don't know how to grab the output

New syslog attached after 4.7 upgrade (and now I can see it over the network) syslog.txt

upgraded to 4.7 so that all these commands will now work can't see the whole screen, but have a line that reads: 40 51 08 00 00 00 e0 Error: UNC 8 sectors at LBA = 0x00000000 = 0

should I upgrade this to 4.7 first?

error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

OK - fingers crossed here that this can help! Syslog attached syslog.txt

I'll see what I can accomplish later - thanks for the help. Actually, it didn't explain it very well at all-that post was what I'd used to try and and get to the syslog via the network... And simply saying "Via the console or telnet session, you can type this command:" doesn't "explain it pretty well" at all- I apologize if I sound snippy - frustrated a bit (not the first, I'm sure!) and w/o having my machine connected to a monitor/keyboard I don't seem to be able to do anything btw-I do have a network connection to the server-which is how I'm able to see the dashboard and attempt the "start" - it's just the "//tower/log/syslog" (from the post that was linked to) that doesn't work.

Trying-when I enter "//tower/log/syslog" I get an "Oops! This link appears to be broken" error message- Any chance we're just looking at a parity drive failing/failed?

short story: rebooted array and all discs (1-11) show green and parity shows orange. I click "start" and after the page refreshes, nothing has changed. What could be causing my array to suddenly not start and what can I do about it? (Parity was checked a couple of weeks ago w/no errors and since I'm running 4.4, I've had this going for awhile) Thanks for any and all help!

OK - attempt #3... Thought I was buying the same (old) MB, actually got a close relative instead- Seemed to boot up fine, except that the the 8 disks on the 2 PCI controller cards show up as red (missing) - some bios setting I might have missed? It never came up before, so I'm hopeful it's just a simple setting that I never had the opportunity to mess with... Board is an ASUS P5LD2-VM REV:1.03G

Small update, unplugged everything, reseated cpu and still get no boot/post screen. Same case/video card/memory/cpu as before with an identical MB Dropped by Fry's to try and p/u a MB speaker and was told they don't carry them. (sigh...)

Thanks for the replies - I'll try a few things today - remember that everything is from the other machine (memory, PS, CPU etc) I like the idea of starting w/minimum configuration just to be sure though- Thanks!

Open to suggestions here-I'm not a complete idiot here, but I've just never (ever) had this happen before: I found an exact replacement for my failing board and moved all the pieces over. I double-checked the connections and fired her up. Fans came on, I heard the HDs cycling on and was initially optimistic-but then nothing else. The boot screen never appeared, keyboard + mouse never powered up, and the USB stick never did either. Is there anything else other than a dead MB that could be causing this??? No warning beeps, no flashing lights, just nothing after the HDs cycling on...

OK-so that seemed a little strange- 1) swapped data leads with one good drive and one of the bad. rebooted and had 3 red drives, with the same 2 showing as missing. 2) put the leads back, then simply swapped data leads on the "bad" drives. rebooted and had 2 reds, but showed "disc configuration wrong" instead this time. clicked to record the new configuration (can't remember the exact term) and all are green again. 3) go run a parity check and the two drives are clearly unhappy (ton of errors) and then both are red again.me Time to pull the board and see if we can find a replacement... Thanks for all the help - fingers crossed for a successful rebuild...

Yeah - not a card as they're both plugged directly into the MB, and have also swapped out the power splitter- Good to know that, although a tad inconvenient (!), swapping out the MB won't ultimately be a death blow...

I think I know the answer here, but was hoping for a little advice before ripping things apart. Been running my unRaid box for a couple of years with very few hitches. Currently (at least until a few hours ago!) had 12 drives (10+1 parity) operating just fine. Parity, 1,2,3 drives running off the MB and the other 8 off two different SATA cards. Suddenly I get huge problems and I'm told that drives 1 + 3 are missing (red)-which is, of course, a bit of a problem. I run a parity check every month, no errors reported, etc, etc - so this is really out of the blue. I realize that w/o actually looking at the equipment you can't begin to give me a 100% diagnostic-but what are the chances that it's the SATA controller on my MB that's decided to conk out as opposed to two different drives (one fairly new) simultaneously doing so? Is a good test to swap #1 and #2 and see if I still get the "drive 1 missing" error? (It would seem that this would indicated a controller issue rather than a physical drive issue) Anything else I could try? If worse comes to worse, what are the chances of "simply" (hah!) swapping the MB for a different one and still keeping all my data intact? Thanks for any and help on this - it's much appreciated!