Hi there I was wondering if anybody could let me know why my 2TB Drive is showing that it has 17TB free. I recently upgrade from 4.7 to 5.0.5 if that helps at all. I have attached a screenshot and any help is greatly appreciated. Thanks

 

http://awesomescreenshot.com/0702jhk4ed

Hi there I was wondering if anybody could let me know why my 2TB Drive is showing that it has 17TB free. I recently upgrade from 4.7 to 5.0.5 if that helps at all. I have attached a screenshot and any help is greatly appreciated. Thanks

 

http://awesomescreenshot.com/0702jhk4ed

 

17TB? Good luck finding a parity drive for that beast.

 

I got nothing.

Try Check Disk File systems.

Does the data display correctly?  i.e. if you go to \\Tower\disk7  do you see the correct set of files?

 

If so, I'd copy them all off to another drive (outside of UnRAID);  then run a Reiserfsck check on the drive.

 

I dont understand why youre upset!  You just got yourself some free storage! 

 

That is definitely weird.  Hopefully RobJ's link has a tool to help you out.

I'm with you, althoralthor, 17Gig of MAGIKstorage is a FEATURE, not a complaint!

 

That said, a very similar problem was reported 3 months ago in the forums, and I didn't bookmark it and now can't find it,

but from memory, garycase nailed the solution at Reply #5 of the thread.

when I had 2 disk have some errors & wanted a reiserfsck --rebuild-tree issues.

I had 3 word documents from my daughter backup all say they where 1.?PB in size.

I could not open, copy or delete them. once I had rescued everything else of that drive.

I formatted the drive as a new disk by itself

Thanks for all the help I have not tried the suggestions yet. But I did try replacing the drive with a 4tb since I upgraded the parity .but the same thing happens on the new drive except now it shows 15tb free instead of 17tb with the 2tb drive. Any suggestions on this thanks again.

It's reasonably clear the issue is with your file system -- NOT the drive.

 

You need to run reiserfsck to find an fix the file system errors.  Before doing this, be sure you have a copy of the drive's directory, so if anything goes awry during the process you'll know what files you need to restore from your backups.    If for any reason you don't have current backups, be sure to update them from the files you can read okay on the drive before you start.

 

Just finished running reiserfsck on the drive and got the results below. Please let me know what to do thanks

 

Bad nodes were found, Semantic pass skipped

2 found corruptions can be fixed only when running with --rebuild-tree

###########

reiserfsck finished at Thu Mar 27 14:18:25 2014

 

Just finished running reiserfsck on the drive and got the results below. Please let me know what to do thanks

 

Bad nodes were found, Semantic pass skipped

2 found corruptions can be fixed only when running with --rebuild-tree

###########

reiserfsck finished at Thu Mar 27 14:18:25 2014

That's [good] news.  Its probably the root cause of the problem.

You should run Reiserfsck with the --rebuild-tree option.

BE SURE you're doing the correct disk [or rather, be sure to do the Broken disk. ].

Just give the command again, like you did for '--check', and using the same device '/mdx', substituting your broken drive number for 'x',  and append the --rebuild-tree flag.

READ THE FOLLOWING PAGE, ESPECIALLY THE PARTS IN RED:

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

 

(Be sure to NOT do the Parity drive! its just bits and has no directory to fix. You'll lose your parity.)

 

Check back if you need help, or unsure.  Running Reiserfsck is not as bad as it sounds...but it is a powerful command line command, and easy to type the wrong flags by mistake. Just go slow and double check your typing.

So I just ran Reiserfsck with the --rebuild-tree option and then this happened and now the disk shows as unformatted if I start the array. Please let me know what to do thanks

 

Pass 1 (will try to insert 482317 leaves):

####### Pass 1 #######

Looking for allocable blocks .. finished

0%....20%....40%....60%....80%....Not enough allocable blocks, checking bitmap...there are 1 allocable blocks, btw

 

out of disk space

Aborted (core dumped)

 

Well ... I hope you did what I said earlier:  "...  Before doing this, be sure you have a copy of the drive's directory, so if anything goes awry during the process you'll know what files you need to restore from your backups.    If for any reason you don't have current backups, be sure to update them from the files you can read okay on the drive before you start. "

 

Apparently whatever was corrupted was more than Reiserfsck could correct successfully.    The fact you've had the issue with both an original drive and a replacement clearly indicates it's a file system issue (since UnRAID simply replicated it when it rebuilt the original drive).

 

At this point, what I'd do is connect the drive to a Windows box (via either an internal SATA port, an eSATA port, or a USB bridge device);  run WD's free Data Lifeguard utility; and do a Write Zeroes (choose the complete write when prompted) to the whole drive.  This will take several hours ... but when it's done the drive can be re-initialized and should be the correct size.

 

As for your UnRAID array -- go to the Utils tab; do a New Config; and assign all of your drives (EXCEPT the bad one, of course -- which you should have already removed from the system), being CERTAIN you assign the correct drive as parity.    Then Start the array and let it do an initial parity sync.    After that's done, you should do a parity check to confirm all went well.

 

Then ... when the write zeroes is completed on the other drive ... you can add it back to your UnRAID system.    You can then either do a Pre-Clear on it (BEFORE you assign it to the array) ... or you can simply add it to the array and UnRAID will clear it (this will take many hours and the array won't be useable during the process -- so a pre-clear is a better way to prepare the drive).

 

Finally, once the drive is back in your system with the correct size, you can restore the data that had been on the drive from your backups.

 

There are other options that can recover files from the drive.  Can you tell us what you believe is on the drive, and how important to you some or all of the files are?

There are other options that can recover files from the drive. Can you tell us what you believe is on the drive, and how important to you some or all of the files are?

Had this same occur (running v5.0.5) and unfortunately, ran reiserfsck --check and then --rebuild-tree with /dev/sdh instead of /dev/md2. Noticed my mistake and stopped it.

Went out and bought another identical drive (WD30EFRX [3TB WD Red]), removed the faulty drive, replaced it, new config'd, reassigned the drives with the new [precleared] drive in place of the faulty drive, and did a rebuild. Unfortunately, it didn't fill in any data for the drive (125MB used, 2.7TB free).

 

With the drive unassigned, tried running reiserfsck --check and then --rebuild-tree with the correct /dev/sdh1 but got the "aborted" message (out of space).

 

Trying to check my other backups to see what it could be beyond old documents, school work, tv shows, and other content.

Plugged the faulty drive into a Windows 7 x64 machine and ran DiskInternals Linux Reader and it shows the drive as 746.52GB.

 

Any other things I can try to access/recover any data off the drive?

Any help is appreciated.

Plugged the faulty drive into a Windows 7 x64 machine and ran DiskInternals Linux Reader and it shows the drive as 746.52GB.

 

That just means the system you plugged it into doesn't support drives > 2TB.  What you're seeing is 3TB modulo 2TB (i.e. the remainder).    Did you plug the drive into a native SATA port or a USB bridge device?  If a bridge device, it may be that you're using a USB bridge that doesn't have > 2TB support.

 

In any event, if you try a different system, you should be able to see the full 3TB.

 

That just means the system you plugged it into doesn't support drives > 2TB.  What you're seeing is 3TB modulo 2TB (i.e. the remainder).    Did you plug the drive into a native SATA port or a USB bridge device?  If a bridge device, it may be that you're using a USB bridge that doesn't have > 2TB support.

 

In any event, if you try a different system, you should be able to see the full 3TB.

Oops. My bad. Plugged it into my system directly instead of an external USB bay & it shows up as a ReiserSF volume. Unfortunately, still can't open the volume ("Can't open disk: ReiserFS Volume 1").

 

Hex preview shows content so I guess my next move is to pick up another 3TB Red and then create an image from Volume 1 to try to read it unless there's another application that may read it?