Go Back   Pro/Forums > ProCooling Technical Discussions > Snap Server / NAS / Storage Technical Goodies
Password
Register FAQ Members List Calendar JavaChat Mark Forums Read

Snap Server / NAS / Storage Technical Goodies The Home for Snap Server Hacking, Storage and NAS info. And NAS / Snap Classifides

Reply
Thread Tools
Unread 08-05-2008, 01:58 PM   #1
TMowreader
Cooling Neophyte
 
Join Date: May 2007
Location: Portland
Posts: 10
Default Snap 4500 Recovery

Hello, I came to work last week, tried to log in to my snap 4500 and am getting the following:

"This is the Guardian Recovery Console. Your server did not complete its previous boot attempt. Please reboot your server now by clicking the "Reboot" button at the bottom of the page. If you have previously rebooted your server and subsequently returned to this page, please contact Customer Support before continuing. "

I've tried repairing the OS with the image on the CD that came with the server, guardianOSImage.gsu, and have tried a fresh install, neither have worked.

Below is the text from the "fresh install" option that eventually fails.

Any help is very much appreciated.

Thanks!

Tyler



Fresh Install Snap Server Root File System
Source Path: D:\GuardianOSImage.gsu
Proxy Server:

--------------------------------------------------------------------------------


Fetching ...
Fetching Archive D:\GuardianOSImage.gsu...
The source file is D:\GuardianOSImage.gsu
The target file is /updater/GuardianOSImage.gsu
Fetching local file D:\GuardianOSImage.gsu to /updater/GuardianOSImage.gsu

Target file may be an image, attempt extraction...
sh: grep: command not found
processing regular file /mnt/pivot/var/log/update-os.log.1
processing regular file /mnt/pivot/system-restore
processing regular file /mnt/pivot/var/log/updater.log
processing regular file /mnt/pivot/htdocs/icons/sysfiles.tgz
processing regular file /mnt/pivot/var/log/updater.status
processing regular file /mnt/pivot/var/lock/samba/winbindd_cache.tdb
processing regular file /mnt/pivot/var/log/updater.log
processing regular file /mnt/pivot/var/log/dr_image_creation.log
processing regular file /mnt/pivot/var/log/system_recover.log
processing regular file /mnt/pivot/htdocs/icons/s2slogs.tgz
processing regular file /mnt/pivot/htdocs/icons/nvlogs.tgz
processing regular file /mnt/pivot/htdocs/icons/edrlogs.tgz

size reclaimed is 25719 against requested 10244096 bytes
sh: grep: command not found
sh: grep: command not found
processing regular file /mnt/pivot/var/log/update-os.log.1
processing regular file /mnt/pivot/system-restore
processing regular file /mnt/pivot/var/log/updater.log
processing regular file /mnt/pivot/htdocs/icons/sysfiles.tgz
processing regular file /mnt/pivot/var/log/updater.status
processing regular file /mnt/pivot/var/lock/samba/winbindd_cache.tdb
processing regular file /mnt/pivot/var/log/updater.log
processing regular file /mnt/pivot/var/log/dr_image_creation.log
processing regular file /mnt/pivot/var/log/system_recover.log
processing regular file /mnt/pivot/htdocs/icons/s2slogs.tgz
processing regular file /mnt/pivot/htdocs/icons/nvlogs.tgz
processing regular file /mnt/pivot/htdocs/icons/edrlogs.tgz

size reclaimed is 0 against requested 10240000 bytes
sh: grep: command not found
CRC ok on image

Platform Bytes of Image File match this machine: 05.01.00


Successfully extracted /updater/install.sh

Successfully extracted /updater/platformbytes.txt

CRC ok on image

Platform Bytes of Image File match this machine: 05.01.00


Successfully extracted *.tgz to pipe

.......................
Current Kernel Version:
4.0.228
200508101416
New Root FS Version:
4.0.228
200508101416
.......................

Continuing Fresh Install
Source Path: D:\GuardianOSImage.gsu
Proxy Server:

--------------------------------------------------------------------------------


