I was not sure what to label this. It is not really a bug, but perhaps a documentation issue. I was following the documentation for the 1.4_rc1 install and ran into a small problem. I was up to the step where you mount /dev/hd1 (the /boot partition). I kept getting an error. The error was unable to mount FS, wrong fs type, bad superblock or too many mounted filesystems (not the exact error but close to it) I could not immediately figure out what the problem was. I had formatted /hde1 as ext2, and the rest of my partitions as XFS. This is how I had my system with 1.0 and 1.2 I know that mixing those fs doesn't hurt. I figured maybe mount was expecting my hd1 to be XFS like the rest of the partitions so I mount /dev/hd1 /mnt/gentoo/boot -t ext2 That got it working, and I was able to continue with the install with no problems. I think maybe the -t option should be added to the documentation. Right now it just mentions mounting reiserfs with the notail.
i noticed you say you did 'mount /dev/hd1' ... can you confirm this is a typo ? as for that error message, you should have not gotten it if you set up the partition type via fdisk/cfdisk correctly and then written/reread the partition table ... could you verify that aspect too ?
It's not a typeo. I just meant the stage where you mount your /dev/hd for me it is /dev/hde1. The first hard drive attached to a promise controller. I setup everything in fdisk, and exited with w to have it write the partition table. My scheme looks like this /dev/hde1 /boot (a) ext2 /dev/hde2 swap /dev/hde3 / (root) xfs /dev/hde4 extended /dev/hde5 /var xfs /dev/hde6 /usr xfs /dev/hde7 /home xfs After using fdisk I went and created the filesystems. (I been using fdisk for years. I know how to use it) mkswap mke2fs /dev/hde1 mkfs.xfs -f -d agcount= -l size=32 /dev/hde3 mkfs.xfs -f -d agcount= -l size=32 /dev/hde5 mkfs.xfs -f -d agcount= -l size=32 /dev/hde6 mkfs.xfs -f -d agcount= -l size=32 /dev/hde7 The agcount= is different for each partition depending on it's size. Off hand I don't remember the size I set for each. This is the same scheme I used when I had Gentoo 1.2 I never got any error messages while going through that install. When I get to the directory creation step, and mounting is that this minor annoyance popped up. mkdir /mnt/gentoo mount /dev/hde3 /mnt/gentoo mkdir /mnt/gentoo/boot mount /dev/hde1 /mnt/gentoo/boot This is the step where the error would pop up. Unable to mount FS. Wrong FS type, bad superblock or too many FS mounted. If I specify that hde1 is ext2 I don't get the error. mount /dev/hde1 /mnt/gentoo/boot -t ext2 It just zips along like it should. I am just trying to point out that if I am gettig the error perhaps others are as well.
Just to add to this. I am installing now on a second box, and when I get to this point it has the same error. Here is a step by step of how I am going through fdisk. This machine also has a promise card so my hd is hde fdisk /dev/hde n p 1 I set the size n p 2 I set the size n p 3 I set the size n e 4 I set it to use remaining space n I set the size n I set the size n I set the size a I set partition hde1 as active t I switch hde2 partition type to 82 w exit and write the partition table now I go through the steps to create the filesystems mkswap /dev/hde2 mke2fs /dev/hde1 mkfs.xfs -f -d agcount= -l size=32 /dev/hde3 mkfs.xfs -f -d agcount= -l size=32 /dev/hde5 mkfs.xfs -f -d agcount= -l size=32 /dev/hde6 mkfs.xfs -f -d agcount= -l size=32 /dev/hde7 mkdir /mnt/gentoo mount /dev/hde3 /mnt/gentoo mkdir /mnt/gentoo/boot mount /dev/hde1 /mnt/gentoo/boot I get that error again here. Unable to mount FS. Wrong FS type, bad superblock or too many FS mounted. Again if I specify that hde1 is ext2 the install does not return an error. It mounts the partition. Strange no? Do you think this could be a bug with Promise controllers? This has now happened on 2 of my boxes both with promise pdc202xx controllers.
i wasnt trying to imply that you have a general lack of knowledge, i just have to step many people who submit bugs through the basic steps to make sure they didnt miss something ;) as for the warning, there should be a note just to cover another little eventuality. it really *shouldnt* happen (its never happened to me), but it does happen and the user may not be a factor i say we just wait till the docs-team adds in the little note and call this a closed issue ;)
Did I hear docs team? ;-) I added it in, and it is in CVS. Cheers, //ZhEN
*** Bug 8632 has been marked as a duplicate of this bug. ***
Looks like the changes are now live. Thanks. Oh, and sorry about the dup.
Moving these so we can remove the "Install CD" component from "Gentoo Linux". I apologize to everyone for this spam, but according to the bugzilla developers, this is the only reasonable way to do this.
