Upgrading Snap 4500

[mchattech]

Has anyone upgraded, or attempted to upgrade, a Snap 4500?

I have a client with one, but they've maxed out the space on it, so was planning on throwing 4 500gigs in there, instead of the 250s it currently has.

I've got a full backup of the server data, but it would be a huge pain to sit and restore it all.

I've been reading the plans of upgrading a 2200...would I follow the same steps to upgrade to the new drives...do one at a time until all four are updated?

Thanks in advance for any help. And if I'm going into uncharted territory, I'll keep everyone updated.

[re3dyb0y]

Yeah, you are


Its a Guardian OS unit, and although now we are starting to get some coming through, but most and our main support is the generally older Snap OS units.

Well, just Snap OS units

[mchattech]

Oh boy, this will be fun...heheh

I may have to put off this project until this weekend/early next week because of previous commitments (and a lack of desire to interfere with their current operations).

I know I have to upgrade the OS from 3.2.019 SP1 to the latest version, 4.1.061.
Beyond that, I'm hoping that I'll just have to go drive by drive, slapping it in and going from there. Hopefully I won't have to break the mirror or do anything that will make me pull out my hair.

[blue68f100]

There was a 12000 that was here last week. He discovered that the power supply was not big enough to boot 4 500 gigs. Better get the specs of the drives, startup surge data, and compare it to your PS. Only had a 120w, needed a 170 to cover the in rush, unless you can do a staggered start.

[mchattech]

Thanks for pointing out the power issue, that's another aspect I have to keep in mind. Unfortunately I wasn't able to open up the server at the time that I was around it, but Snap tech specs say that there's a 250 Watt PS in there. Maxtor has the drive power peeking at about 30 Watts per drive (at spinup), so if there really is a 250er in there, I should be good.

I'm also going to try and see if there are higher cfm fans that I can throw in there, just to help dissipate some of the heat a little bit better.

The big date has been set for this Sunday, so I can work on it uninterrupted...and so no one will be around to see me :bawling: if it fails.

[blue68f100]

Seagate just anounced there 750gig drives. It's using the new perpendicular technology. That would be another boost, with the same power draw.

Just read the speed is close to that of a 10000rpm Raptor

[mchattech]

how sick are those drives? can't wait for 1 TB drives.

[webboy]

Well ive upgraded 2 snap 4400's pretty much the same as the 4500 as per Snap/adaptec. The problem ive run into is gaining full use of the new drive space.

One snap 4400 came stock with 120 gig drives i uped it to 200 gig drives but it formatted them as 169 gigs total which is incorrect.

To upgrade the server you must have 1 original drive in the first slot. The machine WILL NOT boot up with a new fresh drive in it, The Guardian OS is installed on the drive.

I would reccomend purchasing 1 new drive first to see if you can even see the full capacity of the drive. Chances are it will format the drive to the size of the original one :hammer:

How old is the unit? It should handle 400 gig drives fine (no power issues or hardware issues) as it ships now with 4 400 gig drives.

If your in warantee you might want to call adaptec and tell them youve lost 2 drives in the array and just happen to have new drives laying around. and see if they can help reclaim the full use of the discs.

Does any one know if there is a way to adjust partition sizes in linux? You can get to a command prompt on these devices via the serial port.

[blue68f100]

There are some utilities that can read MBR tables and correct them. The Ultimate Boot CD (UDBC (http://www.ultimatebootcd.com/)) is one CD that has all utilities collected together. It is Unix based, so it may work. I used it on repairing my LT when I setup a dualboot and lost access to one of the partitions. I done think Partition magic reads the XFS system.

[mchattech]

Well, if anyone is interested still, I'm working on the server now. I was hoping to start much, much earlier in the day, but got word early this morning that my grandmother had a pretty bad stroke and her condition was not looking great. Needless to say, family definitely comes before work.

Anyway, once I finally got to the office, I discovered that the server backup had not been run in 2 days because someone turned off the machine that handles the backup (Retrospect to an external drive, with a once weekly backup to a Snap 2200) and I was not going to do a thing before I had the most complete backup set possible. So once that was run, I decided to shoot for the moon and threw one of the 500 gig drives right in.

No problems booting up, or accessing the web GUI once it started. It did not see the drive as part of the RAID5 set initially, so I'm currently adding that drive and resyncing. It's reading the drive as the local hot spare, but I'm hoping and praying that it will miraclously add it as just another drive in the RAID set. I should know in about an hour, once the sync has completed, if it's going be kind to me or if it's going to be one of those 3 packs of smokes kind of night.

[mchattech]

Update: After waiting hours for the first drive to sync up, it went through and took its new place in the RAID set. I figured I wouldn't get too eager, and just go drive by drive, rather than pulling all the old drives out (now that one is synced) and putting the other 3 new ones in. That, and I'm unsure how doing that might affect the integrity of the RAID set and the data on it. No sense is risking it with someone else's files.

I'm eager to see, once all the new drives are in, if the Snap automatically reconizes their capacity, rather than adopting the old drives' size. So far it does see the first new drive as having the correct size (about 446 gigs).

And the truly best part? If I play my cards right, I might get to walk away with 4 free 250 giggers....mmmm, I'm smelling a FreeNAS box to call my own.

[blue68f100]

Sorry to hear that about your grandmother.

It's nice when they work as design.
You will need to fail 1 drives at a time if you want to maintain the data on the unit. If you lose 2 you will be sol. Drive 1, I would wait till the last, the OS resides on it. I havn't a clue on how it will handle it. If you can swap out drives hot with out powering down, it shouldn't be a problem.

Can you send me a list of the debug cmds avaliable for the Guardian OS. I would like to compare them to the Snap OS.

[webboy]

Sorry to hear that about your grandmother.

It's nice when they work as design.
You will need to fail 1 drives at a time if you want to maintain the data on the unit. If you lose 2 you will be sol. Drive 1, I would wait till the last, the OS resides on it. I havn't a clue on how it will handle it. If you can swap out drives hot with out powering down, it shouldn't be a problem.

Can you send me a list of the debug cmds avaliable for the Guardian OS. I would like to compare them to the Snap OS.

Debug commands?!??!! Some one found the debug commands? where i havent fount them yet. and there is no /debug directory like the Snap OS.

remember this is a Linux box.

In what slot did you put the 500 gig drive in mchattech ?

[mchattech]

I started with Disk 1 and worked my way up from there. I had to head out while the 3rd drive was syncing, and am on my way back to take care of the fourth drive. I was powering down the 4500 before I replaced a drive, just because I was very tired and extremely paranoid that I would fsk it up.

In between drives 2 and 3 I was able to access data on the server without any problems (reading and writing) so I believe it's all good. I'll let everyone know in about 3.5 hours, when the last drive syncs up.

As far as debug commands, I haven't found them on GuardianOS units. This was actually the first time I had to do ANYTHING with a 4500 and only got in about an hours worth of playing around and gettting familar with the GUI before jumping in....but the whole story isn't worth digging up at this point. :dome:

I'll take a quick look and see if I can find debug commands for it.

[mchattech]

Well, hit a big bump in the road. The drives formatted properly, synced nicely, everything's pretty except it sees the drives as having the original capacity. Not good or fun.

[blue68f100]

Wait ..... Was this is a repeat of a problem reported earlier ??????

Do you have your data backed off where you can play????

I think that happen since the array was built with 250 gig. The array was bassed on it. The size is bassed on the smallest drive.

Did you upgrade to v4.1 like you mentioned earlier????

Set to JBOD (4 x 500) then back to Raid 5.
Check to see if it reconize the drives as 480 gig.

Then I would do a re-format of the drives, making sure no hidden markers from breaking the raid to jbod.

The set the raid 5 array up.

I think this is a repeat of what happen earlier.........

Looks like this is going to be a learning exercise for us. New to Guardian OS.
What works with Snap OS does not seam to apply to the Guardian OS.

[mchattech]

Yeah, I think someone was having a similar issue with a 4400..stupid hard drives. With this though, the drives show up as having 460 some gigs, but within the RAID set only the original amount of space is available. And that missing space doesn't show up anywhere.

I've got full backups of everything, and the original hard drives (250s). I just got the upgrade (don't ask) so that wasn't done before I started syncing the new drives. I'm not sure if that would have helped the situation at all; it seems like they've got those drives locked up pretty good, forcing you to get their upgrades. Nothing like paying $500+ for one FRU

I've been scratching my head try to figure out how do get around this, and the best I can figure is that there's something within the OS limiting/restricting hard drive size. I think I might try running a fresh install (reading up about on adaptec's site) with the new drives in place. Has anyone tried this on a 4200, 4500, 4400, 14000, 15000 or 18000?

[re3dyb0y]

As we've said in other threads

We only have really had 1000,1100,2000,2200,4000,4100 and such which are Snap OS

We are getting Guardian units cmoing through now, but neither me or david (blue68f100) have any hands on experience...

Anyone fancy buying us a small 4200 each :P

[blue68f100]

Like we said, (re3dyb0y & my self) only have experience on the SnapOS.

Here is the other thead http://forums.procooling.com/vbb/showthread.php?t=13093

[webboy]

There is no limitation in hardware or software as per Adaptec Ive called and am having many email threads with techs. But what were attempting to do they havent tried or will support.

I wonder how they are imaging HD in the lab???

The drive space you lost is there its just an unallocated partition on each drive.
It would seem that the OS is retaining the drive size and partition tables of the original drives (that was the case for me). Breaking this is the key. Adaptec says in theory it can be done. At this point im tempted to see if i can find a replacement drive with the os on it as this seems to be the only way. Id like to try and expand the partitions to recover the lost space but i currently have no where to dump all this data too.

[mchattech]

There is no limitation in hardware or software as per Adaptec Ive called and am having many email threads with techs. But what were attempting to do they havent tried or will support.

I wonder how they are imaging HD in the lab???

The drive space you lost is there its just an unallocated partition on each drive.
It would seem that the OS is retaining the drive size and partition tables of the original drives (that was the case for me). Breaking this is the key. Adaptec says in theory it can be done. At this point im tempted to see if i can find a replacement drive with the os on it as this seems to be the only way. Id like to try and expand the partitions to recover the lost space but i currently have no where to dump all this data too.

I'm getting the same thing from them. I have to go out of town this weekend on a business trip, but I'm planning on taking one of the original drives with me to see what I can dig up on it.

In the meantime, I've started setting up a FreeNAS box. If it's going to be a huge hassle to upgrade Snaps in the future, I'd love to over people a much cheaper route to go.

[blue68f100]

You my try JBOD and see if you can use the whole drive.
Then re-format all.
Then build a NEW RAID5 Array.

[mchattech]

I'll have to double check tomorrow, but I don't remember seeing JBOD as an option...just RAID 0, 1 or 5.

[webboy]

I'll have to double check tomorrow, but I don't remember seeing JBOD as an option...just RAID 0, 1 or 5.


There is no option for JBOD Just raid on these boxes (4400 and 4500 dont know about higher models yet)

[mchattech]

Debug commands?!??!! Some one found the debug commands? where i havent fount them yet. and there is no /debug directory like the Snap OS.

remember this is a Linux box.

In what slot did you put the 500 gig drive in mchattech ?

found the debug commands for Guardian. Here's a link for them: http://www.image78.com/guardian_debug.htm

Looked at an original HD (250) on a Windows box...couldn't see much, just looking with Disk Manager. There's 5 or 6 partitions on the drive. Maybe I can get away with scaling up the partitions for the 500 gig drives (wishful thinking). If not (or i don't get the chance to), I plop it into a box and fire me up so Knoppix. Should have enough time this weekend to do that.

[blue68f100]

Thanks for the debug page, looks like it got clipped at a column length of 35.

Nothing jumped out at me, that may help you.

[webboy]

Nicely done it seems that you can also type linux/unix commands it apears that the debug page is really a sh command prompt

[kuoman]

I am new to SNAP server. I am in the process of getting four 250GB HD (replacing the four 120GB currently on the machine). It is running OS 3.2.019 with RAID5 setup.
When I get these four 250GB, what is the upgrading method? I heard, swap one HD at a time and let the new HD sync (hours?) then do the same for the other three HDs.

So which drive do I start first? from drive 1, 2, 3 and then 4 or from drive 4, 3, 2 and 1? Some people mention about losing the OS, will swapping one at a time remove the OS on the system?

[blue68f100]

Boot with drive 1. The hot swap drive 2. Thenpower down and move drive 2 to 1. Reboot, then hotswap the rest of the drives.

[Phoenix32]

Break your RAID 5 first or the OS will make the new drive match the old drive size.

[kuoman]

Break your RAID 5 first or the OS will make the new drive match the old drive size.
By "break" you mean delete RAID 5 right? Which RAID set should I use for upgading the HD?

blue68f100 replied in another post (I won't do doble post, so I will reply on this thread). I don't care about the data, since I have it backed up already. I will do a factory rest, disable CA Antivuris, disable Snapshot then shutdown the system. Remove drive 2, 3 and 4 then power it back on. Insert the new HD to slot 2.
After the system sync drive 1 (old) with drive 2 (new). I power it down and take out drive 1 and 2. Insert new drive (was drive 2) into drive 1 slot.
Power the system up (only slot 1 has drive), I put in new drive in slot 2, 3 and 4 (can I put all 3 at the same time or I have to do one at a time after the drive is synced?)

[Rote8]

The Snap 4500 uses an "invisible N-Way RAID" for the OS in the first 100 MB of each hard drive.
Replacing the drives, one at a time will work, but the data RAID set will still be the original size.
To use the full size of the new drives the original data RAIDset must be deleted and recreated.

Because of this I advise the following method:
Backup the data on the RAID.
Remove the original RAIDset.
Replace 3 drives. (keep the originals untouched, in case something goes wrong)
Go have lunch while the OS RAIDset syncs the N-Way raid.
Once the OS RAIDset is repaired, replace the 4th drive.
Create a new RAIDset using the full drive size.

:nod:

[blue68f100]

By "break" you mean delete RAID 5 right?

YES, You must break/delete the raid array other wise it will revolk recovery console to diaster recovery.

Replace 3 drives. (keep the originals untouched, in case something goes wrong)
Go have lunch while the OS RAIDset syncs the N-Way raid.

WHY, it only takes a few minutes for this process.

[Phoenix32]

David, why do people insist on making this harder or more complicated than it is?

I have done this several hundred times with various GOS revision, hard disk brands, and hard disk sizes without a problem, so listen up.

This is a simple step by step that assumes you do not want to keep your current data (or have backed it up elsewhere). It also assumes you have a working GOS on the unit.

I do break the current data raid before I start, but not always and you don't have to because once you remove the drives as I describe here, its gone anywise. I just do it so I don't get errors in the log telling me it blew up.

1. Remove drives 2 thru 4. Leave drive 1 (or a seed drive) in slot 1.
2. Put one of your new drives in slot 2. (no drives in slot 3 or 4)
3. Boot the unit.

a) I tell people to wait about 15 minutes from here.
b) It takes 5 to 9 minutes to boot the unit depending on your unit and configuration etc. It only takes a couple minutes after full boot for the OS to get copied over from slot 1 to slot 2, but give it 5 to 10 minutes from full boot up to be sure. No big deal.

4. Shut the unit down.
5. Remove the old drive from slot 1.
6. Put your new drive from slot 2 that just got the OS installed into slot 1.
7. Put your other 3 fresh clean new drives into slots 2 thru 4.
8. Boot the unit.
9. Wait 10 minutes from full boot up for the OS to copy to the 3 new drives.

c) At this point, I usually do a hardware reset and a factory default reset and erase the logs etc to clean things up, but not required.

10. Your done.


A child could do it.


Edit Note: This also assumes you were using RAID 5 (by far the most common). If not, then you will need to break the array first.

[bcole]

blue68f100,

I was able get my self out of some jams with advice you've posted here
and was wondering if you have any thoughts on this one

attempting to update my 4500 after another HD failure an repeated reloading
failures, I figured i go ahead and break the raid which i needed to do anyways
in order to install larger HDs now the system is only loading grub Am I sol? is there a way to use grub to relink back to where the os is? I've looked at the drive in with koppix and it appears the guardian stuff is still there.

I do have a full install gsu for my version 4.0.228

all recomendations welcome

Thanks for listening

[Phoenix32]

blue68f100,

I was able get my self out of some jams with advice you've posted here
and was wondering if you have any thoughts on this one



What am I, chopped liver?

Sounds like part of the OS is maybe corrupt.

Answers are;
No
Yes

[bcole]

What am I, chopped liver?



Sorry, didn’t mean to insult you or anyone else
You could possibly be Filet Mignon unless you’re a vegetarian in which case I maybe insulting you again
Never the less I merely pointed to the individual who helped me out before. Help me out here and I’ll
Look upon you as whatever top grade food of your choice, precious metals or gems.
Are we good yet?
I can grovel even more……. In the mean time please help
Thanks again

[Phoenix32]

Find out what IP it is grabbing (like from your router etc). Watch the lights on the front and see if it is going into recovery mode (the light will flash at a normal rate, but will be flashing between yellow and amber). If so, cool, log in via the browser GUI and reload your GSU file.

if no...

Since your data is backed up and the raid broken anywise, pull the drives and try to boot the unit with each drive, one at a time alone, in slot 1, and see if the unit will boot with any of them.

[blue68f100]

blue68f100,

I was able get my self out of some jams with advice you've posted here
and was wondering if you have any thoughts on this one

attempting to update my 4500 after another HD failure an repeated reloading
failures, I figured i go ahead and break the raid which i needed to do anyways
in order to install larger HDs now the system is only loading grub Am I sol? is there a way to use grub to relink back to where the os is? I've looked at the drive in with koppix and it appears the guardian stuff is still there.

I do have a full install gsu for my version 4.0.228

all recomendations welcome

Thanks for listening

Sounds like your may had reference to your older hd's some where. The reason I do not want any raid, AV, snap shots or any software ref to HD's. I'm surprised that it does not launch the recovery console.

I would install one of your original HD and do the OS transfer to the new HD's.

[bcole]

I don't believe it's really booting all the way
all drives act the same (they are the originals not new)
with terminal hooked up I only get prompted with grub
here's what I'm doing to get it where it looks as if it's booted

grub> root (hd0,1)
Filesystem type is xfs, partition type 0x83

grub>kernel /boot/vmlinuz-gos-up root=hda2
[Linux-bzimage, setup=0xa00, size=0x141ae2]

grub> boot

Uncompressing kernel... OK, booting the kernel.
************************************************** ********
************************************************** ********
This device cannot be managed via video/kbd/mouse interface.
The video display output is now disabled
You may access the managment functions from the web your browser.
Thank You,
- Snap Appliance, Inc -
************************************************** ********
************************************************** ********

and there she sits only power & network led no heartbeat
no 'SNAP406572' on net work (default name)
no 'SNAP-1' (original assigned name)
no ip's given out from dhcp (was grabbing 100.100.11.12 before which is first available ip)
not useing 10.10.10.10
not using oringinal assigned ip 100.100.3.3


am I missing something here?

Thanks

[blue68f100]

Like you said it's looking for something that's not there.

From grub I would try to launch the recovery console. But I do not know what it's name actually is. It should be located on the first partition. Then do a clean install.

Have you replaced any of ram or any thing hardware?

[bcole]

not sure why but the hda1 (1st partition) was empty it should have all the *up and *smp files from /boot
on hda2 (2nd partition) + the /grub dir with a grub.conf file. there is script in /install_tools called mkboot.sh inside of it I could see that it creates the grub.conf from the type of system your running copied the portion for my system and created the /grub/grub.conf file. after that when I rebooted my hyperterminal was allowing me to see what was going on
no more hangs. able to see that I found the proper ip and could connect the recovery panel reinstall the os. Guardian also does not seem to want to propagate to drives which have a portion of the same ver OS
I’m assuming all you need to do is smoke the kernels from partition 1&2 and it would treat it as if it was
new and replicate itself.
New related issue
I read that you should be able in debug run “co de format 10000 /reinit” to have snap reinit the drive to it’s full capacity but Guardian OS isn’t recognizing the command is that a SnapOS specific command
Or am I still missing something?

Thanks again

FYI
1st partition contains
a----- 2776780 30-Nov-109 14:36 Guardian-initrd.smp
a----- 2766523 30-Nov-109 14:36 Guardian-initrd.up
a----- 407025 30-Nov-109 14:36 System.map-gos-smp
a----- 385298 30-Nov-109 14:36 System.map-gos-up
a----- 19649 30-Nov-109 14:36 config-gos-smp
a----- 19627 30-Nov-109 14:36 config-gos-up
-d---- 0 30-Nov-109 14:36 grub
-d---- 0 30-Nov-109 14:36 lost+found
a----- 1320674 30-Nov-109 14:36 vmlinuz-gos-smp
a----- 1250189 30-Nov-109 14:36 vmlinuz-gos-up

./grub:
total 130
-d---- 0 30-Nov-109 14:36 .
-d---- 0 30-Nov-109 14:36 ..
a----- 709 30-Nov-109 14:36 grub.conf
a----- 512 30-Nov-109 14:36 stage1
a----- 131008 30-Nov-109 14:36 stage2

[Phoenix32]

#1 Did you do as I told you the first time?

Find out what IP it is grabbing (like from your router etc). Watch the lights on the front and see if it is going into recovery mode (the light will flash at a normal rate, but will be flashing between yellow and amber). If so, cool, log in via the browser GUI and reload your GSU file.

if no...

Since your data is backed up and the raid broken anywise, pull the drives and try to boot the unit with each drive, one at a time alone, in slot 1, and see if the unit will boot with any of them.


#2 If yes, what was the results?

#3 If no, why should I post anything further?

[Phoenix32]

That's what I thought.

[bcole]

it wasn't until I redid the first partition (with knoppix) that the system responded,
I don't believe it's really booting all the way
"all drives act the same "
"and there she sits only power & network led no heartbeat"(middle led out = system not up)

I'm thinking the reason it didn't boot properly from grub was the kernel command
I used “kernel /boot/vmlinuz-gos-up root=hda2 “
root(hd0,1) <-- tells grub to look in 2nd partition since my 1st partition was empty
-----------------------actual guardian grub.conf points to (hd0,0) because the kernel should be there
-----------------------next line is more consistent with kernel statement in the grub.conf file
-----------------------with the exception of /boot which tells which dir the kernel (vmlinuz-gos-up)
-----------------------is located on the partition specified.

“kernel /boot/vmlinuz-gos-up root=/dev/ram ramdisk=16384 console=ttys0,115200n8 rw uppermem 16384”

------------------------I think lacking the console statement was preventing anything being output to the
------------------------hyperterminal conneted to the serial port.there is also a serial and terminal
------------------------statements at the beginig of grub.conf
------------------------ All I got was the same banner output to the vga. There should be 3 options to boot in a terminal setup
-------------------------1st option is normal 2nd being alternate boot 3rd which would boot to recovery console
If anyone knows for sure please verify, I'm only speculating. Strange thing is after system was repaired the /boot dir on partition disapeared
Right now once my system is back up and synced I’ll try to take a day and try to bring it back up with one of the drives where the OS is broke.
The system is up now and resyncing the new drives which had no problem copying the OS or recognizing their size.

Many Thanks To All,
FYI
1st partition contains
a----- 2776780 30-Nov-109 14:36 Guardian-initrd.smp
a----- 2766523 30-Nov-109 14:36 Guardian-initrd.up
a----- 407025 30-Nov-109 14:36 System.map-gos-smp
a----- 385298 30-Nov-109 14:36 System.map-gos-up
a----- 19649 30-Nov-109 14:36 config-gos-smp
a----- 19627 30-Nov-109 14:36 config-gos-up
-d---- 0 30-Nov-109 14:36 grub
-d---- 0 30-Nov-109 14:36 lost+found
a----- 1320674 30-Nov-109 14:36 vmlinuz-gos-smp
a----- 1250189 30-Nov-109 14:36 vmlinuz-gos-up

./grub:
total 130
-d---- 0 30-Nov-109 14:36 .
-d---- 0 30-Nov-109 14:36 ..
a----- 709 30-Nov-109 14:36 grub.conf
a----- 512 30-Nov-109 14:36 stage1
a----- 131008 30-Nov-109 14:36 stage2

also
grub.conf (for snap4500 single processor)
================================================== ========
serial --unit=0 --speed=115200
terminal --timeout=0 serial

default 0
fallback 5
timeout 10

title Opus (default boot)
root (hd0,0)
kernel /vmlinuz-gos-up root=/dev/ram ramdisk=16384 console=ttyS0,115200n8 rw
uppermem 16384
initrd /Guardian-initrd.up

title Opus-alt (use alt kernel from /boot in root filesystem)
root (hd0,1)
kernel /boot/bzImage.alt root=/dev/ram ramdisk=16384 console=ttyS0,115200n8 rw ACCEPTROOT=1
uppermem 16384
initrd /boot/Guardian-initrd.alt

title tserver (start tserver installation only)
root (hd0,0)
kernel /vmlinuz-gos-up root=/dev/ram ramdisk=16384 console=ttyS0,115200n8 rw NOPIVOT=true
uppermem 16384
initrd /Guardian-initrd.up
================================================== ========