Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This is not a big problem - it's an irritation, because it slows boot time. More irritating is the fact that I'm not sure how it happened.
I was busy installing Windows 2000 on VFAT (I only use it to test ASP.NET stuff for go-mono.org) although it's better than every other offering of theirs. Aneeway, I get this message now on startup:
Code:
Dec 30 18:44:21 localhost fsck: dosfsck 2.8, 28 Feb 2001, FAT32, LFN
Dec 30 18:44:21 localhost fsck: There are differences between boot sector and its backup.
Dec 30 18:44:21 localhost fsck: Differences: (offset: original/backup)
Dec 30 18:44:21 localhost fsck: 90:33/fa, 91:c9/33, 92:8e/c9, 93:d1/8e, 94:bc/d1
Dec 30 18:44:21 localhost fsck: , 97:8e/7b, 98:c1/8e, 99:8e/c1, 100:d9/bd
Dec 30 18:44:21 localhost fsck: , 105:4e/00, 106:02/1e, 107:8a/56, 108:56/16
Dec 30 18:44:21 localhost fsck: , 111:08/22, 112:cd/05, 113:13/89, 114:73/7e
Dec 30 18:44:21 localhost fsck: , 117:ff/4e, 118:ff/02, 119:8a/b1, 120:f1/0b
And much, much more. When I first tried to correct this with fsck.vfat it asked me which to copy, backup to original or original to backup. Technically that's a confusing question, as your original is your backup and the new is the err, new, isn't it?
So I can't make this problem go away now because presumably, the original is the same as the backup. (I'm assuming fsck.vfat is talking about the offset of the mbr, but grub is installed there).
Windows is not so hot at managing it's boot sector, and Windows 2000 doesn't even have fdisk. To make sure it was repaired properly I used the Win2000 disk and went into repair mode.
Run fsck.vfat in Linux with the -ar switches to write the repair to the disk.
After that of course, you can re-write the mbr with grub or lilo or whatever.
The moral of the story is: Windows 2000 is really rubbish at managing itself at the partition level.
I know everyone was very anxious to get a solution for that one. Phew!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.