Re: Dangerous file system / disk problem
On Tuesday 08 June 2004 05:20, Ben Paley wrote: On Monday 07 June 2004 16:44, Malcolm Kay wrote: Notice the size recorded for this slice is zero. If the cylinders=155061 heads=16 sectors/track=63 is somewhere near the reasonable possible geometry description then virtually the entire disk has been allocated to the FreeBSD slice. Yes it is, all of it (or, all of it that I could withot going 'dangerously dedicated'). I have never had any intention of putting Windows on this disk. I think W98 just assumed it 'cos it was the primary master. I now have a clearer impression of the situation. I had erroneously understood windows was actually running from that slice and that it must have really been bigger than it appeared. But seriously, does any of this suggest a course of action to you? I'm planning to try the set sysid to 0 plan... what if that doesn't work? Sounds like an excellent idea. Perhaps windows is seeing the slice as a fs it knows about but finds it unformatted, so is offering to do that for you. So maybe setting sysid to zero (which I think registers as an undefined slice) will stop windows making the offer. Whatever else I can't see how this would make the situation worse. Good luck, Malcolm ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dangerous file system / disk problem
On Tuesday 08 June 2004 10:38, Malcolm Kay wrote: On Tuesday 08 June 2004 05:20, Ben Paley wrote: But seriously, does any of this suggest a course of action to you? I'm planning to try the set sysid to 0 plan... what if that doesn't work? Sounds like an excellent idea. Perhaps windows is seeing the slice as a fs it knows about but finds it unformatted, so is offering to do that for you. So maybe setting sysid to zero (which I think registers as an undefined slice) will stop windows making the offer. Whatever else I can't see how this would make the situation worse. This is very comforting - I shall give it a go and let you know how it comes out. Cheers, Ben ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dangerous file system / disk problem
On Sun, 6 Jun 2004 19:31:48 +0100, Ben Paley wrote: ... *** Working on device /dev/ad1 *** parameters extracted from in-core disklabel are: cylinders=155061 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=155061 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 156296322 (76316 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 14 (0x0e),(Primary 'big' DOS (= 32MB, LBA)) start 156296385, size 0 (0 Meg), flag 0 beg: cyl 1022/ head 0/ sector 1; end: cyl 1022/ head 254/ sector 63 The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED ... I don't really understand this, frankly: it certainly gives the right partition type code for the main partition, but I'm not sure of the relevance of the other stuff... does it look ok to you? Or is this partition 2 where the problem is? Partition Magic in Windows sees only one partition on that disk. The slice editor in sysinstall shows this for ad1: ... 5.2-CURRENT. But BSD sees everything ok, it's Windows that's having a problem. I don't feel confident making any changes in Windows, however, because it seems as though my only option there would be to format the partition! Which, from a Windows point of view, would certainly be a solution of sorts... Partition 2 (sysid 14, start 156296385) is bogus. I don't have a clue as to how it might have been created. If the beginning/end c/h/s addresses are to be believed, it overlaps partition 1. I would not dare to format it. Instead, I would use the fdisk -u ad1 command to delete it and hope that it never comes back. If you do this, it would be a good idea to back up your FreeBSD system first, especially since you are probably not very familiar with the fdisk -u command and might possibly make a fatal mistake. Dan Strick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dangerous file system / disk problem
On Monday 07 June 2004 11:17, Dan Strick wrote: Partition 2 (sysid 14, start 156296385) is bogus. I don't have a clue as to how it might have been created. I *guess* it was the W98 installer - if you boot into DOS and invoke setup.exe it's fairly polite, but if you boot from the cdrom, which is what I did, it starts to prepare your hard disk without asking... aagh! I'm pretty sure this is when things began to go wrong. If the beginning/end c/h/s addresses are to be believed, it overlaps partition 1. I would not dare to format it. Instead, I would use the fdisk -u ad1 command to delete it and hope that it never comes back. If you do this, it would be a good idea to back up your FreeBSD system first, especially since you are probably not very familiar with the fdisk -u command and might possibly make a fatal mistake. This is very scary, but thanks for the advice. I had some more advice (not sure if it went to the list or not) to try setting the second partition as unused (sysid=0), so I might try that first to see whether I can avoid risking destroying everything and making my family hate me. Thanks ever so much for your advice, I'll let you know what happens, as soon as I have enough time to give this the attention it requires. Thanks a lot, Ben ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dangerous file system / disk problem
On Mon, 7 Jun 2004 13:10:48 +0100 Ben Paley [EMAIL PROTECTED] wrote: This is very scary, but thanks for the advice. I had some more advice (not sure if it went to the list or not) to try setting the second partition as unused (sysid=0), so I might try that first to see whether I can avoid risking destroying everything and making my family hate me. I'll suggest something sacrilegious - beg, borrow or steal a copy of Windows 2000 - it doesn't mind being installed on the second hard disk. Remember - I never said that. regards, Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dangerous file system / disk problem
On Monday 07 June 2004 04:01, Ben Paley wrote: su-2.05b# fdisk ad1 *** Working on device /dev/ad1 *** parameters extracted from in-core disklabel are: cylinders=155061 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=155061 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 156296322 (76316 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 14 (0x0e),(Primary 'big' DOS (= 32MB, LBA)) start 156296385, size 0 (0 Meg), flag 0 Notice the size recorded for this slice is zero. If the cylinders=155061 heads=16 sectors/track=63 is somewhere near the reasonable possible geometry description then virtually the entire disk has been allocated to the FreeBSD slice. beg: cyl 1022/ head 0/ sector 1; end: cyl 1022/ head 254/ sector 63 The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED su-2.05b# I don't really understand this, frankly: it certainly gives the right partition type code for the main partition, but I'm not sure of the relevance of the other stuff... does it look ok to you? Or is this partition 2 where the problem is? Partition Magic in Windows sees only one partition on that disk. The slice editor in sysinstall shows this for ad1: OffsetSize(ST)End NamePType DescSubtypeFlags 0 63 62 - 12 unused 0 63156296322 156296384 ad1s1 8 freebsd 165 156296385 5103156301487 - 12 unused 0 And this agrees that the second slice is almost non-existent -- 2.5Mb -- certainly not enough for windows. I wonder whether you had the BIOS re-detect the disks after the swap. Maybe the BIOS still thinks the size is that of the disk previously in that position. And sysinstall and windows are both confused by the near zero apparent size of the windows partition. What do you believe is the total disk capacity? Since the slice 2 size is less than 32Mb then sysinstall knows that it can't really have a sysid of 14. Malcolm (Which release of FreeBSD do you run? You used the bsdlabel command to display the FreeBSD disk label on /dev/ad1s1. That suggests you are running FreeBSD 5.x. In my experience, release 5.x won't recognize FreeBSD disk labels in non FreeBSD slices and won't create special files for the partitions in /dev. This suggests that your MBR partition type code is actually correct. I dunno ... but it should be worth checking anyway.) 5.2-CURRENT. But BSD sees everything ok, it's Windows that's having a problem. I don't feel confident making any changes in Windows, however, because it seems as though my only option there would be to format the partition! Which, from a Windows point of view, would certainly be a solution of sorts... Thanks for your help, Ben ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dangerous file system / disk problem
On Monday 07 June 2004 16:44, Malcolm Kay wrote: Notice the size recorded for this slice is zero. If the cylinders=155061 heads=16 sectors/track=63 is somewhere near the reasonable possible geometry description then virtually the entire disk has been allocated to the FreeBSD slice. Yes it is, all of it (or, all of it that I could withot going 'dangerously dedicated'). I have never had any intention of putting Windows on this disk. I think W98 just assumed it 'cos it was the primary master. The slice editor in sysinstall shows this for ad1: Offset Size(ST)End NamePType DescSubtypeFlags 0 63 62 - 12 unused 0 63 156296322 156296384 ad1s1 8 freebsd 165 156296385 5103156301487 - 12 unused 0 And this agrees that the second slice is almost non-existent -- 2.5Mb -- certainly not enough for windows. No. But Windows is runing quite happily on ad0 (or c:\ :-) I wonder whether you had the BIOS re-detect the disks after the swap. Maybe the BIOS still thinks the size is that of the disk previously in that position. And sysinstall and windows are both confused by the near zero apparent size of the windows partition. No, the BIOS knows where the disks are, autodetects with no problem, and the defaults it offers match whats on the disk label (I mean the physical, paper label on the metal disk housing!) - and Windows is fine on the other disk - the problem is, really, that there shouldn't be a windows partition on _this_ disk at all. What do you believe is the total disk capacity? 80Gb, nominally. su-2.05b# df -h Filesystem SizeUsedAvail CapacityMounted on /dev/ad1s1a 989M415M496M 46%/ devfs 1.0K1.0K0B 100% /dev /dev/ad1s1e 496M 5.0M451M1% /tmp /dev/ad1s1f 69G 13G 51G 20% /usr /dev/ad1s1d 496M136M320M30% /var procfs 4.0K4.0K0B 100%/proc [cut - the rest is about ad0] Since the slice 2 size is less than 32Mb then sysinstall knows that it can't really have a sysid of 14. If you say so! It knows more than me about disk geometry and so on, I guess. But seriously, does any of this suggest a course of action to you? I'm planning to try the set sysid to 0 plan... what if that doesn't work? The fact is I really don't understand in any kind of detail how this stuff works - I'm just trying to ask the right questions... Thanks a lot for taking the time to think about this, I appreciate it. Cheers, Ben ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dangerous file system / disk problem
On Sun, 6 Jun 2004 12:13:17 +0100, Ben Paley wrote: I wanted to have FreeBSD on my first drive and Win98 on the second, but of course windows doesn't like being on the second disk, and began preparing my first drive which already had FreeBSD on it! Well, I swapped the drives over, put W98 on the first one, they both boot fine and I didn't lose any data. BUT - Windows now sees my BSD disk (which has never happened before) and keeps offering to format it for me. Partition Magic gives its filesystem type as 'BAD' rather than 'FreeBSD/i386', as it used to. Weirdly, Boot Magic (bundled with Partition Magic) found both operating systems with no difficulty. Perhaps something changed the partition type code in the MBR partition table on your FreeBSD disk. Do fdisk ad1 to display the MBR partition table. The FreeBSD slice should say: sysid 165,(FreeBSD/NetBSD/386BSD) If it says anything else, you can use the command fdisk -u ad1 to change the MBR partition type code back to 165 (decimal). (Which release of FreeBSD do you run? You used the bsdlabel command to display the FreeBSD disk label on /dev/ad1s1. That suggests you are running FreeBSD 5.x. In my experience, release 5.x won't recognize FreeBSD disk labels in non FreeBSD slices and won't create special files for the partitions in /dev. This suggests that your MBR partition type code is actually correct. I dunno ... but it should be worth checking anyway.) Dan Strick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dangerous file system / disk problem
On Sunday 06 June 2004 13:04, Dan Strick wrote: Perhaps something changed the partition type code in the MBR partition table on your FreeBSD disk. Do fdisk ad1 to display the MBR partition table. The FreeBSD slice should say: sysid 165,(FreeBSD/NetBSD/386BSD) If it says anything else, you can use the command fdisk -u ad1 to change the MBR partition type code back to 165 (decimal). su-2.05b# fdisk ad1 *** Working on device /dev/ad1 *** parameters extracted from in-core disklabel are: cylinders=155061 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=155061 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 156296322 (76316 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 14 (0x0e),(Primary 'big' DOS (= 32MB, LBA)) start 156296385, size 0 (0 Meg), flag 0 beg: cyl 1022/ head 0/ sector 1; end: cyl 1022/ head 254/ sector 63 The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED su-2.05b# I don't really understand this, frankly: it certainly gives the right partition type code for the main partition, but I'm not sure of the relevance of the other stuff... does it look ok to you? Or is this partition 2 where the problem is? Partition Magic in Windows sees only one partition on that disk. The slice editor in sysinstall shows this for ad1: Offset Size(ST)End NamePType Desc SubtypeFlags 0 63 62 - 12 unused 0 63 156296322 156296384 ad1s1 8 freebsd 165 156296385 5103156301487 - 12 unused 0 (Which release of FreeBSD do you run? You used the bsdlabel command to display the FreeBSD disk label on /dev/ad1s1. That suggests you are running FreeBSD 5.x. In my experience, release 5.x won't recognize FreeBSD disk labels in non FreeBSD slices and won't create special files for the partitions in /dev. This suggests that your MBR partition type code is actually correct. I dunno ... but it should be worth checking anyway.) 5.2-CURRENT. But BSD sees everything ok, it's Windows that's having a problem. I don't feel confident making any changes in Windows, however, because it seems as though my only option there would be to format the partition! Which, from a Windows point of view, would certainly be a solution of sorts... Thanks for your help, Ben ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
