Guardian OS units

[poma5]

Originally Posted by Phoenix32

And the family grows...

I have an 85 Gig 4000 series snap server
a 360 Gig 4000 series snap server
a 1 terbyte 4500 snap server
and 2, 2 terabyte 520 snap servers
My 4500 and 520 snap servers are running the guardianos verion 4.44.045 SP3.
I contacted Adaptec about updating to the latest version of the guardianos but they want me to pay for the update. I have only had my last 520 snap since may of last year. They do not support OS updates for more than 90 days from what they are telling me. That seems wrong. I told them that I would never buy another snapserver from them again. I have bought and used snapservers since they were owned by Meridian Data but I will never buy from adaptec again.
I do have guardianos up to the version stated above.

Poma5

[bitor]

Sorry to hear that Adaptec has bent you over. You're not the first. It's a great product with very very bad rip off support. If they keep this up...nobody will want new products from them no matter how good it is. It's just to bad.


bitor

[slpken]

Hello, another Newbie here.

Recently inherited a working 750GB Snap Appliance Snap Server 4500 with GuardianOS 2.4.040 running a Pentium 4 3.06GHz CPU with 533fsb, two Gigabit Ethernet cards, and the SCSI card, with 496MB RAM.

Runs fine but want to use it as a repository of all my iTunes and Apple TV music and movies. Some of these have long files names, and this early version of the GuardianOS doesn't support AFP 3.x, so can't go beyond 27.3 filenames of of MacOS 9.

I have to buy new drives to have any hope of reliability for the next 4 years or so, and hope to upgrade to four 500GB or 750GB Barracudas. That's enough grocery money all by itself, so I was really disappointed when I called Adaptec to find out how to upgrade to 4.4.049. $720!!!!!! Can't afford that, so am looking for ways to avoid having to rename 12,000 songs and movies to conform to 27.3.



slpken

[blue68f100]

Welcome to the forum.

Selling of Copyrighted Material is not allowed.

These are commercial grade units so expect prices to follow.

You can setup iTunes to point to a mapped drive.

Buy good drives like the WD RE drives. Stay away from Maxtors.

[rpmurray]

Originally Posted by slpken

so am looking for ways to avoid having to rename 12,000 songs and movies to conform to 27.3.

Connect to the Snap using SMB instead of AFP.

[eschw95458]

Use NFS to connect to your snap server, that should preserve your filenames.

[tvleavitt]

I just acquired a Snap Server 520 for one of my clients. Very nicely priced little open-box unit with 4 250GB drives. Spent most of today poking around trying to figure it out, reading through the manuals, setting up the configuration, etc.

Am trying to figure out how it handles file ownership and permissions... who gets to access files I create on it, and how?

I have a ReadyNAS 1100 on another site. That box has been quirky enough that I wanted something a little bit more stable and solid for these folks. Has some nice features, in that each user gets their own automatically secure home share, which can also be mounted via NFS on external servers. Trying to figure out how to do the same thing here...

[eschw95458]

Snap servers are able to pull user lists from an NT domain (or Samba PDC), or are also capable of participating in an active directory domain. If you don't have a domain, "local" users can be added manually to the server.
Disk space can be carved into one or more volumes, then the volumes divided into one or more "shares". Example create a single volume called "volumeA" then create on that volume a share called "share1" then goto the security tab and find the share you created (share1) click on the "access" button and add whatever domain or local users and groups. Users and groups can have full access, or read only access and can access the files and folders via afp, smb, nfs, ftp. (All dependent on how you set the server up).

Here is a link to the adaptec admin guide http://www.adaptec.com/en-US/support...gos_ug_pdf.htm

[blue68f100]

One thing you need to be aware of.

The def snap share gives every one root access. I would suggest creating a new share without this everyone having admin rights.

Use the security guides to setup the initial shares and users. I always create a share called users. Then I add users shares to that tree with user only have access to his/her share. This prevents a users from browsing share they to have have access rights to. Any uses with root access cnan browse. This is the resason you want to setup the tree properly. Then you can add a shared drive for all use as needed.

You may also need to setup the Raid5 array before any of this can happen.

[[AfZ]PiMp J]

Originally Posted by Phoenix32

I have a couple 250 GB drives (one Seagte and one WD) I pulled from a working SNAP 4500 with OS 4.4 to upgrade to larger hard drives. I had a couple spare sleds, so I just used those. I know the drives will work in a SNAP 4400, 4200, or 4500, but the sleds will only work in a 4200/4500. I cannot speak for other units.

any chance in hell you still have these?
I've got a SnapServer 4400 (well 2 of em) running 4x180gb deathstars, one os 3.2 the other 2.6 and i'd love to upgrade the OS on both of em if the price is swinggable (the closer to free the better)

[blue68f100]

I dought that the HD will contain the OS, Andy generally full test the drives before selling any thing. So the drives will be clean but in perfect working order.

[Phoenix32]

Yup, I use MHDD from the UBCD to check every sector on a drive for weak or bad sectors before I even think about putting a drive in a RAID 5. Or befor a drive ever leaves me to someone else. I also use Spinrite 6 for serious hardcore testing as required. I have a good reputation and want to keep it that way.

[z0ner]

I've got a barely used 640GB 4200 that I'll be selling very soon. It's been in storage for almost a year and I believe has one of the newer (if not the newest) GuardianOS on it. I'll be powering it up to test shortly.

EDIT: Updated to GuardianOS 5.0.125. I might turn her into 2TB (4x500GB) , I haven't decided yet.

[242]

I just got two 18000 with 8x250 each running os 3.2.019 anyone know what version of linux this thing is based off of?

-242

[blue68f100]

I know v4 is RedHat Entriprise. At one time they were using Gentoo very early on. So my guess on v3 is RedHat Enterprise. V3 ( up to v 4.1) allows you to use Putty to SSH in to the shell. V4.4 has moved a lot of functions to the debug page. and requires a shell cmd to gain access.

[242]

Originally Posted by blue68f100

I know v4 is RedHat Entriprise. At one time they were using Gentoo very early on. So my guess on v3 is RedHat Enterprise. V3 ( up to v 4.1) allows you to use Putty to SSH in to the shell. V4.4 has moved a lot of functions to the debug page. and requires a shell cmd to gain access.

Interesting, I figured it would be common knowledge. I decided to take a look under the hood and I am find a few things that would lead me to believe it has a redhat base but I guess the labeled it Quantum Linux

Here is the contents of the release file in /etc
sh-2.04# more quantum-release
Quantum Linux IDE NAS (Opus)

[Phoenix32]

The newer 5.0.125 looks like it is SUSE.

[yfpang]

Dear All,

I'm not sure if I'm posting my question on the correct forum here, as currently I'm having a Quantum SnapServer running on Guardian v2 which is having a problem to boot up.
As from the serial output it seem like it's running fine in the beganing but later it comes to kernel panic.

As for testing I've tried to see if the OS reside in the HD or Flash and it's being reside in the HD.

Hope that there is some people here that may have seen this problem and resolve it before.


Thanks
Pang

[blue68f100]

It would be nice to know which model you have, some of the early ones could run either OS depend bios/firmware size. V2 make it a very old unit. My first guess would be that it may need cleaning, unit over heating, maybe a cooling fan failure. Then I would suspect a HD problem.

[yfpang]

Hi Blue68f100,

The model that currently i have is guardian 4400, which is running on Guardian OS version 2.1.003. As for the unit it's running fine until one of the administrator change the host name and restart the unit.

For this version do you thing it has something to do with the OS image? As the following is part of the serial output from the server :

Hope to hear from you soon

Thanks
Pang

[blue68f100]

If you have a copy of SpinRite, I would shut it down and run it on all the drives. If there is a drive problem it will correct it. Otherwise you may need to reload the GSU file. It's has an error on loading one part. Like maybe all the markers did not get changed.

Have you checked to see if the bios settings have not changed? May be time to replace the Battery. But this is down Phoenix32 line.

EXT2-fs warning: checktime reached, running e2fsck is recommended

VFS: Mounted root (ext2 filesystem).

kmod: failed to exec /sbin/modprobe -s -k char-major-10-152, errno = 2

kmod: failed to exec /sbin/modprobe -s -k char-major-10-152, errno = 2

/dev/Qhwmon: No such device
/dekmod: failed to exec /sbin/modprobe -s -k char-major-10-152, errno = 2

v/Qhwmon: No suckmod: failed to exec /sbin/modprobe -s -k char-major-10-152, errno = 2

h device
/dev/Qhwmon: No such device
/dev/Qhwmon: No such device
Using /lib/modules/i2c-core.o
i2c-core.o: i2c core module

Using /lib/modules/i2c-dev.o
i2c-dev.o: i2c /dev entries driver module

Using /lib/modules/i2c-proc.o
i2c-proc.o version 2.6.1 (20010825)

Using /lib/modules/i2c-piix4.o
Install SMBus adapter driver (i2c-piix4)

i2c-dev.o: Registered 'SMBus OSB4/CSB5 adapter at 0580' as minor 0

i2c-piix4.o: PIIX4 bus detected and initialized

Using /lib/modules/Qhwmon-Modulekmod: failed to exec /sbin/modprobe -s -k char-major-10-152, errno = 2

.o
kmod: failed to exec /sbin/modprobe -s -k char-major-10-152, errno = 2

/dev/Qhwmon: No such device
/dekmod: failed to exec /sbin/modprobe -s -k char-major-10-152, errno = 2

v/Qhwmon: No such device
/dev/Qhwmon: No such device
Qhwmon: proc entries installed OK

Qhwmon: Hardware monitor driver successfully loaded as Manta driver

Using /lib/modules/mtdcore.o
Using /lib/modules/mtdchar.o
Using /lib/modules/chipreg.o
Using /lib/modules/gen_probe.o
Using /lib/modules/cfi_probe.o
Using /lib/modules/cfi_cmdset_0001.o
Using /lib/modules/amd_flash.o
Using /lib/modules/quantumsnap.oGuardian: Found no Flash device


Using /lib/modules/mii.o
Platform = MANTARAY
Using /lib/modules/qinfo_i2c.o
Using /lib/modules/qinfo.o
qinfo: version 2.2 (20020709)

mdctl: fail to stop array /dev/md100root: No such device
starting raid: md100root containing drive /dev/hda2
mdctl: /dev/md100root has been started with 3 drives.
mdctl: fail to stop array /dev/md101swap: No such device
starting raid: md101swap containing drive /dev/hda5
mdctl: /dev/md101swap has been started with 4 drives.
>> root FS exists
***** Running on HARD DISK *****
Not on Clipper: Returning from Linuxrc
Kernel panic: No init found. Try passing init= option to kernel.

Oops: 0002

CPU: 0

EIP: 0010:[<c0230009>] Not tainted

EFLAGS: 00010206

eax: 00000007 ebx: c02f7ee0 ecx: 00000000 edx: 00000488

esi: 00000000 edi: 00000000 ebp: 0008e000 esp: dfde7f84

ds: 0018 es: 0018 ss: 0018

Process swapper (pid: 1, stackpage=dfde7000)

Stack: c02f7ee0 00000000 00000000 0008e000 00000246 00000000 c02304de 00000000

00000000 c02f7ee0 c011c9ee c02f7ee0 00000000 00000000 c02a8900 0000000e

c0105000 c0113c6a c0317f14 00000000 00000000 00000000 c02a88f6 c010539a

Call Trace: [<c02304de>] [<c011c9ee>] [<c0105000>] [<c0113c6a>] [<c010539a>]

[<c01056f3>]

Code: ff 01 0f 8e 25 05 00 00 31 c0 5b 5e 5f 5d 59 5a c3 89 f6 31

<0>Kernel panic: Attempted to kill init!

[Phoenix32]

After reading all that GREEK, which gave me a headache,

It looked to me like the OS is lost, confused, FUBAR, or just having a real bad day, which in turn makes me think Hard Disk, somewhere in the initial 10GB of a drive.

David, it could be a BIOS setting, but I think it's improbable (low odds). When that happens with these, they like to not boot at all until you go in and fix 'em.

I would look to see if you have a failing/failed drive somewhere in that mess and hope your OS is not hosed.

-AND-

David, wasn't the old v2 OS prone to confusing itself by not deleting things it should? I can't remember, but that is your department (punt).

[blue68f100]

I think when they changed the name it did not complete the change to the links when it was rebooted. Inturn scrambling it's brain, the new pointer is not set completely. If the drives test out with SpinRite , he probably should do a clean install.

[yfpang]

Hi blue68f100 and Phoenix32,

Thanks for the advise but I'm still very confuse as to what should i do from now.
Should i get 1 new HD and place it in there just to try booting it up or use the gsu file that I have to make the upgrade.

Furthermore do you think it's possible to copy the OS from the drive since it reside in it's own area that is not being effected by the RAID.

Hope to hear from you and Sorry for the greek word

Thanks
Pang

[blue68f100]

The OS resides on all drives (raid1), part of the watch dog feature.

If you have a copy of spinrite, shut the unit down and run it on all of the drives. Then put them back in in the same order they were removed.

If you have the GSU ( which is the OS Image File) you can try the diaster recovery and reload the OS. This will not impact the data unless you select clean install.

Last if nothing else works you will need to wipe it clean with a clean install.

so
1st spinrite on all of the drives.
2nd reload the OS
3rd and last resort is a clean install ALL DATA WILL ME LOST.