can't open shares any more

[sacretagent]

hi all

 

I am having a problem and i guess it is related to those damn EARS 4K drives

 

i added one to my existing array filled it up to 800 gb and from then on i have nothing else then troubles

 

i have SHFS going up to 100% of processor usage the moment i try to access the share

 

and i get these in my logs

 

Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey 
Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck?
Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey 
Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck?
Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey 
Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck?
Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey 
Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck?
Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey 
Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck?
Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey 
Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck?
Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey 
Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck?
Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey 
Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck?
Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey 
Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck?
Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey 
Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck?
Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey 
Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck?
Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey 
Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck?
Dec 17 21:34:50 p5bplus kernel: REISERFS warning: reiserfs-5082 is_leaf: free space seems wrong: level=1, nr_items=7, free_space=1936 rdkey 
Dec 17 21:34:50 p5bplus kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 51760081. Fsck?

i have some experience with linux and i have read a lot already but i can not really find a reason for above in the logs

i tried to do a filecheck on the disk md4 (which is the EARS 1 GB drive )

but ended up with more problems (disk was disabled by unraid)

so i cleared the disk again and let the array rebuild on the same disk again but the problem still persists

 

so i would like to know if there is something i can do to save my data ?

and how can i get this damn disk to work with unraid ?

would adding the plug on the disk help with my problem ?

 

please let me know if there is anything else what you need to troubleshoot or what i can do more ?

 

[Joe L.]

The issue is that the file system has corruption, not the disk itself.

 

When you cleared the disk the corruption on the "simulated" file system still existed.

 

You need to just follow the procedure as described here in the wiki for that specific disk  ( /dev/md4 ):

http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

 

Joe L.

[lionelhutz]

Your problems are not specifically related to it being an EARS drive or a 4k drive. As far as unRAID is concerned that drive appears to be a 512b sector drive just like all the others before it.

 

It's likely file system corruption but could also be bad hardware. Follow the checks as Joe has suggested.

 

Peter

 

[sacretagent]

Thanks both for the info

i ran reiserfscheck and it found a lot of problems

it said i had to run --rebuild-tree to solve the issues

running that now...

if i am correct i will probably end up with a lost+found folder on that drive

 

will my parity still be intact ? or do i need to run first a parity check (with our without correction through unmenu or just from the normal menu?)

i have a new EADS 1TB disk that i want to add after this is done .....

 

in the hollidays the plan is to change the parity drive to a 2 TB and then add a few 2 TB drives

 

any suggestions on a good drive ? i have 2 hitachi's in the box and they seem to run fine .... only slightly hotter then the WD's... although they broke a few times my Intel raid 5 on one of my 2 other computers with intel raid 5 of 6 x 1 TB disks each ...all EADS and EACS (now) ... never had problems with these... i had one failed on me after about 3 years which i tried to replace by the EARS but boy did that also give problems ... i checked the ears a few times with smart and he passes every time so i think he is not bad ... but still he seems to cause nothing else then problems... if he screws up one more time then i will use him as a download disk ... (pity though to use such a large disk for that)

 

anyway i like unraid and i am planning to build a big box soon (20 drives) so i can eliminate the intel raid 5 setups so that these disks will not have to spin all day ....

[Joe L.]

Thanks both for the info

i ran reiserfscheck and it found a lot of problems

it said i had to run --rebuild-tree to solve the issues

running that now...

if i am correct i will probably end up with a lost+found folder on that drive

You might.

will my parity still be intact ? or do i need to run first a parity check (with our without correction through unmenu or just from the normal menu?)

If you are doing the check on /dev/md4 parity will be in sync with the corrections automatically.

i have a new EADS 1TB disk that i want to add after this is done .....

 

in the hollidays the plan is to change the parity drive to a 2 TB and then add a few 2 TB drives

Best to fix the file-system corruption first then add the drives after you get it all back to normal

any suggestions on a good drive ?

I like the Hitachi 7200 rpm drives. and the Seagate 7200 RPM drives.  I've got no experience with the "green" drives to offer, sorry.

 

Joe L.

[sacretagent]

Thx for the help Joe.L

 

the rebuild tree solved the issue

 

ended up with a lost+found folder though

can not access that folder from the gui though

can access it from putty ... only files and folders with a bunch of numbers as name in there

is it safe to just rm -rf lost+found ?

the parity led is still green after the file system check ... so i can just go ahead and add the new drive ?

 

 

[Joe L.]

Thx for the help Joe.L

 

the rebuild tree solved the issue

 

ended up with a lost+found folder though

can not access that folder from the gui though

can access it from putty ... only files and folders with a bunch of numbers as name in there

is it safe to just rm -rf lost+found ?

the parity led is still green after the file system check ... so i can just go ahead and add the new drive ?

 

 

Those are directories, files and fragments of files.  You can see them on the "disk4" share, or, rename the lost+found folder.

 

Unfortunately, the files will not have their usual extensions, so you'll need to figure out what the were and give them their original names.

 

 

Of course, if nothing is on that disk you can't replace from elsewhere, you can delete them.  (but they might be your favorite movie, or a irreplaceable picture of your pet goldfish, etc.  For that reason you might not want to delete the files so quickly.)