Bug#172244: Problem using ext3
Package: installation-reports
Debian-installer-version:
http://people.debian.org/~tfheen/d-i/images/2002-12-07/cvs/net-1440.img
5839ab97f1373a7f6789dcbf733257d2 net-1440.img
uname -a: N/A
Install Date: about Sun Dec 8 16:00:00 GMT 2002
Method: Boot off floppy with above image. Network install from
www.mirror.ac.uk. No proxy.
Machine: PC, 3 IDE HDDs, no CD.
Processor: PIII/600MHz
Memory: 256MB
Root Device: IDE
Root Size/partition table:
/dev/hda: 5G total
/dev/hda1: target /
/dev/hda5: target swap
/dev/hda5: target /usr
/dev/hda6: target /var
/dev/hda7: target /tmp
/dev/hdc: 17G total
/dev/hdc1: N/A (previously used for playing with debootstrap)
/dev/hdc6: N/A (currently unused swap)
/dev/hdc7: /home (ext3) (will be manually grafted onto new install)
/dev/hdd: 120G total
/dev/hdd1: data (ext3) (will be manually grafted onto new install)
Output of lspci:
Hopefully N/A.
Base System Installation Checklist:
Initial boot worked: [O]
Configure network HW: [O]
Config network: [O]
Detect CD: [ ]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [E]
Install base system: [O]
Install boot loader: [O]
Reboot: [O]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
My system has 2 realteks. I wasn't phased by needing to manually select the
module, but it will be nice when it works perfectly.
'Load installer modules' would be confusing to a newbie. IMO, this should
be made simpler to understand - maybe even removed. I didn't need any
modules anyway. :)
I was able to partition my drives to ext3 and mount them, but what I failed
to realise for a bit was that they weren't actually mounted since ext3
wasn't in the kernel and wasn't there as a module. HOWEVER, the
installation still proceeded to install without having the devices mounted!
It obviously ended up running out of space. In case this ever crops up
again, the error I ended up seeing was something like: "[: Missing ']' on
line 72." when trying to install LILO, but the root cause was that it was
trying to install to the ramdisk and was running out of space.
Another thing is that I didn't need to look for a cdrom, but it kept making
that the default option, even when I was up to the later stages of the
install. Otherwise the default options were nicely done.
Anyway, it has worked with ext2 now, and it's just booted nicely into my new
install. :) You forgot to tell me to take the floppy out though! :)
Best regards, and thanks,
Pete
Reply to: