Snap 4200 VOL0 won't mount

[cianwill]

We had a power outage (while not home) and it lasted longer than the UPS, so down went the server. Now...the server boots and I can connect to it via web admin, but it states that Vol0 is inactive. How can I mount the Volume? I have reset the server to no avail. I have gone into debug.cgi but cannot figure out how to force the mount. The commands that work on my 4000 don't seem to be recognized. Help! It is running Guardian 3.2.026 with 4 80GB drives in raid 5.

Name RAID Set Size Mount Point Status Quotas
VOL0 md0 175.44 GB /hd/vol_mnt0 Not mounted Disabled

Here's something in the logfile that caught my eye:
EXT2-fs warning: checktime reached, running e2fsck is recommended

[Phoenix32]

Is it just me, or are we starting to see more of the Guardian OS units round these parts? Time to stock up on information...

Sorry cianwill, I do not have much of a suggestion here. The only thing I can think of is that maybe the drive got corrupted when the power went out (that does happen to drives sometimes when power is killed). Meaning, maybe you will have to reinitialize the drive(s). But before you go that drastic, let's see what David or some of the others have to suggest...

[re3dyb0y]

Give us a Guardian unit to play with?


Its very hard for us to do much more than guess, or pass on information discovered from these machines with non/few of us having a machine or access to one


The Snap OS is based on BSD, whereas Guardian is based on the mainstream linux kernel.....



Can you do '?' or whatever it is on the snap to give us a list of debug commands?

If so, that could really help us out!

[cianwill]

