F5F Stay Refreshed Software Operating Systems Linux systems can't reach Windows files due to differing file structures and permissions.

Linux systems can't reach Windows files due to differing file structures and permissions.

Linux systems can't reach Windows files due to differing file structures and permissions.

Pages (2): 1 2 Next
M
miknes123
Senior Member
646
01-26-2016, 12:59 PM
#1
HDD 1: boot disk with operating system, HDD 2: storage for movies, projects, music. The first had Windows 10, I switched to Linux Lubuntu. Recently, I connected my file drive to keep working on a project, but it shows an error about NTFS being inaccessible. I assumed Linux and Ubuntu support all Microsoft formats. Is my file locked? How do I get to my files? I tried using the GUI file manager, but it says NTFS isn’t available. Anyone experienced with this issue? Any advice or solutions would be appreciated.
M
miknes123
01-26-2016, 12:59 PM #1

HDD 1: boot disk with operating system, HDD 2: storage for movies, projects, music. The first had Windows 10, I switched to Linux Lubuntu. Recently, I connected my file drive to keep working on a project, but it shows an error about NTFS being inaccessible. I assumed Linux and Ubuntu support all Microsoft formats. Is my file locked? How do I get to my files? I tried using the GUI file manager, but it says NTFS isn’t available. Anyone experienced with this issue? Any advice or solutions would be appreciated.

N
Notional
Junior Member
48
01-28-2016, 12:48 AM
#2
Find an NTFS driver for Lubuntu by searching online sources or checking official repositories.
N
Notional
01-28-2016, 12:48 AM #2

Find an NTFS driver for Lubuntu by searching online sources or checking official repositories.

M
MegaBUFFALO
Member
161
02-01-2016, 05:27 PM
#3
NTFS might sometimes be tricky, so searching for a compatible driver is wise. Initially, I assumed it was installed without checking the proprietary options, but I believe open-source alternatives exist. Check out this guide: https://help.ubuntu.com/community/Mounti...Partitions
M
MegaBUFFALO
02-01-2016, 05:27 PM #3

NTFS might sometimes be tricky, so searching for a compatible driver is wise. Initially, I assumed it was installed without checking the proprietary options, but I believe open-source alternatives exist. Check out this guide: https://help.ubuntu.com/community/Mounti...Partitions

C
CozyTea
Member
106
02-07-2016, 04:41 AM
#4
Doesn't look like driver to me, on my Ubuntu 16.04 the NTFS utilities are included with the default desktop installation. I think your drive is just locked to your old Windows user. Read the man for ntfs-3g. I wont paste it here because I want you read the whole first page but these ntfs-3g options look promising for you:
C
CozyTea
02-07-2016, 04:41 AM #4

Doesn't look like driver to me, on my Ubuntu 16.04 the NTFS utilities are included with the default desktop installation. I think your drive is just locked to your old Windows user. Read the man for ntfs-3g. I wont paste it here because I want you read the whole first page but these ntfs-3g options look promising for you:

L
Lucite01
Junior Member
15
02-07-2016, 05:33 AM
#5
It seems a bit involved. I recommend duplicating the drive and testing extensively. This ensures you can always restore your data if needed. Hope this assists! https://linuxpowerblog.wordpress.com/201...-to-linux/
L
Lucite01
02-07-2016, 05:33 AM #5

It seems a bit involved. I recommend duplicating the drive and testing extensively. This ensures you can always restore your data if needed. Hope this assists! https://linuxpowerblog.wordpress.com/201...-to-linux/

R
Robx_33
Member
141
02-14-2016, 04:45 PM
#6
I searched online for NTFS drivers for Linux but received suggestions that they’re already included in the kernel. I started my main desktop and attempted to access the drive again, which triggered an error similar to what others described. The discussion indicated that Windows wasn’t closing the system correctly. I ran the first recommended terminal command, which returned a list of options, but executing each command individually or together failed. I didn’t notice any issues with the drive name containing spaces, even when naming it "Video Hard Drive." When I tried the second command, it didn’t work because no folder existed. My priority was editing a video using clips from the current file drive, so I needed to identify which drive hosted the OS. I avoided formatting the old drive by only connecting the operating system drive to confirm it wasn’t overwritten. I’m certain I powered off the computer completely before disconnecting power and data from the hard drives. Some sources mentioned that newer Windows versions might not shut down fully, which could explain the problem.
R
Robx_33
02-14-2016, 04:45 PM #6

I searched online for NTFS drivers for Linux but received suggestions that they’re already included in the kernel. I started my main desktop and attempted to access the drive again, which triggered an error similar to what others described. The discussion indicated that Windows wasn’t closing the system correctly. I ran the first recommended terminal command, which returned a list of options, but executing each command individually or together failed. I didn’t notice any issues with the drive name containing spaces, even when naming it "Video Hard Drive." When I tried the second command, it didn’t work because no folder existed. My priority was editing a video using clips from the current file drive, so I needed to identify which drive hosted the OS. I avoided formatting the old drive by only connecting the operating system drive to confirm it wasn’t overwritten. I’m certain I powered off the computer completely before disconnecting power and data from the hard drives. Some sources mentioned that newer Windows versions might not shut down fully, which could explain the problem.

B
banshee45
Senior Member
726
02-14-2016, 05:38 PM
#7
On Windows 8 and newer, disable the fast boot option in BIOS, then restart and shut down your system.
B
banshee45
02-14-2016, 05:38 PM #7

On Windows 8 and newer, disable the fast boot option in BIOS, then restart and shut down your system.

P
Phantomtyger
Junior Member
3
03-02-2016, 07:24 PM
#8
No, you don't necessarily need windows installed.
P
Phantomtyger
03-02-2016, 07:24 PM #8

No, you don't necessarily need windows installed.

K
kervinc
Posting Freak
804
03-04-2016, 04:32 PM
#9
I recently encountered this problem with Ubuntu GNOME. I tried mounting the drive using sudo mount -o ro [drive] [directory]. It seemed to work better when using an arbitrary path, like ~/Windows. Mounting it read-only helped resolve the issue.
K
kervinc
03-04-2016, 04:32 PM #9

I recently encountered this problem with Ubuntu GNOME. I tried mounting the drive using sudo mount -o ro [drive] [directory]. It seemed to work better when using an arbitrary path, like ~/Windows. Mounting it read-only helped resolve the issue.

Q
Qandii
Member
233
03-12-2016, 11:23 AM
#10
NTFS includes security features that restrict access, which is why I suggested reviewing the ntfs-3g documentation earlier. If you're using Windows 8 or newer on this device, ensure fast boot is disabled since it leads to a non-clean shutdown and locks the filesystem.
Q
Qandii
03-12-2016, 11:23 AM #10

NTFS includes security features that restrict access, which is why I suggested reviewing the ntfs-3g documentation earlier. If you're using Windows 8 or newer on this device, ensure fast boot is disabled since it leads to a non-clean shutdown and locks the filesystem.

Pages (2): 1 2 Next