Buffalo Forums

One of our customers has a TeraStation Pro with 4 TB disk with firmware version 1.33. Today the customer told me that he can no longer access the shares on the NAS, while he can still access the web interface: there's only a warning in the home page of the web interface ("RAID Array 1 has low disk space" - it's true, the used hard disk space is 99.08%).

The customer called Buffalo Tech support (here in Italy) and they told him that if the used disk space is over 96-97% it's no longer possibile to access the shares and that he needs to recreate the array: moreover, the only way to recover data (between 3-4 TB of variuos stuff) is to mount 3 HDD on a PC and use a third party utility.

Is it possible there's no other way to recover the array???

Thank you!

how many shared folders do you have created? try accessing the unit via FTP.

Why don't you refer to your backup?

Two shared folders.

Also the FTP access is no longer working. Buffalo support told the customer that there's no way (FTP, SMB etc.) to access the data on the array if the disk is (almost) full.

I'd like to avoid to move about 4 TB of data back and forth... It's strange that there's no other way to access the array... other than restoring a backup and/or recreating the array. I mean, the array is working, there's no disk fault, the system is working... but it's blocking all access to the data on the array!

Thank you for your answer!

You could try booting the NAS into EM and see what that yields although I would venture to agree with the tech support as there might have been a RAID corruption at such a high volume of usage.

Thank you for your answer Dustrega!

I have to questions:

1) if there's a RAID corruption, shouldn't there be a warning or an error in the web home page or in the system logs? I only have a warning about the disk usage...

2) If I boot the NAS in EM mode, is there some way to access the data on the array?

If you boot into EM you can attempt access of the data the same way you would normally but it's no guarantee.  You could also try re-initializing the settings in the GUI and see if that helps.  I thought there might be the possibility of a RAID corruption, no error being generated doesn't mean it can't exist somewhere in that 3+ gigs of data :)