Repair possible file system corruption in virtual Linux guest OS (Virtualbox)Linux Mint won't run...
Germany rejected my entry to Schengen countries
How to counter "I don't like your tone" in a work conversation?
On a piano, are the effects of holding notes and the sustain pedal the same for a single chord?
Is my company merging branches wrong?
How to become an Editorial board member?
If you attack a Tarrasque while swallowed, what AC do you need to beat to hit it?
Working hours and productivity expectations for game artists and programmers
Expand a hexagon
Was murdering a slave illegal in American slavery, and if so, what punishments were given for it?
How can sister protect herself from impulse purchases with a credit card?
Is there a word for pant sleeves?
Eigenvalues of the Laplace-Beltrami operator on a compact Riemannnian manifold
Don't understand notation of morphisms in Monoid definition
Existence of a model of ZFC in which the natural numbers are really the natural numbers
What are the domains of the multiplication and unit morphisms of a monoid object?
Why was Houston selected as the location for the Manned Spacecraft Center?
Connecting circles clockwise in TikZ
Story about encounter with hostile aliens
Was Tyrion always a poor strategist?
Is presenting a play showing Military characters in a bad light a crime in the US?
Schwa-less Polysyllabic German Noun Stems of Germanic Origin
Why is there no current between two capacitors connected in series?
Keeping the dodos out of the field
What does it mean for a program to be 32 or 64 bit?
Repair possible file system corruption in virtual Linux guest OS (Virtualbox)
Linux Mint won't run virtualboxHow to install virtualbox guest addition in a guest machine with the latest Archlinux?Is fsck -N mounted file system dangerousSafe to disable boot fsck on read-only ext3 file system?Linux file system corruption due to improper shutdown (fs ext4)?Cannot access internet from VirtualBox guest (Arch Linux)Bidirectional Drag and Drop/Shared Clipboard is not working with VirtualBox Kali LinuxCan't install VirtualBox Guest Additions in Kali Linux virtual machine under Debian (problems installing the kernel-headers)Ubuntu 17.10 guest in Virtualbox 5.2, Xorg driver not workingOracle VirtualBox on Linux host with Windows guest running terribly slow
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
Background
My power went out during some rain recently while I was away from home. When I got back the power was still out and when it came back on, my system seems to have suffered some issues.
Some information about my system:
It is a desktop running Windows 10 Professional installed on two SSDs setup in RAID0. It also has a RAID5 array of three 6TB disks used for bulk storage of media.
I run pretty much everything inside of a Linux Mint 18.3 Guest OS using Virtualbox.
The main virtual disk (VDI) on which Linux Mint is installed is stored on the SSDs, and all of the media on my RAID5 array is shared with the Linux guest OS via the shared folder feature of VirtualBox.
Details
When power was restored to my place, I tried powering up the machine. The Windows 10 host OS booted fine, it didn't even need to run a disk check or anything that I noticed. Seems to be running fine.
When I tried to start up my Linux Mint VM, it also seemed to boot fine, but when I tried to check for OS updates I get the following error:
E: Can't write /root/.synaptic/selections.update
W: Not using locking for read only lock file /root/.synaptic/lock
W: Not using locking for read only lock file /root/.synaptic/lock.non-interactive
After this I realized that my entire main file system that linux was installed on was mounted in read only mode. I am unable to create a new files or write to any existing files. From what I have read it seems that Linux is automatically booting into read only mode because the file system may be corrupted.
I am currently backing up the entire virtual disk image. It is almost a terabyte, so it still has several hours left, after which I am going to attempt to repair the VM.
Question
The advice I found briefly searching the web was that I should run the fsck command to try to repair the file system, but that I can only do this on an unmounted file system. From what I read it was recommended to boot from a USB/LiveCD and use that to run fsck on the unmounted file system.
Is it possible for me to do this for my VirtualBox VM? If so, how? Does anyone have any other advice on how I can go about attempting to repair this system?
linux linux-mint filesystems virtualbox fsck
New contributor
Cory Gross is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Background
My power went out during some rain recently while I was away from home. When I got back the power was still out and when it came back on, my system seems to have suffered some issues.
Some information about my system:
It is a desktop running Windows 10 Professional installed on two SSDs setup in RAID0. It also has a RAID5 array of three 6TB disks used for bulk storage of media.
I run pretty much everything inside of a Linux Mint 18.3 Guest OS using Virtualbox.
The main virtual disk (VDI) on which Linux Mint is installed is stored on the SSDs, and all of the media on my RAID5 array is shared with the Linux guest OS via the shared folder feature of VirtualBox.
Details
When power was restored to my place, I tried powering up the machine. The Windows 10 host OS booted fine, it didn't even need to run a disk check or anything that I noticed. Seems to be running fine.
When I tried to start up my Linux Mint VM, it also seemed to boot fine, but when I tried to check for OS updates I get the following error:
E: Can't write /root/.synaptic/selections.update
W: Not using locking for read only lock file /root/.synaptic/lock
W: Not using locking for read only lock file /root/.synaptic/lock.non-interactive
After this I realized that my entire main file system that linux was installed on was mounted in read only mode. I am unable to create a new files or write to any existing files. From what I have read it seems that Linux is automatically booting into read only mode because the file system may be corrupted.
I am currently backing up the entire virtual disk image. It is almost a terabyte, so it still has several hours left, after which I am going to attempt to repair the VM.
Question
The advice I found briefly searching the web was that I should run the fsck command to try to repair the file system, but that I can only do this on an unmounted file system. From what I read it was recommended to boot from a USB/LiveCD and use that to run fsck on the unmounted file system.
Is it possible for me to do this for my VirtualBox VM? If so, how? Does anyone have any other advice on how I can go about attempting to repair this system?
linux linux-mint filesystems virtualbox fsck
New contributor
Cory Gross is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
am writing you a full answer ;)
– intika
10 mins ago
You can put a Linux LiveCD ISO into your virtual optical drive, start the machine, boot from it and then runfsckon your partitions.
– Freddy
1 min ago
add a comment |
Background
My power went out during some rain recently while I was away from home. When I got back the power was still out and when it came back on, my system seems to have suffered some issues.
Some information about my system:
It is a desktop running Windows 10 Professional installed on two SSDs setup in RAID0. It also has a RAID5 array of three 6TB disks used for bulk storage of media.
I run pretty much everything inside of a Linux Mint 18.3 Guest OS using Virtualbox.
The main virtual disk (VDI) on which Linux Mint is installed is stored on the SSDs, and all of the media on my RAID5 array is shared with the Linux guest OS via the shared folder feature of VirtualBox.
Details
When power was restored to my place, I tried powering up the machine. The Windows 10 host OS booted fine, it didn't even need to run a disk check or anything that I noticed. Seems to be running fine.
When I tried to start up my Linux Mint VM, it also seemed to boot fine, but when I tried to check for OS updates I get the following error:
E: Can't write /root/.synaptic/selections.update
W: Not using locking for read only lock file /root/.synaptic/lock
W: Not using locking for read only lock file /root/.synaptic/lock.non-interactive
After this I realized that my entire main file system that linux was installed on was mounted in read only mode. I am unable to create a new files or write to any existing files. From what I have read it seems that Linux is automatically booting into read only mode because the file system may be corrupted.
I am currently backing up the entire virtual disk image. It is almost a terabyte, so it still has several hours left, after which I am going to attempt to repair the VM.
Question
The advice I found briefly searching the web was that I should run the fsck command to try to repair the file system, but that I can only do this on an unmounted file system. From what I read it was recommended to boot from a USB/LiveCD and use that to run fsck on the unmounted file system.
Is it possible for me to do this for my VirtualBox VM? If so, how? Does anyone have any other advice on how I can go about attempting to repair this system?
linux linux-mint filesystems virtualbox fsck
New contributor
Cory Gross is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Background
My power went out during some rain recently while I was away from home. When I got back the power was still out and when it came back on, my system seems to have suffered some issues.
Some information about my system:
It is a desktop running Windows 10 Professional installed on two SSDs setup in RAID0. It also has a RAID5 array of three 6TB disks used for bulk storage of media.
I run pretty much everything inside of a Linux Mint 18.3 Guest OS using Virtualbox.
The main virtual disk (VDI) on which Linux Mint is installed is stored on the SSDs, and all of the media on my RAID5 array is shared with the Linux guest OS via the shared folder feature of VirtualBox.
Details
When power was restored to my place, I tried powering up the machine. The Windows 10 host OS booted fine, it didn't even need to run a disk check or anything that I noticed. Seems to be running fine.
When I tried to start up my Linux Mint VM, it also seemed to boot fine, but when I tried to check for OS updates I get the following error:
E: Can't write /root/.synaptic/selections.update
W: Not using locking for read only lock file /root/.synaptic/lock
W: Not using locking for read only lock file /root/.synaptic/lock.non-interactive
After this I realized that my entire main file system that linux was installed on was mounted in read only mode. I am unable to create a new files or write to any existing files. From what I have read it seems that Linux is automatically booting into read only mode because the file system may be corrupted.
I am currently backing up the entire virtual disk image. It is almost a terabyte, so it still has several hours left, after which I am going to attempt to repair the VM.
Question
The advice I found briefly searching the web was that I should run the fsck command to try to repair the file system, but that I can only do this on an unmounted file system. From what I read it was recommended to boot from a USB/LiveCD and use that to run fsck on the unmounted file system.
Is it possible for me to do this for my VirtualBox VM? If so, how? Does anyone have any other advice on how I can go about attempting to repair this system?
linux linux-mint filesystems virtualbox fsck
linux linux-mint filesystems virtualbox fsck
New contributor
Cory Gross is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Cory Gross is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Cory Gross is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 21 mins ago
Cory GrossCory Gross
1011
1011
New contributor
Cory Gross is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Cory Gross is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
am writing you a full answer ;)
– intika
10 mins ago
You can put a Linux LiveCD ISO into your virtual optical drive, start the machine, boot from it and then runfsckon your partitions.
– Freddy
1 min ago
add a comment |
am writing you a full answer ;)
– intika
10 mins ago
You can put a Linux LiveCD ISO into your virtual optical drive, start the machine, boot from it and then runfsckon your partitions.
– Freddy
1 min ago
am writing you a full answer ;)
– intika
10 mins ago
am writing you a full answer ;)
– intika
10 mins ago
You can put a Linux LiveCD ISO into your virtual optical drive, start the machine, boot from it and then run
fsck on your partitions.– Freddy
1 min ago
You can put a Linux LiveCD ISO into your virtual optical drive, start the machine, boot from it and then run
fsck on your partitions.– Freddy
1 min ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});
}
});
Cory Gross is a new contributor. Be nice, and check out our Code of Conduct.
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%2funix.stackexchange.com%2fquestions%2f519745%2frepair-possible-file-system-corruption-in-virtual-linux-guest-os-virtualbox%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Cory Gross is a new contributor. Be nice, and check out our Code of Conduct.
Cory Gross is a new contributor. Be nice, and check out our Code of Conduct.
Cory Gross is a new contributor. Be nice, and check out our Code of Conduct.
Cory Gross is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f519745%2frepair-possible-file-system-corruption-in-virtual-linux-guest-os-virtualbox%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
am writing you a full answer ;)
– intika
10 mins ago
You can put a Linux LiveCD ISO into your virtual optical drive, start the machine, boot from it and then run
fsckon your partitions.– Freddy
1 min ago