[RPi5] Problem mount HardDisk

    • New

    Having 2 ssd's connected through usb (without external power) on a Banana Pi M5 using CE21 havent caused any problems in close to a year, same ssd's on Pi 4 and LE f*cked up almost every week.

    • New
    Quote from MatteN

    Having 2 ssd's connected through usb (without external power) on a Banana Pi M5 using CE21 havent caused any problems in close to a year, same ssd's on Pi 4 and LE f*cked up almost every week.

    you'll have to wait for version 13 stable, otherwise do as I did, install nightly and the ntfs3g addon.

    • New
    Quote from Albert

    you'll have to wait for version 13 stable, otherwise do as I did, install nightly and the ntfs3g addon.

    Cant be bothered, i get most of my media via smb from my network, have spent too much time with failing hdd's connected to LE-machines.

    • New

    Hi,

    I have a few more questions.

    I would like to do a stress test to check the stability, i tried this command: journalctl -f | grep -i underv but it doesn't work.

    And I also wanted to know if it's possible to optimize the rpi, I'm not looking for OC, but to disable or enable useful elements or not. to reduce consumption.

    I'm thinking of the files config.xml and advancedsettings.xml

    Just optimize the device

    • New
    Quote from Albert

    I know that gpu memory, cache, buffer etc. can be added or managed. Or it's really useless ?

    GPU memory is fixed at boot time and we already optimised consumption. Kernel caching has a simple rule: "if you understand the kernel documentation, do what you like, else leave alone" and since 99.99% of users will not understand kernel memory architecture it's best left alone. On the Kodi side users like to tweak cache/buffers settings thus undoing thousands of man-hours of effort to optimise the default settings with a ham-fisted bodge from a forum post where a user with a different use-case and no great clue about the underlying mechanisms said it made things better. As a broad rule cache settting changes will fix one thing and cause three more things. So feel free to go nuts .. do the reading (lots of kernel docs, RPi docs, Kodi docs are out there) but when it all makes no different or causes issues - revert back to the defaults and marvel at how things just work again.

    • New
    Quote from chewitt

    GPU memory is fixed at boot time and we already optimised consumption. Kernel caching has a simple rule: "if you understand the kernel documentation, do what you like, else leave alone" and since 99.99% of users will not understand kernel memory architecture it's best left alone. On the Kodi side users like to tweak cache/buffers settings thus undoing thousands of man-hours of effort to optimise the default settings with a ham-fisted bodge from a forum post where a user with a different use-case and no great clue about the underlying mechanisms said it made things better. As a broad rule cache settting changes will fix one thing and cause three more things. So feel free to go nuts .. do the reading (lots of kernel docs, RPi docs, Kodi docs are out there) but when it all makes no different or causes issues - revert back to the defaults and marvel at how things just work again.

    Hi, I understand what you're saying, and you've convinced me.

    Thank you for these explanations !