Posts by arhodiewithsoul

Quote from arhodiewithsoul

In the meantime, I'm going to backup my current install of Kodi and then see if disabling NTFS3 (https://forums.linuxmint.com/viewtopic.php?t=398433) and using NTFS-3G will resolve this problem.

...well that's a wash.

Doesn't look like I can 'disable' NTFS3 in favour of NTFS-3G. Apt-get commands are ignored and it appears that LibreElec prevents you from making changes to the system.

I couldn't figure out how to permanently set NTFS3 to 'Read-Only' for all NTFS mounted drives as an alternative. Someone cleverer than I would have to offer their assistance in this regard, *if* the write aspect is even the culprit. I would have liked to test this theory as it seems that the NTFS-3G default of setting NTFS drives to Read-Only was somewhat more forgiving.

Crystal mark, chkdsk indicates both 12v HDDs are error free when scanned.

I don't see that there is anything 'wrong' necessarily in the way I have the system set up; it's maybe just a little inefficient... or maybe not, I don't know (?) It is however, something I understand.

Anyway, I have ordered a new HDD, will format that to ExFat and carry on.

Thread

external HDD not detected/mounting v10.95.1 on PI3

hi there. just updating from matrix 19.4 to nexus (libreleec 10.95.1) in my PI3, installation was done tow ways, forts kjust updatont from matrix, next was a clean install using USB-SD creator and new formatted 16gb sd card.

nothing else was installed after, just basic config to start using kodi, but i noticed my external hdd does not appear anywhere, nothing in the dev/media folder, nothing shown in the system information/storage. (by the other hand usb any pendrive is detected correctly)

Hdd…

jordixPI3

March 1, 2023 at 7:04 PM

I'm crosslinking to this thread as it seems to deal with similar issues.

Quote from mattrude

@arhodiewithsoul, I think your best bet, assuming you have the hardware, is to setup a media server, using Ubuntu or Windows, for the storage of you content then connect to it with LibreELEC via SMB (samba).

This will also allow you to expand your setup in the future easier (ie. a second TV).

As far as the drives spontaneously having this issue, either the system was writing data to the drives during a power outage (most likely) or other event that caused the write to not correctly finish, or the drives may just be getting old.

Thanks again!

The power outage happened during a storm last week - though the TV was not on and the drives were not being accessed ie: we were not using the media contained on the drives. The RPi is, however, powered on 24/7 (usually) and the drives connected to it, so when the village lost electricity...

Why is NTFS has a dirty mark and why can't NTFS3 mount dirty NTFS partitions?

https://wiki.archlinux.org/title/NTFS#Unable_to_mount_with_ntfs3_with_partition_marked_dirty When a NTFS partition is marked dirty, NTFS3 cannot mount this on…

unix.stackexchange.com

... a catastrophic power failure causing a sudden disconnect or incorrectly removing the external drive from the RPi would result in the NTFS drive being marked as 'dirty'.

"If the partition is marked dirty it means its metadata is inconsistent and using it in read write mode, e.g. for creating, modifying or deleting file system objects may result in a data loss. Normally chkdsk from Windows must be used to fix it."

Apparently fastboot and hibernation may also result in NTFS disks being marked as dirty...

You're right about setting up a server - I was effectively using the RPi4 as the 'server' as it's powered on constantly and accessible on my home network. The RPi3 upstairs is only used occasionally and up until now, didn't seem to warrant powering yet another device 24/7

In the early days (for me ... XBMC on the RPi model B) I used to leave my pc on (with the external HDDs connected) and had the TV's usb port power the RPi on and off when the TV switched on and off, but I suffered a few occasions of corrupted SD card on the RPi (not to mention a horrific waste of electricity!). Having the RPi share the usb drives an act as THE media server was therefore my 'solution' to that problem ever since...

I'll look into sbc alternatives with Win10/11 as a media server and possibly some sort of dongle for the tv to host Kodi.

In the meantime, I'm going to backup my current install of Kodi and then see if disabling NTFS3 (https://forums.linuxmint.com/viewtopic.php?t=398433) and using NTFS-3G will resolve this problem.

Thank you again mattrude, I appreciate your input

So, to continue the conversation above, as I believe others may find themselves in a similar situation:

I currently have about 4TB of data split over 3 HDDs. I do not currently have the means to copy this data elsewhere in order to format the drives as EXT4 and copy the data back on. Nor do I want to lose the convenience of Win compatibility/ ease of use that NTFS formatting allows.

