[Freedos-user] re: FDISK Corruption - possible smoking gun
Hi (your last mail to the -user list was in html, oops), FreeDOS is right to complain here: There is an official partition type for FAT16 LBA, but you have a partition which is marked as FAT16 CHS while at the same time reaching beyond the 1024 cylinders that CHS can reach! WinXP seems to just ignore the problem. FreeDOS shows a warning and tries to ignore the problem, too, but somehow crashes. Partition Status Mbytes Description Usage Start Cyl End Cyl 1 20 16 Hidden FAT16 0% 0 1 3 7 A 27980 NTFS 98% 16 3582 C: 4 6 494 FAT16 2% 3584 3646 start/end cyl are 1023 WARNING: partition Pri: 4 FS 06 has CHS:3584-0-1 not 1023-254-63 WARNING: partition Pri: 4 FS 06 has CHS:3546-254-63, not 1023-254-63 3646, I assume? WARNING: partition Pri: 4 FS 06 is not LBA Please run FDISK to correct this - using LBA to access partition start 3584-0-1, end 3646-254-63 C:HD1, Pri [ 4], CHS: 3584-0-1, start=28113 MB, size=494 MB Those messages are far too verbose if you ask me! It would have been enough to show only: Partition should be marked as LBA, use FDISK to correct this: start 3584-0-1, end 3646-254-63 C:HD1, Pri [ 4], CHS: 3584-0-1, start=28113 MB, size=494 MB This would already contain all required information (you can add, optionally, the overall drive geometry to the start 3584-0-1, end 3646-254-63 line). Would be nice if Jeremy could reduce the error message verbosity here :-) PS: This is NOT a smoking gun. Your partition table is wrong, but in a mild way, which WinXP fixes silently and which FreeDOS complains about. Nothing caused by FDISK, though. (fixes as in assumes the right value - WinXP does not fix the data on disk. Actually MS FDISK is SO caring / crazy that if you create a FAT16 partition but format it with a FAT32 filesystem, their FDISK will pretend that the partition table would show the correct FAT32 value...) Eric --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] re: FDISK Corruption - possible smoking gun
The original post I sent was the output of FDISK from
booting Beta9SR1. The first time, no complaints.
Current fixed disk drive: 1 (TC: 3648 TH: 254 TS: 63)
Partition Status Mbytes Description Usage Start Cyl End Cyl
1 20 16 Hidden FAT16 0% 0 1
3 7 A 27980 NTFS 98% 16 3582
C: 4 6 494 FAT16 2% 3584 3646
-- Original message -- Hi (your last mail to the -user list was in html, oops), FreeDOS is right to complain here: There is an official partition type for FAT16 LBA, but you have a partition which is marked as FAT16 CHS while at the same time reaching beyond the 1024 cylinders that CHS can reach! WinXP seems to just ignore the problem. FreeDOS shows a warning and tries to ignore the problem, too, but somehow crashes. Partition Status Mbytes Description Usage Start Cyl End Cyl 1 20 16 Hidden FAT16 0% 0 1 3 7 A 27980 NTFS 98% 16 3582 C: 4 6 494 FAT16 2% 3584 3646 start/end cyl are 1023 WARNING: partition Pri: 4 FS 06 has CHS:3584-0-1 not 1023-254-63 WARNING: partition Pri: 4 FS 06 has CHS:3546-254-6
3, not 1023-254-63 3646, I assume? WARNING: partition Pri: 4 FS 06 is not LBA Please run FDISK to correct this - using LBA to access partition start 3584-0-1, end 3646-254-63 C:HD1, Pri [ 4], CHS: 3584-0-1, start=28113 MB, size=494 MB Those messages are far too verbose if you ask me! It would have been enough to show only: Partition should be marked as LBA, use FDISK to correct this: start 3584-0-1, end 3646-254-63 C:HD1, Pri [ 4], CHS: 3584-0-1, start=28113 MB, size=494 MB This would already contain all required information (you can add, optionally, the overall drive geometry to the start 3584-0-1, end 3646-254-63 line). Would be nice if Jeremy could reduce the error message verbosity here :-) PS: This is NOT a smoking gun. Your partition table is wrong,
; but in a "mild" way, which WinXP fixes silently and which FreeDOS complains about. Nothing caused by FDISK, though. ("fixes" as in "assumes the right value" - WinXP does not fix the data on disk. Actually MS FDISK is SO "caring" / crazy that if you create a FAT16 partition but format it with a FAT32 filesystem, their FDISK will pretend that the partition table would show the correct FAT32 value...) Eric --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list
Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] re: FDISK Corruption - possible smoking gun
Hi Eric: OK, let's try again. I apologize profusely for the HTML formatting...I hate it myself. The darned webmail client decided I wanted it for some reason. The original post I sent was the output of FDISK from booting Beta9SR1. The first time, no complaints. Current fixed disk drive: 1 (TC: 3648 TH: 254 TS: 63) Partition Status Mbytes Description Usage Start Cyl End Cyl 1 20 16 Hidden FAT16 0% 0 1 3 7 A 27980 NTFS 98% 16 3582 C: 4 6 494 FAT16 2% 3584 3646 I must have erred in capturing the MBR before I started. (See MBR.TXT attached). The resulting MBR is NEWMBR1.TXT and I'm sure that's right...cause I went and redid it when it didn't look like the original. Recall that the first time I booted Beta9SR1 it ran fine. When I tried to boot the new kernel, it complained and then Beta9SR1 complained. It appears that either simply booting one of these, or more likely, running fdisk, did change the partition table. Is THIS plain text? Mark Hi (your last mail to the -user list was in html, oops), FreeDOS is right to complain here: There is an official partition type for FAT16 LBA, but you have a partition which is marked as FAT16 CHS while at the same time reaching beyond the 1024 cylinders that CHS can reach! WinXP seems to just ignore the problem. FreeDOS shows a warning and tries to ignore the problem, too, but somehow crashes. Partition Status Mbytes Description Usage Start Cyl End Cyl 1 20 16 Hidden FAT16 0% 0 1 3 7 A 27980 NTFS 98% 16 3582 C: 4 6 494 FAT16 2% 3584 3646 start/end cyl are 1023 WARNING: partition Pri: 4 FS 06 has CHS:3584-0-1 not 1023-254-63 WARNING: partition Pri: 4 FS 06 has CHS:3546-254-63, not 1023-254-63 3646, I assume? WARNING: partition Pri: 4 FS 06 is not LBA Please run FDISK to correct this - using LBA to access partition start 3584-0-1, end 3646-254-63 C:HD1, Pri [ 4], CHS: 3584-0-1, start=28113 MB, size=494 MB Those messages are far too verbose if you ask me! It would have been enough to show only: Partition should be marked as LBA, use FDISK to correct this: start 3584-0-1, end 3646-254-63 C:HD1, Pri [ 4], CHS: 3584-0-1, start=28113 MB, size=494 MB This would already contain all required information (you can add, optionally, the overall drive geometry to the start 3584-0-1, end 3646-254-63 line). Would be nice if Jeremy could reduce the error message verbosity here :-) PS: This is NOT a smoking gun. Your partition table is wrong, but in a mild way, which WinXP fixes silently and which FreeDOS complains about. Nothing caused by FDISK, though. (fixes as in assumes the right value - WinXP does not fix the data on disk. Actually MS FDISK is SO caring / crazy that if you create a FAT16 partition but format it with a FAT32 filesystem, their FDISK will pretend that the partition table would show the correct FAT32 value...) Eric --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user 000 33fc 8ec0 8ed8 bec0 7c00 00bf b906 0100 020 a5f3 2eea 0006 4700 4741 203a 0090 0010 040 0001 7c00 17bf 060 b406 bb0e 0007 058a 903c 0774 cd57 5f10 100 eb47 bfee 061d 3d80 7500 b45f cd02 a916 120 000f 5674 c033 d88e c08e bebe b97d 0004 140 3c80 7480 830a 10c6 f6e2 32b0 bbe9 b200 160 b480 bb41 55aa 13cd 5b72 fb81 aa55 5575 200 26bf 8b06 084c 0d89 4c8b 890a 024d 42b4 220 1ebe bb06 0003 5650 b253 cd80 7313 5b30 240 585e 754b b0f1 e931 0080 1bbb b801 1000 260 d88e c08e 03b9 5100 80ba b900 0002 02b4 300 2ab0 cd90 7313 5946 ede2 31b0 5ceb 5b90 320 585e 27eb b290 8a80 0174 4c8b bb02 0003 340 5153 bb52 7c00 01b8 cd02 7313 5a0b 5b59 360 754b b0ed eb31 9033 595a 815b fe3e 557d 400 74aa b005 eb34 9023 00ea 007c b800 1000 420 c08e 8126 1c3e 4701 7541 260d 3e83 011e 440 7547 ea05 0120 1000 33b0 07bb b400 cd0e 460 eb10 56fe 6170 7472 7469 6f69 206e 6174 500 6c62 0065 7245 6f72 2072 6f6c 6461 6e69 520 2067 706f 7265 7461 6e69 2067 7973 7473 540 6d65 4d00 7369 6973 676e 6f20 6570 6172 560 6974 676e 7320 7379 6574 006d 600 * 660 2c00 6344 3800 0100 700 0001 fede 063f 003f b708 0001 0080 720 0701 fe07 b747 0001 b178 01d4 fe00 740 fe0c 68bf 01d6 f3fd 000e fe00 760 fe05 5cbc 01e5 f644 02c2 aa55 0001000 000 fcfa c031 d08e d88e 00bd 8d7c e066 b8fb 020 1fe0 c08e ee89 ef89 00b9 f301 eaa5
