Windows 10 corrupts Ubuntu 18.04 partitions
up vote
3
down vote
favorite
I have a dual boot machine, booting both Windows 10 and Ubuntu. Ubuntu 16.04 works fine, but each time after I boot Windows 10, Ubuntu 18.04 has a corrupted superblock, or so it says. The only way to solve this is to boot into Ubuntu 16.04 and correct it with the new e2fsck. I have installed Ubuntu 18.04 on two different partitions, but both get corrupted by Windows 10. The Computer is an Asus laptop with UEFI and a GPT hard disk. If you need more specific information to solve this, please let me know.
Currently Ubuntu 18.04 is hardly usable as the partition has to be corrected each time after I use Windows 10, which happens at least once a day.
dual-boot uefi ext4
edited Mar 31 at 0:04
Eliah Kagan
80.9k20226364
asked Mar 27 at 22:22
Dirk Heitman
1813
|
show 1 more comment
up vote
3
down vote
favorite
I have a dual boot machine, booting both Windows 10 and Ubuntu. Ubuntu 16.04 works fine, but each time after I boot Windows 10, Ubuntu 18.04 has a corrupted superblock, or so it says. The only way to solve this is to boot into Ubuntu 16.04 and correct it with the new e2fsck. I have installed Ubuntu 18.04 on two different partitions, but both get corrupted by Windows 10. The Computer is an Asus laptop with UEFI and a GPT hard disk. If you need more specific information to solve this, please let me know.
Currently Ubuntu 18.04 is hardly usable as the partition has to be corrected each time after I use Windows 10, which happens at least once a day.
dual-boot uefi ext4
edited Mar 31 at 0:04
Eliah Kagan
80.9k20226364
asked Mar 27 at 22:22
Dirk Heitman
1813
1
Have you installed a driver in Windows that allows you to access ext4 partitions? If so, that's probably your problem. Uninstall it asap.
– heynnema
Mar 28 at 15:14
You were absolutely right, I did install ext2fsd some years ago. It never gave problems, so I forgot about it. Removing it, repairing the 18.04 partitions using the new e2fsck fixed it. The corruption does not happen anymore. Only a few grub2 problems with gpt partitions remain. They also were there in the beginning of 16.04, but went away at some point. Just inconveniences which I should be able to fix. Thanks a lot for the advice.
– Dirk Heitman
Mar 29 at 13:46
1
I'm voting to reopen this. Its closure was not clearly wrong, as it's asking about a stability problem seeming to arise in 18.04. But it turns out this was not a problem specific to a development version of Ubuntu. See the comments above confirming the cause, as well as heynnema's answer. Arguably the problem arose as a result of a bug in the Windows driver being used to access Ubuntu's filesystem, but that's not likely to be reportable on Launchpad, and the goal of this question was to identify and fix the problem, not to keep using that driver.
– Eliah Kagan
Mar 31 at 20:44
@EliahKagan I was about to VTC as 18.04 off-topic. Then I read your comment. Could one of the stakeholders here edit the question and take out all the 18.04 references so someone else doesn't VTC as 18.04 off-topic?
– WinEunuuchs2Unix
Apr 1 at 18:34
@WinEunuuchs2Unix. Sorry to say but the 18.04 reference is relevant, as 18.04 seems to use a new ext4 partition (feature). This causes the ext2fsd driver to misbehave. I agree the problem is not in Ubuntu 18.04, but it is the (only) victim so far. Other users may look here also for the solution. heynnema, thanks again for the quick and accurate answer. Maybe you can add that the fsck in grub will spit out an enormous amount of errors. I gave up after watching the screen for 5 minutes showing errors and switched to 16.04 to fix it.
– Dirk Heitman
Apr 2 at 7:47
|
show 1 more comment
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I have a dual boot machine, booting both Windows 10 and Ubuntu. Ubuntu 16.04 works fine, but each time after I boot Windows 10, Ubuntu 18.04 has a corrupted superblock, or so it says. The only way to solve this is to boot into Ubuntu 16.04 and correct it with the new e2fsck. I have installed Ubuntu 18.04 on two different partitions, but both get corrupted by Windows 10. The Computer is an Asus laptop with UEFI and a GPT hard disk. If you need more specific information to solve this, please let me know.
Currently Ubuntu 18.04 is hardly usable as the partition has to be corrected each time after I use Windows 10, which happens at least once a day.
dual-boot uefi ext4
edited Mar 31 at 0:04
Eliah Kagan
80.9k20226364
asked Mar 27 at 22:22
Dirk Heitman
1813
I have a dual boot machine, booting both Windows 10 and Ubuntu. Ubuntu 16.04 works fine, but each time after I boot Windows 10, Ubuntu 18.04 has a corrupted superblock, or so it says. The only way to solve this is to boot into Ubuntu 16.04 and correct it with the new e2fsck. I have installed Ubuntu 18.04 on two different partitions, but both get corrupted by Windows 10. The Computer is an Asus laptop with UEFI and a GPT hard disk. If you need more specific information to solve this, please let me know.
Currently Ubuntu 18.04 is hardly usable as the partition has to be corrected each time after I use Windows 10, which happens at least once a day.
dual-boot uefi ext4
dual-boot uefi ext4
edited Mar 31 at 0:04
Eliah Kagan
80.9k20226364
asked Mar 27 at 22:22
Dirk Heitman
1813
edited Mar 31 at 0:04
Eliah Kagan
80.9k20226364
asked Mar 27 at 22:22
Dirk Heitman
1813
edited Mar 31 at 0:04
Eliah Kagan
80.9k20226364
edited Mar 31 at 0:04
Eliah Kagan
80.9k20226364
edited Mar 31 at 0:04
Eliah Kagan
80.9k20226364
80.9k20226364
asked Mar 27 at 22:22
Dirk Heitman
1813
asked Mar 27 at 22:22
Dirk Heitman
1813
asked Mar 27 at 22:22
Dirk Heitman
1813
1813
1
Have you installed a driver in Windows that allows you to access ext4 partitions? If so, that's probably your problem. Uninstall it asap.
– heynnema
Mar 28 at 15:14
You were absolutely right, I did install ext2fsd some years ago. It never gave problems, so I forgot about it. Removing it, repairing the 18.04 partitions using the new e2fsck fixed it. The corruption does not happen anymore. Only a few grub2 problems with gpt partitions remain. They also were there in the beginning of 16.04, but went away at some point. Just inconveniences which I should be able to fix. Thanks a lot for the advice.
– Dirk Heitman
Mar 29 at 13:46
1
I'm voting to reopen this. Its closure was not clearly wrong, as it's asking about a stability problem seeming to arise in 18.04. But it turns out this was not a problem specific to a development version of Ubuntu. See the comments above confirming the cause, as well as heynnema's answer. Arguably the problem arose as a result of a bug in the Windows driver being used to access Ubuntu's filesystem, but that's not likely to be reportable on Launchpad, and the goal of this question was to identify and fix the problem, not to keep using that driver.
– Eliah Kagan
Mar 31 at 20:44
@EliahKagan I was about to VTC as 18.04 off-topic. Then I read your comment. Could one of the stakeholders here edit the question and take out all the 18.04 references so someone else doesn't VTC as 18.04 off-topic?
– WinEunuuchs2Unix
Apr 1 at 18:34
@WinEunuuchs2Unix. Sorry to say but the 18.04 reference is relevant, as 18.04 seems to use a new ext4 partition (feature). This causes the ext2fsd driver to misbehave. I agree the problem is not in Ubuntu 18.04, but it is the (only) victim so far. Other users may look here also for the solution. heynnema, thanks again for the quick and accurate answer. Maybe you can add that the fsck in grub will spit out an enormous amount of errors. I gave up after watching the screen for 5 minutes showing errors and switched to 16.04 to fix it.
– Dirk Heitman
Apr 2 at 7:47
|
show 1 more comment
1
Have you installed a driver in Windows that allows you to access ext4 partitions? If so, that's probably your problem. Uninstall it asap.
– heynnema
Mar 28 at 15:14
You were absolutely right, I did install ext2fsd some years ago. It never gave problems, so I forgot about it. Removing it, repairing the 18.04 partitions using the new e2fsck fixed it. The corruption does not happen anymore. Only a few grub2 problems with gpt partitions remain. They also were there in the beginning of 16.04, but went away at some point. Just inconveniences which I should be able to fix. Thanks a lot for the advice.
– Dirk Heitman
Mar 29 at 13:46
1
I'm voting to reopen this. Its closure was not clearly wrong, as it's asking about a stability problem seeming to arise in 18.04. But it turns out this was not a problem specific to a development version of Ubuntu. See the comments above confirming the cause, as well as heynnema's answer. Arguably the problem arose as a result of a bug in the Windows driver being used to access Ubuntu's filesystem, but that's not likely to be reportable on Launchpad, and the goal of this question was to identify and fix the problem, not to keep using that driver.
– Eliah Kagan
Mar 31 at 20:44
@EliahKagan I was about to VTC as 18.04 off-topic. Then I read your comment. Could one of the stakeholders here edit the question and take out all the 18.04 references so someone else doesn't VTC as 18.04 off-topic?
– WinEunuuchs2Unix
Apr 1 at 18:34
@WinEunuuchs2Unix. Sorry to say but the 18.04 reference is relevant, as 18.04 seems to use a new ext4 partition (feature). This causes the ext2fsd driver to misbehave. I agree the problem is not in Ubuntu 18.04, but it is the (only) victim so far. Other users may look here also for the solution. heynnema, thanks again for the quick and accurate answer. Maybe you can add that the fsck in grub will spit out an enormous amount of errors. I gave up after watching the screen for 5 minutes showing errors and switched to 16.04 to fix it.
– Dirk Heitman
Apr 2 at 7:47
1
1
Have you installed a driver in Windows that allows you to access ext4 partitions? If so, that's probably your problem. Uninstall it asap.
– heynnema
Mar 28 at 15:14
Have you installed a driver in Windows that allows you to access ext4 partitions? If so, that's probably your problem. Uninstall it asap.
– heynnema
Mar 28 at 15:14
You were absolutely right, I did install ext2fsd some years ago. It never gave problems, so I forgot about it. Removing it, repairing the 18.04 partitions using the new e2fsck fixed it. The corruption does not happen anymore. Only a few grub2 problems with gpt partitions remain. They also were there in the beginning of 16.04, but went away at some point. Just inconveniences which I should be able to fix. Thanks a lot for the advice.
– Dirk Heitman
Mar 29 at 13:46
You were absolutely right, I did install ext2fsd some years ago. It never gave problems, so I forgot about it. Removing it, repairing the 18.04 partitions using the new e2fsck fixed it. The corruption does not happen anymore. Only a few grub2 problems with gpt partitions remain. They also were there in the beginning of 16.04, but went away at some point. Just inconveniences which I should be able to fix. Thanks a lot for the advice.
– Dirk Heitman
Mar 29 at 13:46
1
1
I'm voting to reopen this. Its closure was not clearly wrong, as it's asking about a stability problem seeming to arise in 18.04. But it turns out this was not a problem specific to a development version of Ubuntu. See the comments above confirming the cause, as well as heynnema's answer. Arguably the problem arose as a result of a bug in the Windows driver being used to access Ubuntu's filesystem, but that's not likely to be reportable on Launchpad, and the goal of this question was to identify and fix the problem, not to keep using that driver.
– Eliah Kagan
Mar 31 at 20:44
I'm voting to reopen this. Its closure was not clearly wrong, as it's asking about a stability problem seeming to arise in 18.04. But it turns out this was not a problem specific to a development version of Ubuntu. See the comments above confirming the cause, as well as heynnema's answer. Arguably the problem arose as a result of a bug in the Windows driver being used to access Ubuntu's filesystem, but that's not likely to be reportable on Launchpad, and the goal of this question was to identify and fix the problem, not to keep using that driver.
– Eliah Kagan
Mar 31 at 20:44
@EliahKagan I was about to VTC as 18.04 off-topic. Then I read your comment. Could one of the stakeholders here edit the question and take out all the 18.04 references so someone else doesn't VTC as 18.04 off-topic?
– WinEunuuchs2Unix
Apr 1 at 18:34
@EliahKagan I was about to VTC as 18.04 off-topic. Then I read your comment. Could one of the stakeholders here edit the question and take out all the 18.04 references so someone else doesn't VTC as 18.04 off-topic?
– WinEunuuchs2Unix
Apr 1 at 18:34
@WinEunuuchs2Unix. Sorry to say but the 18.04 reference is relevant, as 18.04 seems to use a new ext4 partition (feature). This causes the ext2fsd driver to misbehave. I agree the problem is not in Ubuntu 18.04, but it is the (only) victim so far. Other users may look here also for the solution. heynnema, thanks again for the quick and accurate answer. Maybe you can add that the fsck in grub will spit out an enormous amount of errors. I gave up after watching the screen for 5 minutes showing errors and switched to 16.04 to fix it.
– Dirk Heitman
Apr 2 at 7:47
@WinEunuuchs2Unix. Sorry to say but the 18.04 reference is relevant, as 18.04 seems to use a new ext4 partition (feature). This causes the ext2fsd driver to misbehave. I agree the problem is not in Ubuntu 18.04, but it is the (only) victim so far. Other users may look here also for the solution. heynnema, thanks again for the quick and accurate answer. Maybe you can add that the fsck in grub will spit out an enormous amount of errors. I gave up after watching the screen for 5 minutes showing errors and switched to 16.04 to fix it.
– Dirk Heitman
Apr 2 at 7:47
|
show 1 more comment
1 Answer
1
active
oldest
votes
up vote
7
down vote
accepted
In a dual boot configuration with Windows and Ubuntu, Ubuntu can easily read Windows NTFS partitions/disks, however, when booted into Windows, Windows can't natively read/mount Ubuntu ext[2-4] partitions/disks.
Many users try to remedy this by installing a Windows driver (like ext2fsd) that will allow them to read/mount ext[2-4] partitions.
My experience is that these Windows drivers can regularly corrupt the Ubuntu ext[2-4] partitions. Uninstall this driver in Windows, and fsck your Ubuntu partition, and you should be fine.
To check the file system on your Ubuntu partition...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted
- open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Mar 30 at 23:39
heynnema
17.4k22053
Microsoft even agrees with you: blogs.msdn.microsoft.com/commandline/2016/11/17/…
– K7AAY
Jul 11 at 17:36
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
7
down vote
accepted
In a dual boot configuration with Windows and Ubuntu, Ubuntu can easily read Windows NTFS partitions/disks, however, when booted into Windows, Windows can't natively read/mount Ubuntu ext[2-4] partitions/disks.
Many users try to remedy this by installing a Windows driver (like ext2fsd) that will allow them to read/mount ext[2-4] partitions.
My experience is that these Windows drivers can regularly corrupt the Ubuntu ext[2-4] partitions. Uninstall this driver in Windows, and fsck your Ubuntu partition, and you should be fine.
To check the file system on your Ubuntu partition...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted
- open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Mar 30 at 23:39
heynnema
17.4k22053
Microsoft even agrees with you: blogs.msdn.microsoft.com/commandline/2016/11/17/…
– K7AAY
Jul 11 at 17:36
add a comment |
up vote
7
down vote
accepted
In a dual boot configuration with Windows and Ubuntu, Ubuntu can easily read Windows NTFS partitions/disks, however, when booted into Windows, Windows can't natively read/mount Ubuntu ext[2-4] partitions/disks.
Many users try to remedy this by installing a Windows driver (like ext2fsd) that will allow them to read/mount ext[2-4] partitions.
My experience is that these Windows drivers can regularly corrupt the Ubuntu ext[2-4] partitions. Uninstall this driver in Windows, and fsck your Ubuntu partition, and you should be fine.
To check the file system on your Ubuntu partition...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted
- open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Mar 30 at 23:39
heynnema
17.4k22053
Microsoft even agrees with you: blogs.msdn.microsoft.com/commandline/2016/11/17/…
– K7AAY
Jul 11 at 17:36
add a comment |
up vote
7
down vote
accepted
up vote
7
down vote
accepted
In a dual boot configuration with Windows and Ubuntu, Ubuntu can easily read Windows NTFS partitions/disks, however, when booted into Windows, Windows can't natively read/mount Ubuntu ext[2-4] partitions/disks.
Many users try to remedy this by installing a Windows driver (like ext2fsd) that will allow them to read/mount ext[2-4] partitions.
My experience is that these Windows drivers can regularly corrupt the Ubuntu ext[2-4] partitions. Uninstall this driver in Windows, and fsck your Ubuntu partition, and you should be fine.
To check the file system on your Ubuntu partition...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted
- open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Mar 30 at 23:39
heynnema
17.4k22053
In a dual boot configuration with Windows and Ubuntu, Ubuntu can easily read Windows NTFS partitions/disks, however, when booted into Windows, Windows can't natively read/mount Ubuntu ext[2-4] partitions/disks.
Many users try to remedy this by installing a Windows driver (like ext2fsd) that will allow them to read/mount ext[2-4] partitions.
My experience is that these Windows drivers can regularly corrupt the Ubuntu ext[2-4] partitions. Uninstall this driver in Windows, and fsck your Ubuntu partition, and you should be fine.
To check the file system on your Ubuntu partition...
- boot to the GRUB menu
- choose Advanced Options
- choose Recovery mode
- choose Root access
- at the # prompt, type
sudo fsck -f /
- repeat the
fsckcommand if there were errors - type
reboot
If for some reason you can't do the above...
- boot to a Ubuntu Live DVD/USB
- start
gpartedand determine which /dev/sdaX is your Ubuntu EXT4 partition - quit
gparted
- open a
terminalwindow - type
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier - repeat the fsck command if there were errors
- type
reboot
answered Mar 30 at 23:39
heynnema
17.4k22053
answered Mar 30 at 23:39
heynnema
17.4k22053
answered Mar 30 at 23:39
heynnema
17.4k22053
answered Mar 30 at 23:39
heynnema
17.4k22053
17.4k22053
Microsoft even agrees with you: blogs.msdn.microsoft.com/commandline/2016/11/17/…
– K7AAY
Jul 11 at 17:36
add a comment |
Microsoft even agrees with you: blogs.msdn.microsoft.com/commandline/2016/11/17/…
– K7AAY
Jul 11 at 17:36
Microsoft even agrees with you: blogs.msdn.microsoft.com/commandline/2016/11/17/…
– K7AAY
Jul 11 at 17:36
Microsoft even agrees with you: blogs.msdn.microsoft.com/commandline/2016/11/17/…
– K7AAY
Jul 11 at 17:36
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1019790%2fwindows-10-corrupts-ubuntu-18-04-partitions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Have you installed a driver in Windows that allows you to access ext4 partitions? If so, that's probably your problem. Uninstall it asap.
– heynnema
Mar 28 at 15:14
You were absolutely right, I did install ext2fsd some years ago. It never gave problems, so I forgot about it. Removing it, repairing the 18.04 partitions using the new e2fsck fixed it. The corruption does not happen anymore. Only a few grub2 problems with gpt partitions remain. They also were there in the beginning of 16.04, but went away at some point. Just inconveniences which I should be able to fix. Thanks a lot for the advice.
– Dirk Heitman
Mar 29 at 13:46
1
I'm voting to reopen this. Its closure was not clearly wrong, as it's asking about a stability problem seeming to arise in 18.04. But it turns out this was not a problem specific to a development version of Ubuntu. See the comments above confirming the cause, as well as heynnema's answer. Arguably the problem arose as a result of a bug in the Windows driver being used to access Ubuntu's filesystem, but that's not likely to be reportable on Launchpad, and the goal of this question was to identify and fix the problem, not to keep using that driver.
– Eliah Kagan
Mar 31 at 20:44
@EliahKagan I was about to VTC as 18.04 off-topic. Then I read your comment. Could one of the stakeholders here edit the question and take out all the 18.04 references so someone else doesn't VTC as 18.04 off-topic?
– WinEunuuchs2Unix
Apr 1 at 18:34
@WinEunuuchs2Unix. Sorry to say but the 18.04 reference is relevant, as 18.04 seems to use a new ext4 partition (feature). This causes the ext2fsd driver to misbehave. I agree the problem is not in Ubuntu 18.04, but it is the (only) victim so far. Other users may look here also for the solution. heynnema, thanks again for the quick and accurate answer. Maybe you can add that the fsck in grub will spit out an enormous amount of errors. I gave up after watching the screen for 5 minutes showing errors and switched to 16.04 to fix it.
– Dirk Heitman
Apr 2 at 7:47