Re: FAI and debian live
in fact this is where my AOE mount fails, the system ends up read only
and the aufs part is not working.
i've absolutely no clue about AOE. i'm not even sure it's possible with
current live-initramfs. did you try regular nfs based netboot first?
no in fact i cannot use NFS for policy reason here. AOE is a block
device so i don't know why it could not be used :)
apart from that: in order to help you, you would need to make sure that
you did not modify the initrd at all, we would need to know the *exact*
and complete kernel command line that you used to boot, as well as the
version of live-initramfs you've used.
i use:
ii live-initramfs 1.139.1-3 Debian
Live initramfs hook
on the initrd i just added a init-premount/aoe script that:
load aoe module
bring up ethx
do an aoe-discover
and also a udev rule to rename ethx so they are in good order
the boot params are:
append initrd=initrd.img-2.6.26-1-amd64 ip=dhcp
FAI_FLAGS=verbose,createvt FAI_ACTION=install boot=live debug
and i end up like this:
[ 7.698644] udev: renamed network interface eth3 to eth1
[ 7.698644] udev: renamed network interface eth2 to eth0
[ 7.753809] udev: renamed network interface eth0_rename to eth2
[ 7.754500] udev: renamed network interface eth1_rename to eth3
[ 10.877924] floppy0: no floppy controllers found
[ 12.923907] tg3: eth0: Link is up at 100 Mbps, full duplex.
[ 12.923907] tg3: eth0: Flow control is off for TX and off for RX.
[ 13.044967] tg3: eth1: Link is up at 100 Mbps, full duplex.
[ 13.044967] tg3: eth1: Flow control is off for TX and off for RX.
[ 14.174599] eth2: Link is Up 1000 Mbps Full Duplex, Flow Control: None
[ 14.189735] eth3: Link is Up 1000 Mbps Full Duplex, Flow Control: None
[ 41.478419] ide_generic: please use "probe_mask=0x3f" module
parameter for probing all legacy ISA IDE ports
[ 41.478419] Probing IDE interface ide0...
[ 42.056709] Probing IDE interface ide1...
[ 42.621613] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[ 42.628476] ide1 at 0x170-0x177,0x376 on irq 15
[ 42.722967] kjournald starting. Commit interval 5 seconds
[ 42.722967] EXT3-fs: mounted filesystem with ordered data mode.
[ 44.075902] kjournald starting. Commit interval 5 seconds
[ 44.075902] EXT3-fs: mounted filesystem with ordered data mode.
[ 45.404238] kjournald starting. Commit interval 5 seconds
[ 45.404238] EXT3-fs: mounted filesystem with ordered data mode.
[ 46.604481] kjournald starting. Commit interval 5 seconds
[ 46.605154] EXT3-fs: mounted filesystem with ordered data mode.
[ 47.789416] kjournald starting. Commit interval 5 seconds
[ 47.791721] EXT3-fs: mounted filesystem with ordered data mode.
[ 49.044700] kjournald starting. Commit interval 5 seconds
[ 49.046932] EXT3-fs: mounted filesystem with ordered data mode.
[ 50.440357] kjournald starting. Commit interval 5 seconds
[ 50.440357] EXT3-fs: mounted filesystem with ordered data mode.
[ 51.620119] kjournald starting. Commit interval 5 seconds
[ 51.620594] EXT3-fs: mounted filesystem with ordered data mode.
[ 52.924139] kjournald starting. Commit interval 5 seconds
[ 52.924443] EXT3-fs: mounted filesystem with ordered data mode.
[ 54.518098] kjournald starting. Commit interval 5 seconds
[ 54.518098] EXT3-fs: mounted filesystem with ordered data mode.
[ 55.671385] kjournald starting. Commit interval 5 seconds
[ 55.671385] EXT3-fs: mounted filesystem with ordered data mode.
[ 56.854887] kjournald starting. Commit interval 5 seconds
[ 56.854887] EXT3-fs: mounted filesystem with ordered data mode.
[ 58.079040] kjournald starting. Commit interval 5 seconds
[ 58.079041] EXT3-fs: mounted filesystem with ordered data mode.
[ 59.429547] kjournald starting. Commit interval 5 seconds
[ 59.429547] EXT3-fs: mounted filesystem with ordered data mode.
[ 60.670820] kjournald starting. Commit interval 5 seconds
[ 60.670999] EXT3-fs: mounted filesystem with ordered data mode.
[ 61.853922] kjournald starting. Commit interval 5 seconds
[ 61.854404] EXT3-fs: mounted filesystem with ordered data mode.
[ 63.031108] kjournald starting. Commit interval 5 seconds
[ 63.031108] EXT3-fs: mounted filesystem with ordered data mode.
[ 64.259132] kjournald starting. Commit interval 5 seconds
[ 64.259132] EXT3-fs: mounted filesystem with ordered data mode.
[ 65.425751] kjournald starting. Commit interval 5 seconds
[ 65.426576] EXT3-fs: mounted filesystem with ordered data mode.
[ 65.559319] aoe: 0030486265aa e10.0 v00a6 has 585940992 sectors
[ 65.562499] aoe: 0030486265ab e10.1 v00a6 has 97656832 sectors
[ 65.559319] etherd/e10.0:<6> etherd/e10.1: p1
[ 65.575086] p1 p2
[ 66.776502] kjournald starting. Commit interval 5 seconds
[ 66.776502] EXT3-fs: mounted filesystem with ordered data mode.
so it does find the etherdrives but it stop here, the logs ends with:
+ livefs_root=
+ [ -n ]
+ sleep 1
+ [ -z ]
+ panic Unable to find a medium containing a live file system
some command tested as shown in some grep of the live.log :
(initramfs) udevinfo -q name -p /block/etherd!e10.0
etherd/e10.0
(initramfs) /lib/udev/vol_id -t /dev/etherd/e10.0
/dev/etherd/e10.0: unknown volume type
(initramfs) /lib/udev/cdrom_id /dev/etherd/e10.0
(initramfs) /lib/udev/path_id /block/etherd!e10.0
(initramfs)
in the initramfs i put this at the end:
ROOT=/dev/etherd/e10.1p1
but without it i got the same problem
regards,
Jean.
Reply to: