I can't boot after add more space to /root ,
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I think I do something wrong and made filesystem mess , please look that pic , I can't boot , it said emergency mode, please exit to the shell
And after I check the logs
It said my default.target has a problem:
Failed to start default.target: Transaction is destructive
linux fedora filesystems boot root-filesystem
edited Feb 26 at 9:15
Ulrich Schwarz
8,85512643
asked Feb 26 at 9:03
Harmnot
63
add a comment |Â
up vote
0
down vote
favorite
I think I do something wrong and made filesystem mess , please look that pic , I can't boot , it said emergency mode, please exit to the shell
And after I check the logs
It said my default.target has a problem:
Failed to start default.target: Transaction is destructive
linux fedora filesystems boot root-filesystem
edited Feb 26 at 9:15
Ulrich Schwarz
8,85512643
asked Feb 26 at 9:03
Harmnot
63
1
Could do with more information. How did you extend your filesystem? Are you using LVM? Are you using dm-crypt? Are you referencing your /root partition using UUID or device name? Did you extend the partition or create a larger one?
– Pedro
Feb 26 at 12:36
I really forget and I was follow the website to tell me to create new partipation, think I use vgentend and lvexntend to create it , and fdisk also.
– Harmnot
Feb 26 at 13:32
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I think I do something wrong and made filesystem mess , please look that pic , I can't boot , it said emergency mode, please exit to the shell
And after I check the logs
It said my default.target has a problem:
Failed to start default.target: Transaction is destructive
linux fedora filesystems boot root-filesystem
edited Feb 26 at 9:15
Ulrich Schwarz
8,85512643
asked Feb 26 at 9:03
Harmnot
63
I think I do something wrong and made filesystem mess , please look that pic , I can't boot , it said emergency mode, please exit to the shell
And after I check the logs
It said my default.target has a problem:
Failed to start default.target: Transaction is destructive
linux fedora filesystems boot root-filesystem
edited Feb 26 at 9:15
Ulrich Schwarz
8,85512643
asked Feb 26 at 9:03
Harmnot
63
edited Feb 26 at 9:15
Ulrich Schwarz
8,85512643
edited Feb 26 at 9:15
Ulrich Schwarz
8,85512643
edited Feb 26 at 9:15
Ulrich Schwarz
8,85512643
8,85512643
asked Feb 26 at 9:03
Harmnot
63
asked Feb 26 at 9:03
Harmnot
63
asked Feb 26 at 9:03
Harmnot
63
63
1
Could do with more information. How did you extend your filesystem? Are you using LVM? Are you using dm-crypt? Are you referencing your /root partition using UUID or device name? Did you extend the partition or create a larger one?
– Pedro
Feb 26 at 12:36
I really forget and I was follow the website to tell me to create new partipation, think I use vgentend and lvexntend to create it , and fdisk also.
– Harmnot
Feb 26 at 13:32
add a comment |Â
1
Could do with more information. How did you extend your filesystem? Are you using LVM? Are you using dm-crypt? Are you referencing your /root partition using UUID or device name? Did you extend the partition or create a larger one?
– Pedro
Feb 26 at 12:36
I really forget and I was follow the website to tell me to create new partipation, think I use vgentend and lvexntend to create it , and fdisk also.
– Harmnot
Feb 26 at 13:32
1
1
Could do with more information. How did you extend your filesystem? Are you using LVM? Are you using dm-crypt? Are you referencing your /root partition using UUID or device name? Did you extend the partition or create a larger one?
– Pedro
Feb 26 at 12:36
Could do with more information. How did you extend your filesystem? Are you using LVM? Are you using dm-crypt? Are you referencing your /root partition using UUID or device name? Did you extend the partition or create a larger one?
– Pedro
Feb 26 at 12:36
I really forget and I was follow the website to tell me to create new partipation, think I use vgentend and lvexntend to create it , and fdisk also.
– Harmnot
Feb 26 at 13:32
I really forget and I was follow the website to tell me to create new partipation, think I use vgentend and lvexntend to create it , and fdisk also.
– Harmnot
Feb 26 at 13:32
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
You're in initrd (=initramfs) emergency shell environment. You should use it to verify the status of your root filesystem. If your root filesystem is LVM-based, you might want to try commands like lvm pvs, lvm vgchange -ay and lvm vgdisplay to get more information about the status of your LVM volume group(s).
(In emergency shell, the typical LVM commands are all packaged into a single lvm binary: to use regular LVM commands, add a lvm <space> prefix to the command you would usually use.)
You can even try and mount your root filesystem manually, and see the error message that probably occurs when you try to do that.
answered Feb 26 at 10:02
telcoM
10.7k11132
It said 2 logical volumes in volumr group "Fedora" active, and when I run lvm pvs , it said could find device with uuid ,
– Harmnot
Feb 26 at 13:33
So it is unable to find all the PVs belonging to that VG. I guess you added another disk to the "Fedora" VG that contains your root filesystem. Was the new disk on the same disk controller as the old one(s), or is it on a different controller? Perhaps your initramfs did not include the driver for that disk controller: before this it was not a problem, as that disk controller activation could happen later, after mounting the root filesystem. But now it is needed in the initramfs phase. Boot from installation in rescue mode; if it works, rebuild your initramfs. That should hopefully fix it.
– telcoM
Feb 26 at 15:18
1drv.ms/u/s!AsmKoEPFnjbNbzKTyeHuJho43pE This is the link when I run gparted on parted magic, how I can fix that ??
– Harmnot
Feb 26 at 23:45
That is just one LVM physical volume that is part of the "Fedora" volume group. It contains the swap area and at least a part of the root filesystem. It also says there used to be another physical volume (i.e. another disk or partition that was added to the volume group), which cannot be detected now. That one is probably the one which needs fixing. Where is/was it?
– telcoM
Feb 27 at 7:47
I really confused about that, so I re install the fedora, and after this I want to back up my fedora filesystem, how I can backup it?
– Harmnot
Feb 28 at 8:53
 |Â
