gparted ntfs partition mountable but can't resize
Clash Royale CLAN TAG#URR8PPP up vote
2
down vote
favorite
Trying to dual-boot install 18.04 on a machine with Windows 10 already installed. The installer didn't give me the option to shrink windows and dual-boot, so I went to manually repartition.
I tried to shrink the existing Windows 10 NTFS partition in gparted but there's an exclamation mark with a warning.
The warning says that it needs ntfs-3g installed, but it already is.
gparted says its installed and can shrink.
I made sure that Windows had fast startup disabled and had been shut down properly.
I also ran chkdsk /f C: and rebooted and then shut down properly before trying again.
And to prove that it's able to load, I manually mounted the partition!
I also tried resizing with gnome-disks but it goes grey as though it's opening a dialog and freezes until I press alt-F4.
So, in summary:
- ntfs-3g enabled
- Windows fastboot disabled
chkdsk /f C:successful- Windows shut down properly (no hibernate)
- partition mountable from Ubuntu
What else could be stopping it from being able to be shrunk?
dual-boot partitioning gparted ntfs 18.04
asked Apr 28 at 4:52
tudor
1,15521340
add a comment |Â
up vote
2
down vote
favorite
Trying to dual-boot install 18.04 on a machine with Windows 10 already installed. The installer didn't give me the option to shrink windows and dual-boot, so I went to manually repartition.
I tried to shrink the existing Windows 10 NTFS partition in gparted but there's an exclamation mark with a warning.
The warning says that it needs ntfs-3g installed, but it already is.
gparted says its installed and can shrink.
I made sure that Windows had fast startup disabled and had been shut down properly.
I also ran chkdsk /f C: and rebooted and then shut down properly before trying again.
And to prove that it's able to load, I manually mounted the partition!
I also tried resizing with gnome-disks but it goes grey as though it's opening a dialog and freezes until I press alt-F4.
So, in summary:
- ntfs-3g enabled
- Windows fastboot disabled
chkdsk /f C:successful- Windows shut down properly (no hibernate)
- partition mountable from Ubuntu
What else could be stopping it from being able to be shrunk?
dual-boot partitioning gparted ntfs 18.04
asked Apr 28 at 4:52
tudor
1,15521340
The first noticeable thing is that there appears to be no usage of sda4. I would expect to see some if you have W10 in there. It's possibly been corrupted. Can you mount sda4, then run commanddf -hand tell us if it shows any usage?
– Paul Benson
Apr 28 at 7:41
@PaulBenson Yes, the mount correctly shows 37GB of usage with 202GB free and Windows 10 runs correctly. I would expect if the partition were corrupted, thenchkdsk /f C:on Windows would have shown there to be errors.
– tudor
Apr 28 at 11:26
That is really odd, because gparted is showing sda4 as an unused partition, whereasdfshows things correctly. Did you mount sda4 from gparted? Have you tried viewing sda and its partitions inDisks? Once you've mounted sda4 does it show correctly in there? Do you have the partition show as a drive in the Launcher bar? Can you see/open the Windows folders and files without error from Ubuntu?
– Paul Benson
Apr 28 at 15:54
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Trying to dual-boot install 18.04 on a machine with Windows 10 already installed. The installer didn't give me the option to shrink windows and dual-boot, so I went to manually repartition.
I tried to shrink the existing Windows 10 NTFS partition in gparted but there's an exclamation mark with a warning.
The warning says that it needs ntfs-3g installed, but it already is.
gparted says its installed and can shrink.
I made sure that Windows had fast startup disabled and had been shut down properly.
I also ran chkdsk /f C: and rebooted and then shut down properly before trying again.
And to prove that it's able to load, I manually mounted the partition!
I also tried resizing with gnome-disks but it goes grey as though it's opening a dialog and freezes until I press alt-F4.
So, in summary:
- ntfs-3g enabled
- Windows fastboot disabled
chkdsk /f C:successful- Windows shut down properly (no hibernate)
- partition mountable from Ubuntu
What else could be stopping it from being able to be shrunk?
dual-boot partitioning gparted ntfs 18.04
asked Apr 28 at 4:52
tudor
1,15521340
Trying to dual-boot install 18.04 on a machine with Windows 10 already installed. The installer didn't give me the option to shrink windows and dual-boot, so I went to manually repartition.
I tried to shrink the existing Windows 10 NTFS partition in gparted but there's an exclamation mark with a warning.
The warning says that it needs ntfs-3g installed, but it already is.
gparted says its installed and can shrink.
I made sure that Windows had fast startup disabled and had been shut down properly.
I also ran chkdsk /f C: and rebooted and then shut down properly before trying again.
And to prove that it's able to load, I manually mounted the partition!
I also tried resizing with gnome-disks but it goes grey as though it's opening a dialog and freezes until I press alt-F4.
So, in summary:
- ntfs-3g enabled
- Windows fastboot disabled
chkdsk /f C:successful- Windows shut down properly (no hibernate)
- partition mountable from Ubuntu
What else could be stopping it from being able to be shrunk?
dual-boot partitioning gparted ntfs 18.04
asked Apr 28 at 4:52
tudor
1,15521340
asked Apr 28 at 4:52
tudor
1,15521340
asked Apr 28 at 4:52
tudor
1,15521340
asked Apr 28 at 4:52
tudor
1,15521340
1,15521340
The first noticeable thing is that there appears to be no usage of sda4. I would expect to see some if you have W10 in there. It's possibly been corrupted. Can you mount sda4, then run commanddf -hand tell us if it shows any usage?
– Paul Benson
Apr 28 at 7:41
@PaulBenson Yes, the mount correctly shows 37GB of usage with 202GB free and Windows 10 runs correctly. I would expect if the partition were corrupted, thenchkdsk /f C:on Windows would have shown there to be errors.
– tudor
Apr 28 at 11:26
That is really odd, because gparted is showing sda4 as an unused partition, whereasdfshows things correctly. Did you mount sda4 from gparted? Have you tried viewing sda and its partitions inDisks? Once you've mounted sda4 does it show correctly in there? Do you have the partition show as a drive in the Launcher bar? Can you see/open the Windows folders and files without error from Ubuntu?
– Paul Benson
Apr 28 at 15:54
add a comment |Â
The first noticeable thing is that there appears to be no usage of sda4. I would expect to see some if you have W10 in there. It's possibly been corrupted. Can you mount sda4, then run commanddf -hand tell us if it shows any usage?
– Paul Benson
Apr 28 at 7:41
@PaulBenson Yes, the mount correctly shows 37GB of usage with 202GB free and Windows 10 runs correctly. I would expect if the partition were corrupted, thenchkdsk /f C:on Windows would have shown there to be errors.
– tudor
Apr 28 at 11:26
That is really odd, because gparted is showing sda4 as an unused partition, whereasdfshows things correctly. Did you mount sda4 from gparted? Have you tried viewing sda and its partitions inDisks? Once you've mounted sda4 does it show correctly in there? Do you have the partition show as a drive in the Launcher bar? Can you see/open the Windows folders and files without error from Ubuntu?
– Paul Benson
Apr 28 at 15:54
The first noticeable thing is that there appears to be no usage of sda4. I would expect to see some if you have W10 in there. It's possibly been corrupted. Can you mount sda4, then run command
df -h and tell us if it shows any usage?– Paul Benson
Apr 28 at 7:41
The first noticeable thing is that there appears to be no usage of sda4. I would expect to see some if you have W10 in there. It's possibly been corrupted. Can you mount sda4, then run command
df -h and tell us if it shows any usage?– Paul Benson
Apr 28 at 7:41
@PaulBenson Yes, the mount correctly shows 37GB of usage with 202GB free and Windows 10 runs correctly. I would expect if the partition were corrupted, then
chkdsk /f C: on Windows would have shown there to be errors.– tudor
Apr 28 at 11:26
@PaulBenson Yes, the mount correctly shows 37GB of usage with 202GB free and Windows 10 runs correctly. I would expect if the partition were corrupted, then
chkdsk /f C: on Windows would have shown there to be errors.– tudor
Apr 28 at 11:26
That is really odd, because gparted is showing sda4 as an unused partition, whereas
df shows things correctly. Did you mount sda4 from gparted? Have you tried viewing sda and its partitions in Disks? Once you've mounted sda4 does it show correctly in there? Do you have the partition show as a drive in the Launcher bar? Can you see/open the Windows folders and files without error from Ubuntu?– Paul Benson
Apr 28 at 15:54
That is really odd, because gparted is showing sda4 as an unused partition, whereas
df shows things correctly. Did you mount sda4 from gparted? Have you tried viewing sda and its partitions in Disks? Once you've mounted sda4 does it show correctly in there? Do you have the partition show as a drive in the Launcher bar? Can you see/open the Windows folders and files without error from Ubuntu?– Paul Benson
Apr 28 at 15:54
add a comment |Â
3 Answers
3
active
oldest
votes
up vote
1
down vote
Use Windows tools to shrink the Windows partition
I suggest that you boot into Windows, and use the tools available there to shrink the Windows partition.
Do not create any new partition (because Windows will probably create a dynamic partition, which cannot be used by linux). Instead you should leave unallocated drive space.
Boot into Ubuntu live and use
gpartedto create a partition or partitions, that can be used by Ubuntu.
answered May 7 at 14:02
sudodus
20.1k32666
Last time I checked, you can't change the partition you booted from in Windows. Has this changed?
– tudor
May 9 at 0:13
I think you checked very long ago. This has been possible for several years.
– sudodus
May 9 at 3:41
add a comment |Â
up vote
0
down vote
It is possible that the file system is in an inconsistent state and this would prevent the file system from being resized. This commonly happens if Windows was not shutdown properly (e.g., powered off, or hibernated).
The fix is to boot into Windows and perform a proper shutdown. Then boot from live media containing GParted (such as GParted Live) which should not mount any of the partitions. Then try the resize again.
Further be sure that Windows Dynamic Disks are not being used as these are not supported.
answered Apr 28 at 19:39
Curtis Gedak
71644
I'm running this from an Ubuntu 18.04 USB Boot Disk. Your first 2 points are discounted by Point 3 - "chkdsk /f successful" and Point 4 - "Windows was properly shut down (No hibernate)". I will check on the dynamic disks, but I would be really surprised if I chose that as an option.
– tudor
May 3 at 0:55
GParted uses a command similar to the following to determine the used/unused sectors in an NTFS file system:sudo ntfsresize --info --force --no-progress-bar /dev/sda4. You might try running the command from a terminal window to see if it reports any errors that might indicate the source of the problem
– Curtis Gedak
May 4 at 15:19
add a comment |Â
up vote
-1
down vote
It possible to run the live installation in trial mode before attempting to use gparted.
then you can use a terminal to run ntfsfix /dev/sda4 to repair the ntfs partition.
you can now use gparted to resize the partition and create a new one.
answered May 7 at 13:48
kishea
906
We've already established that the ntfs partition does not have any errors, so ntfsfix won't solve this problem.
– tudor
May 26 at 9:57
add a comment |Â
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Use Windows tools to shrink the Windows partition
I suggest that you boot into Windows, and use the tools available there to shrink the Windows partition.
Do not create any new partition (because Windows will probably create a dynamic partition, which cannot be used by linux). Instead you should leave unallocated drive space.
Boot into Ubuntu live and use
gpartedto create a partition or partitions, that can be used by Ubuntu.
answered May 7 at 14:02
sudodus
20.1k32666
Last time I checked, you can't change the partition you booted from in Windows. Has this changed?
– tudor
May 9 at 0:13
I think you checked very long ago. This has been possible for several years.
– sudodus
May 9 at 3:41
add a comment |Â
up vote
1
down vote
Use Windows tools to shrink the Windows partition
I suggest that you boot into Windows, and use the tools available there to shrink the Windows partition.
Do not create any new partition (because Windows will probably create a dynamic partition, which cannot be used by linux). Instead you should leave unallocated drive space.
Boot into Ubuntu live and use
gpartedto create a partition or partitions, that can be used by Ubuntu.
answered May 7 at 14:02
sudodus
20.1k32666
Last time I checked, you can't change the partition you booted from in Windows. Has this changed?
– tudor
May 9 at 0:13
I think you checked very long ago. This has been possible for several years.
– sudodus
May 9 at 3:41
add a comment |Â
up vote
1
down vote
up vote
1
down vote
Use Windows tools to shrink the Windows partition
I suggest that you boot into Windows, and use the tools available there to shrink the Windows partition.
Do not create any new partition (because Windows will probably create a dynamic partition, which cannot be used by linux). Instead you should leave unallocated drive space.
Boot into Ubuntu live and use
gpartedto create a partition or partitions, that can be used by Ubuntu.
answered May 7 at 14:02
sudodus
20.1k32666
Use Windows tools to shrink the Windows partition
I suggest that you boot into Windows, and use the tools available there to shrink the Windows partition.
Do not create any new partition (because Windows will probably create a dynamic partition, which cannot be used by linux). Instead you should leave unallocated drive space.
Boot into Ubuntu live and use
gpartedto create a partition or partitions, that can be used by Ubuntu.
answered May 7 at 14:02
sudodus
20.1k32666
edited May 7 at 14:14
answered May 7 at 14:02
sudodus
20.1k32666
answered May 7 at 14:02
sudodus
20.1k32666
answered May 7 at 14:02
sudodus
20.1k32666
20.1k32666
Last time I checked, you can't change the partition you booted from in Windows. Has this changed?
– tudor
May 9 at 0:13
I think you checked very long ago. This has been possible for several years.
– sudodus
May 9 at 3:41
add a comment |Â
Last time I checked, you can't change the partition you booted from in Windows. Has this changed?
– tudor
May 9 at 0:13
I think you checked very long ago. This has been possible for several years.
– sudodus
May 9 at 3:41
Last time I checked, you can't change the partition you booted from in Windows. Has this changed?
– tudor
May 9 at 0:13
Last time I checked, you can't change the partition you booted from in Windows. Has this changed?
– tudor
May 9 at 0:13
I think you checked very long ago. This has been possible for several years.
– sudodus
May 9 at 3:41
I think you checked very long ago. This has been possible for several years.
– sudodus
May 9 at 3:41
add a comment |Â
up vote
0
down vote
It is possible that the file system is in an inconsistent state and this would prevent the file system from being resized. This commonly happens if Windows was not shutdown properly (e.g., powered off, or hibernated).
The fix is to boot into Windows and perform a proper shutdown. Then boot from live media containing GParted (such as GParted Live) which should not mount any of the partitions. Then try the resize again.
Further be sure that Windows Dynamic Disks are not being used as these are not supported.
answered Apr 28 at 19:39
Curtis Gedak
71644
I'm running this from an Ubuntu 18.04 USB Boot Disk. Your first 2 points are discounted by Point 3 - "chkdsk /f successful" and Point 4 - "Windows was properly shut down (No hibernate)". I will check on the dynamic disks, but I would be really surprised if I chose that as an option.
– tudor
May 3 at 0:55
GParted uses a command similar to the following to determine the used/unused sectors in an NTFS file system:sudo ntfsresize --info --force --no-progress-bar /dev/sda4. You might try running the command from a terminal window to see if it reports any errors that might indicate the source of the problem
– Curtis Gedak
May 4 at 15:19
add a comment |Â
up vote
0
down vote
It is possible that the file system is in an inconsistent state and this would prevent the file system from being resized. This commonly happens if Windows was not shutdown properly (e.g., powered off, or hibernated).
The fix is to boot into Windows and perform a proper shutdown. Then boot from live media containing GParted (such as GParted Live) which should not mount any of the partitions. Then try the resize again.
Further be sure that Windows Dynamic Disks are not being used as these are not supported.
answered Apr 28 at 19:39
Curtis Gedak
71644
I'm running this from an Ubuntu 18.04 USB Boot Disk. Your first 2 points are discounted by Point 3 - "chkdsk /f successful" and Point 4 - "Windows was properly shut down (No hibernate)". I will check on the dynamic disks, but I would be really surprised if I chose that as an option.
– tudor
May 3 at 0:55
GParted uses a command similar to the following to determine the used/unused sectors in an NTFS file system:sudo ntfsresize --info --force --no-progress-bar /dev/sda4. You might try running the command from a terminal window to see if it reports any errors that might indicate the source of the problem
– Curtis Gedak
May 4 at 15:19
add a comment |Â
up vote
0
down vote
up vote
0
down vote
It is possible that the file system is in an inconsistent state and this would prevent the file system from being resized. This commonly happens if Windows was not shutdown properly (e.g., powered off, or hibernated).
The fix is to boot into Windows and perform a proper shutdown. Then boot from live media containing GParted (such as GParted Live) which should not mount any of the partitions. Then try the resize again.
Further be sure that Windows Dynamic Disks are not being used as these are not supported.
answered Apr 28 at 19:39
Curtis Gedak
71644
It is possible that the file system is in an inconsistent state and this would prevent the file system from being resized. This commonly happens if Windows was not shutdown properly (e.g., powered off, or hibernated).
The fix is to boot into Windows and perform a proper shutdown. Then boot from live media containing GParted (such as GParted Live) which should not mount any of the partitions. Then try the resize again.
Further be sure that Windows Dynamic Disks are not being used as these are not supported.
answered Apr 28 at 19:39
Curtis Gedak
71644
edited Apr 28 at 19:45
answered Apr 28 at 19:39
Curtis Gedak
71644
answered Apr 28 at 19:39
Curtis Gedak
71644
answered Apr 28 at 19:39
Curtis Gedak
71644
71644
I'm running this from an Ubuntu 18.04 USB Boot Disk. Your first 2 points are discounted by Point 3 - "chkdsk /f successful" and Point 4 - "Windows was properly shut down (No hibernate)". I will check on the dynamic disks, but I would be really surprised if I chose that as an option.
– tudor
May 3 at 0:55
GParted uses a command similar to the following to determine the used/unused sectors in an NTFS file system:sudo ntfsresize --info --force --no-progress-bar /dev/sda4. You might try running the command from a terminal window to see if it reports any errors that might indicate the source of the problem
– Curtis Gedak
May 4 at 15:19
add a comment |Â
I'm running this from an Ubuntu 18.04 USB Boot Disk. Your first 2 points are discounted by Point 3 - "chkdsk /f successful" and Point 4 - "Windows was properly shut down (No hibernate)". I will check on the dynamic disks, but I would be really surprised if I chose that as an option.
– tudor
May 3 at 0:55
GParted uses a command similar to the following to determine the used/unused sectors in an NTFS file system:sudo ntfsresize --info --force --no-progress-bar /dev/sda4. You might try running the command from a terminal window to see if it reports any errors that might indicate the source of the problem
– Curtis Gedak
May 4 at 15:19
I'm running this from an Ubuntu 18.04 USB Boot Disk. Your first 2 points are discounted by Point 3 - "chkdsk /f successful" and Point 4 - "Windows was properly shut down (No hibernate)". I will check on the dynamic disks, but I would be really surprised if I chose that as an option.
– tudor
May 3 at 0:55
I'm running this from an Ubuntu 18.04 USB Boot Disk. Your first 2 points are discounted by Point 3 - "chkdsk /f successful" and Point 4 - "Windows was properly shut down (No hibernate)". I will check on the dynamic disks, but I would be really surprised if I chose that as an option.
– tudor
May 3 at 0:55
GParted uses a command similar to the following to determine the used/unused sectors in an NTFS file system:
sudo ntfsresize --info --force --no-progress-bar /dev/sda4 . You might try running the command from a terminal window to see if it reports any errors that might indicate the source of the problem– Curtis Gedak
May 4 at 15:19
GParted uses a command similar to the following to determine the used/unused sectors in an NTFS file system:
sudo ntfsresize --info --force --no-progress-bar /dev/sda4 . You might try running the command from a terminal window to see if it reports any errors that might indicate the source of the problem– Curtis Gedak
May 4 at 15:19
add a comment |Â
up vote
-1
down vote
It possible to run the live installation in trial mode before attempting to use gparted.
then you can use a terminal to run ntfsfix /dev/sda4 to repair the ntfs partition.
you can now use gparted to resize the partition and create a new one.
answered May 7 at 13:48
kishea
906
We've already established that the ntfs partition does not have any errors, so ntfsfix won't solve this problem.
– tudor
May 26 at 9:57
add a comment |Â
up vote
-1
down vote
It possible to run the live installation in trial mode before attempting to use gparted.
then you can use a terminal to run ntfsfix /dev/sda4 to repair the ntfs partition.
you can now use gparted to resize the partition and create a new one.
answered May 7 at 13:48
kishea
906
We've already established that the ntfs partition does not have any errors, so ntfsfix won't solve this problem.
– tudor
May 26 at 9:57
add a comment |Â
up vote
-1
down vote
up vote
-1
down vote
It possible to run the live installation in trial mode before attempting to use gparted.
then you can use a terminal to run ntfsfix /dev/sda4 to repair the ntfs partition.
you can now use gparted to resize the partition and create a new one.
answered May 7 at 13:48
kishea
906
It possible to run the live installation in trial mode before attempting to use gparted.
then you can use a terminal to run ntfsfix /dev/sda4 to repair the ntfs partition.
you can now use gparted to resize the partition and create a new one.
answered May 7 at 13:48
kishea
906
answered May 7 at 13:48
kishea
906
answered May 7 at 13:48
kishea
906
answered May 7 at 13:48
kishea
906
906
We've already established that the ntfs partition does not have any errors, so ntfsfix won't solve this problem.
– tudor
May 26 at 9:57
add a comment |Â
We've already established that the ntfs partition does not have any errors, so ntfsfix won't solve this problem.
– tudor
May 26 at 9:57
We've already established that the ntfs partition does not have any errors, so ntfsfix won't solve this problem.
– tudor
May 26 at 9:57
We've already established that the ntfs partition does not have any errors, so ntfsfix won't solve this problem.
– tudor
May 26 at 9:57
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1029065%2fgparted-ntfs-partition-mountable-but-cant-resize%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
The first noticeable thing is that there appears to be no usage of sda4. I would expect to see some if you have W10 in there. It's possibly been corrupted. Can you mount sda4, then run command
df -hand tell us if it shows any usage?– Paul Benson
Apr 28 at 7:41
@PaulBenson Yes, the mount correctly shows 37GB of usage with 202GB free and Windows 10 runs correctly. I would expect if the partition were corrupted, then
chkdsk /f C:on Windows would have shown there to be errors.– tudor
Apr 28 at 11:26
That is really odd, because gparted is showing sda4 as an unused partition, whereas
dfshows things correctly. Did you mount sda4 from gparted? Have you tried viewing sda and its partitions inDisks? Once you've mounted sda4 does it show correctly in there? Do you have the partition show as a drive in the Launcher bar? Can you see/open the Windows folders and files without error from Ubuntu?– Paul Benson
Apr 28 at 15:54