Forwarding to the group so future searchers can profit by your research, and solution. On Sat, 23 May 2015 20:16:28 +0300 Angelo Moreschini <mrangelo.fedora@xxxxxxxxx> wrote: > The problem was really related to nature of the partition /dev/sda2 on > which is realized a "volume group" managed by LVM: > > > *[angelo_user@localhost ~]$ sudo blkid /dev/sda2* > > *[sudo] password for angelo_user: * > > */dev/sda2: UUID="dSjgjG-WTMY-0ewW-A9Uy-9ent-yPi3-tSZJoj" > TYPE="LVM2_member" PARTUUID="8b5a6842-02"* > > > Now I think to understand that e2fsck can 'only run on normal > partitions (eg ext3.) and from here the error: */dev/sda2 is in > use . e2fsck Cannot continue, aborting.*: > > > Probably it is possible to run directly e2fsck also on LVM > partitions .. > > But being without this experience, I tried to explore things on my way > finding that in the / dev directory there is a /dev/mapper directory > that is used to manage partitions LVM: > > > *[angelo_user@localhost ~]$ ls -l /dev/mapper* > > *total 0* > > *crw-------. 1 root root 10, 236 May 23 18:56 control* > > *lrwxrwxrwx. 1 root root 7 May 23 18:56 fedora_localhost-home > -> ../dm-2* > > *lrwxrwxrwx. 1 root root 7 May 23 18:56 fedora_localhost-root > -> ../dm-1* > > *lrwxrwxrwx. 1 root root 7 May 23 18:56 fedora_localhost-swap > -> ../dm-0* > > > I saw in this way that the directory to be monitored is really / > dev / dm-1, and using idblk: > > > *[angelo_user@localhost ~]$ sudo blkid /dev/dm-2* > > *[sudo] password for angelo_user: * > > */dev/dm-2: UUID="a7d2153f-401c-40e8-b01d-9c2c7f8b84ad" TYPE="ext4"* > > > I saw this is a partition with file system extr4 on which it is > possible to run e2fsck > > > > The problem was solved , in this way, running e2fsck on / dev /dm-2 > > > > > > On Thu, May 21, 2015 at 4:54 PM, stan <stanl-fedorauser@xxxxxxxxxxx> > wrote: > > > On Thu, 21 May 2015 09:38:57 +0300 > > Angelo Moreschini <mrangelo.fedora@xxxxxxxxx> wrote: > > > > > What does > > > cat /etc/mtab show? > > > > > > this is the output : > > > > [snip] > > > > > don't seem me to be /dev/sda2 inside.... > > > > You're right, it isn't the rescue holding the partition. > > [snip] > > > > > > *But perhaps it is a problem that we didn't consider before*: > > > the partition /dev/sda2 have other sub partitions and root is > > > inside one of them... > > > > > > > > > This is the result of lsblk command : > > > > > > root@sysresccd /root % > > > * lsblk*NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > > > sda 8:0 0 149.1G 0 disk > > > ├─sda1 8:1 0 500M 0 part > > > └─sda2 8:2 0 148.6G 0 part > > > ├─fedora-swap 253:0 0 2G 0 lvm > > > ├─fedora-home 253:1 0 96.6G 0 lvm > > > └─fedora-root 253:2 0 50G 0 lvm > > > sr0 11:0 1 394.1M 0 rom /livemnt/boot > > > loop0 7:0 0 279.9M 1 loop /livemnt/squashfs > > > root@sysresccd /root % > > > > > > *I am thinking that in this situation <PERHAPS> il is not > > > possible to work on /dev/sda2 ....* > > > perhaps need to work directly on the sub partitions... > > > <fedora-root 253:2 0 50G 0 lvm > > > > > > > I am not sure but perhaps this can be the problem that fsck > > > doesn't work on /dev/sda2.... > > > > > > What do you think about ? > > > > I think you are right. And once you are talking about lvm, I'm out > > of the picture. I tried it a long time ago, found it solved a > > problem I don't have, and complicated things, so I stopped using > > it. Someone else will have to help you with lvm partitions. > > > > Perhaps it is as simple as running the fsck > > on /dev/mapper/fedora-root, but that is just a guess on my part. > > -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx 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