show 1 more comment
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
You're in initrd (=initramfs) emergency shell environment. You should use it to verify the status of your root filesystem. If your root filesystem is LVM-based, you might want to try commands like lvm pvs, lvm vgchange -ay and lvm vgdisplay to get more information about the status of your LVM volume group(s).
(In emergency shell, the typical LVM commands are all packaged into a single lvm binary: to use regular LVM commands, add a lvm <space> prefix to the command you would usually use.)
You can even try and mount your root filesystem manually, and see the error message that probably occurs when you try to do that.
answered Feb 26 at 10:02
telcoM
10.7k11132
It said 2 logical volumes in volumr group "Fedora" active, and when I run lvm pvs , it said could find device with uuid ,
– Harmnot
Feb 26 at 13:33
So it is unable to find all the PVs belonging to that VG. I guess you added another disk to the "Fedora" VG that contains your root filesystem. Was the new disk on the same disk controller as the old one(s), or is it on a different controller? Perhaps your initramfs did not include the driver for that disk controller: before this it was not a problem, as that disk controller activation could happen later, after mounting the root filesystem. But now it is needed in the initramfs phase. Boot from installation in rescue mode; if it works, rebuild your initramfs. That should hopefully fix it.
– telcoM
Feb 26 at 15:18
1drv.ms/u/s!AsmKoEPFnjbNbzKTyeHuJho43pE This is the link when I run gparted on parted magic, how I can fix that ??
– Harmnot
Feb 26 at 23:45
That is just one LVM physical volume that is part of the "Fedora" volume group. It contains the swap area and at least a part of the root filesystem. It also says there used to be another physical volume (i.e. another disk or partition that was added to the volume group), which cannot be detected now. That one is probably the one which needs fixing. Where is/was it?
– telcoM
Feb 27 at 7:47
I really confused about that, so I re install the fedora, and after this I want to back up my fedora filesystem, how I can backup it?
– Harmnot
Feb 28 at 8:53
 |Â
