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

Thing is, at the rd break, it might not be active. Check with blkid.
If not, then
vgchange -ay




--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org