Hallo Eric,
ich verstehe es einfach nicht: Erst erhalte ich unter Qemu und Virtualbox ständig diese Fehler beim Ausführen von Format - und plötzlich sind sie weg.
Was bedeuten diese Error 36, und 129 sowie
+***bad sectors: 1 (code 0x201) on WRITE
+***bad sectors: 1 (code 0x201) on READ
One of the first 5 sectors is broken. Format not possible
bzw. unknown unit for driver
Wie können solche Fehler in einer vhd passieren? Ich arbeite mit SSD-Festplatten. Wo kann ich bei der Fehlersuche ansetzen?
Bei der Suche ist mir aufgefallen, daß ich bei mehreren Festplatten im System mit jeweils einer primären Partition mit fdisk ALLE Festplatten auf
AKTIV setzen kann, ohne daß sich FreeDOS daran stört. Das war mir neu. Es startet einfach von der ersten Festplatte im System.
Gruß
Willi
Sent: Sunday, July 11, 2021 at 12:16 AM
From: "Wilhelm Spiegl" <wilhelm.spi...@mail.com>
To: freedos-devel@lists.sourceforge.net
Subject: Re: [Freedos-devel] FDISK issue
From: "Wilhelm Spiegl" <wilhelm.spi...@mail.com>
To: freedos-devel@lists.sourceforge.net
Subject: Re: [Freedos-devel] FDISK issue
Sorry for disturbing once again.
The vhd formatted by Windows 10 (FAT) Nr. 2 does not give out an error message when booting without fdconfig / fdautoexec.bat.
Willi
Beer will follow now!
Sent: Sunday, July 11, 2021 at 12:02 AM
From: "Wilhelm Spiegl" <wilhelm.spi...@mail.com>
To: freedos-devel@lists.sourceforge.net
Subject: Re: [Freedos-devel] FDISK issue
From: "Wilhelm Spiegl" <wilhelm.spi...@mail.com>
To: freedos-devel@lists.sourceforge.net
Subject: Re: [Freedos-devel] FDISK issue
Now it becomes absolutely confusing:
format d: /u says:
Full formatting (wiping all data)
Zapping / checking 443889 sectors and after a standard message
[Error 36]
I repeated with format d: /u /d:
FAT1x size: 217, using FAT16
Disk size 217MBytes, FAT16
[debug] enabled accessing flags
...
Full formatting (wiping all data)
Zapping / checking 443889 sectors and after a standard message
+***bad sectors: 1 (code 0x201) on WRITE
+***bad sectors: 1 (code 0x201) on READ
One of the first 5 sectors is broken. Format not possible
Repeated once again:
format d: /q /d
...
Warning: Resets cluster marks, if any
File system creation
Boot sector -> 0
Drive_IO (Write 0 Count 1) [FAT12/16] (drive d)
critical error during DOS disk access
DOS driver error (hex):01
Description: Unknown unit for driver
Program terminated
Same problem with 484 MB partition (other virtual machine).
Format d:
/q /u exits with error 129,
/u exits with error 36,
/y exits with error 129,
/q /d with the unknown unit for driver
/u /d with the bad sectors
When removing the vhd from virtualbox and adding the vhd as hd at Win10 it asks for formatting.
Windows HD manager says: 484 MB RAW, no failures, active, primary partition, so these settings seem to be correct.
After formatting by Windows 10 the vhd works fine in FD as drive d. I added files an ran chkdsk, no problem.
Win-result: 507.535.360 Bytes,
8.192 Bytes per cluster,
61955 total clusters
If I have a little time I will try if the problem also occurs with the first HD when creating a partition from diskette.
Willi
Cheers! But with more alcohol (5 percent - no ... water...now!)
Sent: Saturday, July 10, 2021 at 10:38 PM
From: "Eric Auer" <e.a...@jpberlin.de>
To: freedos-devel@lists.sourceforge.net
Subject: Re: [Freedos-devel] FDISK issue
From: "Eric Auer" <e.a...@jpberlin.de>
To: freedos-devel@lists.sourceforge.net
Subject: Re: [Freedos-devel] FDISK issue
Hi!
> Boot sector unreadable, disk not yet formatted.
You can skip that check by explicitly requesting a
not undoable formatting, see FORMAT /? and use /U
or better /Q /U for quick unconditional format.
> Cannot find existing format - Not saving UNFORMAT data. Please enter
> volume label (none) etc. No label, disk will have no creation timestamp.
> Quick formatting (only flushing metadata)
> Warning, resets bad cluster markings, if any
> DRIVE_IO (WRITE 0, count 1) [FAT12(16] [drive D*]
> Critical error during DOS disk access
> DOS driver error (hex):01
> Description: unknown unit for driver
> Program terminated.
> [Error 129]
So it tries to use FAT16 access for FAT32 drives?
As you say /D made no difference, did /D display
useful extra details? D for debug mode, that is.
If I understand you correctly, you tried to make
tha partition FAT32 in FDISK? Have you checked if
it worked by looking at the FDISK status after a
reboot?
> format version is 0.91w
> Same results with format d: /d
This version is the first which uses OpenWatcom C,
can you check whether FORMAT 0.91v works better?
> If I do the same with a bigger virtual HD (ca. 550 MB size) fdisk
> creates a FAT32 partition and format has NO problems.
> I tried both two times.
>
> Any ideas? Is it reproducable?
As said, please compare FORMAT 0.91v here. You should
also ask WHICHFAT D: to see which partition type the
DOS kernel wants for D: or you could even check whether
using a non-FreeDOS kernel makes a difference for you.
Whichfat: https://auersoft.eu/soft/specials/
Format 0.91v: https://auersoft.eu/soft/by-others/
Regards, Eric
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
_______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
