Re: Unsucessful with 5.0-CURRENT Installation on a 120G IDE HDD
Hmm, OK. Let me rephrase it all. I have a 120G IDE disk, which is under LBA mode. It is the second disk on my system. I have been using it with my old (julyish) -current for a while now as a backup disk thingy. My disk layout: ad1s1: 8997MB FreeBSD slice ad1s3: 50995MB FreeBSD slice ad1s2: 54478MB FAT32 slice (Note the order) This is how Sysinstall's fdisk reports it in 5.0-CURRENT-20021028. The sizes are displayed correctly here, but when I try labeling the disk through sysinstall's Configure-Label, It shows: Disk: ad3 Partition name: ad3s1 Free: 0 blocks (0MB) Disk: ad3 Partition name: ad3s3 Free: 102110549 blocks (49858MB) Part Mount Size Newfs Part Mount Size Newfs - - - - ad3s1anone128MB * ad3s2 none 54478MB DOS ad3s1bnone 1008MB * ad3s1enone256MB * ad3s1fnone256MB * ad3s1gnone 7348MB * ad3s3anone128MB * -- Notice the sizes ad3s3bnone 1008MB * -- Note, ad3 should only show up as one partition, which, is 50995MB in size. The size 1000MB and 128MB DOES NOT MAKE SENSE AT ALL. Also NOTE, that the DOS partition shows has the right size, without any problems. This problem does not occur on my older -current, which, was before GEOM or even KSE III was integrated. On IRC, I have been told that it could be that geom_mbr is somehow messed up, but I cant say anything on that. FWIW, I have used up around 12G on the FreeBSD (ad1s3) slice, and around 20G on my DOS slice. The data got there, because I sliced the disk on my older -current, but I dont think that has got anything to do with it. FDISK Data: Script started on Fri Nov 1 05:04:33 2002 vmnet-current:1m/usr/src/sys/geomm# fdisk ad3 *** Working on device /dev/ad3 *** parameters extracted from in-core disklabel are: cylinders=232581 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=232581 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 18426492 (8997 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA)) start 122865120, size 111571425 (54478 Meg), flag 0 beg: cyl 1023/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 18426555, size 104438565 (50995 Meg), flag 80 (active) beg: cyl 1023/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 4 is: UNUSED Script done on Fri Nov 1 05:04:37 2002 When I go to Configure-Fdisk in sysinstall, it shows this WARNING message, which, I dont get in my old NON-GEOM system. If there is anymore data you would like, then please do not hesitate to contact me. Cheers. -- Hiten Pandya [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] On Fri, Nov 01, 2002 at 05:35:21PM -0800, walt wrote the words in effect of: Hiten Pandya wrote: Hi there. I tried installing the 5.0-CURRENT-20021028-JPSNAP ISO today, on my 120G harddrive, which is the second one on the system. Sysinstall failed to get the right geometry of the disk, even though the BIOS was in LBA mode. My 50G FreeBSD partition (ad1s3) as two partitions, 1000MB and a 128MB. Sorry, I'm not understanding that sentence. Is there a typographical error in there somewhere, perhaps? 1000MB + 128MB 50GB The DOS partition (ad1s2) on the harddrive was just right, and nothing wrong it, but only the FreeBSD partitions messed up. Sorry, I'm still confused. You have two different FBSD partitions on the same disk (s3 and s1)? I made a 8G partition on the front of the disk (ad1s1), in which I was planning to install FreeBSD. Now, I am not sure what the real cause is, i.e. why are we not allowed to install on an 8G partition on a 120G disk? No reason. It should work. Is the install failing at some point with error messages? Did the install finish but now you can't boot the new system? It could be that I am doing something very wrong, but I would like to get to the bottom of this, as I lost about 15G worth of data, I'm confused again. Data on the FreeBSD partition? Which FBSD partition? How did the data get there and in what way is it lost now, exactly? i.e. fdisk still shows that the partition is there, but fsck_ffs is not proceeding. You mean when you try to boot the 8GB partition, or the 50GB partition? Is fsck complaining about something? What is it saying? Please
Re: Unsucessful with 5.0-CURRENT Installation on a 120G IDE HDD
Hiten Pandya wrote: Hmm, OK. Let me rephrase it all. I have a 120G IDE disk, which is under LBA mode. It is the second disk on my system. I have been using it with my old (julyish) -current for a while now as a backup disk thingy. My disk layout: ad1s1: 8997MB FreeBSD slice ad1s3: 50995MB FreeBSD slice ad1s2: 54478MB FAT32 slice Here you are discussing ad1, which should (I think) be the slave drive on the first IDE controller. This is how Sysinstall's fdisk reports it in 5.0-CURRENT-20021028. The sizes are displayed correctly here, but when I try labeling the disk through sysinstall's Configure-Label, It shows: Disk: ad3 Partition name: ad3s1 Free: 0 blocks (0MB) Disk: ad3 Partition name: ad3s3 Free: 102110549 blocks (49858MB) Here you are discussing ad3, which should be the slave drive on the *second* IDE controller. Are you intending to discuss two different physical disks here? I'm still a bit confused. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unsucessful with 5.0-CURRENT Installation on a 120G IDE HDD
On Sat, Nov 02, 2002 at 10:38:33AM -0800, walt wrote the words in effect of: Hiten Pandya wrote: Hmm, OK. Let me rephrase it all. I have a 120G IDE disk, which is under LBA mode. It is the second disk on my system. I have been using it with my old (julyish) -current for a while now as a backup disk thingy. My disk layout: ad1s1: 8997MB FreeBSD slice ad1s3: 50995MB FreeBSD slice ad1s2: 54478MB FAT32 slice Here you are discussing ad1, which should (I think) be the slave drive on the first IDE controller. This is how Sysinstall's fdisk reports it in 5.0-CURRENT-20021028. The sizes are displayed correctly here, but when I try labeling the disk through sysinstall's Configure-Label, It shows: Disk: ad3 Partition name: ad3s1 Free: 0 blocks (0MB) Disk: ad3 Partition name: ad3s3 Free: 102110549 blocks (49858MB) Here you are discussing ad3, which should be the slave drive on the *second* IDE controller. Are you intending to discuss two different physical disks here? I'm still Oops, change that ad3 into ad1. -- Hiten Pandya [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unsucessful with 5.0-CURRENT Installation on a 120G IDE HDD
Hiten Pandya wrote: On Sat, Nov 02, 2002 at 10:38:33AM -0800, walt wrote the words in effect of: Hiten Pandya wrote: Hmm, OK. Let me rephrase it all. I have a 120G IDE disk, which is under LBA mode. It is the second disk on my system. I have been using it with my old (julyish) -current for a while now as a backup disk thingy. My disk layout: ad1s1: 8997MB FreeBSD slice ad1s3: 50995MB FreeBSD slice ad1s2: 54478MB FAT32 slice Here you are discussing ad1, which should (I think) be the slave drive on the first IDE controller. This is how Sysinstall's fdisk reports it in 5.0-CURRENT-20021028. The sizes are displayed correctly here, but when I try labeling the disk through sysinstall's Configure-Label, It shows: Disk: ad3 Partition name: ad3s1 Free: 0 blocks (0MB) Disk: ad3 Partition name: ad3s3 Free: 102110549 blocks (49858MB) Here you are discussing ad3, which should be the slave drive on the *second* IDE controller. Are you intending to discuss two different physical disks here? I'm still Oops, change that ad3 into ad1. Okay. Well, I see that just today sysinstall/label.c was updated to correct an error. I have no idea if that may be your problem, but errors do creep in regularly into -CURRENT, so it's possible. My gut feeling is that your files are still there ready to be used but probably not with the system you are using now. I would download a -STABLE installation floppy from the FBSD ftp site and see if you can use that disklable editor to examine the disk. If the disklabel looks correct then you can proceed to install a -STABLE system on that disk using the *existing* label, and your data should be intact. If the disklabel still looks bad then you have a bigger problem. You really need to save every label somewhere and restore it later if it gets trashed. I just use a pencil and paper and write it all down and tape the paper to the computer--very primitive but it's saved my backside more than once ;-) When fooling with -CURRENT you need to be ready for such disasters, and often all it takes is a pencil and paper and five minutes of preparation. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unsucessful with 5.0-CURRENT Installation on a 120G IDE HDD
On Sat, Nov 02, 2002 at 02:42:41PM -0800, walt wrote the words in effect of: Okay. Well, I see that just today sysinstall/label.c was updated to correct an error. I have no idea if that may be your problem, but errors do creep in regularly into -CURRENT, so it's possible. My gut feeling is that your files are still there ready to be used but probably not with the system you are using now. I would download a -STABLE installation floppy from the FBSD ftp site and see if you can use that disklable editor to examine the disk. If the disklabel looks correct then you can proceed to install a -STABLE system on that disk using the *existing* label, and your data should be intact. If the disklabel still looks bad then you have a bigger problem. You really need to save every label somewhere and restore it later if it gets trashed. I just use a pencil and paper and write it all down and tape the paper to the computer--very primitive but it's saved my backside more than once ;-) When fooling with -CURRENT you need to be ready for such disasters, and often all it takes is a pencil and paper and five minutes of preparation. Yup. Anyway, no one to blame, because I was aware it -current was gonna punish me one day anyway, so. no regrets. I will try your method out anyway. Lets see how it goes. :) Thanks again. -- Hiten Pandya [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Unsucessful with 5.0-CURRENT Installation on a 120G IDE HDD
Hi there. I tried installing the 5.0-CURRENT-20021028-JPSNAP ISO today, on my 120G harddrive, which is the second one on the system. Sysinstall failed to get the right geometry of the disk, even though the BIOS was in LBA mode. My 50G FreeBSD partition (ad1s3) as two partitions, 1000MB and a 128MB. The DOS partition (ad1s2) on the harddrive was just right, and nothing wrong it, but only the FreeBSD partitions messed up. I made a 8G partition on the front of the disk (ad1s1), in which I was planning to install FreeBSD. Now, I am not sure what the real cause is, i.e. why are we not allowed to install on an 8G partition on a 120G disk? It could be that I am doing something very wrong, but I would like to get to the bottom of this, as I lost about 15G worth of data, i.e. fdisk still shows that the partition is there, but fsck_ffs is not proceeding. This could be because of GEOM or something, but I am not sure, as I cannot try a non-GEOM sysinstall anyway. Also, is there a way I can get that 15G worth of data back, somehow, or do I just have to say bye-bye to it? All help will be appreciated. Cheers. -- Hiten [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unsucessful with 5.0-CURRENT Installation on a 120G IDE HDD
On Fri, Nov 01, 2002 at 08:56:44PM +, Hiten Pandya wrote the words in effect of: Hi there. I tried installing the 5.0-CURRENT-20021028-JPSNAP ISO today, on my 120G harddrive, which is the second one on the system. Sysinstall failed to get the right geometry of the disk, even though the BIOS was in LBA mode. My 50G FreeBSD partition (ad1s3) as two partitions, 1000MB and a 128MB. The DOS partition (ad1s2) on the harddrive was just right, and nothing wrong it, but only the FreeBSD partitions messed up. I made a 8G partition on the front of the disk (ad1s1), in which I was planning to install FreeBSD. Now, I am not sure what the real cause is, i.e. why are we not allowed to install on an 8G partition on a 120G disk? It could be that I am doing something very wrong, but I would like to get to the bottom of this, as I lost about 15G worth of data, i.e. fdisk still shows that the partition is there, but fsck_ffs is not proceeding. This could be because of GEOM or something, but I am not sure, as I cannot try a non-GEOM sysinstall anyway. Also, is there a way I can get that 15G worth of data back, somehow, or do I just have to say bye-bye to it? All help will be appreciated. Cheers. Please let me know what type of information is needed for debugging this problem. Cheers. -- Hiten Pandya [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unsucessful with 5.0-CURRENT Installation on a 120G IDE HDD
Hiten Pandya wrote: Hi there. I tried installing the 5.0-CURRENT-20021028-JPSNAP ISO today, on my 120G harddrive, which is the second one on the system. Sysinstall failed to get the right geometry of the disk, even though the BIOS was in LBA mode. My 50G FreeBSD partition (ad1s3) as two partitions, 1000MB and a 128MB. Sorry, I'm not understanding that sentence. Is there a typographical error in there somewhere, perhaps? 1000MB + 128MB 50GB The DOS partition (ad1s2) on the harddrive was just right, and nothing wrong it, but only the FreeBSD partitions messed up. Sorry, I'm still confused. You have two different FBSD partitions on the same disk (s3 and s1)? I made a 8G partition on the front of the disk (ad1s1), in which I was planning to install FreeBSD. Now, I am not sure what the real cause is, i.e. why are we not allowed to install on an 8G partition on a 120G disk? No reason. It should work. Is the install failing at some point with error messages? Did the install finish but now you can't boot the new system? It could be that I am doing something very wrong, but I would like to get to the bottom of this, as I lost about 15G worth of data, I'm confused again. Data on the FreeBSD partition? Which FBSD partition? How did the data get there and in what way is it lost now, exactly? i.e. fdisk still shows that the partition is there, but fsck_ffs is not proceeding. You mean when you try to boot the 8GB partition, or the 50GB partition? Is fsck complaining about something? What is it saying? Please be very specific about error messages. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
