Posts by wolf7250

  • SSD connected over USB won't mount

    Quote from VLouis

    Backup the data on your SSD and change the partition to be compatible with the LE images. That you need to do once, and you will be able to update the LE directly from LE server.

    Thanks for the suggestion! I am actually planning to convert my old Windows 10 Lenovo to a Linux distro. So that would be a good opportunity to change the partition to be compatible with LE images.

  • SSD connected over USB won't mount

    Looking through the debug logfile, these lines seem relevant... though not sure what they mean.

    Bash
    Jan 11 13:36:04.363184 MobileKodi udevil[541]: mount: /var/media/sda1-ata-Samsung_SSD_860_: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
Jan 11 13:36:04.363184 MobileKodi udevil[541]:        dmesg(1) may have more information after failed mount system call.
Jan 11 13:36:04.371122 MobileKodi kernel: EXT4-fs (sda1): The kernel was not built with CONFIG_QUOTA and CONFIG_QFMT_V2

    One of the lines above seems to prompt to check the dmesg output.... again looking at those, I see a repetition of "kernel not built with CONFIG_QUOTA and CONFIG_QFMT_V2"...

    Code
    [   14.531981] EXT4-fs (sda1): The kernel was not built with CONFIG_QUOTA and CONFIG_QFMT_V2

    Again, I don't know what this means or why it's happening....

    EDIT: Googling this, I suspect it is because I created the EXT4 filesystem on OpenMediaVault which has support for quota metadata.... am I going down the right track with my understanding? And what are my options?

  • SSD connected over USB won't mount

    Hi, I have a Pine64 rock64 board that I am running LibreELEC 12.2.1 on.
    I have an SSD formatted as EXT4 that I am attempting to mount over USB. The SSD drive is in a USB enclosure with external power.

    Unfortunately, it doesn't seem to mount, and I can't make sense of the logs...
    Is someone able to help?
    Thanks :)

    https://paste.libreelec.tv/prime-bison.log


    Output from dmesg after a reboot with the drive attached is here:
    paste.libreelec.tv/sterling-dinosaur.log

  • OSMC Wifi dongle disconnects on Rpi2

    Hi All,

    I've been having an issue with the OSMC wifi dongle consistently disconnecting from my Rpi2.

    I have just recently installed the latest version of LibreELEC onto a brand new SD card. Everything works well except for Wifi. Unfortunately running a LAN cable to the Pi is not an option at the moment and I had a spare OSMC wifi dongle so I thought I would use that.

    The wifi works perfectly well initially, however consistently after a couple hours (give or take) the wifi disconnects and the dongle doesn't appear to be recognised anymore. The only method I have found to resolve it is to either reboot or unplug and reinsert the dongle. This works for a couple hours until another disconnect.

    Thinking that it might be a driver issue I tried the fix outlined here:

    RE: [Solved] OSMC WiFi dongle on RPi

    The dmesg output below was capture after attempting the steps in the link above. As far as I can tell (could be wrong) from the dmesg, the driver seems to be fine.

    I have managed to collect full debug logs, dmesg output and lsusb output. Please see these below:

    Debug Logs

    dmesg output

    lsusb output

    Does anybody have an idea as to what might be causing this?

    Thanks :)

  • TVHeadend won't tune properly

    Looking here there doesn't seem to be a zap tool in the DVB-Tools addon. There is t2scan and looking at the documentation it looks as though I can use that and it can output to a channels.conf file.

    Where does the TvHeadend config live in the LibreELEC directory? Am I able to update the channels.conf file directly from command line using t2scan?

  • TVHeadend won't tune properly

    I am having issues with tuning an initial TvHeadend server on my Rock64 (4GB).

    The hardware that I have got in the setup is:

    • Rock64
    • Sony PlayTV (DVB-T receiver)
    • Signal Amplifier
    • Quad Shielded cabling

    The are 6 muxes for my area (Melbourne, Australia) I have been able to get the expected channels on all muxes except one. The misbehaving mux will not tune any channels no matter what I try. I ran w_scan with the following command

    w_scan -ft -c AU

    and it found all expected channels on all mixers (see attached txt file), so I can't understand why it won't work!

    As far as I can tell the settings for the mux in TvHeadend appear to be correct (see attached screenshot).

    Is someone able to help? Thanks in advance.

    P.S. I should also note that I have an existing RaspberryPi 2B that has been connected to the same cable and signal amplifier and TvHeadend works without issue

    EDIT:

    I decided to try running the startup wizard from scratch again. Now only 2 (out of 6) muxes tune and I'm getting 16 channels when when I should be getting 50 odd :(

  • issue on Rock64 images.

    Quote from kostaman

    EDIT : I just updated to LibreELEC-RK3328.arm-9.1-nightly-20190410-a2cd6c2-rock64

    Problem gone. Maybe intermittent so i'll have to keep testing when i have time.

    Unfortunately updating to this nightly has not made any difference for me :(.

    Quote from mike2002

    wolf7250,

    another point to check, be sure to have a good quality micro SD card. It's really important.

    Thanks mike2002 for the suggestion :) I am actually using eMMC so it's not related to micro SD card quality.