Installing ...
/updater
image: GuardianOSImage.gsu
install.sh
lost+found
platformbytes.txt
version
Using IMAGE target file '/updater/GuardianOSImage.gsu' and install script './fullinstall.sh'
-rw-r--r-- 1 0 0 119247977 Aug 5 22:00 GuardianOSImage.gsu
./install_tools/
./install_tools/grub/
./install_tools/grub/stage1
./install_tools/grub/grub
./install_tools/grub/stage2
./install_tools/extattrb.fix.sh
./install_tools/checkguest
./install_tools/checkver
./install_tools/dd
./install_tools/raidtab.crippled.adelie
./install_tools/extperm.fix.sh
./install_tools/flashupdate.sh
./install_tools/fstab
./install_tools/fullinstall.sh
./install_tools/fullupgrade.sh
./install_tools/installroot.sh
./install_tools/manufacture.sh
./install_tools/mkboot.sh
./install_tools/mkdir
./install_tools/mkfs.xfs
./install_tools/mknod
./install_tools/mkraid
./install_tools/mkswap
./install_tools/passupd
./install_tools/raidhotadd
./install_tools/raidstart
./install_tools/raidstop
./install_tools/raidtab
./install_tools/raidtab.adelie
./install_tools/raidtab.clipper
./install_tools/raidtab.crippled
./install_tools/tpaImport.sh
./install_tools/reshare
./install_tools/raidtab.crippled.clipper
./install_tools/raidtab.crippled.emperor
./install_tools/raidtab.crippled.manta
./install_tools/raidtab.crippled.n1000
./install_tools/raidtab.crippled.vmware
./install_tools/raidtab.emperor
./install_tools/raidtab.manta
./install_tools/raidtab.vmware
./install_tools/sfdisk
./install_tools/touch
./install_tools/updatesnaps
./install_tools/sfdisk.out.developer
./install_tools/mdctl
./install_tools/upgraderoot.sh
./install_tools/sfdiskmap
./install_tools/pickhintdevice
./install_tools/partitionize.sh
./install_tools/s2spropmerge.jar
CRC ok on image

Platform Bytes of Image File match this machine: 05.01.00


Successfully extracted *.tgz to pipe

Starting ./fullinstall.sh
./fullinstall.sh script
Archiving Netvault license file
Archiving FLAPI DB file
root installation script
requires pwd, sfdisk, mknod, mkraid, mkswap, mkdir, mount, mkfs.xfs
cp and tar

a version of each is located in this directory

Make sure the disks aren't busy...
mknod /dev/md0 b 9 0
mknod /dev/md100root b 9 100
mknod /dev/md101swap b 9 101
attempting to stop raids (if present)
raidstop -c RAIDFILE /dev/md100root
raidstop -c RAIDFILE /dev/md101swap

---->>>> partitioning /dev/hda...

sfdisk -f -H255 -S63 /dev/hda < sfdiskmap.out

Disk /dev/hda: 30515 cylinders, 255 heads, 63 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/hda: unrecognized partition
Old situation:
No partitions found
New situation:
Units = sectors of 512 bytes, counting from 0

Device Boot Start End #sectors Id System
/dev/hda1 * 47 32129 32083 83 Linux
/dev/hda2 32130 1124549 1092420 83 Linux
/dev/hda3 1124550 2216969 1092420 5 Extended
/dev/hda4 2216970 485964800 483747831 83 Linux
/dev/hda5 1124551 1670759 546209 83 Linux
/dev/hda6 1670761 2216969 546209 83 Linux
Successfully wrote the new partition table

Re-reading the partition table ...


---->>>> partitioning /dev/hdc...

sfdisk -f -H255 -S63 /dev/hdc < sfdiskmap.out

Disk /dev/hdc: 30515 cylinders, 255 heads, 63 sectors/track
Old situation:
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/hdc1 * 0+ 1 2- 16041+ 83 Linux
/dev/hdc2 2 69 68 546210 83 Linux
/dev/hdc3 70 137 68 546210 5 Extended
/dev/hdc4 138 30249- 30112- 241873915+ 83 Linux
/dev/hdc5 70+ 103 34- 273104+ 83 Linux
/dev/hdc6 104+ 137 34- 273104+ 83 Linux
New situation:
Units = sectors of 512 bytes, counting from 0

Device Boot Start End #sectors Id System
/dev/hdc1 * 47 32129 32083 83 Linux
/dev/hdc2 32130 1124549 1092420 83 Linux
/dev/hdc3 1124550 2216969 1092420 5 Extended
/dev/hdc4 2216970 485964800 483747831 83 Linux
/dev/hdc5 1124551 1670759 546209 83 Linux
/dev/hdc6 1670761 2216969 546209 83 Linux
Successfully wrote the new partition table

Re-reading the partition table ...


---->>>> partitioning /dev/hde...

sfdisk -f -H255 -S63 /dev/hde < sfdiskmap.out

Disk /dev/hde: 30515 cylinders, 255 heads, 63 sectors/track
Old situation:
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/hde1 * 0+ 1 2- 16041+ 83 Linux
/dev/hde2 2 69 68 546210 83 Linux
/dev/hde3 70 137 68 546210 5 Extended
/dev/hde4 138 30249- 30112- 241873915+ 83 Linux
/dev/hde5 70+ 103 34- 273104+ 83 Linux
/dev/hde6 104+ 137 34- 273104+ 83 Linux
New situation:
Units = sectors of 512 bytes, counting from 0

Device Boot Start End #sectors Id System
/dev/hde1 * 47 32129 32083 83 Linux
/dev/hde2 32130 1124549 1092420 83 Linux
/dev/hde3 1124550 2216969 1092420 5 Extended
/dev/hde4 2216970 485964800 483747831 83 Linux
/dev/hde5 1124551 1670759 546209 83 Linux
/dev/hde6 1670761 2216969 546209 83 Linux
Successfully wrote the new partition table

Re-reading the partition table ...


---->>>> partitioning /dev/hdg...

sfdisk -f -H255 -S63 /dev/hdg < sfdiskmap.out

Disk /dev/hdg: 30515 cylinders, 255 heads, 63 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/hdg: unrecognized partition
Old situation:
No partitions found
New situation:
Units = sectors of 512 bytes, counting from 0

Device Boot Start End #sectors Id System
/dev/hdg1 * 47 32129 32083 83 Linux
/dev/hdg2 32130 1124549 1092420 83 Linux
/dev/hdg3 1124550 2216969 1092420 5 Extended
/dev/hdg4 2216970 485964800 483747831 83 Linux
/dev/hdg5 1124551 1670759 546209 83 Linux
/dev/hdg6 1670761 2216969 546209 83 Linux
Successfully wrote the new partition table

Re-reading the partition table ...


---->>>> clean up /dev/hda...

mdctl --destroywithextremeprejudice /dev/hda4
mdctl: Could not destroy superblock on /dev/hda4

---->>>> clean up /dev/hdc...

mdctl --destroywithextremeprejudice /dev/hdc4

---->>>> clean up /dev/hde...

mdctl --destroywithextremeprejudice /dev/hde4

---->>>> clean up /dev/hdg...

mdctl --destroywithextremeprejudice /dev/hdg4
mdctl: Could not destroy superblock on /dev/hdg4


********* Discovering Expansion Units *********
mkraid -c /updater/install_tools/raidtab.crippled /dev/md100root
DESTROYING the contents of /dev/md100root now!
/dev/hda2: device too small (0kB)
mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
handling MD device /dev/md100root
analyzing super-block
mkraid -c /updater/install_tools/raidtab.crippled /dev/md101swap
DESTROYING the contents of /dev/md101swap now!
/dev/hda5: device too small (0kB)
mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
handling MD device /dev/md101swap
analyzing super-block

--->hotadding /dev/hdc...
using /dev/hdc2 and /dev/hdc5
raidhotadd -c /updater/install_tools/raidtab /dev/md100root /dev/hdc2
/dev/md100root: can not hot-add disk: array not running!
raidhotadd -c /updater/install_tools/raidtab /dev/md101swap /dev/hdc5
/dev/md101swap: can not hot-add disk: array not running!

--->hotadding /dev/hde...
using /dev/hde2 and /dev/hde5
raidhotadd -c /updater/install_tools/raidtab /dev/md100root /dev/hde2
/dev/md100root: can not hot-add disk: array not running!
raidhotadd -c /updater/install_tools/raidtab /dev/md101swap /dev/hde5
/dev/md101swap: can not hot-add disk: array not running!

