I used ext2 for /boot and /tmp. the Ubuntu installer did not like this. Also, I previously set a partition for NTFS, which the installer didn't like. When I clicked 'format' it formatted every selected partion to ext3, if I mkfs.ext2 myself, then it says there are unresolved errors in the ext2 partition (which turned out to work just fine). I just left my NTFS partition unformatted and unmounted (for dual boot sometime later)
-Chris On 6/15/06, Christopher Hamilton <[EMAIL PROTECTED]> wrote: > > That was my assumption, however it was late at night here in Singapore so > I posponed until the morning. > > I repartitioned the disk, this time completely -- the only thing I saved > previously: my IBM recovery 3.4gb partition (it didn't end on a cylendar > boundry, but this sholudn't be a problem, correct?) I then rebooted the > computer, just a fall back to old partitioning rules: fdisk, reboot, format, > install. Everything worked beautifully > > Thanks! > -Chris > > > > > > On 6/15/06, Jonathan Carter <[EMAIL PROTECTED]> wrote: > > > > Could the: > > "Error reading inode xxxx" > > messages be caused by disk failure? > > > > Perhaps ubiquity doesn't yet have proper exceptions for disk failures? > > > > -- > > installer crashed > > https://launchpad.net/bugs/49730 > > > > > > -- > > ------------------------------------- > Christopher Hamilton > Lehigh University > Undergraduate Computer Engineering > IMRC Webteam > LTS A&S Tech > WIRED Consultant > Internship: Counter March Systems > Contact: 267-210-4176 > -- ------------------------------------- Christopher Hamilton Lehigh University Undergraduate Computer Engineering IMRC Webteam LTS A&S Tech WIRED Consultant Internship: Counter March Systems Contact: 267-210-4176 -- installer crashed https://launchpad.net/bugs/49730 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
