hoamskilet

anybody?

Ran into a weird problem tonight. Server has been running strong for a few years now. All of a sudden tonight I couldn't connect. Machine was on and running, but wouldn't even show up as a connected device when I logged into my router. Long story short, if I unplug all my hard drives (I have 6), it will boot up and start to load from the USB drive. If I plug any one of the hard drives in, the MB will post and then just go to a black screen and sits there. Thoughts?

can that be run from within the gui or does it have to be done from a terminal?

ran the reiserfsck check and this is the message it came back with: reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md1 Will put log info to 'stdout' The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (488378637): (Input/output error).

ok, I will try that tonight. Thanks

That confirms that the drive is bad => it's actually not surprising, but good to confirm before you attempt recovery using the Linux tools on the UnRAID server. Just to be certain -- you ARE connecting the drive via an internal SATA port, and not via a USB bridge device ... right? As long as that's the case, there's nothing else to try with the desktop. yes it's connected to an internal sata port. so at this point am I pretty much boned on that drive? basically my only next step is to add the new drive and let it rebuild whatever it can?

Finally got it to open something up on that drive. This is the screen that popped up

Got that linux reader running. The drive shows up no problem, but when I double click on it a window that says "Reading file tree" pops up and then the program more or less freezes

Awesome, that sounds logical/safe. I'll work on that later tonight and report back. Thank you guys so much for the help

Do you have ANY spare ports -- or are you maxed out with the 6 drives you have? Also, do you have a Windows PC with a spare SATA port on it? Yeah, my board is maxed out at 6 ports. Need to get a pci card to add ports. Yes, I have a desktop with free ports

doh, forgot to add to my last post that I pulled the sata cable and relaced it with a completely different one and pulled the power and reseated it. Still came up unmountable. Is there a "go to" pci card that has worked well for adding ports?

Alright, I gotta put it on hold for a bit anyway. Knew I had extra slots in the case, but forgot to check my sata ports and I need some more. So what's the consensus route here....is grabbing a 2nd new drive going to be the best route? I'd rather not spend the money if I don't have to, but it it's the best route I will

uhh.....yes, haha

NO => this isn't a good option at this point, since a parity sync has already been running (for over a day) on the v6 setup. There's NO chance that parity is valid -- using that option would simply result in a known-bad parity disk which would not be in a reasonable condition to rebuild the failed disk. The new parity sync has already corrupted at least the first 1% of the disk, so any rebuild would be very unlikely to have any reasonable chance of recovery. IF you want to try this anyway, buy TWO new disks => one to try this with; and one to actually put in the array. You'll need to do this FIRST ... before you do ANY writes to the array at all. Basically you would do a New Config with all of the current disks (including the bad one), with the "parity is already valid" box checked; Start the array; Stop the array; unassign the bad disk; Start the array (so it shows as "missing"); Stop the array; assign a NEW disk to that slot; then Start the array and let it do a rebuild. When that finished, you Stop the array; do a New Config -- this time assigning the OTHER new disk to that slot and NOT checking the "parity is already valid" box; then Start the array and let it do a new parity sync; then (after that finishes) format the new drive; and you'll then have a good, parity-protected array. Meanwhile, you'll have both the original and the "rebuilt-but-known-bad" copy that you can attempt to do some recovery from "outside" of the array. There IS a chance that the "rebuilt-but-known-bad" copy may have some recoverable data in the area past where the aborted parity sync had already written ... but realistically this simply isn't a good option at this point. This is indeed what you need to do r.e. attempting recovery -- Reiserfsck is VERY good at recovering data from corrupted disks; so there IS a chance. But at this point you may as well get a good v6 array running and ready to copy any recovered data to. Did this failure happen after you'd shut down v4.7, or did you not run a parity check in 4.7 before shutting it down to upgrade it? As I noted earlier (too late now), THAT would have been the time to do a rebuild ... BEFORE you upgraded to the new version. But at this point it's simply not an option. One other thought: Did you check the cables as I suggested earlier? IF the issue is simply a loose cable; then a New Config with all of the drives original drives assigned will let you do a good parity sync and everything will be fine with no need to replace the drive. I'd definitely unplug; then replug both the SATA and power cables to the problem drive and try it before doing anything else. If it mounts, you're good to go Alright, I've got a new drive. While I'm in there, I will try checking the cables of the old drive and see if that helps. In the mean time, if that doesn't help, what are the steps I need to do to try and recovery seperate from the array?

sounds good. I've got plenty of slots, so I'll just leave the old one in