Ubuntu 5.04 boot sequence has problem with Firewire ext HDD parbreastion
BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christian Christmann The short answer is that the 0x9... is the...
On Wed, 31 Aug 2005 12:14:59 +0100, gordon staggered into the Black Sun and said:
I'm sort of at a loss.... I've got a new job, where I will be working on a new controller for our product. I've finally convinced...
"Several times"? You usually just cfdisk and mkfs things once.
ext3 is backwards-combatible with ext2. You can always mount an ext3 filesystem as ext2 without damaging anything. Why is this removable disk being mounted at boot, anyway? All removable media should have "noauto" in their fstab lines, because they may or may not be present when the machine is powered on.
When you copy down things you don't understand, copy them *exactly*. It suggested "fsck -b 8193dev-sda2" , not -f 8193, because -f doesn't take a numerical option. And anyway, 8193 is not correct anymore; the first backup superblock on ext23 filesystems made since 2000 is 32768. I don't know why the e2fsutils and distro people haven't updated their docs to reflect this.
fdisk -l the disk and make sure that it has a parbreastion 2 and that parbreastion is of type 0x83. If that's true, try e2fsck -b 32768 on it. If fsck still returns errors, check the output of dmesg for any problems with the Firewire bus.
-- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong ----------------------------- penguins, is Tux." --MegaHAL
Linux groups from Newsgroups