config questions

[Bjorn Meyer]

Aside from what is in the log files, this is what is output to the
console from: fai-setup -v >fai-log.log

fai.log is the file that is generated and placed in the nfsroot.

The 2 log files that I want to attach, puts the message over the 15K
limit. So I'm unable to post them here. I could send them to you
directly instead.

Can not write log, openpty() failed (/dev/pts not mounted?)
Can not write log, openpty() failed (/dev/pts not mounted?)
/sys/class/net/ is not available, persistent interface names not saved.
ls: cannot access /boot/vmlinuz-*: No such file or directory
Can not write log, openpty() failed (/dev/pts not mounted?)
Can not write log, openpty() failed (/dev/pts not mounted?)
WARNING: These unknown packages are removed from the installation list: sysutils
install_packages: read config file /etc/fai/NFSROOT
install_packages: executing chroot /data/srv/fai/nfsroot apt-get clean
WARNING: These unknown packages are removed from the installation list: sysutils
install_packages: executing chroot /data/srv/fai/nfsroot apt-get -y -o
Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold"
--fix-missing install fai-nfsroot module-init-tools dhcp3-client ssh
rdate lshw hwinfo portmap bootpc rsync lftp rsh-client less dump
reiserfsprogs usbutils psmisc pciutils hdparm smartmontools parted
mdadm lvm2 dnsutils ntpdate dosfstools cvs jove xfsprogs xfsdump
dialog discover mdetect console-tools console-common expect iproute
udev subversion grub lilo read-edid
Extracting templates from packages: 100%
Can not write log, openpty() failed (/dev/pts not mounted?)
Can not write log, openpty() failed (/dev/pts not mounted?)
Can not write log, openpty() failed (/dev/pts not mounted?)
Can not write log, openpty() failed (/dev/pts not mounted?)
Looking for keymap to install:
NONE
Looking for keymap to install:
NONE
Adding system-user for exim (v4)
Updating certificates in /etc/ssl/certs....done.
Running hooks in /etc/ca-certificates/update.d....done.
W: mdadm: failed to load MD subsystem.
Generating array device nodes... /var/lib/dpkg/info/mdadm.postinst:
line 29: /dev/MAKEDEV: No such file or directory
failed.
Generating mdadm.conf... done (failed to scan arrays; /proc probably
not mounted).
update-initramfs: deferring update (trigger activated)
Creating SSH2 RSA key; this may take some time ...
Creating SSH2 DSA key; this may take some time ...
install_packages: executing chroot /data/srv/fai/nfsroot apt-get clean
install_packages: executing chroot /data/srv/fai/nfsroot dpkg
--configure --pending
install_packages: executing chroot /data/srv/fai/nfsroot dpkg -C
install_packages: executing chroot /data/srv/fai/nfsroot apt-get clean
rm: cannot remove `dev/MAKEDEV': No such file or directory


On Wed, May 28, 2008 at 1:23 PM, Alex Volkov <avolkov at gmail.com> wrote:
> Could you send me complete output of fai-setup -v ?
>
> Alex.
>
> On Wed, 2008-05-28 at 12:56 -0600, Bjorn Meyer wrote:
>> Unfortunately, now I am unable to successfully run fai-setup -v.
>> I wanted to do a reinstall so that I knew what steps I took to get a
>> running install. That didn't work so well.
>> I get the following as the last few lines before aborting.
>>
>> Shadow passwords are now on.
>> rm: cannot remove `dev/MAKEDEV': No such file or directory
>> Aborting
>> Removing `local diversion of /sbin/discover-modprobe to
>> /sbin/discover-modprobe.distrib'
>>
>>
>>
>> On Wed, May 28, 2008 at 10:45 AM, Alex Volkov <avolkov at gmail.com> wrote:
>> > On Tue, 2008-05-27 at 10:49 -0600, Bjorn Meyer wrote:
>> >> On Tue, May 27, 2008 at 10:16 AM, Bjorn Meyer <bjorn.m.meyer at gmail.com> wrote:
>> >> > I am as sure as what I have seen in the logs. I do agree, that
>> >> > something didn't complete correctly. However that is is little odd
>> >> > since it works fine if I just take out the /boot partition and let it
>> >> > install to /.
>> >> >
>> >> > I will try another install and check this before I reboot. If it is
>> >> > wrong, I will try to edit and see what the results are.
>> >> >
>> >> > Thanks for pointing that out. I did dig through that a bit, but
>> >> > skipped right over that one.
>> >> >
>> >> > Bjorn
>> >> >
>> >> >
>> >> > On Tue, May 27, 2008 at 12:53 AM, Eymen Alyaz <alyaz at ins.uni-bonn.de> wrote:
>> >> >> Bjorn Meyer schrieb:
>> >> >>> ...
>> >> >>> Here are the 2 kernel entries that it creates.
>> >> >>>
>> >> >>> title           Debian GNU/Linux, kernel 2.6.18-6-686
>> >> >>> root            (hd0,0)
>> >> >>> kernel          /vmlinuz-2.6.18-6-686 root=/dev/hda5 ro
>> >> >>> initrd          /initrd.img-2.6.18-6-686
>> >> >>
>> >> >> according to your parition layout, the kernel line should look like:
>> >> >> kernel /vmlinuz-2.6.18-6-686 root=/dev/hda2, not /dev/hda5.
>> >> >> because you partitioned with:
>> >> >>
>> >> >> (look at your first mail)
>> >> >> disk_config disk1
>> >> >> primary     /boot     100     defaults     ;boot -j ext3
>> >> >> primary     /         1024    defaults     ;-c -j ext3
>> >> >> #logical     /         1024    defaults     ;-c -j ext3
>> >> >> logical     swap      500
>> >> >>
>> >> I tried again, and the menu list is being set up correctly. With the
>> >> above config, it is being set to hda2.
>> >> If I set / to be logical it is being set to hda5.
>> >> My apologies, I may have pasted this incorrectly.
>> >>
>> >> >> are you sure grub is properly installed?
>> >> >>
>> >> >> Regards,
>> >> >> Eymen Alyaz
>> >> >>
>> >> >>
>> >> >
>> >
>> > Maybe grub setup script did not run properly. Check that a
>> > file /srv/fai/config/files/boot/grub/menu.lst/postinst
>> > contains something like the following:
>> > ########################################
>> > #! /bin/bash
>> >
>> > error=0 ; trap "error=$((error|1))" ERR
>> >
>> > set -a
>> >
>> > # during softupdate use this file
>> > [ -r $target/var/log/fai/disk_var.sh ] && .
>> > $target/var/log/fai/disk_var.sh
>> >
>> > # if class NOMBR is defined, write boot loader into root partition, not
>> > into mbr
>> > ifclass NOMBR && BOOT_DEVICE=$BOOT_PARTITION
>> >
>> > grub-install --no-floppy --root-directory=$target $BOOT_DEVICE
>> > GROOT=$(device2grub $BOOT_PARTITION)
>> > perl -pi -e 's/#(\w+)#/$ENV{$1}/' $2
>> > $ROOTCMD /usr/sbin/update-grub
>> > echo "Grub installed on $BOOT_DEVICE on $GROOT"
>> >
>> > exit $error
>> > ###################################################
>> > and its permissions are set to executable. I had similar problems
>> > booting into the new system, when I accidentally deleted the file.
>> >
>> >
>> > Alex.
>> >
>> >
>> >
>
>