I don't agree, this is a bug either in the base version of e2fsprogs used or in the Ubuntu patches. To prove this I built the latest e2fsprogs-1.41.9.tar.gz from SourceForge and ran
So the latest official tools have no difficulty in identifying the partition and type. Not only that but the line in /etc/fstab has the FS type fully specified so no excuses for not identifying it.
Re. your suggestion to wipe and reformat - I stated earlier that I used gparted to create this partition so that won't help. _All_ other major Linux distros (suse, fedora, gentoo, mandriva, slackware) recognize this partition - that must say something.
This is a real killer bug for me. If Karmic ships with this bug then I will have to jump ships.
I don't agree, this is a bug either in the base version of e2fsprogs used or in the Ubuntu patches. To prove this I built the latest e2fsprogs- 1.41.9. tar.gz from SourceForge and ran
sudo /home/lvr/ e2fs/sbin/ blkid -c /dev/null /dev/sdb1 0cef-4d78- acd1-9a01ebd878 33" TYPE="ext2"
/dev/sdb1: LABEL="boot" UUID="41584c58-
So the latest official tools have no difficulty in identifying the partition and type. Not only that but the line in /etc/fstab has the FS type fully specified so no excuses for not identifying it.
Re. your suggestion to wipe and reformat - I stated earlier that I used gparted to create this partition so that won't help. _All_ other major Linux distros (suse, fedora, gentoo, mandriva, slackware) recognize this partition - that must say something.
This is a real killer bug for me. If Karmic ships with this bug then I will have to jump ships.