Buffalo Forums

Products => Storage => Topic started by: slipdog on January 16, 2013, 03:57:30 AM

Title: I30 error message then I7 checking error message Help Needed badly please
Post by: slipdog on January 16, 2013, 03:57:30 AM

Hi,

I have a serious issue!

Equipment is a Linkstation Duo 4TB Raid 1.

 

Two weeks ago the array had to be rebuilt which had taken about 10 hours, all been fine after that until now!

I had a lock up with the nas drive with error on navigator software saying I30 but no LED flashes on the nas itself and it would not power down (totally frozen)

After powering back up after a power off i got I7 error on navigator and LED flashes on the nas meaning Checking! after about 10 hours no errors showing which then i thought everything was ok again!

 

I have 4 shared folders and only 3 of them work, the 4th one comes up with a network error message saying windows cannot access \\LS-WXL99B\Movies (as if its vanished but the icon is still there)

 

The data must be there as the drive is saying 67% used, there is about between 550 - 600 GB of data that was in this folder.

 

How can i recover from this?

 

I thought having a raid one config means the data is safe on at least one of the drives but i cant access it!!

 

Please please please could someone try and advise me of what to do now.

 

I dont want to just start randomly try and work it out as i may make things worse in the learning process.

 

Thanks in advance

 

Slip

Title: Re: I30 error message then I7 checking error message Help Needed badly please
Post by: davo on January 17, 2013, 05:30:40 AM

Corrupt share, it will need to be deleted and recreated. However, before doing this, reset the unit to defaults via the admin page, unmap all shares on the workstation. reboot the workstation and try and map the one share you ar ehaving an issue with using its IP.

Title: Re: I30 error message then I7 checking error message Help Needed badly please
Post by: slipdog on January 26, 2013, 07:05:33 AM

Hi, Thanks for the reply Davo.

 

Unfortunately your method did not work, in the end it just created a new blank share.

 

This is what i did for anyone else who happens to be in the same situation that i was.

 

I removed HDD 1 from buffalo chasis, i connected a USB to Sata conversion kit (from ebay, very cheap) to the HDD.

 

I then downloaded some software called UFS Explorer Recovery (which gave me the ability to read the xfs file structure on a windows 7 PC.

 

Upon connecting the HDD windows complained the HDD needs formating, after closing this about 3 times it stop asking!

 

Running the UFS software it could then read the drive but only gave me the few shares i could see before and not showing the corrupt one.

 

It was showing 3 corrupt partition tables, so i selected re-construct partitions.

 

It did not re-constuct it as i had imagined it would do, but albeit it created lots of folders called inodes and in there was all my data so i was able to make a FULL recovery.

 

There was no option to copy to another nas drive on the network or any other network capable storage so it was transfered to the local HDD's and then transfered back to NAS. (makes double the time to recover!)

 

I am annoyed that i could not recover from a mirror raid config, so you always need a backup of your backup and lessons have been learned from this, i now have one nas backing up the other! expensive ish but what amount of money is it really if you lost all your data/photos/music/movies etc.

 

Hope this helps someone.

 

Cheers

 

Slip

Browser ID: smf (is_webkit)
Templates: 1: Printpage (default).
Sub templates: 4: init, print_above, main, print_below.
Language files: 1: index+Modifications.english (default).
Style sheets: 0: .
Hooks called: 55 (show)
Files included: 27 - 1055KB. (show)
Memory used: 735KB.
Tokens: post-login.
Queries used: 10.

[Show Queries]