Filesystem corruption on shutdown/reboot
I have a system which dual boots between Windows 10 and Ubuntu 17.10. This system contains an SSD (both OSes are there) a couple of internal disks, one of which is formatted in NTFS and the other one in EXT4 and an external disk, formatted in NTFS. Most of the time I use linux.
Mountpoints for all the disks except for the EXT4 disk have been created automatically by ubuntu, since they were all present when I installed ubuntu. The EXT4 disk was added later, and I manually created a mountpoint and fstab entry, pointing to a subdirectory under my home directory (i.e. orestis/newdisk).
The issue is that most of the time when I reboot or shutdown the system, the filesystem becomes corrupted, with invalid superblock and inode counts. The damage does not appear to be permanent, since an fsck restores everything to working order, but it is annoying and time consuming.
I have been using pycharm and python virtual environments with this disk, but I have tried to make sure that everything is closed and even issue unmount manually, to no avail. The thing is that I've had no similar issue with other disks. The disk is new and has been checked thoroughly for hardware errors
mount hard-drive filesystem shutdown ext4
asked Nov 1 '18 at 8:07
OrestisOrestis
163
add a comment |
I have a system which dual boots between Windows 10 and Ubuntu 17.10. This system contains an SSD (both OSes are there) a couple of internal disks, one of which is formatted in NTFS and the other one in EXT4 and an external disk, formatted in NTFS. Most of the time I use linux.
Mountpoints for all the disks except for the EXT4 disk have been created automatically by ubuntu, since they were all present when I installed ubuntu. The EXT4 disk was added later, and I manually created a mountpoint and fstab entry, pointing to a subdirectory under my home directory (i.e. orestis/newdisk).
The issue is that most of the time when I reboot or shutdown the system, the filesystem becomes corrupted, with invalid superblock and inode counts. The damage does not appear to be permanent, since an fsck restores everything to working order, but it is annoying and time consuming.
I have been using pycharm and python virtual environments with this disk, but I have tried to make sure that everything is closed and even issue unmount manually, to no avail. The thing is that I've had no similar issue with other disks. The disk is new and has been checked thoroughly for hardware errors
mount hard-drive filesystem shutdown ext4
asked Nov 1 '18 at 8:07
OrestisOrestis
163
add a comment |
I have a system which dual boots between Windows 10 and Ubuntu 17.10. This system contains an SSD (both OSes are there) a couple of internal disks, one of which is formatted in NTFS and the other one in EXT4 and an external disk, formatted in NTFS. Most of the time I use linux.
Mountpoints for all the disks except for the EXT4 disk have been created automatically by ubuntu, since they were all present when I installed ubuntu. The EXT4 disk was added later, and I manually created a mountpoint and fstab entry, pointing to a subdirectory under my home directory (i.e. orestis/newdisk).
The issue is that most of the time when I reboot or shutdown the system, the filesystem becomes corrupted, with invalid superblock and inode counts. The damage does not appear to be permanent, since an fsck restores everything to working order, but it is annoying and time consuming.
I have been using pycharm and python virtual environments with this disk, but I have tried to make sure that everything is closed and even issue unmount manually, to no avail. The thing is that I've had no similar issue with other disks. The disk is new and has been checked thoroughly for hardware errors
mount hard-drive filesystem shutdown ext4
asked Nov 1 '18 at 8:07
OrestisOrestis
163
I have a system which dual boots between Windows 10 and Ubuntu 17.10. This system contains an SSD (both OSes are there) a couple of internal disks, one of which is formatted in NTFS and the other one in EXT4 and an external disk, formatted in NTFS. Most of the time I use linux.
Mountpoints for all the disks except for the EXT4 disk have been created automatically by ubuntu, since they were all present when I installed ubuntu. The EXT4 disk was added later, and I manually created a mountpoint and fstab entry, pointing to a subdirectory under my home directory (i.e. orestis/newdisk).
The issue is that most of the time when I reboot or shutdown the system, the filesystem becomes corrupted, with invalid superblock and inode counts. The damage does not appear to be permanent, since an fsck restores everything to working order, but it is annoying and time consuming.
I have been using pycharm and python virtual environments with this disk, but I have tried to make sure that everything is closed and even issue unmount manually, to no avail. The thing is that I've had no similar issue with other disks. The disk is new and has been checked thoroughly for hardware errors
mount hard-drive filesystem shutdown ext4
mount hard-drive filesystem shutdown ext4
asked Nov 1 '18 at 8:07
OrestisOrestis
163
asked Nov 1 '18 at 8:07
OrestisOrestis
163
asked Nov 1 '18 at 8:07
OrestisOrestis
163
asked Nov 1 '18 at 8:07
OrestisOrestis
163
asked Nov 1 '18 at 8:07
OrestisOrestis
163
163
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Well, it would appear that the cause of the issue was the existence of the ext2fsd driver (and possibly another similar windows driver I had been toying with). Although I don't remember having booted windows each time this issue occured. Uninstalling the ext2 drivers seems to have resolved the issue for now.
See:
How can I prevent Windows 10 from corrupting the ext4 superblock every time?
answered 3 hours ago
OrestisOrestis
163
Thanks for sharing your solution :-)
– sudodus
3 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f1089121%2ffilesystem-corruption-on-shutdown-reboot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Well, it would appear that the cause of the issue was the existence of the ext2fsd driver (and possibly another similar windows driver I had been toying with). Although I don't remember having booted windows each time this issue occured. Uninstalling the ext2 drivers seems to have resolved the issue for now.
See:
How can I prevent Windows 10 from corrupting the ext4 superblock every time?
answered 3 hours ago
OrestisOrestis
163
Thanks for sharing your solution :-)
– sudodus
3 hours ago
add a comment |
Well, it would appear that the cause of the issue was the existence of the ext2fsd driver (and possibly another similar windows driver I had been toying with). Although I don't remember having booted windows each time this issue occured. Uninstalling the ext2 drivers seems to have resolved the issue for now.
See:
How can I prevent Windows 10 from corrupting the ext4 superblock every time?
answered 3 hours ago
OrestisOrestis
163
Thanks for sharing your solution :-)
– sudodus
3 hours ago
add a comment |
Well, it would appear that the cause of the issue was the existence of the ext2fsd driver (and possibly another similar windows driver I had been toying with). Although I don't remember having booted windows each time this issue occured. Uninstalling the ext2 drivers seems to have resolved the issue for now.
See:
How can I prevent Windows 10 from corrupting the ext4 superblock every time?
answered 3 hours ago
OrestisOrestis
163
Well, it would appear that the cause of the issue was the existence of the ext2fsd driver (and possibly another similar windows driver I had been toying with). Although I don't remember having booted windows each time this issue occured. Uninstalling the ext2 drivers seems to have resolved the issue for now.
See:
How can I prevent Windows 10 from corrupting the ext4 superblock every time?
answered 3 hours ago
OrestisOrestis
163
answered 3 hours ago
OrestisOrestis
163
answered 3 hours ago
OrestisOrestis
163
answered 3 hours ago
OrestisOrestis
163
163
Thanks for sharing your solution :-)
– sudodus
3 hours ago
add a comment |
Thanks for sharing your solution :-)
– sudodus
3 hours ago
Thanks for sharing your solution :-)
– sudodus
3 hours ago
Thanks for sharing your solution :-)
– sudodus
3 hours ago
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.
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%2f1089121%2ffilesystem-corruption-on-shutdown-reboot%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
