SNAP OS based file browser?

[vunnax]

Is there any way to mount SNAP OS based HDD (SNAP server 2000 HDD to be exact) onto PC and browse files that were stored there from Windows/Linux environment in PC?
I know that SNAP OS is based on Linux distribution, but also it is somehow costumized, so probably mounting it to Linux will not help? Or...?

Please can ynone help me? My SNAP Server 2000 died (System LED off, HDD LED Off) and I cannot find the way to restore my personal valuable files from it...

[blue68f100]

NO. Since it's highly modified nothing but another snapOS unit will work. Unless you send it to a recovery service, $$$.

Confirm the PS is good. On the 2000 there is a fuse on the MB that can be replaced. Also there is a wire fuse block (black w/4-5 wire loops showing). if that is blow just bypass them.

[vunnax]

Good news! I managed to find the other Snap 2000 machine (and got it for free ). So, now first I have to upgrade to 3.4.807 version, because my disks in the old one were 160 GBs ( I succesfully updated to v3.4.807 there), and I guess I cannot run them without updating OS.

I have a version 4.0.860 from Overland, but I am not sure if it will work on 2000 or even if it works would I be able to read disks that were built on version 3.4?

Please can anyone help and send me v3.4.807 (or any version that will work with large disks on 2000 and would be able to read HDDs built with v3.4)?

[blue68f100]

Just install the HD and boot it up. If the OS is newer on the HD's it normally updates the firmware. Installing v4 is the way to go if your have 64meg of memory.

Did you checked to see if the fuse was blow on the MB of the failed unit?

[vunnax]

Thanks for the tip, I'll try to install it today.

Ragarding fuse on the old machine, it was not broken, so most probably it is CPU failure, since fan for CPU was not working and it was overheating, and at the end it died!

[vunnax]

I've installed 160GB HDDs from the old Snap into new one. All LEDs are normally on and it seems that Snap was normally booting, but with Assist I cannot find it on the network.
1. Can you tell me if jumbers on both HDDs should be set to Master?
2. Should I maybe reset the new Snap and then try it out?
3. Any other tips so that I can connect to Snap?

[vunnax]

I've reseted to factory defaults (IP address and Administrative password) and connected to SNAP.
But, ufortunately, SNAP did not load OS version from the HDD, but have the old one from the flash (v3.1.626), so I cannot see large disks, or any disk data now...
First, is it correct that I set both HDD jumpers to "Master" setting?
Second, what to do to be able to read data from this 160 GB disks?

Thanks in advance...

[blue68f100]

On the older 2000 units (Meridian or Qunatium) the drives are master/slave like they were removed. If you noted the jumper position when you removed them.

Are you planing on continuing use of the 2000, or are you going to just remove the data and send it on it's way?

If going on its way, I would just use 1 HD if you were in RAID1. That way you have a BU of your data on second HD. Updated the OS to v4 and retrieve the data. Once you only use a single HD, your raid1 will be broken. But once the second HD is installed the raid can be made/resynced.

[vunnax]

Thank you for you hel and tips...
I succesfully retreived data;
First, when I put old HDDs in new Snap, I could not see Snap on network... Then, I reseted to factory dafaults, and Snap appeared in Assist application.
After that I was not able to see HDD content and that worried me... SnapOS had older version of software (3.1.626) and I had prepared new 4.0.860, but was affraid to run because I didn't know if data structure is different between versions 3 and 4. As you wrote me, it is not, so I updated to v4, and then I was able to see one mirror disk. The other one is actually empty and I can see 128 GBs, I think I maybe formatted it or something when I was trying to run it on older SW version...
Nevertheless one mirror was enough and now I am backing it up on my PC and "normal" NTFS partition disk (just in case ) . After that I will try to rebuild RAID1 and continue tu use Snap in my home network.

Ehanks again for your help...

[blue68f100]

Glad you were able to retrieve your data. Long as the data in on the master, switching to raid 1 is no problem. I have some tips in the FAQ's on this. Since this was a RAID1 it may be reporting a broken raid. I find it easier to force it to JBOD use the debug cmd then just change the drive config to raid1 and let it sync.

[vunnax]

OK, now, about resyncing a mirror...
On the old drive 1 (drive 10000) I had broken mirror (and it was addresses as partition 10000, logical disk 50000)...
So, first I created JOBD, and formatted drive 2 and after reboot I had each of two drives separated with all the data on drive 1 and drive 2 empty (drive 1 partition: 10000 and drive 2 partition: 10010.
After that I issued in debug window command:
co de config mirror 10000 10010

and then rebooted...

After reboot I could normally connect and see the progress of recreating the mirror; it lasted for some 5-6 hours, and after that when I tried to connect I could not anymore...
I physically turned SNAP off and on and then it started again with creating the mirror from the beginning... I left it during the night.
Tomorrow, after some 12 hours I could not connect to it again!

So, if I turn it off and on again I guess it will start again with rebuilding the mirror... Well, it is obvious that something is wrong here... Any ideas?

[blue68f100]

I try to avoid the debug cmds if I can. Once in JBOD use the web gui to build the mirror. It's been so long since I had to do that function I do not recall how long it takes.

Every time you stop a function by turning it off it will run a check on the HD's, this alone can take hours. before moving to the next task.

[vunnax]

I could not recreate the mirror... Probably some HDD problem; I am sending part from the log:

002D1454
$002D8496
$002DF71A
$002B2187
$002B0957
$002BC3D6
$002BD7B6
$002B1EDF
$002B07E5
$002BC2B4
$002B0AAC
$0010413C
$001041F6
================================
System 3/8/2011 5:01:29
F PANIC : Maximum yield time exceeded at $002BCE96 System 3/8/2011 5:01:29
S System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:35
Boot Count: 12 System 3/7/2011 23:54:53
F Call Stack :
$00105131
$002D1454
$002D8496
$002DF71A
$002B2187
$002B0957
$002BC3D6
$002BD7B6
$002B1EDF
$002B07E5
$002BC2B4
$002B0AAC
$0010413C
$001041F6
================================
System 3/7/2011 4:13:58
F PANIC : Maximum yield time exceeded at $002BCE96 System 3/7/2011 4:13:58
S System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:35
Boot Count: 11 System 3/6/2011 23:06:41



What do you think?

[blue68f100]

Not quite enough of the log to tell what it was doing before it went into a Panic Attack.
A Panic attack, is normal when things are not right. Is this setup with the good HD in the Master position (drive0, 10000) and the failed HD in Slave. If this is the same HD that failed I would take it to a pc where you can run diagnostics on the HD. I suspect you are dealing with a failed HD. If you have spinrite the bad area will appear about 4-5% into the check.