GNU bash, version 2.04.25(1)-release (i386-quantum-linux-gnu)
These shell commands are defined internally. Type `help' to see this list.
Type `help name' to find out more about the function `name'.
Use `info bash' to find out more about the shell in general.

A star (*) next to a name means that the command is disabled.

%[DIGITS | WORD] [&] . filename
: [ arg... ]
alias [-p] [name[=value] ... ] bg [job_spec]
bind [-lpvsPVS] [-m keymap] [-f fi break [n]
builtin [shell-builtin [arg ...]] case WORD in [PATTERN [| PATTERN].
cd [-PL] [dir] command [-pVv] command [arg ...]
compgen [-abcdefjkvu] [-A action] complete [-abcdefjkvu] [-pr] [-A a
continue [n] declare [-afFrxi] [-p] name[=value
dirs [-clpv] [+N] [-N] disown [-h] [-ar] [jobspec ...]
echo [-neE] [arg ...] enable [-pnds] [-a] [-f filename]
eval [arg ...] exec [-cl] [-a name] file [redirec
exit [n] export [-nf] [name ...] or export
false fc [-e ename] [-nlr] [first] [last
fg [job_spec] for NAME [in WORDS ... ;] do COMMA
function NAME { COMMANDS ; } or NA getopts optstring name [arg]
hash [-r] [-p pathname] [name ...] help [-s] [pattern ...]
history [-c] [-d offset] [n] or hi if COMMANDS; then COMMANDS; [ elif
jobs [-lnprs] [jobspec ...] or job kill [-s sigspec | -n signum | -si
let arg [arg ...] local name[=value] ...
logout popd [+N | -N] [-n]
printf format [arguments] pushd [dir | +N | -N] [-n]
pwd [-PL] read [-ers] [-t timeout] [-p promp
readonly [-anf] [name ...] or read return [n]
select NAME [in WORDS ... ;] do CO set [--abefhkmnptuvxBCHP] [-o opti
shift [n] shopt [-pqsu] [-o long-option] opt
source filename suspend [-f]
test [expr] time [-p] PIPELINE
times trap [arg] [signal_spec ...] or tr
true type [-apt] name [name ...]
typeset [-afFrxi] [-p] name[=value ulimit [-SHacdflmnpstuv] [limit]
umask [-p] [-S] [mode] unalias [-a] [name ...]
unset [-f] [-v] [name ...] until COMMANDS; do COMMANDS; done
variables - Some variable names an wait [n]
while COMMANDS; do COMMANDS; done { COMMANDS ; }

[cianwill]

Above is what I get by going into http://SNAP/admin/debug.cgi

Whether or not this is the correct debug menu, I have no clue. I am running off of the same info that I would use to TS my older Snap OS's

Any help would be greatly apperciated, I need that data off the 4200.

[re3dyb0y]

Hmm

That looks more like a modified shell on a linux box...

Hmm

[blue68f100]

Originally Posted by cianwill

We had a power outage (while not home) and it lasted longer than the UPS, so down went the server. Now...the server boots and I can connect to it via web admin, but it states that Vol0 is inactive. How can I mount the Volume? I have reset the server to no avail. I have gone into debug.cgi but cannot figure out how to force the mount. The commands that work on my 4000 don't seem to be recognized. Help! It is running Guardian 3.2.026 with 4 80GB drives in raid 5.

Name RAID Set Size Mount Point Status Quotas
VOL0 md0 175.44 GB /hd/vol_mnt0 Not mounted Disabled

Here's something in the logfile that caught my eye:
EXT2-fs warning: checktime reached, running e2fsck is recommended

Did you run the e2fsck ?

And do you have access to the maintance section???

I'm going to look at the Gentoo forums and see if they have any thing of interest.

The snap OS cmd will not work on the Grardian os. Built of of different platforms.

[blue68f100]

Found this on Gentoo site. they were refering to the -f flag,

# fsck.ext3 -fcyv /dev/hda1

But I have now idea what your drive id is. The is in reference to a ext3 partition. Yours is e2 .

e2fsck: No such file or directory while trying to open /dev/hdb1
/dev/hdb1:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

Just read if you had a drive failure you will get this error too.

[cianwill]

Well,

I have tried to run e2fsck....but i don't think it is working. Maintenace section? Hmmm, well the drives themselves are showing a status of OK.
dev info does not work, but I will go into the logfile and see if there is something about the drives...I will past in what info I can find.

[cianwill]

Here is some of the logfile:

XFS: log mount failed kernel Sep 16 03:10:28
XFS: log mount/recovery failed kernel Sep 16 03:10:28
XFS: failed to locate log tail kernel Sep 16 03:10:28
XFS: extended permissions ON kernel Sep 16 03:10:28
XFS: log mount failed kernel Sep 16 03:10:28
XFS: log mount/recovery failed kernel Sep 16 03:10:28
XFS: failed to locate log tail kernel Sep 16 03:10:28
XFS: extended permissions ON kernel Sep 16 03:10:28
disk 3, s:0, o:1, n:3 rd:3 us:1 dev:hdg4 kernel Sep 16 03:10:28
disk 2, s:0, o:1, n:2 rd:2 us:1 dev:hde4 kernel Sep 16 03:10:28
disk 1, s:0, o:1, n:1 rd:1 us:1 dev:hdc4 kernel Sep 16 03:10:28
disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hda4 kernel Sep 16 03:10:28
--- rd:4 wd:4 fd:0 kernel Sep 16 03:10:28
RAID5 conf printout: kernel Sep 16 03:10:28
disk 3, s:0, o:1, n:3 rd:3 us:1 dev:hdg4 kernel Sep 16 03:10:28
disk 2, s:0, o:1, n:2 rd:2 us:1 dev:hde4 kernel Sep 16 03:10:28
disk 1, s:0, o:1, n:1 rd:1 us:1 dev:hdc4 kernel Sep 16 03:10:28
disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hda4

[cianwill]

Here is what I get when trying fsck.ext2 -fcyv /dev/hda4

e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
fsck.ext2Couldn't find ext2 superblock, trying backup blocks...
: Bad magic number in super-block while trying to open /dev/hda4

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193

[blue68f100]

Geading on Gentoo forums, This error will show when you have a drive failure.

Try the -b 8193 superblock option.

ls will do a dir list
df -h will give you file system usage

You may want to try the other drives too
fsck.ext2 -fcyv /dev/hdc4
fsck.ext2 -fcyv /dev/hde4
fsck.ext2 -fcyv /dev/hdg4

[cianwill]

Command: fsck.ext2 -b 8139

Usage: fsck.ext2 [-panyrcdfvstFSV] [-b superblock] [-B blocksize] [-I inode_buffer_blocks] [-P process_inode_size] [-l|-L bad_blocks_file] [-C fd] device Emergency help: -p Automatic repair (no questions) -n Make no changes to the filesystem -y Assume "yes" to all questions -c Check for bad blocks -f Force checking even if filesystem is marked clean -v Be verbose -b superblock Use alternative superblock -B blocksize Force blocksize when looking for superblock -l bad_blocks_file Add to badblocks list -L bad_blocks_file Set badblocks list

Not sure if I am doing this correctly

[cianwill]

Th is what I get with df -h

Filesystem Size Used Avail Use% Mounted on
/dev/md100root 529M 265M 264M 50% /

[cianwill]

Here is the drive status:

RAID Set Name: md0
Type: RAID 5 (checksummed)
RAID Size: 219.25 GB
RAID Status: OK

Location Model Size Status Actions
Drive 1 80 GB Maxtor-6Y080L0 73.10 GB OK
Drive 2 80 GB Maxtor-6Y080L0 73.10 GB OK
Drive 3 80 GB Maxtor-6Y080L0 73.10 GB OK
Drive 4 80 GB Maxtor-6Y080L0 73.10 GB OK

[blue68f100]

Looks like every thing is back to normal.

I would to a shut down then restart and see if it comes up now.

[cianwill]

ok, just ran fsck /dev hd1 and got this:
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 e2fsck: need terminal for interactive repairs

So, does this mean I need something hooked up to the snap server?

[cianwill]

The drives have always shown a status of ok...it's the volume that won't mount. Which means my shares don't work...arghhh I have raid 5 for keeping data safe and now I can't even use it.

[blue68f100]

The 4200 has a svga and ps2 port for monitor and keyboard. I thinks it is telling you that you need a direct connection to do the repairs.

Use the -f flag and see if it fixes the problem.

If you have the gsu file for your version of OS you may want to re-install it if nothing else works.

I'm surprised it not a option when in maintance mode.

Have you searched Adpatec (Snap Appliance) knowledge base ????

[cianwill]

Thanks, I'll try to hook up a monitor and KB.
These are my only options in Maintenance:

OS Update Upgrade the server's operating system.

Factory Defaults Reset the server to factory defaults.

Disaster Recovery Prepare for and recover from server failure.

Add-on Features Manage Add-on Features

Host File Editor Identify your backup server to the Snap Server.

Shutdown or Reboot Restart or power down the server.

I am digging through Adaptec now...

[blue68f100]

Try Disaster recovery

It would be my first choice.

[cianwill]

unfortunately, I don't have any images to recover from. I never got that far...

[blue68f100]

Give this a try.

fsck.ext2 -b 8139 -fcyv

You may have to break down and give Adaptec a Call

Or locate the other guy that just came here earlier looking for the Guardian OS. And see if he can help you. sopymattw?

Go to gentoo.org forum and ask for help.

[blue68f100]

How big was your UPS and was it a network type or std desktop pc type. I want to know if I need to upgrade my UPS units.

[cianwill]

APC 1100 desktop type - power must have been out for more than 30-40 minutes.
Now i need to figure out how to view the devices like I can on my other snaps (config devices info) because I may have a HD going bad. The log file has a line stating that there is a bad drive (raid1: Disk failure on hdg2, disabling device. ) However, when I look at the HD's in Storage they look fine. So if I need to replace one I need to be absolutely sure which one it is. Thanks for the advice, I'll look on Gentoo. I did not find anything on Adaptec.