Date: Sun, 9 Jun 2002 13:04:37 +0200 (SAST) From: Willie Viljoen <will@laserfence.net> To: Terry Lambert <tlambert2@mindspring.com> Cc: freebsd-fs@freebsd.org Subject: Re: Strange filesystem problem revisited... Message-ID: <20020609130117.N201-100000@phoenix.vh.laserfence.net> In-Reply-To: <3D031DC7.5C0C6C14@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Terry, strangely enough, here it does the exact reverse, one of the partitions on the FreeBSD slice (ad0s1h), /home, usually suffers from the most damage, but it can still be repaired by fsck in single user mode. This is however the last partition in the slice, and is followed directly by the first DOS partition (a Primary DOS, seen in Windows as C) which is where all the problems usually pop up, so I think you might be on to something there. The box is a very generic ATX tower, Asus P3V133 board, Intel Celeron 333, but I don't think it will use a partition for sleep, so that's most likely ruled out. From what you describe, I think the problem probably is partition overlap. How can I repair this, and which partitionion tools would you recomend, as MS fdisk certainly isn't apt for this sort of system. To get back to my first paragraph, when I say exact reverse, I mean that ad0s1h requires some fdisking, and Windows becomes completely unbootable. Will On Sun, 9 Jun 2002, Terry Lambert wrote: > Willie Viljoen wrote: > > For months, this problem seemed to dissapear, then yesterday, I > > reinstalled my windows partition (used mostly for games, so, used very > > seldom) > > > > This morning, when I got to the machine, the problem had returned. Could > > this have anything to do with the mounted FAT32 file systems? If so, why > > does it not appear when those FAT32s are mounted, but have nothing on > > them? > > Most likely, the Windows partition overlaps the BSD partition, > or there is a difference in observed geometry between the BSD > and DOS view of the drive. The other alternative is that it's > "just coincidence" (unlikely). > > You didn't say what the box was. If you enabled power management, > the BSD partition may be being used by the box as the "sleep" > partition (old IBM Thinkpad BIOS identified the first non-DOS > partition as the sleep partition, for example). So turning on APM > may have caused the problems (also unlikely: generally, such an > occurance would render the FreeBSD partition unbootably corrupt). > > -- Terry > > > -- Willie Viljoen Private IT Consultant 214 Paul Kruger Avenue Universitas Bloemfontein 9321 South Africa +27 51 522 15 60, a/h +27 51 522 44 36 +27 82 404 03 27 will@laserfence.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020609130117.N201-100000>