--->hotadding /dev/hdg...
using /dev/hdg2 and /dev/hdg5
raidhotadd -c /updater/install_tools/raidtab /dev/md100root /dev/hdg2
/dev/md100root: can not hot-add disk: array not running!
raidhotadd -c /updater/install_tools/raidtab /dev/md101swap /dev/hdg5
/dev/md101swap: can not hot-add disk: array not running!
mkswap /dev/md101swap
mkswap: error: swap area needs to be at least 40kB
Usage: mkswap [-c] [-v0|-v1] [-pPAGESZ] /dev/name [blocks]
mkfs.xfs -f /dev/md100root
Error getting MD array info from /dev/md100root
Mounting new root to /mnt/pivot
/dev/md100root: Invalid argument
mount: you must specify the filesystem type
Execution of ./fullinstall.sh Failed!

Fresh Install Failed!

Last edited by TMowreader; 08-05-2008 at 01:59 PM. Reason: Forgot the install txt....
TMowreader is offline   Reply With Quote
Unread 08-06-2008, 04:53 AM   #2
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: Snap 4500 Recovery

I think the HD it is installing on is failing/bad. When you get superblock errors these are normal bad, media failure where it is stored.

I would have pulled the HD's and ran Spinrite on them before attempting clean install.

I hope you do not need the data off at this point since you opted for a clean install.

What to do next.

Run spinrite and see what it finds.
Replace drive 1 and see if it will boot from drive 2.

A Plus side you have access to the recovery console, without this there is no way of installing the OS. unless you have another Guardian OS Unit. So do not do anything that will destroy drive 1 at this time unless you have another unit or a replacement HD with the OS installed.

Your OS is fairly new for an old unit. Is this an update that was applied later on? Most 4500 were shipped with v2 or 3 from Adaptec. The reason I ask is that there was a partition change from v2 to v3 if I recall, required more space.

What brand of HD are installed in the unit? Originals?

Being linux you can look at the HD's just not the raid5 partition. The Boot part is on a raid1 across all HD's. So removing drive 1 may be a good option. But give the watchdog time to respond. Also have you connected a null modem cable to the com port and monitored the boot process? Or is this where the log came from. Some times it will give you more information. And I assume you do not have a service contact other wise you would not be here.
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5,
1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5,
1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy

Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820
blue68f100 is offline   Reply With Quote
Unread 08-06-2008, 07:33 AM   #3
TMowreader
Cooling Neophyte
 
Join Date: May 2007
Location: Portland
Posts: 10
Default Re: Snap 4500 Recovery

Thanks for the reply Blue.

I've got the server at my desk, when looking at the front, which drive is drive 1 and which option should I choose in SpinRite?

When you say replace drive1 and see if it will boot from drive two. Do you mean swap where drive 1 and two are, or buy a new hdd for 1 and put two in ones place?

Tyler
TMowreader is offline   Reply With Quote
Unread 08-06-2008, 07:56 AM   #4
TMowreader
Cooling Neophyte
 
Join Date: May 2007
Location: Portland
Posts: 10
Default Re: Snap 4500 Recovery

I ran SpinRite on the far left drive while looking at the front of the server. There were 5 Linux partions, 4 of which tested fine and the 5th it told me that I should not run spinrite as the size of the drive was different then what the bios said it was. I'm guessin that's the RAID 5 partition, is it ok to run spinrite on that partition? Everything was fine on the other partitions, no problems at all.

Tyler
TMowreader is offline   Reply With Quote
Unread 08-06-2008, 03:29 PM   #5
TMowreader
Cooling Neophyte
 
Join Date: May 2007
Location: Portland
Posts: 10
Default Re: Snap 4500 Recovery

This issue is resolved.

I took the first and second drives out, ran spinrite level two on each of the 4 partitions on each drive, it found nothing, but when i put them back in and booted it up, it booted to the regular guardian OS. The RAID was broken, but it booted up. All the data on the server was backup data of another server, so I deleted the RAID and it is now resynching the new one.

Once it's complete, I'll make DR images of both servers.

Thanks for the help.

Tyler
TMowreader is offline   Reply With Quote
Reply

Tags
4500, failed, guardian, recovery, snap


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 06:40 PM.


Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2022, Jelsoft Enterprises Ltd.
(C) 2005 ProCooling.com
If we in some way offend you, insult you or your people, screw your mom, beat up your dad, or poop on your porch... we're sorry... we were probably really drunk...
Oh and dont steal our content bitches! Don't give us a reason to pee in your open car window this summer...