Ok so I tried what you had said and get the following RedBoot> exec -c "console=ttyS0,115200 rw root=/dev/md0 mem=2...@0xa0000000" -r 0x01800000 Base address unknown - use "-b" option
On Sun, Nov 7, 2010 at 7:24 AM, JF Straeten <[email protected]> wrote: > > Hi José, > > > On Sat, Nov 06, 2010 at 09:07:37PM -0700, Jose Solorio wrote: > > > At the end of the installation installation its ask's me if I want to > reboot > > or if I want to go back. I guess its my fault for using two different > > instructions. I followed the instruction from this vid tutorial > > http://www.youtube.com/watch?v=eEgVSlLXw5g. > > I don't see the need to touch the boot_script_data at 6:37, and I > believe that loading both .pkg and initrd + zImage is redundant. > > In my understanding, .pkg is to flash the firmware from the Ipstor > interface and the two other files are to boot it by manualy loading > what is needed. You shouldn't need to do both (though doing it seems > harmless). > > > > After getting to a certain part I continued reading he instructions > > on the debian site. Initially what I had done when the nas was still > > working with Ipstor was 1. load the firmware ss4000e.pkg from the > > debian site. 2. load ramdisk.gz and zImage from debian site via > > ymodem. > > Steps 1 and 2 are probably redundant (at least in my understanding. I > installed mine last year by only loading initrd/zimage by tftp.) > > > > After I reboot, this is what I get: > > > > +No network interfaces found > > > > EM-7210 ver.T04 2005-12-12 (For ver.AA) > > == Executing boot script in 1.000 seconds - enter ^C to abort > > RedBoot> load ramdisk.gz > > Using default protocol (TFTP) > > Can't load 'ramdisk.gz': invalid parameter > > RedBoot> load zImage > > Using default protocol (TFTP) > > Can't load 'zImage': invalid parameter > > RedBoot> exec > > Base address unknown - use "-b" option > > RedBoot> > > > Yes, the problem occurs at 9:36 in your vid : your exec is exec'ing > nothing... > > Could you try to enter this line at the above RedBoot prompt : > > exec -c "console=ttyS0,115200 rw root=/dev/md0 mem=2...@0xa0000000" -r > 0x01800000 > > (or without the "-r ..." parameter.) > > Warning : replace "/dev/md0" with your real root device if it's > different. (The vid takes the first raid array for the root fs, > so I assume it's md0, but not sure.) > > > If the nas boot normaly with one of these lines, we should figure a > way to get it back in the boot_script_data to boot automatically. > > So, does it work ? > > > When I ctrl+c into the nas and type fconfig boot_script_data this is what > i > > get: > > > > +No network interfaces found > > > > EM-7210 ver.T04 2005-12-12 (For ver.AA) > > == Executing boot script in 1.000 seconds - enter ^C to abort > > ^C > > RedBoot> fconfig boot_script_data > > boot_script_data: > > .. load ramdisk.gz > > .. load zImage > > .. exec > > Enter script, terminate with empty line > > >> > > I don't understand why do you do this at the begining of the vid ? You > type fconfig to edit boot_script_data, but you cancel it with "n". > Don't type fconfig at first ;) > > Hih, > > -- > > JFS. > > > -- > To UNSUBSCRIBE, email to [email protected] > with a subject of "unsubscribe". Trouble? Contact > [email protected] > Archive: http://lists.debian.org/[email protected] > > -- Jose Solorio Network/Systems Admin www.bitbytebit.net 760-458-7943
