On Sat, Feb 28, 2015 at 4:12 AM, Chris Murphy lists@colorremedies.com wrote:
On Feb 28, 2015 3:37 AM, "Angelo Moreschini" mrangelo.fedora@gmail.com wrote:
Hi
I tried with e2fsck -f /dev/sdc1 but I got the message:
Buried in my long first reply: "booting with parameter rd.break=cmdline"
Chances are it's not sdc1 damaged. It's lv-root.
WARNING!!! The filesystem is mounted. If you continue you ***WILL*** cause ***SEVERE*** filesystem damage.
Of curse I didn't continue...
How I have to do this test ? Have I to boot the computer using some utility that didn't need the hard disk ?
On Thu, Feb 26, 2015 at 6:35 PM, Chris Murphy lists@colorremedies.com wrote:
On Thu, Feb 26, 2015 at 5:22 AM, Angelo Moreschini mrangelo.fedora@gmail.com wrote:
Hi Chris,
I would be more inclined to to think about a electrical problem, since the only rep-plugging of the connectors of the HD solves the problem ..
Cable connectors are often a source of problems.
This is what I get with the command blkid (the output concern only the partition where is the OS Fedora):
/dev/sdc1: UUID="4b1e5e09-306b-4c17-8c2f-653b32e1b956" TYPE="ext4" PARTUUID="0008635c-01" /dev/sdc2: UUID="Vtbdeq-eq6H-sbMY-Mpme-UyFk-jx77-I5Z20K" TYPE="LVM2_member" PARTUUID="0008635c-02" /dev/mapper/fedora-root: UUID="2d224b16-d37f-4eee-820a-dfcd5929e05e" TYPE="ext4" /dev/mapper/fedora-swap: UUID="54d55595-8c35-4e84-8566-89d8b6f340e8" TYPE="swap"
so I should do : e2fsck -f /dev/sdc1 and after e2fsck -f /dev/sdc2
Yes for sdc1, but not for sdc2 which is an LVM PV. You need to do e2fsck -f /dev/mapper/fedora/root
So I just had to do this, and LVM isn't activate this early in the boot process using cmdline. Adding this to the end of the GRUB boot entry linux line (after rhgb quiet) works: rd.break=pre-mount And then F10 or cntrl-x to boot. And then at the prompt: e2fsck -f /dev/mapper/VG-root ##assumes ext file system