I have an issue with a replacement drive that shows unmountable after the rebuild completes.

unRaid version 6.1.6

 

Here's how I got in this situation:

I was replacing my old 2 TB parity drive with a 4TB drive. This completed without an apparent hitch.

I then wanted to replace an old 1TB  data drive with another data drive.

 

I have 10 data drives.

 

I moved all the data from drive 7 to other drives. My intent was to then replace this 1 TB drive with the 4TB drive.

 

Unfortunately this is where things went awary. I accidentally replaced drive 8 with the 4TB drive (Not the blank disk 7). I was a bit slow to catch it was rebuilding the drive 8 on the new 4TB. I now know I probably should have let this, but I panniced and stopped the rebuild.

 

I then shut down and swapped disk 8 back in. I mistakenly thought things would go back to the way the preciously were.... I now know this is not the case. The rebuild started on my old drive 8. This made me nervous, and I stopped it. As i have no other backup of this data.

 

I dropped in my old 2 TB parity drive into the disk 8 slot and started the rebuild hoping it would rebuild on this drive. Thus preserving my old drive 8 as a backup.

 

The rebuild completed (after 20 odd hours)... however the drive shows as unmountable.

 

I ran a check on the drive, and it indicates I should run reiserfsck --rebuild-tree. ( Note I am doing this through the GUI).

 

When I do this I get a warning message and asked to enter 'Yes' continue. When I do this I get a list of command options. Do I need to re-enter the "reiserfsck --rebuild-tree" command at this point, or is the rebuild running?

 

BTW: I am a unix/linux novice.

 

 

 

You might try mounting the original disk outside the array with Unassigned Devices plugin and see if you can read it.

I tried the unassigned devices tool. The drive shows up, but every time I try to mount it... it just clocks for a second or 2 and stays unmounted.

 

 

 

I tried inserting a brand new drive in the slot (2TB WD black). Then let the rebuild commence. It ran for about 18 hours, and finished without errors. I got the message the drive has returned to normal operation. However, this drive shows as unmountable as well. When I look at the disk settings on that drive the File System Status shows: "Unmountable - No file system (32)"

 

I did not preformat this drive. I simply inserted it in the slot, and let the rebuild commence. Did I miss a step, or this a sign my parity is not rebuilding correctly?

You can try switching the file system for that drive to "auto" and see if it makes a difference

Are you following the wiki?

 

Check Disk Filesystems

Unfortunately this is where things went awary. I accidentally replaced drive 8 with the 4TB drive (Not the blank disk 7). I was a bit slow to catch it was rebuilding the drive 8 on the new 4TB. I now know I probably should have let this, but I panniced and stopped the rebuild.

 

I then shut down and swapped disk 8 back in. I mistakenly thought things would go back to the way the preciously were.... I now know this is not the case. The rebuild started on my old drive 8. This made me nervous, and I stopped it. As i have no other backup of this data.

 

I dropped in my old 2 TB parity drive into the disk 8 slot and started the rebuild hoping it would rebuild on this drive. Thus preserving my old drive 8 as a backup.

 

The rebuild completed (after 20 odd hours)... however the drive shows as unmountable.

 

There’s something not right with your description, if you really started to rebuild disk8 to a 4tb disk it wouldn’t be possible to abort that and rebuild to the old smaller disk, you had to have done another step here, possibly the cause of the unmountable disk

Are you following the wiki?

 

Check Disk Filesystems

 

I was able to rebuild the tree and recover some of the files on one of the drives that rebuild completed on (but wouldn't mount).

Nasty chore since most of the files were randomly named. I was able to use TRID to id the file types on many of the files. Which help me find my photos, and document files. The media files are so scrambled, as to not be worth effort of recovering. Easier just to recopy them from the media. I was mainly interested in recovering my photos and documents.

 

I then intended to rebuild the tree on original disk 8. Hoping to have first practiced this exercise on one of the rebuild drives. However, I have other issues now. After powering down and inserting the old 8 drive, the server won't come back up.

 

I keep getting "bios does not find proper hardware configuration". Even after pulling the 8 I am still getting that message.

 

I checked the cable connections, but I still get this message...

That or the system gets to a point where it tries to load unraid. The last thing it will flash is something about NVRAM then goes blank screen with an unresponsive cursor.

On some tries it acts like it's powering up but I get nothing on the monitor.

 

I suspect something is wrong beyond a drive issue... either a bad controller, bad board, or other hardware.

Does that sound right?

 

If so, I am guessing I can spend a ton of time trouble shooting what component (if not multiple) has gone awry. This is a 7-8 year old server, and I am thinking my best bet may be to get a new one. Then move the drives over. Thoughts?

 

Check your bios boot order, looks like it changed when you added one disk and it’s probably trying to boot from a disk instead of the flash drive.

Check your bios boot order, looks like it changed when you added one disk and it’s probably trying to boot from a disk instead of the flash drive.

 

Good call!

 

I couldn't even find the flash drive as an option in the boot sequence. The flash drive was actually not seated correctly. I had to re-seat it, and then fix the boot sequence.

 

The maids were here yesterday. I am betting while they were dusting in the office, they accidentally bumped the thumb drive with their dusting wands hard enough to loosen it a tad.

 

It's the only reason I could think that thing would have gotten lose.