Holy crap dude.  I don't know what you are talking about.  Disk 4 is a lost cause.  Totally.  Superblock on disk5 can't be repaired no matter what I do.

 

I don't know what you think I am not following but I got two disks that crapped the bed and I am getting terrible advice and links to a bunch of other places....

 

Don't add anything.  I wish Joe L. was around anyway....

I read another post that suggested moving the drive to other ports.  I had an entire card free so I tried it and this is where I am FYI:

 

Status Disk Mounted Device Model/Serial Temp Reads Writes Errors Size Used %Used Free

OK parity /dev/sda ST32000542AS_5XW1D19C 27°C 243 319

OK /dev/md1 /dev/sdc ST32000542AS_5XW18K0D 29°C 189 77

OK /dev/md2 /dev/sdb ST32000542AS_5XW2061D 30°C 154 76

OK /dev/md3 /dev/sdd ST32000542AS_5XW1BAFV 27°C 187 81

DISK_DSBL_NP /dev/md4

OK /dev/md5 /dev/sdh 00M_WD-WCAZA1055519 28°C 73 0

OK /dev/md6 /dev/sde 00M_WD-WCAZA1055748 27°C 194 82

 

Neil

 

Why don't you read your own posts. You post 42 & 44 both clearly said you are rebuilding the superblock and then doing other checks on disk4 and that it was device sde. This despite me posting to try rebuilding the superblock on disk5. And then you complain I give you bad advice? How the hell can anyone give you good advice when your responses describing what you are doing are complete crap? Then you go and complain and act all offended when I point out  that you first posted you're working on disk4 and then you claim that was disk5 and disk4 is a write off. Yet, there is no indication you actually tried to fix disk4, but then how would I know, you could have easily posted some response about disk4 and called it disk5.

 

If you read back I did ask if those drives were on a seperate card or had something different compared to the other drives. Don't recall any response to that one either.

 

FYI, trying to fix the drive and having it actually get repaired are 2 different things. Don't blame the  messenger if the repair attempts don't work.

 

Go buy a RAID card and have fun making those EARS drives reliably work with one of those. Personally, I'd like it better if you weren't here.

 

In case you are too stupid to figure it out, try disk4 on the new controller too...

 

Peter

 

ps, you're the kind of person who would probably go back and edit their posts to "prove" I was wrong so I'm quoting them here;

 

Post 42

Disk 4

 

root@Storage:/boot# reiserfsck --rebuild-sb /dev/sde1

reiserfsck 3.6.21 (2009 www.namesys.com)

 

*************************************************************

** If you are using the latest reiserfsprogs and  it fails **

** please  email bug reports to [email protected], **

** providing  as  much  information  as  possible --  your **

** hardware,  kernel,  patches,  settings,  all reiserfsck **

** messages  (including version),  the reiserfsck logfile, **

** check  the  syslog file  for  any  related information. **

** If you would like advice on using this program, support **

** is available  for $25 at  www.namesys.com/support.html. **

*************************************************************

 

Will check superblock and rebuild it if needed

Will put log info to 'stdout'

 

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

 

reiserfs_open: the reiserfs superblock cannot be found on /dev/sde1.

 

