- WLUG - wlug.mailman3.com

Re: [Wlug] August Speaker proposal

by Mike Frysinger

On Wednesday 28 July 2004 06:03 pm, Andy Stewart wrote: > Given all of the interest, who am I to say "no"? :-) i know i'd attend for the first time in a while ;) -mike

July 28, 2004

Re: [Wlug] August Speaker proposal

by Andy Stewart

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 28 July 2004 10:10 am, Jeff Moyer wrote: > Hello, > > If there is interest, Dan Walsh is willing to give a presentation on > SELinux for the next meeting. Takers? > > -Jeff Given all of the interest, who am I to say "no"? :-) Jeff, let's you and I chat offline and have you introduce me to Dan so we can work out the particulars. Thanks! Andy - -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBCCLOHl0iXDssISsRAhhPAJ9926nsgJ9pcMLsfgX6+BdLJMHtmgCgg0PE dnl9noGAs5mu4Ar0qJUvZBU= =JFzJ -----END PGP SIGNATURE-----

July 28, 2004

Re: [Wlug] August Speaker proposal

by Mike Frysinger

On Wednesday 28 July 2004 10:10 am, Jeff Moyer wrote: > If there is interest, Dan Walsh is willing to give a presentation on > SELinux for the next meeting. Takers? ++interest -mike

July 28, 2004

Re: [Wlug] August Speaker proposal

by frank p

> > If there is interest, Dan Walsh is willing to give a presentation on > > SELinux for the next meeting. Takers? > > Sounds good to me! I'll second that... and how can you go wrong when two frank's agree? -frank p

July 28, 2004

Re: [Wlug] August Speaker proposal

by Frank Sweetser

On Wed, Jul 28, 2004 at 10:10:49AM -0400, Jeff Moyer wrote: > Hello, > > If there is interest, Dan Walsh is willing to give a presentation on > SELinux for the next meeting. Takers? Sounds good to me! -- Frank Sweetser fs at wpi.edu WPI Network Engineer GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC

July 28, 2004

August Speaker proposal

by Jeff Moyer

Hello, If there is interest, Dan Walsh is willing to give a presentation on SELinux for the next meeting. Takers? -Jeff

July 28, 2004

Re: [Wlug] Partition table blues

by Gregory Avedissian

Brian, Here's the info you asked for. I'll be busy reading for awhile. Greg kervnel version 2.4.20-4GB-athlon sfdisk -H 63 -l Disk /dev/hdb: 3737 cylinders, 63 heads, 63 sectors/track Warning: The partition table looks like it was made for C/H/S=*/255/63 (instead of 3737/63/63). For this listing I'll assume that geometry. Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/hdb1 * 0+ 1023 1024- 8225248+ c Win95 FAT32 (LBA) /dev/hdb2 0 - 0 0 0 Empty /dev/hdb3 0 - 0 0 0 Empty /dev/hdb4 0 - 0 0 0 Empty Brian Waite wrote: >>>What does the kernel think the disk size is on bootup? >>> >>>dmesg | grep hdb >> >> ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:DMA >>hdb: IBM-DTLA-307030, ATA DISK drive >>hdb: attached ide-disk driver. >>hdb: host protected area => 1 >>hdb: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(100) >> hdb: hdb1 >> >> >> >>>What does the BIOS say in the CMOS setup screen for the disk geometry? >> >>capacity 30740 MB >>cylinder 59560 >>head 16 >>precomp 0 >>landing zone 59559 >>sector 63 >> >> >>>What does the disk say on the label for the geometry? >> >>Model: DTLA-307030 >>Capacity: 30.7 GB >>LBA 60.036.480 sectors >>CHS: 16383/16/63 >>MLC: F80033 >> >>And here's more: >> >>DOS fdisk reports the partition as being 8032 MB. >>Win98 reports it (C:) as 5.8 GB. >> >>gnu parted reports it as: (note that the drive is temporarily connected as >>hdb for convenience) >> >>ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:DMA >>hdb: IBM-DTLA-307030, ATA DISK drive >>hdb: attached ide-disk driver. >>hdb: host protected area => 1 >>hdb: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(100) >> hdb: hdb1 >> >>and here are the fdisk and sfdisk outputs again for reference: >> >>fdisk -l >> Device Boot Start End Blocks Id System >>/dev/hdb1 * 1 1123 9020466 c Win95 FAT32 (LBA) >> >>sfdisk -l >>Disk /dev/hdb: 1123 cylinders, 255 heads, 63 sectors/track >>Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 >> >> Device Boot Start End #cyls #blocks Id System >>/dev/hdb1 * 0+ 1122 1123- 9020466 c Win95 FAT32 (LBA) >>/dev/hdb2 0 - 0 0 0 Empty >>/dev/hdb3 0 - 0 0 0 Empty >>/dev/hdb4 0 - 0 0 0 Empty >> >> >>_______________________________________________ >>Wlug mailing list >>Wlug(a)mail.wlug.org >>http://mail.wlug.org/mailman/listinfo/wlug >> > > > It looks to me like the kernel is not getting the head count right. > What is the output when you do > sfdisk -H 63 -l > It may not help but maybe you can get a bit closer > BTW exactly what kernel version are you on? > uname -a > > Thanks > Brian > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

July 26, 2004

Re: [Wlug] Partition table blues

by Charles R. Anderson

On Mon, Jul 26, 2004 at 02:27:01PM -0400, Gregory Avedissian wrote: > >What does the kernel think the disk size is on bootup? > hdb: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(100) > >What does the BIOS say in the CMOS setup screen for the disk geometry? > capacity 30740 MB > cylinder 59560 > head 16 > precomp 0 > landing zone 59559 > sector 63 The BIOS and kernel agree on the size of the disk. 59560/(255/16) = 3737 cylinders. I would however make sure the BIOS is set to LBA mode if it isn't, which should cause the heads to become 255. > >What does the disk say on the label for the geometry? > > Model: DTLA-307030 > Capacity: 30.7 GB > LBA 60.036.480 sectors > CHS: 16383/16/63 > MLC: F80033 Strange. That doesn't add up at all. Ah, here it is: "There is an industry convention to give C/H/S=16383/16/63 for disks larger than 8.4 GB" [1] > And here's more: > DOS fdisk reports the partition as being 8032 MB. > Win98 reports it (C:) as 5.8 GB. Interesting. > gnu parted reports it as: (note that the drive is temporarily connected as > hdb for convenience) > hdb: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(100) Agrees with the kernel above. > sfdisk -l > Disk /dev/hdb: 1123 cylinders, 255 heads, 63 sectors/track > Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Here is the problem. sfdisk is seeing the wrong number geometry. I would attempt to fix the C/H/S values in the partition table with sfdisk. First I would read [1] in it's entirety--it goes into all the gory details of geometry and size limits. Here are some useful documents on geometry and partitioning: [1] http://www.tldp.org/HOWTO/Large-Disk-HOWTO.html [2] http://www.microsoft.com/windows2000/techinfo/reskit/en-us/default.asp?url=… [3] http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-u…

July 26, 2004

Re: [Wlug] Partition table blues

by Brian Waite

> > What does the kernel think the disk size is on bootup? > > > > dmesg | grep hdb > ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:DMA > hdb: IBM-DTLA-307030, ATA DISK drive > hdb: attached ide-disk driver. > hdb: host protected area => 1 > hdb: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(100) > hdb: hdb1 > > > > > > What does the BIOS say in the CMOS setup screen for the disk geometry? > > capacity 30740 MB > cylinder 59560 > head 16 > precomp 0 > landing zone 59559 > sector 63 > > > What does the disk say on the label for the geometry? > > Model: DTLA-307030 > Capacity: 30.7 GB > LBA 60.036.480 sectors > CHS: 16383/16/63 > MLC: F80033 > > And here's more: > > DOS fdisk reports the partition as being 8032 MB. > Win98 reports it (C:) as 5.8 GB. > > gnu parted reports it as: (note that the drive is temporarily connected as > hdb for convenience) > > ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:DMA > hdb: IBM-DTLA-307030, ATA DISK drive > hdb: attached ide-disk driver. > hdb: host protected area => 1 > hdb: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(100) > hdb: hdb1 > > and here are the fdisk and sfdisk outputs again for reference: > > fdisk -l > Device Boot Start End Blocks Id System > /dev/hdb1 * 1 1123 9020466 c Win95 FAT32 (LBA) > > sfdisk -l > Disk /dev/hdb: 1123 cylinders, 255 heads, 63 sectors/track > Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 > > Device Boot Start End #cyls #blocks Id System > /dev/hdb1 * 0+ 1122 1123- 9020466 c Win95 FAT32 (LBA) > /dev/hdb2 0 - 0 0 0 Empty > /dev/hdb3 0 - 0 0 0 Empty > /dev/hdb4 0 - 0 0 0 Empty > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > It looks to me like the kernel is not getting the head count right. What is the output when you do sfdisk -H 63 -l It may not help but maybe you can get a bit closer BTW exactly what kernel version are you on? uname -a Thanks Brian

July 26, 2004

Re: [Wlug] Partition table blues

by Gregory Avedissian

Charles R. Anderson wrote: > On Mon, Jul 26, 2004 at 12:55:36AM -0400, Gregory Avedissian wrote: > >>The disk in question is around 30GB, and originally, 6 GB were taken by >>windows on hda1, 1GB by swap on hda2, 8GB for hda3, and 10GB for hda5, >>leaving 3.7GB unallocated space in the extended partition. I did this by >>making the win partition with the win98 fdisk, and then making the linux >>partitions with the suse intall disk. It looks like the numbers aren't >>adding up right. > > > Ok, you need to stop right here and find out why fdisk thinks the disk > is only 9GB before doing anything else. I can think of one reason. > The MBR also stores C/H/S values. Normally, C*H*S*512 on the MBR > should match the disk capacity. Since yours doesn't appear to, > perhaps you overwrote the MBR C/H/S values when you restored the copy > you had in /boot. Did you perhaps make that backup from a different > sized disk? Linux 2.4 will trust the MBR values over the BIOS values. > Linux 2.6 trusts the BIOS over the MBR (leading to the aforementioned > Windows interop problem after installing a Linux 2.6 distro). > I'm sure I made the backups from the right disk. This was about a week ago when I installed this drive, and it was the only harddrive in the machine at the time. Once I got everything installed and working, I made the backups with debug and in linux with dd. I have noticed on several previous linux installations that disk geometry reported by linux is accompanied by messages that say something like "this is not the geometry we expected." I always have ignored those messages, because everything was working. I thought that was normal, but if I'm doing something consistently wrong on installation, I'd like to know about it. > What does the kernel think the disk size is on bootup? > > dmesg | grep hdb ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:DMA hdb: IBM-DTLA-307030, ATA DISK drive hdb: attached ide-disk driver. hdb: host protected area => 1 hdb: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(100) hdb: hdb1 > > What does the BIOS say in the CMOS setup screen for the disk geometry? capacity 30740 MB cylinder 59560 head 16 precomp 0 landing zone 59559 sector 63 > What does the disk say on the label for the geometry? Model: DTLA-307030 Capacity: 30.7 GB LBA 60.036.480 sectors CHS: 16383/16/63 MLC: F80033 And here's more: DOS fdisk reports the partition as being 8032 MB. Win98 reports it (C:) as 5.8 GB. gnu parted reports it as: (note that the drive is temporarily connected as hdb for convenience) ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:DMA hdb: IBM-DTLA-307030, ATA DISK drive hdb: attached ide-disk driver. hdb: host protected area => 1 hdb: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(100) hdb: hdb1 and here are the fdisk and sfdisk outputs again for reference: fdisk -l Device Boot Start End Blocks Id System /dev/hdb1 * 1 1123 9020466 c Win95 FAT32 (LBA) sfdisk -l Disk /dev/hdb: 1123 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/hdb1 * 0+ 1122 1123- 9020466 c Win95 FAT32 (LBA) /dev/hdb2 0 - 0 0 0 Empty /dev/hdb3 0 - 0 0 0 Empty /dev/hdb4 0 - 0 0 0 Empty

