Date: Tue, 28 Sep 2004 13:37:22 -0700 From: "Darren Pilgrim" <dmp@bitfreak.org> To: "'Roman Kurakin'" <rik@cronyx.ru>, "'Dimitry Andric'" <dimitry@andric.com> Cc: current@FreeBSD.ORG Subject: RE: "NTLDR missing" after 5-RELEASE install Message-ID: <000201c4a59a$f8294f60$162a15ac@spud> In-Reply-To: <41591FFE.3040206@cronyx.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
[ Note to Roman: Please adjust your mail client to wrap lines at more acceptable range of 72-76 characters. Thanks. ] From: Roman Kurakin > > I've seen this before 5.0 release and made some investigation of this > proble. I didn't look this thread carefully so excuse me if information > I give to all you is useless. > > My investigation show that FreeBSD reads full partition table, and after > modification puts it back. It fix all entries from its own point of view. > Windows dies from change of end of partition entry. As I understand with > large disk it shouldn't mean anything at all. But windows checks it. You > may save this entry and after installation of FreeBSD put it back. Just like in UFS, there are structures in NTFS that have to be changed if the size of the volume changes. Also like UFS, NTFS doesn't place data sequentially on the disk. A large, mostly-empty, NTFS volume can have data at or near the end of the volume. The slicing issue is well-known with NTFS. A reliable way to add a non-Windows slice to a computer with Windows installed is to use a volume management tool like PM. If you don't need to resize a slice, use the Disk Management administrative tool to create an unformatted partition, then change the media descriptor when you go to install FreeBSD. NT is so picky it's even recommended that you use the NT boot loader.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000201c4a59a$f8294f60$162a15ac>