what the version of ReiserFS do you use[1-4]

       (1)   3.6.x

       (2) >=3.5.9 (introduced in the middle of 1999) (if you use linux 2.2, choose this one)

       (3) < 3.5.9 converted to new format (don't choose if unsure)

       (4) < 3.5.9 (this is very old format, don't choose if unsure)

       (X)   exit

1

 

Enter block size [4096]:

 

 

No journal device was specified. (If journal is not available, re-run with --no-journal-available option specified).

Is journal default? (y/n)[y]: y

 

Did you use resizer(y/n)[n]: n

rebuild-sb: no uuid found, a new uuid was generated (689282ab-b4d3-444a-9166-88dcd9b381c5)

 

rebuild-sb: You either have a corrupted journal or have just changed

the start of the partition with some partition table editor. If you are

sure that the start of the partition is ok, rebuild the journal header.

Do you want to rebuild the journal header? (y/n)[n]: y

Reiserfs super block in block 16 on 0x841 of format 3.6 with standard journal

Count of blocks on the device: 488378624

Number of bitmaps: 14905

Blocksize: 4096

Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 0

Root block: 0

Filesystem is NOT clean

Tree height: 0

Hash function used to sort names: not set

Objectid map size 0, max 972

Journal parameters:

       Device [0x0]

       Magic [0x0]

       Size 8193 blocks (including 1 for journal header) (first block 18)

       Max transaction length 1024 blocks

       Max batch size 900 blocks

       Max commit age 30

Blocks reserved by journal: 0

Fs state field: 0x1:

        some corruptions exist.

sb_version: 2

inode generation number: 0

UUID: 689282ab-b4d3-444a-9166-88dcd9b381c5

LABEL:

Set flags in SB:

Mount count: 1

Maximum mount count: 30

Last fsck run: Sat Apr 16 08:57:07 2011

Check interval in days: 180

Is this ok ? (y/n)[n]: y

The fs may still be unconsistent. Run reiserfsck --check.

 

root@Storage:/boot# reiserfsck --check /dev/sde1

reiserfsck 3.6.21 (2009 www.namesys.com)

 

*************************************************************

** If you are using the latest reiserfsprogs and  it fails **

** please  email bug reports to [email protected], **

** providing  as  much  information  as  possible --  your **

** hardware,  kernel,  patches,  settings,  all reiserfsck **

** messages  (including version),  the reiserfsck logfile, **

** check  the  syslog file  for  any  related information. **

** If you would like advice on using this program, support **

** is available  for $25 at  www.namesys.com/support.html. **

*************************************************************

 

Will read-only check consistency of the filesystem on /dev/sde1

Will put log info to 'stdout'

 

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

###########

reiserfsck --check started at Sat Apr 16 08:59:29 2011

###########

Replaying journal: No transactions found

Zero bit found in on-disk bitmap after the last valid bit.

Checking internal tree..  

 

Bad root block 0. (--rebuild-tree did not complete)

 

Aborted

 

 

 

Post 44

Disk 4 when I click on it in unraid says:

 

Partition format: MBR: unaligned

 

Great.  

Im not anything like that dude.  Im not going back to change history.  You are snooty and obnoxious and my data is going down the drain so Im a bit frustrated and frickin exhausted screwing around with this and 4 other computer projects gone wrong.  The beginning of this whole thing I was given BAD advice.

 

I appreciate the community and it was the reason I invested so heavily in this product.

 

No crap I wouldn't use ear drives in a raid card if they were free.  Despite who you think I am, im not a total moron.

 

Thanks for your help.

 

I ran the script to repair the partion on disk FOUR (4) and it fixed the partition and now it seems to think the drive is new.  I don't know what to do next but I can't start anything.  Both drives are on the new controller for grins and giggles. Going to get dinner and be back soon.

 

Trust me I can't get past this without someone's help so I don't want to seem ungrateful.  I do appreciate the help but I am very overwhelmed with all the tabs in firefox I have open and which drive and which letters are which.  I wrote of disk 4 a while ago for some reason but I can't tell you why for sure.

 

I'm sorry.

Disk4 is "new" because once you run the array without a disk the array no longer cares if the original disk is put back. Now, any disk put into that slot is assumed to be new and will be rebuild if you start.

 

Try assigning disk4 as the cache disk and see if you can access the data.

 

Can you access the data on disk5 now?

Can you access the simulated data on disk4 now?

 

Peter

 

I assigned disk 4 as the cache disk and it reads as unformatted

Could I copy my config from the USB before I started it with disk4 missing and try to get disk4 working in the array without disk5?  I was hoping that I could get disk5 to rebuild from parity.

 

I have two blank drives ready to go pre-cleared and everything if needed.

 

Thanks!

 

Neil

 

I doubt a rebuild will work. Both drives are damaged and the parity was created based on earlier drives that were OK. So, you will end up with a damaged drive again. Still, once again I will ask - when the array is running without disk4 assigned can you see the simulated data on disk4?

 

If your answer for the simulated disk4 is no then I think you will have to format the real disk4 drive (as a cache) and then stop the array and do a --scan-whole-partition to recover the data. Then, start the array again and sorting the data out from the lost+found directory. The format won't overwrite the whole disk but it will lose the file table meaning the disk will appear blank.

 

You can copy the disk to one of the other ones first by using this command so if the recovery goes bad you have another copy you can go back to and try again. The command is;

 

dd if=/dev/sdX of=/dev/sdX bs=4096

 

If is the source and of is the designation. Don't get them wrong because it is permanent.

 

Peter

How do I know about the simulated data on disk4?  Im not sure I can start the array right now.  I just started it and all I see are disk1 2 3 and 6

 

Neil

 

Running --scan-whole-partition on Disk 4.  Not sure what to do when it is finished in about an hour?

 

Neil

 

Finished.  tried mounting that drive as a cache drive but still shows unformatted.  Am I supposed to do something else to fix this drive up before doing that?

Ok screw me but somehow disk 5 is mounted and working?!?!?!?! I wonder if I can replace disk4 and see if it will rebuild.  Anyone have any thoughts on this pleasssssse?

Replaced disk4 and currently rebuilding.  Finally the computer gods have shined down upon me!

 

Thanks for all the help!!!

Rebuild completed but disk 4 is empty:

 

disk4 ST2000DL003-9VT1_5YD1BCQH 27°C 1,953,514,552 1,953,422,088

 

Very strange.  This was a new drive but apparently nothing could be rebuilt from parity? 

 

Makes me wonder about the integrity of the rest of my array?!

 

Parity reads as a-ok.  Any thoughts?

How does disk5 look? I bet it's got damaged or missing files which then caused the disk4 rebuild to go badly.

 

Try running the --scan-whole-partition on the rebuilt disk4 and see if any files are found.

 

I'd run one last check on disk5 and confirm the file-system is OK.

 

Peter

Yeah there were a few things in lost and found.  At this point I am trying to recover my recordings which are out of sync and then I will blow this box away and sync back over.  Im not taking any more chances.

 

Neil