Partition mount/access error and Windows (dual boot) cannot be accessed.
by paulomatheus from LinuxQuestions.org on (#6DE55)
I have the following situation: I use Slackware on the HD (/sda) and Windows on the SSD (/sdb). I created a partition on the HD to save documents that I could access regardless of whether I was on Linux or Windows. It always worked, but today when trying to access this partition through Slackware, the following error appeared:
"An error occurred while accessing 'Novo volume', the system responded: The requested operation has failed: Error mounting system-managed device /dev/sda3: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error"
It was strange, and I entered Windows to check if there was an error there, or if it was only in Linux. Well, for Windows it worked, I accessed it normally. Soon, I realized that it was something with Slackware, and I should solve it there. I entered Slackware and went to Google the possible solution, that's when I saw that some people solved the situation through the command: "fsck /dev/<partition with error>" I used this command, and some confirmations appeared if I wanted to correct it. I allowed the corrections, and then went to check if it would work to access the partition. The error continued. So, I went to access Windows and... I got an error. The message appears: "A disk read error occurred. Press Ctrl+Alt+Del to restart". I found it strange that a command on the HD (/sda) could have interfered with Windows that is on the SSD (sdb). That's when I went to the /etc/lilo.conf file and verified that the boot is being in sda:
Code:boot = /dev/sdaAnd the Windows boot configuration partition is being at /sda3:
Code:# Windows bootable partition config begins
other = /dev/sda3
label = windows
table = /dev/sda
# Windows bootable partition config endsIn this scenario, could the fsck command have corrupted the Windows boot files? Or was it just a coincidence that Windows stopped working after that command?
Why were Windows Boot files created in /sda3 and not in /sdb? Since Windows is installed on the SSD and not the HD?
How to solve this situation? (partition sda3 is not being accessed, and cannot be mounted, and Windows cannot be accessed).
My partition structure is in a print attached to this post, named "lsblk".
Attached Thumbnails
"An error occurred while accessing 'Novo volume', the system responded: The requested operation has failed: Error mounting system-managed device /dev/sda3: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error"
It was strange, and I entered Windows to check if there was an error there, or if it was only in Linux. Well, for Windows it worked, I accessed it normally. Soon, I realized that it was something with Slackware, and I should solve it there. I entered Slackware and went to Google the possible solution, that's when I saw that some people solved the situation through the command: "fsck /dev/<partition with error>" I used this command, and some confirmations appeared if I wanted to correct it. I allowed the corrections, and then went to check if it would work to access the partition. The error continued. So, I went to access Windows and... I got an error. The message appears: "A disk read error occurred. Press Ctrl+Alt+Del to restart". I found it strange that a command on the HD (/sda) could have interfered with Windows that is on the SSD (sdb). That's when I went to the /etc/lilo.conf file and verified that the boot is being in sda:
Code:boot = /dev/sdaAnd the Windows boot configuration partition is being at /sda3:
Code:# Windows bootable partition config begins
other = /dev/sda3
label = windows
table = /dev/sda
# Windows bootable partition config endsIn this scenario, could the fsck command have corrupted the Windows boot files? Or was it just a coincidence that Windows stopped working after that command?
Why were Windows Boot files created in /sda3 and not in /sdb? Since Windows is installed on the SSD and not the HD?
How to solve this situation? (partition sda3 is not being accessed, and cannot be mounted, and Windows cannot be accessed).
My partition structure is in a print attached to this post, named "lsblk".
Attached Thumbnails