[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ss4000-e Install how to set up so it boots



Ok after countless hours (days/weeks) I am happy to say that we have success!! :)
Here is what I have done. After reading about adadm I came to the conclusion that booting from md devices can only be done with raid 0,1,10. Since I had all my devices as raid 5 devices that may have been the issue. I rebooted the device and went the boot_script_data. This is what my final looks like:
>> fis load -b 0x01800000 ramdisk.gz
>> fis load -b 0x01008000 zImage.gz
>> exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000
after I hit enter twice and saved the configuration. I typed "g" at the "Redboot>" prompt then hit enter, rebooted, and got me to the "Initramfs" prompt
I decided to re-install again. This time when it came to the disks I did guided and used sda and thats when I noticed how it partitioned the drive.. it creates a partition for /, /boot and a swap partition. I think this may have been my point of failure as well.

If you look at the debian install guide : http://d-i.alioth.debian.org/manual/en.armel/ch06s03.html#di-partition
Under section
6.3.2.4. Configuring Multidisk Devices (Software RAID)
It says the following:

Note

Make sure that the system can be booted with the partitioning scheme you are planning. In general it will be necessary to create a separate file system for /boot when using RAID for the root (/) file system. Most boot loaders do support mirrored (not striped!) RAID1, so using for example RAID5 for / and RAID1 for /boot can be an option.

At any rate I continued with the guided partition method. After it went through the installation it asked me for which packages, I was going to install ssh server but hit enter instead of spacebar and the installation went on to complete. It asked me if I wanted to reboot....... MOMENT OF TRUTH!! I hit enter for it to reboot and say the same screen ..... loading kernel followed by a lot of other details :) and then finally a Login prompt. Logged into see that it had a user:host:~# .

Again I thank you for all the help you gave JFS. I hope this helps someone else along the way, I think the key is that I messed with the boot_script_data and from what I understand now your not supposed to do THAT!! haha. Cheers and good luck.

On Tue, Nov 9, 2010 at 2:27 PM, JF Straeten <jfstraeten@scarlet.be> wrote:
On Tue, Nov 09, 2010 at 11:24:54PM +0100, JF Straeten wrote:

> (Please keep trafic on the list as I may be useful for others...)
                                   ^^^
                       Please read: "it"

A+

--

JFS.



--
Jose Solorio
Network/Systems Admin
www.bitbytebit.net
760-458-7943

Reply to: