Posts by Meiden


    Same issue here.


    He compilado yo una imagen de LE 8 con Kodi 17.1. Si la quieres te la paso.


    I've compiled an image of LE 8 with Kodi 17.1. I can share it with you.


    Do the external HDD each have a label name?


    Connect both drives, and give us the result of the following commands

    Code
    1. blkid | pastebinit
    2. mount | pastebinit


    I didn't set any label name


    Here are the results:
    VVeR
    BMdB

    Code
    1. /dev/mmcblk0: PTUUID="99176dab" PTTYPE="dos"
    2. /dev/mmcblk0p1: SEC_TYPE="msdos" UUID="176D-2AFE" TYPE="vfat" PARTUUID="99176dab-01"
    3. /dev/mmcblk0p2: UUID="f2c26989-d7ab-4c16-9d6a-36e40c02035b" TYPE="ext4" PARTUUID="99176dab-02"
    4. /dev/loop0: TYPE="squashfs"
    5. /dev/sda1: UUID="5B9AA4821C625CCB" TYPE="ntfs" PARTUUID="24f17d68-01"
    6. /dev/sdb1: UUID="3bc77ff7-b2b5-4e2d-9ad5-98fabc815330" TYPE="ext4" PARTUUID="000dcb72-01"




    How could I set a label name?
    [hr]
    Ok, I found out how to set a label for an EXT4 filesystem using e2label, but it doesn't work with my NTFS hdd.
    [hr]
    OK, I got it using ntfslabel. They are set on a fix point right now, exactly as you said. Thank you very much!!!!
    [hr]
    The workaround is just like this:


    For ext2/3/4 you can use e2label like this: e2label /dev/device new-label-name-here
    For NTFS you can use ntfs-3g like this: ntfslabel /dev/device new-label-name-here


    And the hdd will mount in the same point.

    Hi there,


    I have two external hard drives connected to my pi2. If I remove anyone of them or I change the plug where they are connected (I'm using a HUB) they mount in another point and all the files added to my library are unable to open.


    Is there any way to set a fix mount point for each hdd?

    Tried to get son benchmarks of my sdcard, it seems that the sdbench script gets some kind of errors:



    [font="Monaco, Consolas, Courier, monospace"]awk: cmd. line:1: Division by zero ¿LibreELEC related?[/font]


    There was a problem booting #0322 (which is no longer available on the server) but the problem is fixed in #0322b, unless it's a different problem. Can you grab a screenshot/photo if it happens again?


    Sorry Milhouse, my problem was with #0322 build, and I didn't realize that you updated the file on the repository after that. I've just flashed the new #0322b build and it's working flawlessly.


    Thank you very much and sorry for the confussion. My mistake.

    Thank you very much.
    [hr]


    That would be strange. We tested that yesterday in the evening and had the same issue. We reported and Milhouse fixed it. I installed #322b myself yesterday in the evening without having issues.


    I'll report to him.


    Cheers


    Sorry mate, I didn't realize that you changed the file in the downloads directory. You are right, my problem was with #322, not with #322b.


    I'm going to try the new version right now.


    Thank you mate.
    [hr]
    Working like a charm.


    Thank you!

    I tried to update from OE 6.95.1 to LE RPi2.arm-7.0-Milhouse-20160322183009-#0322b-g2f1b279 build and it resulted in a Kernel Panic.


    After that, I went back to my OE backup and I updated RPi2.arm-7.0-devel-20160321035214-#0321-g3ab346e.tar successfully.


    Is that .tar file bugged?

    I don't know where to post this. I'm unable to activate my account because I didn't receive the confirmation e-mail. Neither I can't start a thread asking for help nor I can't find a resend confirmation option in my account settings. Can you help me, chewitt?