Sed: write error during boot on latest generic beta

  • Can you run this command and post the result?

    Code
    1. /usr/sbin/fsck -T -M -p -a UUID=5DDB-A25D UUID=755545e4-49d7-4a92-a665-93dc96612141

    Support my work with small (or big) Paypal donation


    Amlogic devices works better with CoreELEC

    Blu-ray Disc Java menus support - forum thread, Github

    my lamp addon (unofficial/community with limited support)
    my touchscreen support and instructions by Grruhn (now touchscreen addon exists in repository)

  • There is no code change between 9.1.502 and 9.2.


    "sed: write error" is printed because /dev/kmsg refuse to been written with more than 1024 bytes at once (more than 4500 in your case).


    The error is harmless, just as the fsck error. I see two options:

    1. Ignore the error and wait for 9.2.1
    2. Boot another Linux system (i.e. from USB stick) and use fsck.fat to fix the error on file system UUID=5DDB-A25D
  • Can you run this command and post the result?

    Code
    1. /usr/sbin/fsck -T -M -p -a UUID=5DDB-A25D UUID=755545e4-49d7-4a92-a665-93dc96612141

    Hi, running that command does nothing

    Just like hitting enter on the keyboard without entering any text.


    There is no code change between 9.1.502 and 9.2.


    "sed: write error" is printed because /dev/kmsg refuse to been written with more than 1024 bytes at once (more than 4500 in your case).


    The error is harmless, just as the fsck error. I see two options:

    1. Ignore the error and wait for 9.2.1
    2. Boot another Linux system (i.e. from USB stick) and use fsck.fat to fix the error on file system UUID=5DDB-A25D

    As long as the error is harmless I'm happy to leave it as it is. Like I mentioned in a earlier post, this error was introduced in le 9.1.502

    I confirmed that be going back to le 9.1.501 when I first noticed the error and the error is not present in 9.1.501.


    What about the other 2 errors I get before the sed write error.


    Ive done a little research on these 2 and appears 1 is related to the amd vega 8 graphics that is built into my amd ryzen 3 2200g, and the other is related to VM.


    Couldn't find any answers to solve them even more so with libreelec being quite closed in terms of altering stuff via ssh.


    Thanks all.

  • Ive done a little research on these 2 and appears 1 is related to the amd vega 8 graphics that is built into my amd ryzen 3 2200g, and the other is related to VM.

    What does VM mean, and which error triggers it?

    Beast Mode

  • virtualization is what VM has something to do with which stands for virtual machine.


    That is what I believe to first error to be related to.


    The second error that says something to do with a connector is related to the vega 8 graphics.


    This is my findings on Google but I can't find fixes for these, it appears later kernels have one fixed but not the other, I'm no Linux expert I'm just going on what I have read on the Internet.


    Thanks

  • virtualization is what VM has something to do with which stands for virtual machine.

    So you use a virtual machine to run LE. I don't use VM, but there is a chance that it does an encapsulation of hardware / software, which may lead to the "system mode" (see above).


    I think LE programming will stay as close as possible on hardware level to get max. performance, so I don't expect a fix by update.


    If you have more than one OS (LE + X), try Grub boot manager, and don't use VM for LE anymore.

    Beast Mode

  • So you use a virtual machine to run LE. I don't use VM, but there is a chance that it does an encapsulation of hardware / software, which may lead to the "system mode" (see above).


    I think LE programming will stay as close as possible on hardware level to get max. performance, so I don't expect a fix by update.


    If you have more than one OS (LE + X), try Grub boot manager, and don't use VM for LE anymore.

    I think I must of worded that last post incorrectly.


    I don't run le on a vm at all. I install le direct to my ssd.


    What I was trying to say was that a Google search of the first error that appears during boot is related to a amd virtualization error.

    I have checked my bios and it is currently disabled so not sure why I would get the error.

    If I was to be running Ubuntu, from what I have read on a few Linux forums regarding this error it appears I can blacklist something to stop this. I'm not sure what this means but some of the forums also say its fixed in later kernels.

    If it's a warning I will just ignore it but if its a error that could cause problems I suppose I need to sort it. I'm not a Linux expert so I don't have a clue when it comes to errors. I've always used raspberry pi's before deticating an actual computer for my main living room. Only ever had 1 boot message with a pi and that was quickly resolved.

    Think I'll have a play with some bios settings for now see if anything changes. Something I've learned recently with modern motherboards is that the latest bios is not always the best.


    Thanks

  • Sorry for my misunderstanding of virtualization technology and virtual machine. ;)

    Think I'll have a play with some bios settings for now see if anything changes.

    Good idea. Check the audio options, too.

    Beast Mode