Ok, I'm new to Unix but can say that I pick things up fast when it comes to technology.

I have a Linkstation Mini LS-WS1.0TGL/R1 that needs restoring, it was given to me my former company has it was failing to start up properly. Unfortunately I couldn't tell you what exactly was causing this but when I brought the device home it would just flash the blue light. I created the same network environment it was in when it was at their office, but it continued to flash the blue light.

There is the possible some smart person in their office may have pressed the reset button.

In the past I've been able to saved data and the file structure from failed RAID's before by using handy bits of software, personally I quite like Ontrack and UFS Explorer. However these aren't working to well for me with this particular problem.

So far I have mounted the drives in my machine and tried UFS Explorer to recreate the RAID-0, which works ok but when I browse the drive the file system comes up as:

sharespool

I can only assume from what I've read and see in the office, is that share is the place where all the folders are kept.

Now I've done a complete recovery + restore with UFS Explorer and it does restore lots of files, but is missing the file structure. As you can imagine this is highly frustrating when there's nearly 800Gb of data labelled Unknown000001, especially when some of the files saved by the company aren't recognised by UFS. Oh and to top it off it takes 4hours and sometimes crashes at 98%!

So on this note I stumbled on these forum pages... which I might say are brilliant. Now this particular thread caught my eye and I've given it a go. viewtopic.php?f=61&t=22396#p140008

Sorry to say thought that after carrying out this process, the share folder is still empty. Now I know the data is still on the drive because UFS is finding it.

The big question is what next ?

For anyone that would like to offer assistance below is my Superblock details after creating the raid in Ubuntu.... I need be honest and say I'm still learning what a superblock is but I though it might be of use to someone. If any other reports are needed then please let me know.

as I believe the are on partion no. 6. Then I follow this command with

mkdir -p /mnt/lsminimount -t xfs /dev/md1 /mnt/lsmini

I'm assuming in the first code line where I create the raid, I call it md1 as opposed to what your suggesting md6. Will naming it different make a diffence? Don't forget I can see the share folder when it's called md1, just not the contence of what should be in it.

As i'm a novice and just guessing on the above, I'll try your suggestion and see how I get on

Now what is good way forward, with out doing more damage than I may I've already done?

Oxygen8, since doing a bit more reading I may agree with your comment. So do I now try assemble? Also could you explain how buffalo created a stardard share folder when the drive are plugged in my machine? Do you mean it created a new folder before the drive were removed. Also if assemble is the right thing to do then it might be prudent to change the post I was looking at.

Stonie, helpful comment on the first post which I'm assuming if I tried it first would provided some good results, is it worh giving it a go now? Not quite sure what your meaning on the second post. Could you expand a bit?

As you re posted 'I'm new to this' but I'm starting to feel a little bit of hand holding would be helpful as I do not wish to wreck what data I may have left.

Who is online

Users browsing this forum: No registered users and 2 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum