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

Re: Problem during the reboot phase (netinst mage 2004-05-16)

Hello Stex,

SteX wrote:


Hi all,
I tried to install new d-i on my HP9000/C3000. First it seems all to work
fine during the installation; I used the automatic selection of the partitions,
but when it rebooted I found the following error

Attempting to boot first valid device on FWSCSI ...

BOOTABLE DEVICE FOUND:
  Path Number        Device Path              Device Type and Utilities
  -----------        -----------------        -------------------------
P0 FWSCSI.6.0 COMPAQ ST32171WC IPL Booting... Boot IO Dependent Code (IODC) revision 0 

HARD Booted.
palo ipl 1.4 root@c3k Fri Mar 26 16:18:24 MST 2004

Partition Start(MB) End(MB) Id Type
1               1      33   f0 Palo
2              34     157   83 ext2
5             158     818   83 ext2
6             819    1910   83 ext2
7            1911    2005   82 swap

PALO(F0) partition contains:
   0/vmlinux64 6666431 bytes @ 0x48000

Information: No console specified on kernel command line. This is normal.
PALO will choose the console currently used by firmware (serial).
Command line for kernel: 'root=/dev/sdb5 HOME=/ console=ttyS0 TERM=vt102
palo_kernel=2/boot/vmlinux'
Selected kernel: /boot/vmlinux from partition 2
ERROR: open /boot/vmlinux from partition 2 failed

What should the problem be?
Thank you in advance

Regards

Stex
Excuse me but I don't have enough time experiment new d-i (so I have no clue of default partitioning), but I recently work on palo-1.5 and it seems that in fact palo don't find '/boot/vmlinux'; it could be because: 
   - it is not install at all
   - it doesn't stand at the expected place (ie into /boot).
In the first case just reboot in interactive mode and choose to boot on '0/vmlinux64' and try to re-install the kernel you want.
In the second case reboot also in interactive mode and iirc with palo-1.4 you already have the 'l' (ell) option to list available files and change your boot kernel name to match the existing one.
That said, I am quite sure that your partion 2 is your boot partition (normaly mounted as /boot) and not your root? And so just remove /boot from the kernel location when you reboot in interactive mode so that your boot cmd looks like: Information: No console specified on kernel command line. This is normal. PALO will choose the console currently used by firmware (serial).Current comman:3/vmlinux root=/dev/md2 HOME=/ console=ttyS0 TERM=vt102 0: 2/vmlinux 1: root=/dev/md2 2: HOME=/ 3: console=ttyS0 
4: TERM=vt102

hth,
   Joel
PS: if you need more info on howto boot in interactive mode, please have a look at Grant's mail: <http://lists.debian.org/debian-hppa/2004/05/msg00048.html>
Reply to: