Uploaded image for project: 'Core ReactOS'
  1. Core ReactOS
  2. CORE-14036

Virtual PC 2004, Floppy: random failures to access disk image after boot. (regression)

    Details

    • Type: Bug
    • Status: Untriaged
    • Priority: Critical
    • Resolution: Unresolved
    • Fix Version/s: 0.4.8
    • Component/s: Drivers
    • Labels:
    • Environment:

      Virtual PC 2004 SP1 (5.3.582.27)

      Description

      Noticed while testing after CORE-12908 fix, which is made impractical (as in blocked) by the current issue.

      Steps:

      1. Setup VPC with both CD image and Floppy image.
      2. Fully boot CD > ReactOS.
      3. Open Command Prompt
      4. dir A:
      5. chkdsk A:

      Results (are not all 100% confirmed, but enough to get the idea):

      Always works:
      (as much as I tested)
      livecd-76032
      livecd-0.4.7-dev-514-gc609406
      livecd-0.4.7-dev-518-g75f1637
       
      Random failure:
      (sometimes/often: dir fails, chkdsk succeeds, then dir succeeds.
      Or: dir succeeds, chkdsk fails.)
      livecd-0.4.7-dev-525-g1e2424e
      livecd-0.4.7-dev-550-g85d9a38
      livecd-0.4.7-dev-600-gb5289a2
      livecd-0.4.7-dev-646-gc15036c
      livecd-0.4.7-dev-711-g959d9c6
      livecd-0.4.8-dev-135-g0b2bbd1
      livecd-0.4.8-dev-187-g4b34e44
      livecd-0.4.8-dev-189-gf884d29
      livecd-0.4.8-dev-190-gdfb7763
       
      Always(?) broken:
      (dir and/or chkdsk seem to deal with corrupted data.)
      livecd-0.4.8-dev-194-g748c872
      

      2 examples:

      Bad-Good case seems to be about
      floppy/ioctl.c:259) UNKNOWN IOCTL CODE: 0x240nn.

      (ntoskrnl/kd/kdio.c:105) ReactOS 0.4.8-dev (Build 20171112-0.4.8-dev-135-g0b2bbd1) (Commit 0b2bbd1125a935fb50e979812d3a34cfde500882)
       
      Good-Good:
      (ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\fastfat.sys at FC0DA000 with 39 pages
       
      Bad-Good:
      (drivers/storage/floppy/ioctl.c:259) UNKNOWN IOCTL CODE: 0x24000
      (drivers/filesystems/cdfs/fsctl.c:244) Allowing mount of CDFS volume on non-CD device
      FFSLoadDiskLabel() No BSD disklabel found, trying to find BSD file system on "normal" partition.
      FFSLoadDiskLabel() No BSD file system was found on the "normal" partition.
      (drivers/storage/floppy/ioctl.c:259) UNKNOWN IOCTL CODE: 0x24000
      (drivers/filesystems/cdfs/fsctl.c:244) Allowing mount of CDFS volume on non-CD device
      FFSLoadDiskLabel() No BSD disklabel found, trying to find BSD file system on "normal" partition.
      FFSLoadDiskLabel() No BSD file system was found on the "normal" partition.
      (ntoskrnl/mm/ARM3/sysldr.c:176) Loading: \SystemRoot\system32\drivers\fastfat.sys at FC0CF000 with 39 pages
       
      One B-G test with 048-187:
      -(drivers/filesystems/cdfs/fsctl.c:244) Allowing mount of CDFS volume on non-CD device
      +(drivers/storage/floppy/ioctl.c:259) UNKNOWN IOCTL CODE: 0x24038
      

      Good-Bad case seems to be about corrupted data.

      (ntoskrnl/kd/kdio.c:105) ReactOS 0.4.8-dev (Build 20171121-0.4.8-dev-187-g4b34e44) (Commit 4b34e44782e44afe2af5277887d8e7df0d436a87)
       
      Good-Bad:
      -(sdk/lib/fslib/vfatlib/vfatlib.c:354) VfatPrint -- Starting check/repair pass.
      -(sdk/lib/fslib/vfatlib/vfatlib.c:354) VfatPrint -- Starting verification pass.
      -(sdk/lib/fslib/vfatlib/vfatlib.c:354) VfatPrint -- \??\A:: 42 files, 2364/2847 clusters
      +(sdk/lib/fslib/vfatlib/check/common.c:59) Unrecoverable problem!
      +(sdk/lib/fslib/vfatlib/vfatlib.c:354) VfatPrint -- DIE! (sdk/lib/fslib/vfatlib/check/boot.c:345) Logical sector size (63603 bytes) is not a multiple of the physical sector size.
      

        Attachments

          Activity

            People

            • Assignee:
              bug zilla Bug Zilla
              Reporter:
              Serge Gautherie Serge Gautherie
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: