Hello all, not quite sure if this belongs on this list, so let me know if it doesn't! I downloaded 4.10-RELEASE last night and had a go at installing it this morning. I wanted to put it onto the same disk as 5.2.1-RELEASE and repartitioned the drive ad1s1 - 5.2.1 ad1s2 - 4.10 ad1s3 - FreeBSD but nothing on it ad1s4 - ufs filesystem however disklabel in the install program got it wrong and (i think) swapped the disklabels for the first and second slices around. The result was that 4.10 booted up fine, but appeared to have the wrong disklabel (the ones that should have been on slice 1) and I lost my 5.2.1 install (could not boot and could not mount the drives, with mount complaining of an invalid super block and the bootloader complaining about no ufs filesystem). Luckilly i managed to overwrite the disklabels by using the install program again (this time the 5.2.1 installation cd) and get all my data back, but lost the 4.10 installation. In summary im not sure what all this means or what to do about it, but there if almost definately a bug somewhere (I'm pretty sure I didn't do anything wrong) so be careful! - Lachlan -- James Lachlan Kanaley phone: (02) 9517 3209 mobile: 0427 368 345 email: kanaley@student.usyd.edu.au web: http://users.tpg.com.au/adslclfu
On Fri, 28 May 2004, J Lachlan Kanaley wrote:> Hello all, not quite sure if this belongs on this list, so let me > know if it doesn't! > > I downloaded 4.10-RELEASE last night and had a go at installing it > this morning. I wanted to put it onto the same disk as > 5.2.1-RELEASE and repartitioned the drive > ad1s1 - 5.2.1 > ad1s2 - 4.10 > ad1s3 - FreeBSD but nothing on it > ad1s4 - ufs filesystemInteresting layout :)> however disklabel in the install program got it wrong and (i think) > swapped the disklabels for the first and second slices around. The > result was that 4.10 booted up fine, but appeared to have the wrong > disklabel (the ones that should have been on slice 1) and I lost my > 5.2.1 install (could not boot and could not mount the drives, with > mount complaining of an invalid super block and the bootloader > complaining about no ufs filesystem).I wonder if this was more due to installing a non-UFS2 loader that thought it should be looking at the UFS2 (5.2) partition. 5.x loaders will work fine for 4.x systems, but not the other way around. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org