Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04
-
@notverypunny said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
Is bitlocker or another encryption / security solution in play? I think bitlocker would have caused grief with the linux install in general, but I've never had the pleasure of messing around with it too much.
How about just booting a live linux? Can you see and automount the windows partition from a live disk?
Other possibility, is it ReFS instead of NTFS?
I’ve not set up bitlocker, but it is listed in Disk management. And I have looked into this.
-
@gjacobse said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
@notverypunny said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
Is bitlocker or another encryption / security solution in play? I think bitlocker would have caused grief with the linux install in general, but I've never had the pleasure of messing around with it too much.
How about just booting a live linux? Can you see and automount the windows partition from a live disk?
Other possibility, is it ReFS instead of NTFS?
I’ve not set up bitlocker, but it is listed in Disk management. And I have looked into this.
I had a weird problem once where Bitlocker turned itself on. Caused all kinds of problems with what i was trying to do (images)... killed it and life was good.
-
Can you try accessing that partition from a live ubuntu installer?
-
@gjacobse said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
@dbeato said in Dual Boot: Unable to access Windows from Ubuntu:
@gjacobse said in Dual Boot: Unable to access Windows from Ubuntu:
Installed Windows, shrank drive, installed Ubuntu 18.04.
Unable to mount the Windows drive even though shutdown is clean.
Windows is (or should be) sda4,..
sda1 - ntfs
sda2 - vfat /boot/efi
sda3 -
sda4 -
sda5 ext4I'm following this (which has worked in the past)
https://askubuntu.com/questions/978746/how-to-mount-ntfs-partition-in-ubuntu-16-04
What happens when you mount sda1?
sda is listed as the recovery partition,.. and likely doesn't have any of the User data.
That being said,.. I'll check that.
Follow up, yes I can mount and access /dev/sda1.
But there isn't anything there other than the recovery.
-
@gjacobse said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
@gjacobse said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
@dbeato said in Dual Boot: Unable to access Windows from Ubuntu:
@gjacobse said in Dual Boot: Unable to access Windows from Ubuntu:
Installed Windows, shrank drive, installed Ubuntu 18.04.
Unable to mount the Windows drive even though shutdown is clean.
Windows is (or should be) sda4,..
sda1 - ntfs
sda2 - vfat /boot/efi
sda3 -
sda4 -
sda5 ext4I'm following this (which has worked in the past)
https://askubuntu.com/questions/978746/how-to-mount-ntfs-partition-in-ubuntu-16-04
What happens when you mount sda1?
sda is listed as the recovery partition,.. and likely doesn't have any of the User data.
That being said,.. I'll check that.
Follow up, yes I can mount and access /dev/sda1.
But there isn't anything there other than the recovery.
Interesting, that's so weird.
-
What does this command show:
lsblk -f -
@dbeato said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
What does this command show:
lsblk -fredacted -
@gjacobse But that is now that command...
-
@dbeato said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
@gjacobse But that is now that command...
redacted -
@gjacobse still not the command
-
@dbeato said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
@gjacobse still not the command
lsblk -f NAME FSTYPE LABEL UUID MOUNTPOINT loop0 squashfs /snap/gnome-logs/45 loop1 squashfs /snap/core/4917 loop2 squashfs /snap/gnome-calculator/180 loop3 squashfs /snap/gnome-system-monitor/51 loop4 squashfs /snap/gnome-characters/103 loop5 squashfs /snap/gtk-common-themes/319 loop6 squashfs /snap/core/6130 loop7 squashfs /snap/gnome-logs/37 loop8 squashfs /snap/gnome-calculator/260 loop9 squashfs /snap/gnome-3-26-1604/70 loop10 squashfs /snap/gnome-system-monitor/57 loop11 squashfs /snap/gnome-3-26-1604/74 loop12 squashfs /snap/gnome-characters/139 loop13 squashfs /snap/skype/66 loop14 squashfs /snap/gtk-common-themes/818 loop15 squashfs /snap/core/6259 sda ├─sda1 ntfs Recovery 027ED5D87ED5C497 /media/windows ├─sda2 vfat 30D7-1C6E /boot/efi ├─sda3 ├─sda4 └─sda5 ext4 ade0b36a-cebd-41e7-bf39-f3950255dfcd / -
@gjacobse said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
@gjacobse said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
@dbeato said in Dual Boot: Unable to access Windows from Ubuntu:
@gjacobse said in Dual Boot: Unable to access Windows from Ubuntu:
Installed Windows, shrank drive, installed Ubuntu 18.04.
Unable to mount the Windows drive even though shutdown is clean.
Windows is (or should be) sda4,..
sda1 - ntfs
sda2 - vfat /boot/efi
sda3 -
sda4 -
sda5 ext4I'm following this (which has worked in the past)
https://askubuntu.com/questions/978746/how-to-mount-ntfs-partition-in-ubuntu-16-04
What happens when you mount sda1?
sda is listed as the recovery partition,.. and likely doesn't have any of the User data.
That being said,.. I'll check that.
Follow up, yes I can mount and access /dev/sda1.
But there isn't anything there other than the recovery.
That is all that should be there.. your list proved that.
-
I believe this is because of the Windows 10 does not fully restart, it actually hibernates... maybe disable fastboot on Windows 10. Then try to mount it again.
-
@dbeato said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
I believe this is because of the Windows 10 does not fully restart, it actually hibernates... maybe disable fastboot on Windows 10. Then try to mount it again.
Turned off,.. still getting same error that sda4 doesn't seem to have a valid NTFS
-
@dbeato said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
I believe this is because of the Windows 10 does not fully restart, it actually hibernates... maybe disable fastboot on Windows 10. Then try to mount it again.
Or hold down the Shift key and restart.
-
System shows it's NTFS - so,.. what the what?
-
Windows DUMBASS-ory..
Talking to my brother, he mentioned some 'issues' with Windows not releasing the lock on the partition. He suggested and this is the really dumb part on windows.
To boot Windows and RESTART normally.
Since grub starts Ubuntu by default, it booted normally into Ubuntu.
I did the lsblk -f as before, only this time for /dev/sda4 - there is a UID for it. AND it shows as NTFS..
so,.. FFS Windows,.. FYS. now,.. to see how to prevent this stupidness in the future.
-
@gjacobse said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
Windows DUMBASS-ory..
Talking to my brother, he mentioned some 'issues' with Windows not releasing the lock on the partition. He suggested and this is the really dumb part on windows.
To boot Windows and RESTART normally.
Since grub starts Ubuntu by default, it booted normally into Ubuntu.
I did the lsblk -f as before, only this time for /dev/sda4 - there is a UID for it. AND it shows as NTFS..
so,.. FFS Windows,.. FYS. now,.. to see how to prevent this stupidness in the future.
This why someone suggested that you go into Windows and do a full shutdown with shift shutdown.... normal shutdowns now aren’t full shut downs to allow the system to boot faster.
-
@Dashrender said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
@gjacobse said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
Windows DUMBASS-ory..
Talking to my brother, he mentioned some 'issues' with Windows not releasing the lock on the partition. He suggested and this is the really dumb part on windows.
To boot Windows and RESTART normally.
Since grub starts Ubuntu by default, it booted normally into Ubuntu.
I did the lsblk -f as before, only this time for /dev/sda4 - there is a UID for it. AND it shows as NTFS..
so,.. FFS Windows,.. FYS. now,.. to see how to prevent this stupidness in the future.
This why someone suggested that you go into Windows and do a full shutdown with shift shutdown.... normal shutdowns now aren’t full shut downs to allow the system to boot faster.
But he did that and it made no difference
-
@JaredBusch said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
@Dashrender said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
@gjacobse said in Dual Boot: Unable to access Windows NTFS Filesystem from Ubuntu 18.04:
Windows DUMBASS-ory..
Talking to my brother, he mentioned some 'issues' with Windows not releasing the lock on the partition. He suggested and this is the really dumb part on windows.
To boot Windows and RESTART normally.
Since grub starts Ubuntu by default, it booted normally into Ubuntu.
I did the lsblk -f as before, only this time for /dev/sda4 - there is a UID for it. AND it shows as NTFS..
so,.. FFS Windows,.. FYS. now,.. to see how to prevent this stupidness in the future.
This why someone suggested that you go into Windows and do a full shutdown with shift shutdown.... normal shutdowns now aren’t full shut downs to allow the system to boot faster.
But he did that and it made no difference
Yup - a FULL shutdown didn't do anything more that the SHIFT shutdown.