show 1 more comment
up vote
1
down vote
You're in initrd (=initramfs) emergency shell environment. You should use it to verify the status of your root filesystem. If your root filesystem is LVM-based, you might want to try commands like lvm pvs, lvm vgchange -ay and lvm vgdisplay to get more information about the status of your LVM volume group(s).
(In emergency shell, the typical LVM commands are all packaged into a single lvm binary: to use regular LVM commands, add a lvm <space> prefix to the command you would usually use.)
You can even try and mount your root filesystem manually, and see the error message that probably occurs when you try to do that.
answered Feb 26 at 10:02
telcoM
10.7k11132
It said 2 logical volumes in volumr group "Fedora" active, and when I run lvm pvs , it said could find device with uuid ,
– Harmnot
Feb 26 at 13:33
So it is unable to find all the PVs belonging to that VG. I guess you added another disk to the "Fedora" VG that contains your root filesystem. Was the new disk on the same disk controller as the old one(s), or is it on a different controller? Perhaps your initramfs did not include the driver for that disk controller: before this it was not a problem, as that disk controller activation could happen later, after mounting the root filesystem. But now it is needed in the initramfs phase. Boot from installation in rescue mode; if it works, rebuild your initramfs. That should hopefully fix it.
– telcoM
Feb 26 at 15:18
1drv.ms/u/s!AsmKoEPFnjbNbzKTyeHuJho43pE This is the link when I run gparted on parted magic, how I can fix that ??
– Harmnot
Feb 26 at 23:45
That is just one LVM physical volume that is part of the "Fedora" volume group. It contains the swap area and at least a part of the root filesystem. It also says there used to be another physical volume (i.e. another disk or partition that was added to the volume group), which cannot be detected now. That one is probably the one which needs fixing. Where is/was it?
– telcoM
Feb 27 at 7:47
I really confused about that, so I re install the fedora, and after this I want to back up my fedora filesystem, how I can backup it?
– Harmnot
Feb 28 at 8:53
 |Â
show 1 more comment
up vote
1
down vote
up vote
1
down vote
You're in initrd (=initramfs) emergency shell environment. You should use it to verify the status of your root filesystem. If your root filesystem is LVM-based, you might want to try commands like lvm pvs, lvm vgchange -ay and lvm vgdisplay to get more information about the status of your LVM volume group(s).
(In emergency shell, the typical LVM commands are all packaged into a single lvm binary: to use regular LVM commands, add a lvm <space> prefix to the command you would usually use.)
You can even try and mount your root filesystem manually, and see the error message that probably occurs when you try to do that.
answered Feb 26 at 10:02
telcoM
10.7k11132
You're in initrd (=initramfs) emergency shell environment. You should use it to verify the status of your root filesystem. If your root filesystem is LVM-based, you might want to try commands like lvm pvs, lvm vgchange -ay and lvm vgdisplay to get more information about the status of your LVM volume group(s).
(In emergency shell, the typical LVM commands are all packaged into a single lvm binary: to use regular LVM commands, add a lvm <space> prefix to the command you would usually use.)
You can even try and mount your root filesystem manually, and see the error message that probably occurs when you try to do that.
answered Feb 26 at 10:02
telcoM
10.7k11132
answered Feb 26 at 10:02
telcoM
10.7k11132
answered Feb 26 at 10:02
telcoM
10.7k11132
answered Feb 26 at 10:02
telcoM
10.7k11132
10.7k11132
It said 2 logical volumes in volumr group "Fedora" active, and when I run lvm pvs , it said could find device with uuid ,
– Harmnot
Feb 26 at 13:33
So it is unable to find all the PVs belonging to that VG. I guess you added another disk to the "Fedora" VG that contains your root filesystem. Was the new disk on the same disk controller as the old one(s), or is it on a different controller? Perhaps your initramfs did not include the driver for that disk controller: before this it was not a problem, as that disk controller activation could happen later, after mounting the root filesystem. But now it is needed in the initramfs phase. Boot from installation in rescue mode; if it works, rebuild your initramfs. That should hopefully fix it.
– telcoM
Feb 26 at 15:18
1drv.ms/u/s!AsmKoEPFnjbNbzKTyeHuJho43pE This is the link when I run gparted on parted magic, how I can fix that ??
– Harmnot
Feb 26 at 23:45
That is just one LVM physical volume that is part of the "Fedora" volume group. It contains the swap area and at least a part of the root filesystem. It also says there used to be another physical volume (i.e. another disk or partition that was added to the volume group), which cannot be detected now. That one is probably the one which needs fixing. Where is/was it?
– telcoM
Feb 27 at 7:47
I really confused about that, so I re install the fedora, and after this I want to back up my fedora filesystem, how I can backup it?
– Harmnot
Feb 28 at 8:53
 |Â