July 26, 2004

Re: [Wlug] Partition table blues

by Charles R. Anderson

On Mon, Jul 26, 2004 at 12:55:36AM -0400, Gregory Avedissian wrote: > The disk in question is around 30GB, and originally, 6 GB were taken by > windows on hda1, 1GB by swap on hda2, 8GB for hda3, and 10GB for hda5, > leaving 3.7GB unallocated space in the extended partition. I did this by > making the win partition with the win98 fdisk, and then making the linux > partitions with the suse intall disk. It looks like the numbers aren't > adding up right. Ok, you need to stop right here and find out why fdisk thinks the disk is only 9GB before doing anything else. I can think of one reason. The MBR also stores C/H/S values. Normally, C*H*S*512 on the MBR should match the disk capacity. Since yours doesn't appear to, perhaps you overwrote the MBR C/H/S values when you restored the copy you had in /boot. Did you perhaps make that backup from a different sized disk? Linux 2.4 will trust the MBR values over the BIOS values. Linux 2.6 trusts the BIOS over the MBR (leading to the aforementioned Windows interop problem after installing a Linux 2.6 distro). What does the kernel think the disk size is on bootup? dmesg | grep hdb What does the BIOS say in the CMOS setup screen for the disk geometry? What does the disk say on the label for the geometry?

July 26, 2004

Re: [Wlug] Partition table blues

by doug waud

Hi again Greg Gregory Avedissian wrote: > Thanks, Charles. I was afraid that hdb designation would be confusing. > That's just temporary, so I can do things to that drive from a working > linux intall on another disk. I've got three drives within reach of the > IDE cables, and I keep switching cables and jumpers to do all this. Now why did you not let us know that right from the start!? In particular, your second post had lines like > dd if=/dev/hda of=/boot/boot.MBR bs=512 count=1 > dd if=/dev/hda of=/boot/boot.446.MBR bs=446 count=1 > > I restored with: > > dd if=/boot/boot.MBR of=/dev/hda bs=512 count=1 all of which referred to /dev/hda! It is hard to tell without mind-reading exactly what you did. Do you see why you *must* tell us *exactly* what you did/are doing. There is no way we can guess that you moved the drive from /dev/hda to /dev/hdb (and god-knows-what-else!). In turn, if we are assuming the /dev/hda you reported is correct, we stand a good chance of telling you to do something which could be a disaster if it is mounted as /dev/hdb. Now I hope you can see why I kept harping on telling us *what* you did rather than what you *think* you did. > The disk in question is around 30GB, and originally, 6 GB were taken by > windows on hda1, 1GB by swap on hda2, 8GB for hda3, and 10GB for hda5, > leaving 3.7GB unallocated space in the extended partition. I did this by > making the win partition with the win98 fdisk, and then making the linux > partitions with the suse intall disk. It looks like the numbers aren't > adding up right. > >> >>> Disk /dev/hdb: 1123 cylinders, 255 heads, 63 sectors/track >> >> >> >> That equals 18040995 sectors of 512 bytes/each = 9,236,989,440 bytes Yes! You claim it is a 30 gig disk and, as Chuck points out, it is coming out about 9. Note that this is even before you get into the details of partitions. At this point I have not the slightest idea of where we are, especially since you have been swapping drives in god-knows-what order and fdisk /mbr on again an unknown (to us) drive. >> (snip,snip) >> The Win95 partition is just about the entire disk, leaving only 31.5 >> 1024-byte blocks left = 32,256 bytes. Where could any Linux >> partitions have fit? > > > On the other 24GB which appear not to be partitioned. See comments above, the summary for /dev/hdb *total* says there are not another 24 GB! > I'm a little > bothered by the math, though. You came up with 9GB, and I made that > partition 6GB. You *think* you did. It would appear the fact is that you really do not know what you did! >>> OK, one more idea. Can I use the partition tool to set the partitions >>> again without formatting them, and then be able to access them? >> >> If you are absolutely sure of the correct start/end of all the >> partitions on the disk, then yes, you should be able to re-set them in >> the partition table and regain access to the data without formatting >> them. This is much more likely to happen if there are no extended >> partitions (hdb5 or higher). Chuck, you are more optimistic than I! :-) I think that right now we are flying blind. Also, he now refers to a /dev/hd5 and and extended partition, so the cards would appear to be stacked even more solidly against him. > > No, I'm not sure, just assuming that if I use the same partition tool > with the same drive, it'll come up with the same numbers. Guess I need > to double-check the size of my win partition and make sure it hasn't > changed. In fact, I seem to recall noticing that hda1 ended well below > cyl 1023 when I set it up. At 8225280 bytes/cylinder, 6GB should end at > cyl 750, not 1125. The partition tool shows the end of hda1 at 1023, and > the end of hda2 at 1154. Uh-oh. Now, once again, that comes out of the blue (unless I lost something in all this long exchange). You just give the numbers in your edited version rather than tell us *exactly* what you did and then show us *exactly* what came out. > I better sleep on it before I do anything else. As I indicated earlier, prayer might be more effective! > Maybe parted didn't work because I gave it the wrong numbers? That "it' says a lot! Yes, wrong numbers is one of a zillion (and climbing) possibilities. doug

