rainestorme / murkmod

A continuation of fakemurk and mush that includes a plugin manager and additional useful utilities.
MIT License
21 stars 17 forks source link

failed to create loop partition #93

Closed coolestDude19 closed 1 week ago

coolestDude19 commented 1 month ago

Describe the bug After the devmode installer finishes downloading the chromeOS recovery image, it fails when it tries to create a loop partition

To Reproduce Steps to reproduce the behavior:

  1. Go to 'the devmode installer'
  2. Click on 'any option'
  3. Wait for it to 'finish downloading the recovery image'
  4. See error

Expected behavior I expected it to create a loop partition and install murkmod successfully

Screenshots In comments

System

Additional context None

coolestDude19 commented 1 month ago

IMG_20241011_18344082

rainestorme commented 1 month ago

I'm not sure what could cause this issue, can you run fdisk -l and losetup -f and send over the outputs?

coolestDude19 commented 1 month ago

IMG_20241012_13084050 IMG_20241012_13085857

rainestorme commented 1 month ago

Interesting. Your losetup appears to be printing FINDING FREE!!!, which is absolutely not supposed to happen. I have no idea what could possibly cause this, and testing on my own octopus device yields no result. Seeing as I can't reproduce this, I'll close this issue. If someone else has the same problem, please comment.

coolestDude19 commented 1 month ago

Ok. I'll try a few things to see if I can fix that but thanks for the help.

ifee11ikeiediagcmdrn commented 1 month ago

im gay. not

baseattackforce commented 1 month ago

the same thing has happened to me, boten (after recovering to v129)

baseattackforce commented 1 month ago

for context, i had previously installed murkmod, but it was stuck on the "chrome" bootsplash screen, so i recovered to latest using a drive and tried to reinstall murkmod and i got this error.

kingofnetflix commented 1 week ago

having this same issue (octopus fleex on v130)

rainestorme commented 1 week ago

Anyone having this issue - please run losetup -f and post the exact text of the results. You can most likely accomplish this with these commands (in vt2, as root, after logging into the system):

touch /home/chronos/user/Downloads/losetup_output.txt
losetup -f > /home/chronos/user/Downloads/losetup_output.txt
chmod 777 /home/chronos/user/Downloads/losetup_output.txt

Then the output file will be in your Downloads folder which you can upload here. This is only necessary because I need to be able to see the exact spacing that's used by this quirky little implementation of losetup - I can't find any instance of this in the main util-linux repo.

kingofnetflix commented 1 week ago

Anyone having this issue - please run losetup -f and post the exact text of the results. You can most likely accomplish this with these commands (in vt2, as root, after logging into the system):

touch /home/chronos/user/Downloads/losetup_output.txt
losetup -f > /home/chronos/user/Downloads/losetup_output.txt
chmod 777 /home/chronos/user/Downloads/losetup_output.txt

Then the output file will be in your Downloads folder which you can upload here. This is only necessary because I need to be able to see the exact spacing that's used by this quirky little implementation of losetup - I can't find any instance of this in the main util-linux repo.

There was no /home/chronos/user/Downloads/, but the output of losetup -f was so small that I can just type it here:

FINDING FREE!!!
/dev/loop11

I also got it to say /dev/loop12 (I think I logged in and logged out), but I rebooted and logged in and it showed that above. Just rebooting without logging in outputs /dev/loop10 instead. They all still output FINDING FREE!!!.

IMO, I suspect it's something to do with the newer versions of ChromeOS. I tried this same thing on my octopus board with v107 and it didn't fail. Unfortunately, v107 is too old for my district as I require a immediate update.

If you need extra information, I am on ChromeOS v130 at the time running this script and using the 'latest version' option (I also spoofed my kernver to 1 with SH1MMER Legacy, developer mode unblocked)

rainestorme commented 1 week ago

Yep, I found the patch - see codesearch. I can add a workaround in just a second.

Packjackisback commented 1 week ago

Yep. Just head -2 | tail -1

Packjackisback commented 1 week ago

My repo has the fix, I can make a pr if needed