search

rainestorme / murkmod

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

sed: couldn't write 118 items to /usr/bin/sedUmOhcx: No space left on device #112

Open xytrux opened 4 days ago

xytrux commented 4 days ago

Describe the bug Apparently when updating murkmod, it mentions that there is no space left on a directory that just does not exist.

To Reproduce Steps to reproduce the behavior:

  1. Go to mush
  2. Go to 25
  3. Error

Expected behavior Updating murkmod

Screenshots If applicable, add screenshots or videos of the problem to help explain your situation.

System (please complete the following information):

Additional context Add any other context about the problem here.

Packjackisback commented 3 days ago

Are there any other messages before that?

Eboi47 commented 3 days ago

It would help if you put the full terminal output here, this would help determine the source of the error.

xytrux commented 3 days ago

Closing as I had to reinstall everything again (maybe fixed but still cannot update.)

xytrux commented 3 days ago 
Welcome to mush, the murkmod developer shell.

If you got here by mistake, don't panic! Just close this tab and carry on.

Do you want to use the default ChromeOS bootsplash? [y/N] n

Updating to 16033.58.0. THIS MAY DELETE ALL USER DATA! Press enter to confirm, Ctrl+C to cancel.

Dumping emergency revert backup to stateful (this might take a while)...
Finding correct partitions...
Connection to 127.0.0.1 closed.
Dumping kernel...
dd: failed to open 'p': No such file or directory
Connection to 127.0.0.1 closed.
Dumping rootfs...
dd: failed to open 'p1': No such file or directory
Connection to 127.0.0.1 closed.
Creating restore flag...
Connection to 127.0.0.1 closed.
Connection to 127.0.0.1 closed.
Backups complete, actually updating now...
Connection to 127.0.0.1 closed.
Downloading 16033.58.0 from "https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_16033.58.0_trogdor_recovery_stable-channel_mp-v14.bin.zip"...
Pseudo-terminal will not be allocated because stdin is not a terminal.
1644425728 bytes (1.6 GB, 1.5 GiB) copied, 358 s, 4.6 MB/s 

3216718+1 records in
3216718+1 records out
1646960013 bytes (1.6 GB, 1.5 GiB) copied, 358.954 s, 4.6 MB/s
Unzipping update binary...
Pseudo-terminal will not be allocated because stdin is not a terminal.
4861134848 bytes (4.9 GB, 4.5 GiB) copied, 69 s, 70.5 MB/s 
gzip: stdin: invalid compressed data--length error

9693869+0 records in
9693869+0 records out
4963260928 bytes (5.0 GB, 4.6 GiB) copied, 69.9774 s, 70.9 MB/s
Connection to 127.0.0.1 closed.
Invoking image patcher...
                      __                      .___
  _____  __ _________|  | __ _____   ____   __| _/
 /     \|  |  \_  __ \  |/ //     \ /  _ \ / __ | 
|  Y Y  \  |  /|  | \/    <|  Y Y  (  <_> ) /_/ | 
|__|_|  /____/ |__|  |__|_ \__|_|  /\____/\____ | 
      \/                  \/     \/            \/

        The fakemurk plugin manager - v6.1.1
/usr/share/vboot/bin/ssd_util.sh
Not using a custom bootsplash.
Will unfuck stateful partition upon boot.
Creating loop device...
/dev/loop9
Setting up loop with /dev/loop9 and /mnt/stateful_partition/update_tmp//image.bin
Disabling kernel verity...
DEBUG: Prerequisite check
DEBUG: Probing Kernel B information
DEBUG: Reading Kernel B from partition 4
DEBUG: Checking if Kernel B is valid
DEBUG: Changing boot parameter to remove rootfs verification
DEBUG: New kernel config: console= loglevel=7 init=/sbin/init cros_secure drm.trace=0x106 root=PARTUUID=%U/PARTNROFF=1 rootwait rw dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=0 dm="1 vroot none ro 1,0 5324800 verity payload=ROOT_DEV hashtree=HASH_DEV hashstart=5324800 alg=sha256 root_hexdigest=582a4097a2516ad5165d9cedaf2889c90077ec5ade43c936b312544e4a08e423 salt=86cd5ffbca1de1974dae6fb0e9d0f2daf8c99a035aa66a486b486d575f51e86f" noinitrd vt.global_cursor_default=0 kern_guid=%U cros_lsb_release_hash=Vfvu47yb64v7NyuqCTag5RuoAwGjzgEzbLWj62nO36c= cpuidle.governor=teo irqchip.gicv3_pseudo_nmi=1
ssd_util.sh: INFO: Kernel B: Disabled rootfs verification.
DEBUG: Removing rootfs verification for legacy boot configuration.
DEBUG: Re-signing Kernel B from /tmp/tmp.RAUd0eX9Fm to /tmp/tmp.OYcu9Lc9AQ
DEBUG: Using key: /usr/share/vboot/devkeys/kernel_data_key.vbprivk
DEBUG: Creating new kernel image (vboot+code+config)
DEBUG: for debug purposes, check *.dbgbin
DEBUG: Verifying new kernel and keys
DEBUG: Backup old kernel blob
ssd_util.sh: INFO: Backup of Kernel B is stored in: /mnt/stateful_partition/cros_sign_backups/kernel_B_20241121_170809.bin
DEBUG: Writing Kernel B to partition 4
DEBUG: Make the root file system writable if needed.
DEBUG: Non-ext2 partition: /dev/loop95, skip.
ssd_util.sh: INFO: Kernel B: Re-signed with developer keys successfully.
DEBUG: Complete.
ssd_util.sh: INFO: Successfully re-signed 1 of 1 kernel(s)  on device /dev/loop9.
ssd_util.sh: INFO: Please remember to reboot before updating the kernel on this device.
Enabling RW mount...
DEBUG: Prerequisite check
DEBUG: Probing Kernel A information
DEBUG: Reading Kernel A from partition 2
DEBUG: Checking if Kernel A is valid
ssd_util.sh: INFO: Skipping resign for /dev/loop9
ssd_util.sh: INFO: dev: /dev/loop9 658505728
ssd_util.sh: INFO: Disabling rootfs ext2 RO bit hack
DEBUG: Complete.
Mounting target...
Staging populator...
Murkmod-ing root...
Disabling autoupdates...
Installing startup scripts...
Detected newer version of CrOS, using new chromeos_startup
Installing murkmod components...
Installing startup services...
Installing other utilities...
Chmod-ing everything...
Done.
Adding murkmod bootsplash...
Done. Have fun.
exiting successfully
Connection to 127.0.0.1 closed.
Connection to 127.0.0.1 closed.
Connection to 127.0.0.1 closed.
Performing update...
Overwriting partitions in 3 (this is your last chance to cancel)...2...1...
Installing kernel patch to p...
65536+0 records in
65536+0 records out
33554432 bytes (34 MB, 32 MiB) copied, 0.193174 s, 174 MB/s
Connection to 127.0.0.1 closed.
Installing root patch to p1...
359514624 bytes (360 MB, 343 MiB) copied, 2 s, 180 MB/s
dd: writing to 'p1': No space left on device
740217+0 records in
740216+0 records out
378990592 bytes (379 MB, 361 MiB) copied, 2.16029 s, 175 MB/s
Connection to 127.0.0.1 closed.
Setting kernel priority...
ERROR: missing drive argument
Connection to 127.0.0.1 closed.
ERROR: missing drive argument
Connection to 127.0.0.1 closed.
ERROR: invalid argument to -i: "-P"

Usage: cgpt add [OPTIONS] DRIVE

Add, edit, or remove a partition entry.

Options:
  -D NUM       Size (in bytes) of the disk where partitions reside;
                 default 0, meaning partitions and GPT structs are
                 both on DRIVE
  -i NUM       Specify partition (default is next available)
  -b NUM       First block (a.k.a. start of partition)
  -s NUM       Size (in blocks)
  -t GUID      Partition Type GUID
  -u GUID      Partition Unique ID
  -l LABEL     Label
  -S NUM       set Successful flag (0|1)
  -T NUM       set Tries flag (0-15)
  -P NUM       set Priority flag (0-15)
  -R NUM       set Required flag (0|1)
  -B NUM       set Legacy Boot flag (0|1)
  -A NUM       set raw 16-bit attribute value (bits 48-63)

Use the -i option to modify an existing partition.
The -b, -s, and -t options must be given for new partitions.

The partition type may also be given as one of these aliases:

    firmware    ChromeOS firmware
    kernel      ChromeOS kernel
    rootfs      ChromeOS rootfs
    data        Linux data
    basicdata   Basic data
    reserved    ChromeOS reserved
    efi         EFI System Partition
    unused      Unused (nonexistent) partition
    minios      ChromeOS miniOS
    hibernate   ChromeOS hibernate

Connection to 127.0.0.1 closed.
Setting crossystem and vpd block_devmode...
Connection to 127.0.0.1 closed.
Connection to 127.0.0.1 closed.
Cleaning up...
Connection to 127.0.0.1 closed.
Done! Press enter to continue.
xytrux commented 3 days ago

Crazy

xytrux commented 3 days ago 

                      __                      .___
  _____  __ _________|  | __ _____   ____   __| _/
 /     \|  |  \_  __ \  |/ //     \ /  _ \ / __ | 
|  Y Y  \  |  /|  | \/    <|  Y Y  (  <_> ) /_/ | 
|__|_|  /____/ |__|  |__|_ \__|_|  /\____/\____ | 
      \/                  \/     \/            \/

        The fakemurk plugin manager - v6.1.1
Checking for emergency shell...
Installing patched files...
Checking for legacy fakemurk daemon...
Creating stateful partition files...
Patching policy...
Use murkmod reccomended pollen config? [Y/n] y
Setting chronos user password...
New password: Retype new password: passwd: Authentication token manipulation error
passwd: password unchanged
Checking sudo perms...
chronos ALL=(ALL) NOPASSWD: ALL
Looks like sudo permissions are already set correctly.
Setting crossystem cros_debug...
sed: couldn't write 118 items to /usr/bin/sedGEN8qu: No space left on device
cat: /mnt/stateful_partition/fakemurk_version: No such file or directory

Analytics collected.
Done. If cros_debug was enabled for the first time, a reboot may be required. Press any key to exit.

this is the initial error