show 1 more comment
It said 2 logical volumes in volumr group "Fedora" active, and when I run lvm pvs , it said could find device with uuid ,
– Harmnot
Feb 26 at 13:33
So it is unable to find all the PVs belonging to that VG. I guess you added another disk to the "Fedora" VG that contains your root filesystem. Was the new disk on the same disk controller as the old one(s), or is it on a different controller? Perhaps your initramfs did not include the driver for that disk controller: before this it was not a problem, as that disk controller activation could happen later, after mounting the root filesystem. But now it is needed in the initramfs phase. Boot from installation in rescue mode; if it works, rebuild your initramfs. That should hopefully fix it.
– telcoM
Feb 26 at 15:18
1drv.ms/u/s!AsmKoEPFnjbNbzKTyeHuJho43pE This is the link when I run gparted on parted magic, how I can fix that ??
– Harmnot
Feb 26 at 23:45
That is just one LVM physical volume that is part of the "Fedora" volume group. It contains the swap area and at least a part of the root filesystem. It also says there used to be another physical volume (i.e. another disk or partition that was added to the volume group), which cannot be detected now. That one is probably the one which needs fixing. Where is/was it?
– telcoM
Feb 27 at 7:47
I really confused about that, so I re install the fedora, and after this I want to back up my fedora filesystem, how I can backup it?
– Harmnot
Feb 28 at 8:53
It said 2 logical volumes in volumr group "Fedora" active, and when I run lvm pvs , it said could find device with uuid ,
– Harmnot
Feb 26 at 13:33
It said 2 logical volumes in volumr group "Fedora" active, and when I run lvm pvs , it said could find device with uuid ,
– Harmnot
Feb 26 at 13:33
So it is unable to find all the PVs belonging to that VG. I guess you added another disk to the "Fedora" VG that contains your root filesystem. Was the new disk on the same disk controller as the old one(s), or is it on a different controller? Perhaps your initramfs did not include the driver for that disk controller: before this it was not a problem, as that disk controller activation could happen later, after mounting the root filesystem. But now it is needed in the initramfs phase. Boot from installation in rescue mode; if it works, rebuild your initramfs. That should hopefully fix it.
– telcoM
Feb 26 at 15:18
So it is unable to find all the PVs belonging to that VG. I guess you added another disk to the "Fedora" VG that contains your root filesystem. Was the new disk on the same disk controller as the old one(s), or is it on a different controller? Perhaps your initramfs did not include the driver for that disk controller: before this it was not a problem, as that disk controller activation could happen later, after mounting the root filesystem. But now it is needed in the initramfs phase. Boot from installation in rescue mode; if it works, rebuild your initramfs. That should hopefully fix it.
– telcoM
Feb 26 at 15:18
1drv.ms/u/s!AsmKoEPFnjbNbzKTyeHuJho43pE This is the link when I run gparted on parted magic, how I can fix that ??
– Harmnot
Feb 26 at 23:45
1drv.ms/u/s!AsmKoEPFnjbNbzKTyeHuJho43pE This is the link when I run gparted on parted magic, how I can fix that ??
– Harmnot
Feb 26 at 23:45
That is just one LVM physical volume that is part of the "Fedora" volume group. It contains the swap area and at least a part of the root filesystem. It also says there used to be another physical volume (i.e. another disk or partition that was added to the volume group), which cannot be detected now. That one is probably the one which needs fixing. Where is/was it?
– telcoM
Feb 27 at 7:47
That is just one LVM physical volume that is part of the "Fedora" volume group. It contains the swap area and at least a part of the root filesystem. It also says there used to be another physical volume (i.e. another disk or partition that was added to the volume group), which cannot be detected now. That one is probably the one which needs fixing. Where is/was it?
– telcoM
Feb 27 at 7:47
I really confused about that, so I re install the fedora, and after this I want to back up my fedora filesystem, how I can backup it?
– Harmnot
Feb 28 at 8:53
I really confused about that, so I re install the fedora, and after this I want to back up my fedora filesystem, how I can backup it?
– Harmnot
Feb 28 at 8:53
 |Â
show 1 more comment
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f426622%2fi-cant-boot-after-add-more-space-to-root%23new-answer', 'question_page');
);
Post as a guest
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
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
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
1
Could do with more information. How did you extend your filesystem? Are you using LVM? Are you using dm-crypt? Are you referencing your /root partition using UUID or device name? Did you extend the partition or create a larger one?
– Pedro
Feb 26 at 12:36
I really forget and I was follow the website to tell me to create new partipation, think I use vgentend and lvexntend to create it , and fdisk also.
– Harmnot
Feb 26 at 13:32