guran <[EMAIL PROTECTED]> writes: > Hi > > VERSION: (rsync ftp.sunet.se) > Mandrake Linux Cooker-i586 20011208 18:54 > > This is from stage1.log:
Finally this "stage1.log" is useful :-)). > * guessing type of /dev/hda1 > * guessing type of /dev/hda5 > * guessing type of /dev/hda6 > * guessing type of /dev/hda7 > * guessing type of /dev/hda8 > * guessing type of /dev/hda9 > * mounting /dev/hda9 on /tmp/hdimage as type ext2 > * Total Memory: 256 Mbytes > * trying to load /tmp/image/Mandrake/base/mdkinst_stage2.bz2 as a ramdisk > * mounting /dev/ram3 on /tmp/stage2 as type ext2 Yes we don't have ext3 driver in stage1, but it should not be needed, normally. > But this is from report.bug (earlier than stage1.log): Euh ? report.bug should contain stage1.log. > <6>Journalled Block Device driver loaded > <6>kjournald starting. Commit interval 5 seconds > <6>EXT3 FS 2.4-0.9.15, 06 Nov 2001 on ide0(3,8), internal journal > <6>EXT3-fs: mounted filesystem with ordered data mode. > <6>kjournald starting. Commit interval 5 seconds > <6>EXT3 FS 2.4-0.9.15, 06 Nov 2001 on ide0(3,6), internal journal > <6>EXT3-fs: mounted filesystem with ordered data mode. > <6>kjournald starting. Commit interval 5 seconds > <6>EXT3 FS 2.4-0.9.15, 06 Nov 2001 on ide0(3,7), internal journal > <6>EXT3-fs: mounted filesystem with ordered data mode. > ... > > Here is the report: > * err, fstab and partition table do not agree for hda9 type: ext3 vs ext2 Pixel, could this error come from the fact that hda9 was mounted ext2 during stage1, although it's actually ext3? It would surprise me but..? -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