Mattrude identified the error in my logs (response #27, #28) and explained what seems to have occurred.

In order to resolve this, I need to understand more clearly what to do (and more importantly is achievable by me) so as to not waste my time.

From searching various Kodi specific forums, it appears that this is a common problem, but it is not well understood (by me). At least, I have not been able to find a conclusive solution other than plugging the drives into my laptop/pc and back into the RPi every time I encounter this 'fault'.

I know that Kodi v19 and RPi 4 was stable. I know that every Kodi iteration since XBMC Dharma and the RPi (B+?) has worked and was stable. So something has changed between v19 and v20 or LE10 and LE11. The avenue I have chosen to blindly walk down is NTFS support with Linux.

From searching Linux specific forums:

Kernel 5.15 : ntfs3 vs ntfs-3g

www.linuxquestions.org

and

new driver NTFS3 - Linux Mint Forums

The links above are to conversations around NTFS3 and the old implementation of NTFS-3G (FUSE) in Linux. It would suggest that similar problems with NTFS drives has been encountered following the adoption of NTFS3 in the kernel (5.15). Subsequent updates to the kernel seems to have resolved some of these problems, but not for everyone.

Maybe NTFS-3G being a 'read-only' solution did not throw up these errors due to not having 'write' permissions/ capabilities?

Would it be possible to sudo apt-get NTFS-3G and implement it on my machine (LE11) without causing conflict (with NTFS3)?

Is it possible to 'disable' NTFS3 in favour of NTFS-3G?

If anyone with more knowledge on the subject could pitch in and clarify/ explain things better please?

Many thanks

Quote from mattrude

Hi arhodiewithsoul,

It looks like your hard drives are formatted as NTFS and are being marked as "dirty" by the system (meaning the system has decided they are having issues and flipped a flag to have them checked).

NTFS is a Windows format and LibreELEC dose not have the needed utilities to check and repair any problems on these drives.

From your Logs:

Code

Jun 18 18:48:19.535178 MaximusPi systemd[1]: Starting udevil-mount@-dev-sda1.service...
Jun 18 18:48:19.567347 MaximusPi kernel: ext3: Unknown parameter 'fmask'
Jun 18 18:48:19.567525 MaximusPi kernel: ext2: Unknown parameter 'fmask'
Jun 18 18:48:19.567613 MaximusPi kernel: ext4: Unknown parameter 'fmask'
Jun 18 18:48:19.567675 MaximusPi kernel: squashfs: Unknown parameter 'fmask'
Jun 18 18:48:19.567733 MaximusPi kernel: hfsplus: unable to parse mount options
Jun 18 18:48:19.567797 MaximusPi kernel: hfs: unable to parse mount options
Jun 18 18:48:19.567854 MaximusPi kernel: UDF-fs: bad mount option "fmask=0133" or missing value
Jun 18 18:48:19.570678 MaximusPi kernel: F2FS-fs (sda1): Magic Mismatch, valid(0xf2f52010) - read(0xc0856600)
Jun 18 18:48:19.570812 MaximusPi kernel: F2FS-fs (sda1): Can't find valid F2FS filesystem in 1th superblock
Jun 18 18:48:19.570873 MaximusPi kernel: F2FS-fs (sda1): Magic Mismatch, valid(0xf2f52010) - read(0x0)
Jun 18 18:48:19.570928 MaximusPi kernel: F2FS-fs (sda1): Can't find valid F2FS filesystem in 2th superblock
Jun 18 18:48:19.570982 MaximusPi kernel: fuseblk: Unknown parameter 'fmask'
Jun 18 18:48:19.620671 MaximusPi kernel: ntfs3: sda1: volume is dirty and "force" flag is not set!
Jun 18 18:48:19.620906 MaximusPi udevil[7193]: mount: mounting /dev/sda1 on /media/Persephone failed: Invalid argument
Jun 18 18:48:19.621825 MaximusPi udevil[7189]: mount: mounting /dev/sda1 on /media/Persephone failed: No such device
Jun 18 18:48:19.692860 MaximusPi systemd[1]: Finished udevil-mount@-dev-sda1.service.

Display More

When you run the check/repair on the drives in windows, it flips the flag on the drive saying all is well now.

Unfortunately this problem may continue to happen with your current setup.

Reformatting the drive will delete ALL DATA on the drive, so you must back it up first (I understand that is not always do-able). You may have to look at serving the data from a different system (windows or a linux distribution that handles NTFS).

Display More

Thank you for your reply!

From reading threads on the Kodi forum, I suspected that this might be the case - I noted that other users have formatted their drives to EXT4. It's strange though that this check has only been implemented with Nexus - the HDDs have been connected to a RPi since XBMC Dharma (2011/2012) days without any issue...

...sorry I just re-read your message "or a Linux distro that handles NTFS". So, an alternate solution may be to have to HDDs connected to a Win/Linux (NTFS happy) device and my Kodi RPi remotely access that.

Some further reading and thinking to do.

Many thanks for taking the time to investigate my problem and the helpful information contained in your reply.

Hi all,

I'm having similar behaviour with LibreElec 11.0.1 (Kodi Nexus 20) and my external HDDs.

I have 2x WD Elements with their own separate 12v power source and 1x 2.5" HDD connected via powered usb hub. The RPi (4, 2Gb) is powered by a RPi official product 5v charger.

The installation of LE/Nexus was clean, YouTube add-on, otherwise vanilla (as far as I'm aware).

The HDDs (WD) are recognised under 'System/System info/storage' and files are shared over a local network via Samba/ SMB.

If we have a power cut or I reboot the RPi, the HDDs no longer show. If I pull the power or usb lead, a popup on Kodi states "...device successfully removed".

If I reconnect the drive/s they are not recognised.

If I connect them to my pc and allow it to scan the drive and/or 'fix' errors (no errors detected), then eject, reconnect to the RPi, everything works again.

Separately, the 2.5" HDD sticks in a reading loop where it keeps disconnecting/reconnecting and is unusable. I have tried connecting it through the powered usb hub and to the RPi usb 3.0 ports directly with the same results. If I plug it into the pc, it operates correctly and all files are present, all operations are normal.

Any assistance offered would be gratefully received.

Log files pasted to http://ix.io/4yzh