July 26, 2004

Re: [Wlug] Partition table blues

by Gregory Avedissian

Thanks, Charles. I was afraid that hdb designation would be confusing. That's just temporary, so I can do things to that drive from a working linux intall on another disk. I've got three drives within reach of the IDE cables, and I keep switching cables and jumpers to do all this. The disk in question is around 30GB, and originally, 6 GB were taken by windows on hda1, 1GB by swap on hda2, 8GB for hda3, and 10GB for hda5, leaving 3.7GB unallocated space in the extended partition. I did this by making the win partition with the win98 fdisk, and then making the linux partitions with the suse intall disk. It looks like the numbers aren't adding up right. > >>Disk /dev/hdb: 1123 cylinders, 255 heads, 63 sectors/track > > > That equals 18040995 sectors of 512 bytes/each = 9,236,989,440 bytes > total. > > >>Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 > > > Taking the blocks as 1024 bytes, thats 9020497.5 blocks. > > >> Device Boot Start End #cyls #blocks Id System >>/dev/hdb1 * 0+ 1122 1123- 9020466 c Win95 FAT32 (LBA) > > > The Win95 partition is just about the entire disk, leaving only 31.5 > 1024-byte blocks left = 32,256 bytes. Where could any Linux > partitions have fit? On the other 24GB which appear not to be partitioned. I'm a little bothered by the math, though. You came up with 9GB, and I made that partition 6GB. > > >>OK, one more idea. Can I use the partition tool to set the partitions >>again without formatting them, and then be able to access them? > > > If you are absolutely sure of the correct start/end of all the > partitions on the disk, then yes, you should be able to re-set them in > the partition table and regain access to the data without formatting > them. This is much more likely to happen if there are no extended > partitions (hdb5 or higher). > No, I'm not sure, just assuming that if I use the same partition tool with the same drive, it'll come up with the same numbers. Guess I need to double-check the size of my win partition and make sure it hasn't changed. In fact, I seem to recall noticing that hda1 ended well below cyl 1023 when I set it up. At 8225280 bytes/cylinder, 6GB should end at cyl 750, not 1125. The partition tool shows the end of hda1 at 1023, and the end of hda2 at 1154. Uh-oh. I better sleep on it before I do anything else. Maybe parted didn't work because I gave it the wrong numbers? Thanks, Greg

July 26, 2004

Re: [Wlug] Partition table blues

by Charles R. Anderson

On Sun, Jul 25, 2004 at 10:34:39PM -0400, Gregory Avedissian wrote: > That was linux fdisk I was talking about. It only shows the windows > partition. sfdisk -l shows four partitions - one windows, and three empty > ones, with no start or end cylinders. I'm not sure what that's about. There are always 4 primary partition entries in the partition table in first sector of the drive (MBR). The unused ones are filled with zeros. > Disk /dev/hdb: 1123 cylinders, 255 heads, 63 sectors/track That equals 18040995 sectors of 512 bytes/each = 9,236,989,440 bytes total. > Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Taking the blocks as 1024 bytes, thats 9020497.5 blocks. > Device Boot Start End #cyls #blocks Id System > /dev/hdb1 * 0+ 1122 1123- 9020466 c Win95 FAT32 (LBA) The Win95 partition is just about the entire disk, leaving only 31.5 1024-byte blocks left = 32,256 bytes. Where could any Linux partitions have fit? > OK, one more idea. Can I use the partition tool to set the partitions > again without formatting them, and then be able to access them? If you are absolutely sure of the correct start/end of all the partitions on the disk, then yes, you should be able to re-set them in the partition table and regain access to the data without formatting them. This is much more likely to happen if there are no extended partitions (hdb5 or higher). What happened to make Windows take over the entire disk? Are you sure /dev/hdb is still /dev/hdb, and didn't change due to a disk failure or recabling of the IDE bus? Is Windows 98 installed to /dev/hdb1? It is highly unusual to have Windows boot from anything other than /dev/hdaN.

July 26, 2004

Re: [Wlug] Partition table blues

by Gregory Avedissian

Doug, That was linux fdisk I was talking about. It only shows the windows partition. sfdisk -l shows four partitions - one windows, and three empty ones, with no start or end cylinders. I'm not sure what that's about. Here's the output for fdisk and sfdisk when that drive is hooked up as slave: fdisk -l Device Boot Start End Blocks Id System /dev/hdb1 * 1 1123 9020466 c Win95 FAT32 (LBA) sfdisk -l Disk /dev/hdb: 1123 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/hdb1 * 0+ 1122 1123- 9020466 c Win95 FAT32 (LBA) /dev/hdb2 0 - 0 0 0 Empty /dev/hdb3 0 - 0 0 0 Empty /dev/hdb4 0 - 0 0 0 Empty Here's what I tried. I went into yast2 partitioning tool, setup the drive the way I did the first time, wrote down the cylinder numbers, then hit ABORT, so it wouldn't write to the disk. Then ran "parted -i /dev/hdb", then used the cylinder numbers for the "rescue partitions near START and END" function. It scanned, returned no errors, and made no changes. I don't get it, and I'm out of ideas for now. OK, one more idea. Can I use the partition tool to set the partitions again without formatting them, and then be able to access them? Thanks for all your help, Greg doug waud wrote: > Hi again > > Gregory Avedissian wrote: > >> Hi Doug, >> >> I tried fdisk /mbr and it worked easily. As expected, I only have a >> windows partition (verified by fdisk). I suspect that I'm less than >> halfway there. > > > I'm glad you finally tried that! At least the easy part is taken care of > so you can now focus on a smaller problem. > > I admit to some guessing here, but I would suggest you try both the > Windows fdisk (just because I am a bit anal; I don't expect it to know > about the linux partitions) and the Linux fdisk. (You may have done this > but I can't tell since you say just "fdisk".) > >>> However, once that is working, you can boot into your linux system >>> (by one of the ways I mentioned in an earlier post, and run LILO >>> which is smart enough to leave the Windows part working and simply >>> add the stuff for other things you want to boot (as specified in >>> lilo.conf --- which I assume is OK if it was working earlier and you >>> have not edited it). >> >> >> No, there's no lilo.conf and never was one on that installation. > > > Oops! Sorry about that; I misread an earlier email. :-( > >> There is (was) a grub/menu.lst, which serves the same function, but as >> far as I understand it, the partition table needs to contain >> information about linux partitions for either of these to work. > > > I suspect that is true (can't recall off hand). If so, then remember to > pray when you run the Linux fdisk! :- > > And do run the linux fdisk, i.e. > fdisk /dev/hda > and then chose option p (as in *P*rint the partition table. If you get a > nice listing, then don't screw around with parted! > > >> I went ahead and booted the rescue system and tried a grub-install >> /dev/hda, and it returned a message saying that no /dev/root was found. >> >> Maybe I'll try parted again, now that I can find where hda1 ends. > > > But do try both Windows fdisk and Linux fdisk (with the P option) first! > > doug > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

July 26, 2004

Re: [Wlug] Partition table blues

by doug waud

Hi again Gregory Avedissian wrote: > Hi Doug, > > I tried fdisk /mbr and it worked easily. As expected, I only have a > windows partition (verified by fdisk). I suspect that I'm less than > halfway there. I'm glad you finally tried that! At least the easy part is taken care of so you can now focus on a smaller problem. I admit to some guessing here, but I would suggest you try both the Windows fdisk (just because I am a bit anal; I don't expect it to know about the linux partitions) and the Linux fdisk. (You may have done this but I can't tell since you say just "fdisk".) >> However, once that is working, you can boot into your linux system (by >> one of the ways I mentioned in an earlier post, and run LILO which is >> smart enough to leave the Windows part working and simply add the >> stuff for other things you want to boot (as specified in lilo.conf >> --- which I assume is OK if it was working earlier and you have not >> edited it). > > No, there's no lilo.conf and never was one on that installation. Oops! Sorry about that; I misread an earlier email. :-( > There > is (was) a grub/menu.lst, which serves the same function, but as far as > I understand it, the partition table needs to contain information about > linux partitions for either of these to work. I suspect that is true (can't recall off hand). If so, then remember to pray when you run the Linux fdisk! :- And do run the linux fdisk, i.e. fdisk /dev/hda and then chose option p (as in *P*rint the partition table. If you get a nice listing, then don't screw around with parted! > I went ahead and booted the rescue system and tried a grub-install > /dev/hda, and it returned a message saying that no /dev/root was found. > > Maybe I'll try parted again, now that I can find where hda1 ends. But do try both Windows fdisk and Linux fdisk (with the P option) first! doug

July 26, 2004

Re: [Wlug] Partition table blues

by Gregory Avedissian

Hi Doug, I tried fdisk /mbr and it worked easily. As expected, I only have a windows partition (verified by fdisk). I suspect that I'm less than halfway there. > >> This morning, I read that it shouldn't be used on disks that have more >> than four partitions. I have five partitions and some unclaimed space. >> I might try it later today. > > > I don't know where that came from. It came from ms. Maybe they're just playin' with our heads. > > However, once that is working, you can boot into your linux system (by > one of the ways I mentioned in an earlier post, and run LILO which is > smart enough to leave the Windows part working and simply add the stuff > for other things you want to boot (as specified in lilo.conf --- which > I assume is OK if it was working earlier and you have not edited it). No, there's no lilo.conf and never was one on that installation. There is (was) a grub/menu.lst, which serves the same function, but as far as I understand it, the partition table needs to contain information about linux partitions for either of these to work. I went ahead and booted the rescue system and tried a grub-install /dev/hda, and it returned a message saying that no /dev/root was found. Maybe I'll try parted again, now that I can find where hda1 ends. Thanks, Greg

July 26, 2004

Re: [Wlug] Partition table blues

by doug waud

Hi all (again!) J Schonberg wrote: > I know that the original question was based on a suse8.2 installation > but I'm guessing this is the Linux 2.6 kernel bug that has been > discussed at length in other places. Have you tried sfdisk? I don't follow your logic. Since Greg is using SuSE 8.2, he is a long way from a 2.6 kernel. So I don't see how you can diagnose his problem as a 2.6 not-ready-for-prime-time bug. doug

July 25, 2004

Re: [Wlug] Partition table blues

by Gregory Avedissian

Hi Doug, I haven't tried fdisk /mbr because I don't really fully understand what it does and have never seen a good explanation of how it will affect linux partitions. This morning, I read that it shouldn't be used on disks that have more than four partitions. I have five partitions and some unclaimed space. I might try it later today. Beside that, anything of value is on the linux side of the disk. (That's not a microsoft slur, it's just where I have my files.) So, while I would like to be able to get the whole thing back to its original working order as a learning exercise, I'm more motivated to get to the linux partitions. Thanks again, Greg doug waud wrote: > Hi again > > This time, let's try focussing on one thing to try. > > I don't see that you have ever tried the standard way to restore the MBR > for Windows --- boot a Windows floppy with fdisk on it and type > fdisk /mbr > and, if you still cannot boot windows, add a > sys c: > > It is not clear from here why you did not try this. > > doug > > > Gregory Avedissian wrote: > >> doug waud wrote: >> >>> Hi again Greg >>> >>> Gregory Avedissian wrote: >>> >>>> There were three backups of the mbr. One made under dos with >>>> debug.exe, and the others made with linux as, >>>> >>>> dd if=/dev/hda of=/boot/boot.MBR bs=512 count=1 >>>> dd if=/dev/hda of=/boot/boot.446.MBR bs=446 count=1 >>>> >>>> I restored with: >>>> >>>> dd if=/boot/boot.MBR of=/dev/hda bs=512 count=1 >>>> I think maybe I picked the wrong one. >> >> >> >> > I admit I would have used the second, safer (since it does not >> touch the >> > partition table), but I don't see why the 512 bs variant would not >> have >> > worked unless you had changed the partition table since making that >> > boot.MBR file. >> >> No, I didn't change the partition table. I made these backups within >> days of installing, so that I would have copies of a new, working mbr. >> >>> >>> It is hard to tell what went wrong until you tell us what you were >>> doing just before the system no longer would boot. (Those two lines >>> creating the boot.xyz files would only read from the first 512 or 446 >>> bytes not do any writing there so they cannot be the cause of your >>> troubles.) >>> >>> >>> Why don't you boot from a bootable floppy? Alternatively, start the >>> SuSE recovery mechanism which includes "boot an installed system" as >>> an option. If all that is screwed up it the MBR, you could then >>> simply run LILO to refresh it. >>> >> >> I had a new win98 installation working ok, then I installed suse8.2 >> and set it up so that it would boot with GRUB from floppy. I don't recall >> if I ever tried to boot from the harddrive to get into windows after I >> installed suse, but I know I could get there from the floppy. >> >> When I did try to boot off the hard drive two days ago, it hung with >> the message, "Disk boot failure. Insert system disk." >> >> I could still boot to win or linux from the grub floppy at this point. >> I tried restoring the mbr in dos with debug.exe, and that didn't help. >> I could still boot to linux with the floppy, and I can't remember if I >> could still boot to windows. Then I tried restoring with >> dd if=/boot/boot.MBR of=/dev/hda bs=512 count=1 >> >> After that, I couldn't boot from the grub floppy anymore. Trying to >> boot the installed system from the rescue disk also failed. I then >> booted to the rescue system. Output of sfdisk -l looked like this: >> >> Disk /dev/hda: 3737 cylinders, 255 heads, 63 sectors/track >> /dev/hda: unrecognized partition >> No partitions found >> >> Repeating the restore procedure with debug.exe didn't help, either. >> >> >> Thanks, >> Greg >> > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

July 25, 2004

Re: [Wlug] Partition table blues

by J Schonberg

I know that the original question was based on a suse8.2 installation but I'm guessing this is the Linux 2.6 kernel bug that has been discussed at length in other places. Have you tried sfdisk? Details and a solution here : http://www.redhat.com/archives/fedora-devel-list/2004-May/msg00908.html Cheers. Jason. --- doug waud <douglas.waud(a)umassmed.edu> wrote: > Hi again > > This time, let's try focussing on one thing to try. > > I don't see that you have ever tried the standard way to restore > the MBR > for Windows --- boot a Windows floppy with fdisk on it and type > fdisk /mbr > and, if you still cannot boot windows, add a > sys c: > > It is not clear from here why you did not try this. > > doug > > > Gregory Avedissian wrote: > > doug waud wrote: > > > >> Hi again Greg > >> > >> Gregory Avedissian wrote: > >> > >>> There were three backups of the mbr. One made under dos with > >>> debug.exe, and the others made with linux as, > >>> > >>> dd if=/dev/hda of=/boot/boot.MBR bs=512 count=1 > >>> dd if=/dev/hda of=/boot/boot.446.MBR bs=446 count=1 > >>> > >>> I restored with: > >>> > >>> dd if=/boot/boot.MBR of=/dev/hda bs=512 count=1 > >>> I think maybe I picked the wrong one. > > > > > > > I admit I would have used the second, safer (since it does not > touch the > > > partition table), but I don't see why the 512 bs variant would > not have > > > worked unless you had changed the partition table since making > that > > > boot.MBR file. > > > > No, I didn't change the partition table. I made these backups > within > > days of installing, so that I would have copies of a new, working > mbr. > > > >> > >> It is hard to tell what went wrong until you tell us what you > were > >> doing just before the system no longer would boot. (Those two > lines > >> creating the boot.xyz files would only read from the first 512 > or 446 > >> bytes not do any writing there so they cannot be the cause of > your > >> troubles.) > >> > >> > >> Why don't you boot from a bootable floppy? Alternatively, start > the > >> SuSE recovery mechanism which includes "boot an installed > system" as > >> an option. If all that is screwed up it the MBR, you could then > simply > >> run LILO to refresh it. > >> > > > > I had a new win98 installation working ok, then I installed > suse8.2 > > and set it up so that it would boot with GRUB from floppy. I > don't recall > > if I ever tried to boot from the harddrive to get into windows > after I > > installed suse, but I know I could get there from the floppy. > > > > When I did try to boot off the hard drive two days ago, it hung > with the > > message, "Disk boot failure. Insert system disk." > > > > I could still boot to win or linux from the grub floppy at this > point. I > > tried restoring the mbr in dos with debug.exe, and that didn't > help. I > > could still boot to linux with the floppy, and I can't remember > if I > > could still boot to windows. Then I tried restoring with > > dd if=/boot/boot.MBR of=/dev/hda bs=512 count=1 > > > > After that, I couldn't boot from the grub floppy anymore. Trying > to boot > > the installed system from the rescue disk also failed. I then > booted to > > the rescue system. Output of sfdisk -l looked like this: > > > > Disk /dev/hda: 3737 cylinders, 255 heads, 63 sectors/track > > /dev/hda: unrecognized partition > > No partitions found > > > > Repeating the restore procedure with debug.exe didn't help, > either. > > > > > > Thanks, > > Greg > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail

July 25, 2004

Re: [Wlug] Partition table blues

by doug waud

Hi again This time, let's try focussing on one thing to try. I don't see that you have ever tried the standard way to restore the MBR for Windows --- boot a Windows floppy with fdisk on it and type fdisk /mbr and, if you still cannot boot windows, add a sys c: It is not clear from here why you did not try this. doug Gregory Avedissian wrote: > doug waud wrote: > >> Hi again Greg >> >> Gregory Avedissian wrote: >> >>> There were three backups of the mbr. One made under dos with >>> debug.exe, and the others made with linux as, >>> >>> dd if=/dev/hda of=/boot/boot.MBR bs=512 count=1 >>> dd if=/dev/hda of=/boot/boot.446.MBR bs=446 count=1 >>> >>> I restored with: >>> >>> dd if=/boot/boot.MBR of=/dev/hda bs=512 count=1 >>> I think maybe I picked the wrong one. > > > > I admit I would have used the second, safer (since it does not touch the > > partition table), but I don't see why the 512 bs variant would not have > > worked unless you had changed the partition table since making that > > boot.MBR file. > > No, I didn't change the partition table. I made these backups within > days of installing, so that I would have copies of a new, working mbr. > >> >> It is hard to tell what went wrong until you tell us what you were >> doing just before the system no longer would boot. (Those two lines >> creating the boot.xyz files would only read from the first 512 or 446 >> bytes not do any writing there so they cannot be the cause of your >> troubles.) >> >> >> Why don't you boot from a bootable floppy? Alternatively, start the >> SuSE recovery mechanism which includes "boot an installed system" as >> an option. If all that is screwed up it the MBR, you could then simply >> run LILO to refresh it. >> > > I had a new win98 installation working ok, then I installed suse8.2 > and set it up so that it would boot with GRUB from floppy. I don't recall > if I ever tried to boot from the harddrive to get into windows after I > installed suse, but I know I could get there from the floppy. > > When I did try to boot off the hard drive two days ago, it hung with the > message, "Disk boot failure. Insert system disk." > > I could still boot to win or linux from the grub floppy at this point. I > tried restoring the mbr in dos with debug.exe, and that didn't help. I > could still boot to linux with the floppy, and I can't remember if I > could still boot to windows. Then I tried restoring with > dd if=/boot/boot.MBR of=/dev/hda bs=512 count=1 > > After that, I couldn't boot from the grub floppy anymore. Trying to boot > the installed system from the rescue disk also failed. I then booted to > the rescue system. Output of sfdisk -l looked like this: > > Disk /dev/hda: 3737 cylinders, 255 heads, 63 sectors/track > /dev/hda: unrecognized partition > No partitions found > > Repeating the restore procedure with debug.exe didn't help, either. > > > Thanks, > Greg >

July 25, 2004

Re: [Wlug] Partition table blues

by Gregory Avedissian

doug waud wrote: > Hi again Greg > > Gregory Avedissian wrote: > >> There were three backups of the mbr. One made under dos with >> debug.exe, and the others made with linux as, >> >> dd if=/dev/hda of=/boot/boot.MBR bs=512 count=1 >> dd if=/dev/hda of=/boot/boot.446.MBR bs=446 count=1 >> >> I restored with: >> >> dd if=/boot/boot.MBR of=/dev/hda bs=512 count=1 >> I think maybe I picked the wrong one. > I admit I would have used the second, safer (since it does not touch the > partition table), but I don't see why the 512 bs variant would not have > worked unless you had changed the partition table since making that > boot.MBR file. No, I didn't change the partition table. I made these backups within days of installing, so that I would have copies of a new, working mbr. > > It is hard to tell what went wrong until you tell us what you were doing > just before the system no longer would boot. (Those two lines creating > the boot.xyz files would only read from the first 512 or 446 bytes not > do any writing there so they cannot be the cause of your troubles.) > > > Why don't you boot from a bootable floppy? Alternatively, start the SuSE > recovery mechanism which includes "boot an installed system" as an > option. If all that is screwed up it the MBR, you could then simply run > LILO to refresh it. > I had a new win98 installation working ok, then I installed suse8.2 and set it up so that it would boot with GRUB from floppy. I don't recall if I ever tried to boot from the harddrive to get into windows after I installed suse, but I know I could get there from the floppy. When I did try to boot off the hard drive two days ago, it hung with the message, "Disk boot failure. Insert system disk." I could still boot to win or linux from the grub floppy at this point. I tried restoring the mbr in dos with debug.exe, and that didn't help. I could still boot to linux with the floppy, and I can't remember if I could still boot to windows. Then I tried restoring with dd if=/boot/boot.MBR of=/dev/hda bs=512 count=1 After that, I couldn't boot from the grub floppy anymore. Trying to boot the installed system from the rescue disk also failed. I then booted to the rescue system. Output of sfdisk -l looked like this: Disk /dev/hda: 3737 cylinders, 255 heads, 63 sectors/track /dev/hda: unrecognized partition No partitions found Repeating the restore procedure with debug.exe didn't help, either. Thanks, Greg

July 25, 2004

Re: [Wlug] Partition table blues

by doug waud

Hi again Greg Gregory Avedissian wrote: > There were three backups of the mbr. One made under dos with debug.exe, > and the others made with linux as, > > dd if=/dev/hda of=/boot/boot.MBR bs=512 count=1 > dd if=/dev/hda of=/boot/boot.446.MBR bs=446 count=1 > > I restored with: > > dd if=/boot/boot.MBR of=/dev/hda bs=512 count=1 > I think maybe I picked the wrong one. I admit I would have used the second, safer (since it does not touch the partition table), but I don't see why the 512 bs variant would not have worked unless you had changed the partition table since making that boot.MBR file. > also tried restoring with > debug.exe, according to a long set of instructions that I could provide > but not explain. Unfortunately, the only copies of the linux versions > were on the hard drive, so I couldn't repeat that unless (until) I can > suck the files off the lost drive. Why don't you boot from a bootable floppy? Alternatively, start the SuSE recovery mechanism which includes "boot an installed system" as an option. If all that is screwed up it the MBR, you could then simply run LILO to refresh it. > There's a good possibility of retrieving those files, along with the > data files I want, thanks to a friend. Or see above. > And I probably won't even keep > the drive as a win/linux combo, but start over again with two drives. While I agree that's a good idea in general, it will still not prevent you blowing away something if you put your mind to it! :-) > But I'd still like to know where I went wrong and if there's a way to > reverse it. It is hard to tell what went wrong until you tell us what you were doing just before the system no longer would boot. (Those two lines creating the boot.xyz files would only read from the first 512 or 446 bytes not do any writing there so they cannot be the cause of your troubles.) Note that generally, when you are asking for help, providing your diagnosis (i.e. "I blew away the MBR") is not very helpful. Rather your should provide an objective description of what is not happening correctly, like "I can no longer boot linux" etc. The point is that, since you are in over your head (or you would not be posting a query), your diagnosis is not going to be very reliable so anyone trying to help you will need to know what your were actually doing just before the problem arose not what you think you did. They can then make their diagnosis and/or prognosis/treatment. doug

July 25, 2004

Problem with mount command

by Andy Stewart

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 HI Everybody, I have a problem with 'mount' between versions 2.11x and 2.12. Under 2.11x, this command worked just fine: mount -o port=3049,intr localhost:/null /crypt However, with the 2.12 version of mount, the command hangs and never returns. I have to kill the mount process to recover. Strace reports that the process is hanging at the "mount" call. Also, under 2.12, I do see entries in /var/log/messages indicating that a successful request was made to export /null: Jul 24 18:51:58 tux mountd[1843]: NFS mount of /null attempted from 127.0.0.1 Jul 24 18:51:58 tux mountd[1843]: /null has been mounted by 127.0.0.1 However, in another window, the "mount" command by itself does not show the NFS mount. All other NFS exporting/importing operations work just fine. The difference seems to be the two versions of mount and the use of the "port" option. I've downloaded the util-linux sources but so far cannot find a change that would effect this behavior. In case you are wondering what brought all of this about, I am trying to get my cryptographic file system (CFS by Matt Blaze) working under SuSE 9.1. I found a version of /bin/mount from another Linux system, and using that, I can access my files, but I really want to know why version 2.12 of util-linux broke/changed things. Any thoughts would be appreciated. Thanks! Andy - -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBAwW9Hl0iXDssISsRAiB6AJ0fLoy8/P0GXccouoAvJA5PhclAVACcCv2J 13io+TWed0PHS0xYQpZV7fE= =Dufw -----END PGP SIGNATURE-----

July 25, 2004

Re: [Wlug] Partition table blues

by Gregory Avedissian

There were three backups of the mbr. One made under dos with debug.exe, and the others made with linux as, dd if=/dev/hda of=/boot/boot.MBR bs=512 count=1 dd if=/dev/hda of=/boot/boot.446.MBR bs=446 count=1 I restored with: dd if=/boot/boot.MBR of=/dev/hda bs=512 count=1 I think maybe I picked the wrong one. I also tried restoring with debug.exe, according to a long set of instructions that I could provide but not explain. Unfortunately, the only copies of the linux versions were on the hard drive, so I couldn't repeat that unless (until) I can suck the files off the lost drive. There's a good possibility of retrieving those files, along with the data files I want, thanks to a friend. And I probably won't even keep the drive as a win/linux combo, but start over again with two drives. But I'd still like to know where I went wrong and if there's a way to reverse it. Thanks, Greg doug waud wrote: > Hi Greg > > Gregory Avedissian wrote: > >> Yup. I blew it away. I had win98 and suse 8.2 on the same hard drive, >> booting linux from floppy. Noticed that I could no longer boot windows >> from the hard drive, so I attemted to restore the mbr that I'd saved >> earlier. > > > You don't say how you tried to "restore" but it sounds like you might > have tried to do it within SuSE by copying the mbr copy SuSE makes into > the mbr space. If so, you still have another option. You can use windows > fdisk as > fdisk /mbr > You may then have to do something to get command.com and msdos.sys files > back into place; I think the command is > > sys c: > > but am not sure (long time since I have played with Windows) (i.e. > sometimes just the fdisk /mbr is not enough). I believe all this > requires a dos/windows boot disk which should have the requisite tools > on it. Read the manual to confirm that sys command :-) > > Also, can you boot into Linux (you made a boot disk didn't you) and > simply run LILO. > > Try the simple things before screwing around with parted. > > Finally, it is generally a good idea to be more specific about what you > did to get into trouble and what you have tried. It makes Dx and Rx > easier for the reader. > > doug > > PS now you know why it is a good idea to have a hard copy of /etc/fstab > and of the output of fdisk -l for each hard drive in your system! :-) > > PPS My spelling checker thinks fdisk should be frisk and sys should be > sighs. :-) > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

July 24, 2004