Someone swapping their drives from NTFS to EXT4 would at least eliminate or confirm the issue is related to NTFS; if the problem goes away it's something in the in-kernel filesystem driver. If it occurs with EXT4 then it's something else.
i did this . . . all ok. drive appeared and was able to write to it. still need some help on getting old files on new drive so if someone can suggest something for post #36, i would appreciate it.
ok so i tested the drive with paragon hard disk manager and some 'minor problems' discovered but nothing big . . . i run windows and can move the files to another disk but if windows doesn't talk to ext4, then how to write back? i downloaded hirens boot disk and can boot to that and see if a tool can talk both ntfs and ext4 so i can move the contents - any other suggestions welcome.
so no go . . . moved the files within the windows environment to another usb drive and all ok . . . booted into hirens and connected both drives and used diskgenius to delete and repartition the former ntfs drive to ext4 - all was done ok. diskgenius can 'see' the target drive (as it partitioned it and formatted it) and the source (ntfs) but cannot move the files for some reason. how are other people doing this? do i need a live bootable linux usb with tools to do this? will that be able to see and act on ntfs and ext4? thanks.
Yes, this should result in better experience.
ok so i tested the drive with paragon hard disk manager and some 'minor problems' discovered but nothing big . . . i run windows and can move the files to another disk but if windows doesn't talk to ext4, then how to write back? i downloaded hirens boot disk and can boot to that and see if a tool can talk both ntfs and ext4 so i can move the contents - any other suggestions welcome.
Mario77 In LE11 the NTFS driver changed from user space ntfs-3g to in kernel ntfs3. The behavior may be different.
General recommendation: use NTFS for Windows only and native file systems like ext4 for Linux.
so the solution would be to offload the content and create a new volume with ext4? don't understand the windows part as i thought this was a linux distribution (libreelec) - thanks
ok so i don't have the system here at work but it is a zotac mini-pc about 4 years old with a Celeron processor and an external 1 tb drive from western digital.
here is the log file
hi all - any insights here or still collecting info . . . thx.
Yes please. ATM we have nothing to work with. No info about hardware, no info about file system, no log file.
ok so i don't have the system here at work but it is a zotac mini-pc about 4 years old with a Celeron processor and an external 1 tb drive from western digital.
here is the log file
ok will do this . . . first time so will use the kodi log uploader add-on as seems straightforward
ok brought system to my work and reproduced the problem - still not mounting the storage. is there a command to force it? i have used the kodi add-on log uploader and not sure if you have the logs at this point or i paste the url here?
As you can see at post #3, reformatting the drive can be a fix. Theory now is that bad file systems cause mounting problems.
To be sure, we need to see logs. So give us logs about your mounting attempts.
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link
ok will do this . . . first time so will use the kodi log uploader add-on as seems straightforward
Just to update, this is still an issue with LibreELEC 11.0.0.
glad you said that . . . just upgraded and this the case for me as well . . .
hi all - thanks for chiming in . . . this was an odd problem and might not be applicable to others but in case it it . . . so the problem - as i saw it - was that it needed to lock the drive to perform the write but couldn't for some reason (not that it Was locked) . . . it wouldn't proceed without that in place . . . used a partition tool and partitioned the device to a gpt partition over mbr . . . really don't know if that did it but someone allowed the write to proceed and thus i did get the image on the stick. thx again.
hi all - long-time user here . . . this is the 'easy' part but having trouble for some reason . . . 2 different usb sticks, 2 different image programs and 2 different images (rolled back to see if it was the image file) . . . not sure what is happening or if you all can help as not a libreelec-specific issue but . . . also, changed the file system to fat to see if that will help but originally ntfs.
thanks for any suggestions
michael
