Package: e2fsprogs Version: 1.37-2sarge1 Severity: normal
-- System Information: Debian Release: 3.1 Architecture: i386 (i586) Kernel: Linux 2.4.27-2-386 Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Versions of packages e2fsprogs depends on: ii e2fslibs 1.37-2sarge1 ext2 filesystem libraries ii libblkid1 1.37-2sarge1 block device id library ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libcomerr2 1.37-2sarge1 common error description library ii libss2 1.37-2sarge1 command-line interface parsing lib ii libuuid1 1.37-2sarge1 universally unique id library -- no debconf information Machine-type: Compaq Proliant 1500 P166 (dual P166, but kernel not SMP yet) Controller type: SCSI Hardware RAID: SMART-2/P RAID Array Controller (/dev/ida - module cpqarray) Hard drives: 5 x 18.2 GB SCSI-UW in a RAID 5 array (transparently accessed as a single logical disk) /boot is a normal ext3 partition everything else (including root) exists on lvm2 volumes. Kernel: kernel-image-2.4.27-2-386 Default initrd from netinst cd The problem: a nice little segfault in the initrd startup scripts The source: /usr/lib/e2initrd_helper (/bin/e2initrd_helper in the initrd) Details: I have mucked about with echo's in the initrd scripts and see the following: magical initrd stuff call e2fsprogs script e2fsprogs calls initrd.ext3-add-journal which executes roottype=`/bin/e2initrd_helper -r /dev2/root2` which segfaults It doesn't seem to do anything bad to the system. Commenting out the roottype= line removes the segfault, but that's not a solution for what is probably the larger number of users out there. I'll send other information if you ask. Cheers, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
