Re: Booting an LDOM (can't find kernel)
On Mon, Jul 25, 2016 at 1:55 PM, <rodent@netbsd.org> wrote:
> On Mon, Jul 25, 2016 at 06:56:35AM +0200, John Paul Adrian Glaubitz wrote:
>>
>> It's panicking because you specified the wrong root device:
>>
>> [90779.943892] EXT4-fs (vdiska1): mounting ext3 file system using the ext4 subsystem
>> [90779.951847] EXT4-fs (vdiska1): mounted filesystem with ordered data mode. Opts: (null)
>> [90780.025922] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
>> [90780.025922]
>> [90780.026642] CPU: 0 PID: 1 Comm: init Tainted: G E 4.5.0-2-sparc64-smp #1 Debian 4.5.2-1
>> [90780.027297] Call Trace:
>> [90780.027511] [000000000055777c] panic+0xdc/0x260
>> [90780.027860] [000000000046a270] do_exit+0xb30/0xb40
>> [90780.028224] [000000000046a330] do_group_exit+0x30/0xc0
>> [90780.029623] [000000000046a3dc] SyS_exit_group+0x1c/0x40
>> [90780.030027] [0000000000406294] linux_sparc_syscall+0x34/0x44
>> [90780.031618] Press Stop-A (L1-A) to return to the boot prom
>> [90780.032028] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
>> [90780.032028]
>>
>> You specified vdiska1 which is your boot part:
>>
>> > Kernel command line: root=/dev/vdiska1 ro console=ttyS0,9600,8n1
>>
>> /dev/vdiska1 is the boot partition for SILO, not the root filesystem.
>
> There's only two partitions: vdiska1 which contains everything and vdiska2
> which is swap.
>
please make a small ext2/ext3 partition (i suggest at least 300Mb in
size) at the beginning of disk, so /boot should be your /dev/sda1 ,
then make everything else (root fs, swap, etc...). Works for me (in
LDOMs and physical servers).
Reply to: