Closed coolestDude19 closed 1 week ago
I'm not sure what could cause this issue, can you run fdisk -l
and losetup -f
and send over the outputs?
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.
Ok. I'll try a few things to see if I can fix that but thanks for the help.
im gay. not
the same thing has happened to me, boten (after recovering to v129)
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.
having this same issue (octopus fleex on v130)
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.
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)
Yep, I found the patch - see codesearch. I can add a workaround in just a second.
Yep. Just head -2 | tail -1
My repo has the fix, I can make a pr if needed
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:
Expected behavior I expected it to create a loop partition and install murkmod successfully
Screenshots In comments
System
Additional context None