* Nico Dietrich <[EMAIL PROTECTED]> [2004-05-13 20:22]:By hand. Sorry, this installation report was written in two steps; after aborting the installation the first time, i installed fedora again, so i included the fedora generated fstab.
LABEL=/ / ext3 defaults 1 1 LABEL=/home /home ext3 defaults 1 2
How did you get those LABELs? Did you do that by hand after d-i?
the debian fstab is: # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 /dev/hda5 none swap sw 0 0 /dev/hda7 /mnt/share vfat umask=0003,gid=users 0 2 /dev/hda8 / ext3 defaults,errors=remount-ro 0 1 /dev/hda6 /home ext3 defaults 0 2 /dev/hdc /mnt/cdrom iso9660 ro,user,noauto 0 0
Everything worked fine until the installer tried to create the ext3 file
system after formating the root partition. The error message was: Filesystem has incompatible feature enabled. The first time i aborted the installation, because i thought i cannot use the root-partition. I
Can you show the output of: tune2fs -l /dev/hda1 (or whatever your root partition is)
karl:~# tune2fs -l /dev/hda8 tune2fs 1.35 (28-Feb-2004) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: b9fc2b59-6a1c-45aa-8740-4eb7f78aef42 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal filetype needs_recovery sparse_super Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 1026144 Block count: 2048752 Reserved block count: 102437 Free blocks: 1472895 Free inodes: 929107 First block: 0 Block size: 4096 Fragment size: 4096 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 16288 Inode blocks per group: 509 Last mount time: Fri May 14 00:14:36 2004 Last write time: Fri May 14 00:14:36 2004 Mount count: 8 Maximum mount count: 30 Last checked: Thu Jan 1 01:00:00 1970 Check interval: 0 (<none>) Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal inode: 8 First orphan inode: 602682 Journal backup: inode blocks
yes - i put the bootable flag. the root partition is an extended partition, /dev/hda8.
When you marked your root partition in d-i, did you specify any special filesystem features?
wasn't there something that lilo can only handle boot partition in the first x GB of the disk...? maybe that's the reason for the error message.
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
