FAT32 Issues with ReactOS crashes/bsod and Scandisk 98 or XP chkdsk

Ask your support questions in here

Moderator: Moderator Team

Post Reply
floogy
Posts: 4
Joined: Mon Oct 04, 2021 3:39 am

FAT32 Issues with ReactOS crashes/bsod and Scandisk 98 or XP chkdsk

Post by floogy »

Hi. Im relatively new to ReactOS. I normally only try ReactOS in virtualbox for a short time to see possibl progress in development.

I'm using reactos-bootcd-0.4.15-dev-4557-g884356a-x86-gcc-lin-dbg

Now I'm working on a retro computer, which was not exactly the setup of my first complete system in early 2000. Back in Time I bought a Medion MT4 MT40 PIII 667MHz, Mainboard MD2000 (MSI 6318), Chipsatz VIA Apollo Pro 133A with 256MB. But I found a Medion/Lifetec PC Life PII 400Mhz Sys22 MSN: 1000 0689 with Intel SR440BX Mainboard and a Pentium III 450 MHz CPU (exchanged due to Browser-Support with SSE) and 512MB SDRAM.

I inserted two IDE HDDs, which I partitioned and formatted under Ubuntu 20.04LTS on my newer i5 PC.

I installed successfully twice on each HDD ReactOS, but it crashed on my experiments to get the Samba package working. I thought, that might brake the file systems. Therefore I started a Windows 98 floppy disk, which contains fdisk, format, and scandisk. I had issues to get access to partition C: (512, FAT16, Hd0), D: (4GB, one of 6 partitions of 33GB/160GB hd0) and F: (4GB whole hd1). I could repair Partition F: with scandisk (win '98), but C: wasn't accessible to scandisk.

Then I exchanged Hd0 with a harddisk with a Windows XP System, and it was able to repair and access all drives, like reactOS. I also exchanged Hd1 with hd0 to repair all other drives.

The files are reappearing, but under Windows 98 floppy with DOS 7.10 on a partition with many files and directories I can still only see one empty folder and can still not access to C: (512MB, FAT16). What's that?

Is this due to the usage of fdisk and mkfs.vfat under linux? The Drives are above limit for Windows 98 floppy Disk (I think DOS 7.10)?

ReactOS could read those partitions (FAT16, FAT32).

But on reinstallation and choosing NOT to repartition and reformat, it seems to freeze, once on 1%, once on 2% and now at 100% copying the files.

I don't unstand it. There is a patch with ME scandisk and defrag files for Windows 98 for Huge Harddisks at MDGX. But there is the limit at 137GB?
MadWolf
Posts: 688
Joined: Sat Dec 31, 2005 4:19 am
Contact:

Re: FAT32 Issues with ReactOS crashes/bsod and Scandisk 98 or XP chkdsk

Post by MadWolf »

hi
I have windows 98se lite installed on VirtualBox I have attached the ReactOS hard drive to the VM and Windows 98 has no problem seeing the drive I can see all the files on the drive and Scandisk has no problem scanning the drive

maybe it is a problem with the driver the windows 98 boot disk uses for the hard drive controller or it is the boot disk you are using
floogy
Posts: 4
Joined: Mon Oct 04, 2021 3:39 am

Re: FAT32 Issues with ReactOS crashes/bsod and Scandisk 98 or XP chkdsk

Post by floogy »

I guess the issue may comes from partitioning the drive in linux. XP and ReatOS don't have such an issue to access the fat partitions.

Here is someone with a similar issue.
https://www.vogons.org/viewtopic.php?t=60952

I also had to left a >510MB unallocated space, because in that aerea are a lot of bad sectors.
Also I got more than 1 Primary partiton, because I thought to need it for booting multiple OSes.

Code: Select all

| p1 FAT16 t:6 | p2 FAT 32 t:c | unalloc | p4 ext4 t:83 || p3 ext partition t:5 | p5 swap t:82 | p6 FAT32 t:c | || 
| 512MB        | 3,3GB         | 510MB   | 12GB         || 15,2GB               | 4GB          | 11,2GB       | || 
I'll may try to align the partitions or recreate them. I don't know. Or experimenting in virtualbox, because the old computer is slooow.

Code: Select all

floogy@ubuntu-SSD1:~$ sudo sfdisk --dump /dev/sdh > /media/floogy/My\ Book/Data/outsourced\ data/images/SAMSUNG-SP1624N-160GB-33GB_sn-S0BGJ10L201400_firm-UZ100-04-6p_reactos_p6.sfd
[sudo] Passwort für floogy: 
floogy@ubuntu-SSD1:~$ file /media/floogy/My\ Book/Data/outsourced\ data/images/SAMSUNG-SP1624N-160GB-33GB_sn-S0BGJ10L201400_firm-UZ100-04-6p_reactos_p6.sfd
/media/floogy/My Book/Data/outsourced data/images/SAMSUNG-SP1624N-160GB-33GB_sn-S0BGJ10L201400_firm-UZ100-04-6p_reactos_p6.sfd: ASCII text
floogy@ubuntu-SSD1:~$ cat /media/floogy/My\ Book/Data/outsourced\ data/images/SAMSUNG-SP1624N-160GB-33GB_sn-S0BGJ10L201400_firm-UZ100-04-6p_reactos_p6.sfd
label: dos
label-id: 0x5f0e6f3f
device: /dev/sdh
unit: sectors

/dev/sdh1 : start=        2048, size=     1048576, type=6
/dev/sdh2 : start=     1050624, size=     6951877, type=c
/dev/sdh3 : start=     9059000, size=    25163080, type=83
/dev/sdh4 : start=    34222080, size=    31833164, type=5
/dev/sdh5 : start=    34224128, size=     8388608, type=82
/dev/sdh6 : start=    42614784, size=    23440460, type=c
floogy@ubuntu-SSD1:~$ sudo fdisk -l /dev/sdh
Festplatte /dev/sdh: 31,51 GiB, 33820284928 Bytes, 66055244 Sektoren
Festplattenmodell: SP1624N         
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: dos
Festplattenbezeichner: 0x5f0e6f3f

Gerät      Boot   Anfang     Ende Sektoren Größe Kn Typ
/dev/sdh1           2048  1050623  1048576  512M  6 FAT16
/dev/sdh2        1050624  8002500  6951877  3,3G  c W95 FAT32 (LBA)
/dev/sdh3        9059000 34222079 25163080   12G 83 Linux
/dev/sdh4       34222080 66055243 31833164 15,2G  5 Erweiterte
/dev/sdh5       34224128 42612735  8388608    4G 82 Linux Swap / Solaris
/dev/sdh6       42614784 66055243 23440460 11,2G  c W95 FAT32 (LBA)
Last edited by floogy on Tue May 17, 2022 9:36 pm, edited 1 time in total.
Post Reply

Who is online

Users browsing this forum: No registered users and 26 guests