Potential issue with prl_disk_tool

Discussion in 'General Questions' started by RajivS1, Mar 6, 2021.

  1. RajivS1

    RajivS1 Bit poster

    Messages:
    4
    Hi,
    For some reason (I'm not entirely sure) my Mac restarted while my Ubuntu 18.04 VM was running. When I tried to start it again, it said that it was checking the disk for corruption. Then, about a minute later, my computer freezes and restarts. If I try to start the VM again, it tries to check the disk and the computer freezes and restarts. I tried verifying the disk with `prl_disk_tool` as mentioned in https://kb.parallels.com/113241, but that also seemed to freeze my computer. The VM is now starting again without needing to check for corruption (not sure why), but I thought I should report this issue.

    macOS 11.3 Beta (20E5196f)
    MacBook Pro (13-inch, 2018)
    Parallels Desktop 16.1.2 (49151)
     
  2. RajivS1

    RajivS1 Bit poster

    Messages:
    4
    The same issue just happened when I tried to reclaim disk space as well, so I wonder if the root cause is there.
     
  3. Maria@Parallels

    Maria@Parallels Problem solver

    Messages:
    8,115
    Hi, could you update your Parallels Desktop to the latest build and check the issue please?
     
  4. RajivS1

    RajivS1 Bit poster

    Messages:
    4
    Thanks, I think that fixed it! I didn't think to manually check the latest version as the "check for updates" button reported that I was on the newest version.
     
  5. Maria@Parallels

    Maria@Parallels Problem solver

    Messages:
    8,115
    Thanks a lot for sharing your results.
    If you have any additional questions please let us know.
     
  6. RajivS1

    RajivS1 Bit poster

    Messages:
    4
    Hi Maria, unfortunately the problem happened twice more with Parallels 16.1.3. The entire system freezes and then restarts, and it shows the following report:


    Code:
    panic(cpu 2 caller 0xffffff800894ba25): userspace watchdog timeout: no successful checkins from com.apple.logd in 120 seconds
    service returned not alive with context : unresponsive dispatch queue(s): com.apple.firehose.io-wl
    service: com.apple.logd, total successful checkins since load (481 seconds ago): 37, last successful checkin: 120 seconds ago
    service: com.apple.WindowServer, total successful checkins since load (450 seconds ago): 45, last successful checkin: 0 seconds ago
    service: com.apple.remoted, total successful checkins since load (480 seconds ago): 47, last successful checkin: 0 seconds ago
    
    Backtrace (CPU 2), Frame : Return Address
    0xffffffb097bfb670 : 0xffffff8005687f3d
    0xffffffb097bfb6c0 : 0xffffff80057ce493
    0xffffffb097bfb700 : 0xffffff80057bea6a
    0xffffffb097bfb750 : 0xffffff800562ca2f
    0xffffffb097bfb770 : 0xffffff800568775d
    0xffffffb097bfb890 : 0xffffff8005687a53
    0xffffffb097bfb900 : 0xffffff8005e95d04
    0xffffffb097bfb970 : 0xffffff800894ba25
    0xffffffb097bfb980 : 0xffffff800894b660
    0xffffffb097bfb9a0 : 0xffffff8005e175de
    0xffffffb097bfb9f0 : 0xffffff800894aa34
    0xffffffb097bfbb20 : 0xffffff8005e217fb
    0xffffffb097bfbc80 : 0xffffff8005779fc1
    0xffffffb097bfbd90 : 0xffffff800568d5bd
    0xffffffb097bfbe00 : 0xffffff8005663c25
    0xffffffb097bfbe60 : 0xffffff800567b1b2
    0xffffffb097bfbef0 : 0xffffff80057a2d8d
    0xffffffb097bfbfa0 : 0xffffff800562d216
          Kernel Extensions in backtrace:
             com.apple.driver.watchdog(1.0)[ED420E80-24C5-3763-BB5F-3D48A2C855D1]@0xffffff8008949000->0xffffff800894bfff
    
    Process name corresponding to current thread: watchdogd
    Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev
    
    Mac OS version:
    20E5196f
    
     
  7. Maria@Parallels

    Maria@Parallels Problem solver

    Messages:
    8,115
    Hey, could you collect the tech report once the issue reproduced and post the report's ID here please?
     
  8. EdE1

    EdE1 Bit poster

    Messages:
    1
    I had this issue and managed to fix it.
    When using Win10 with Parallels Version 16.1.3 (49160), when accessing a particular file in Windows, my system locked up and there was a kernel panic, causing a reboot.
    I was able to restart the VM, but there was another kernel panic when attempting to access that file.
    From then on, any attempt to restart the Windows VM at all would cause a kernel panic and a reboot.
    I tried using the prl_disk_tool to check the hdd file, but that also caused a kernel panic and a reboot every time.
    I finally solved the problem by copying the hdd file to an external drive, deleting the original file, and then copying the file back to its original location.
    From then on, the Win10 VM started with no issues, and the prl_disk_tool did not show any errors with the hdd file.
     
  9. JorgeU

    JorgeU Bit poster

    Messages:
    1
    Hell all, with a VM running WINDOWS 11 and parallels desktop 16 for Mac Standard Edition ver 16.5.1 (49187) I had the same error described above. My VM ran out of space while downloading a massive file, that made my macbook pro mid 2014 on Big Sur ver 11.5.1 (20G80) to also hang with kernel panic errors while trying to open the VM, reclaim space (59 GB), remove snapshots (99 GB) or use PRL_DISK_TOOL as described previously in this thread. I finally copied the .PVM file (180 GB) into a clean 2TB SAMSUNG SSD T7, deleted the original one from the mbp drive and put it back from the T7. I opened the new PVM file from the mac WIN11 opened smoothly. Upon shutdown I noticed the VM size was reduced to 120GB as I set it up to auto reclaim on shutdown.
     

Share This Page