Re: After a power cut my machine cannot boot

[Patrick O'Callaghan]

On Wed, 2015-09-09 at 21:11 -0400, Sam Varshavchik wrote:
> Paul Smith writes:
> 
> > Is there something, apart buying a UPS, that one can do in order to
> > minimize the severity of the damage that a power outage can cause?
> 
> A UPS, paired with auto-shutdown software is the best possible
> defense  
> against damage due to unexpected power loss. But that's merely a
> formality,  
> since apcupsd or nut should be able to support most retail UPSes you
> can buy  
> off the shelf.
> 
> I've never had filesystem damage in ~20 years I've been running off
> UPSes. I  
> usually have a power failure 1-2 times a year. Each time my UPSes
> gave me  
> sufficient time to log in to every server, and bring it down.
> 
> Even the few times one of them turned out to have a weak battery it
> still  
> had enough juice for the autoshutdown to kick in immediately, and
> bring the  
> server down all by itself, without waiting for me.
> 
> The money I've spent on all my UPSes has paid for itself over, and
> over  
> again.

I agree. I lived in South America for many years, where power was
unreliable (not just failures but brownouts and voltage variations) and
a UPS was essential. The one I had for several years wasn't well
supported on Linux but I used a journal and avoided serious problems.

poc

-- 
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

Re: After a power cut my machine cannot boot

[Patrick O'Callaghan]

On Wed, 2015-09-09 at 16:20 -0700, Joe Zeff wrote:
> On 09/09/2015 04:00 PM, Paul Smith wrote:
> > Thanks, Patrick. The default clean installation of F21 does not
> > already install a journaling filesystem?
> 
> I think that the default is ext4, which is journalling.  LVM is also 
> the default, and I've no idea how that handles these things.  My
> advice is, if you're a home user you probably don't need it.

I agree that you don't need LVM (if that's what you meant). I do think
you need a journalling filesystem.

However in the present case it's conceivable that the power fail did
some damage to the actual drive, especially if there was also a power
spike, in which case a journal may not save you. You might have better
protection with a mirrored drive, but really there are no guarantees.
Backup often.

poc
-- 
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

Re: After a power cut my machine cannot boot

[Sam Varshavchik]

Paul Smith writes:


On Wed, Sep 9, 2015 at 7:26 PM, Joe Zeff  wrote:
>>
>> on a F21 machine, there occured a power cut. And now I cannot boot the
>> machine, and when I use the rescue mode and try to run again
>>
>> yum update
>
>
> I know I'm coming in late, and judging from other replies this probably
> won't work, but have you tried yum-complete-transaction?  I'd suggest using
> --skip-broken, but that only checks for certain errors in the files rather
> than doing what the name implies.
>
> Going off-topic for a moment, and presuming that dnf acts the same way (I
> don't, as yet, have a box using it.) should there be a bugzilla either
> complaining that the switch doesn't actually do what it says (e.g.,  
skipping
> to the next package if this one is broken instead of only being able to  
pull

> it out of the transaction if the signature (I think it is.) doesn't match.)
> or requesting that it be renamed to something more appropriate, with the
> current switch being left as an alias for the correct one to keep scripts
> from breaking.  I'm neutral on the subject, although I'd prefer that
> something be done to keep people from wasting time trying in cases where it
> doesn't apply.

Thanks, Joe. I have just tried

yum-complete-transaction

but with no success: the error message ("/lib64/libidn.so.11: file too  
short").


This is a critical system library. It has been hopelessly corrupted. You  
cannot run anything. libidn.so.11 is a critical system library, used  
probably by 99% of binaries on an average system. Any command someone will  
suggest for you try won't work, because the command itself needs libidn.so. 
11, and it's broken.


If you have another working system, it should be possible to recover this  
library using a rescue disk; by first fscking the filesystem to get it into a  
consistent state, and then meticulously restoring the corrupted files from  
another good system.


However, this procedure does require a fairly good amount of technical  
experience and knowledge. Furthermore, all you know is that libidn.so is  
corrupted. You have absolutely no guarantees, whatsoever, that this is the  
only corrupted system library. After fixing it, it's fairly likely that you  
will discover that another critical system library is similarly corrupted. I  
can pretty much guarantee you that this is the case.


Eventually, you will get to the point where you apparently restored all the  
critical files, and you are seemly able to boot, but probably won't be able  
to boot all the way through to the desktop, due to some less-critical  
libraries being similarly corrupted, or other kinds of critical files  
missing, but that doesn't come up until a later point in the boot process,  
and the error message is lost somewhere that's not easy to find. All you  
know that that the boot hangs, with no immediate indication as to what's  
broken.


I'm just giving you the most likely scenario I think you will end up with,  
if you try to continue along the path of trying to salvage this system.  
Based on what you already wrote in this thread, I think the best thing for  
you to do is to simply reformat and reinstall. Using a rescue disk, it  
should be possible for you to salvage any individual files you need off this  
system, before reinstalling it, if necessary.


And once you have everything reinstalled, invest in a good UPS so you won't  
have to do this again.




pgp_lPJTfS_yp.pgp
Description: PGP signature
-- 
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

Re: After a power cut my machine cannot boot

[Joe Zeff]

On 09/09/2015 03:45 PM, Paul Smith wrote:

I will try sysresccd, as Heinz advises. In case that does not work, I
will reinstall the system. Fortunately, I have a backup of my home
directory and all important files!


If you have /home on its own partition, you can just reuse it without 
reformatting, and if you don't, you probably should.

--
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

Re: After a power cut my machine cannot boot

[Joe Zeff]

On 09/09/2015 04:00 PM, Paul Smith wrote:

Thanks, Patrick. The default clean installation of F21 does not
already install a journaling filesystem?


I think that the default is ext4, which is journalling.  LVM is also the 
default, and I've no idea how that handles these things.  My advice is, 
if you're a home user you probably don't need it.

--
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

Re: After a power cut my machine cannot boot

[Paul Smith]

On Wed, Sep 9, 2015 at 11:09 PM, Sam Varshavchik  wrote:
>> >>
>> >> on a F21 machine, there occured a power cut. And now I cannot boot the
>> >> machine, and when I use the rescue mode and try to run again
>> >>
>> >> yum update
>> >
>> > I know I'm coming in late, and judging from other replies this probably
>> > won't work, but have you tried yum-complete-transaction?  I'd suggest
>> > using
>> > --skip-broken, but that only checks for certain errors in the files
>> > rather
>> > than doing what the name implies.
>> >
>> > Going off-topic for a moment, and presuming that dnf acts the same way
>> > (I
>> > don't, as yet, have a box using it.) should there be a bugzilla either
>> > complaining that the switch doesn't actually do what it says (e.g.,
>> > skipping
>> > to the next package if this one is broken instead of only being able to
>> > pull
>> > it out of the transaction if the signature (I think it is.) doesn't
>> > match.)
>> > or requesting that it be renamed to something more appropriate, with the
>> > current switch being left as an alias for the correct one to keep
>> > scripts
>> > from breaking.  I'm neutral on the subject, although I'd prefer that
>> > something be done to keep people from wasting time trying in cases where
>> > it
>> > doesn't apply.
>>
>> Thanks, Joe. I have just tried
>>
>> yum-complete-transaction
>>
>> but with no success: the error message ("/lib64/libidn.so.11: file too
>> short").
>
>
> This is a critical system library. It has been hopelessly corrupted. You
> cannot run anything. libidn.so.11 is a critical system library, used
> probably by 99% of binaries on an average system. Any command someone will
> suggest for you try won't work, because the command itself needs
> libidn.so.11, and it's broken.
>
> If you have another working system, it should be possible to recover this
> library using a rescue disk; by first fscking the filesystem to get it into
> a consistent state, and then meticulously restoring the corrupted files from
> another good system.
>
> However, this procedure does require a fairly good amount of technical
> experience and knowledge. Furthermore, all you know is that libidn.so is
> corrupted. You have absolutely no guarantees, whatsoever, that this is the
> only corrupted system library. After fixing it, it's fairly likely that you
> will discover that another critical system library is similarly corrupted. I
> can pretty much guarantee you that this is the case.
>
> Eventually, you will get to the point where you apparently restored all the
> critical files, and you are seemly able to boot, but probably won't be able
> to boot all the way through to the desktop, due to some less-critical
> libraries being similarly corrupted, or other kinds of critical files
> missing, but that doesn't come up until a later point in the boot process,
> and the error message is lost somewhere that's not easy to find. All you
> know that that the boot hangs, with no immediate indication as to what's
> broken.
>
> I'm just giving you the most likely scenario I think you will end up with,
> if you try to continue along the path of trying to salvage this system.
> Based on what you already wrote in this thread, I think the best thing for
> you to do is to simply reformat and reinstall. Using a rescue disk, it
> should be possible for you to salvage any individual files you need off this
> system, before reinstalling it, if necessary.
>
> And once you have everything reinstalled, invest in a good UPS so you won't
> have to do this again.

I thank you, Sam, and the other respondents. And yes, I can run almost
no program because of that file...

I will try sysresccd, as Heinz advises. In case that does not work, I
will reinstall the system. Fortunately, I have a backup of my home
directory and all important files!

Is there something, apart buying a UPS, that one can do in order to
minimize the severity of the damage that a power outage can cause?

Paul
-- 
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

Re: After a power cut my machine cannot boot

[Patrick O'Callaghan]

On Wed, 2015-09-09 at 23:45 +0100, Paul Smith wrote:
> Is there something, apart buying a UPS, that one can do in order to
> minimize the severity of the damage that a power outage can cause?

Use a journaling filesystem.

poc
-- 
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

Re: After a power cut my machine cannot boot

[Paul Smith]

On Wed, Sep 9, 2015 at 11:51 PM, Patrick O'Callaghan
 wrote:
>
>> Is there something, apart buying a UPS, that one can do in order to
>> minimize the severity of the damage that a power outage can cause?
>
> Use a journaling filesystem.

Thanks, Patrick. The default clean installation of F21 does not
already install a journaling filesystem?

Paul
-- 
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

Re: After a power cut my machine cannot boot

[Sam Varshavchik]

Paul Smith writes:


Is there something, apart buying a UPS, that one can do in order to
minimize the severity of the damage that a power outage can cause?


A UPS, paired with auto-shutdown software is the best possible defense  
against damage due to unexpected power loss. But that's merely a formality,  
since apcupsd or nut should be able to support most retail UPSes you can buy  
off the shelf.


I've never had filesystem damage in ~20 years I've been running off UPSes. I  
usually have a power failure 1-2 times a year. Each time my UPSes gave me  
sufficient time to log in to every server, and bring it down.


Even the few times one of them turned out to have a weak battery it still  
had enough juice for the autoshutdown to kick in immediately, and bring the  
server down all by itself, without waiting for me.


The money I've spent on all my UPSes has paid for itself over, and over  
again.




pgpmqYwUSa2ty.pgp
Description: PGP signature
-- 
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

Re: After a power cut my machine cannot boot

[Paul Smith]

On Wed, Sep 9, 2015 at 7:08 PM, Dave Stevens  wrote:
>> >
>> >> "/lib64/libidn.so.11: file too short".
>> >
>> > Have you repaired your crashed filesystems already?
>> > If you have, try "dnf reinstall libidn libidn2".
>>
>> Thanks for your reply, Heinz.
>>
>> What can I do to repair the filesystem?
>
> first run (as root) fdisk -l and paste the output here.

Thanks, Dave. Unfortunately, I cannot paste any output here, as I do
not have a graphical console on the problematic machine -- it cannot
boot in graphical mode.

Paul
-- 
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

Re: After a power cut my machine cannot boot

[Paul Smith]

On Wed, Sep 9, 2015 at 7:26 PM, Joe Zeff  wrote:
>>
>> on a F21 machine, there occured a power cut. And now I cannot boot the
>> machine, and when I use the rescue mode and try to run again
>>
>> yum update
>
>
> I know I'm coming in late, and judging from other replies this probably
> won't work, but have you tried yum-complete-transaction?  I'd suggest using
> --skip-broken, but that only checks for certain errors in the files rather
> than doing what the name implies.
>
> Going off-topic for a moment, and presuming that dnf acts the same way (I
> don't, as yet, have a box using it.) should there be a bugzilla either
> complaining that the switch doesn't actually do what it says (e.g., skipping
> to the next package if this one is broken instead of only being able to pull
> it out of the transaction if the signature (I think it is.) doesn't match.)
> or requesting that it be renamed to something more appropriate, with the
> current switch being left as an alias for the correct one to keep scripts
> from breaking.  I'm neutral on the subject, although I'd prefer that
> something be done to keep people from wasting time trying in cases where it
> doesn't apply.

Thanks, Joe. I have just tried

yum-complete-transaction

but with no success: the error message ("/lib64/libidn.so.11: file too short").

Paul
-- 
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

After a power cut my machine cannot boot

[Paul Smith]

Dear All,

While doing

yum update

on a F21 machine, there occured a power cut. And now I cannot boot the
machine, and when I use the rescue mode and try to run again

yum update

I get the following error:

"/lib64/libidn.so.11: file too short".

Any ideas? I have already tried to get the libidn rpm from a repo, but
again I get the same error with wget ("/lib64/libidn.so.11: file too
short").

Thanks in advance,

Paul
-- 
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

Re: After a power cut my machine cannot boot

[Pete Travis]

On Sep 9, 2015 1:58 PM, "Paul Smith"  wrote:
>
> On Wed, Sep 9, 2015 at 7:26 PM, Joe Zeff  wrote:
> >>
> >> on a F21 machine, there occured a power cut. And now I cannot boot the
> >> machine, and when I use the rescue mode and try to run again
> >>
> >> yum update
> >
> >
> > I know I'm coming in late, and judging from other replies this probably
> > won't work, but have you tried yum-complete-transaction?  I'd suggest
using
> > --skip-broken, but that only checks for certain errors in the files
rather
> > than doing what the name implies.
> >
> > Going off-topic for a moment, and presuming that dnf acts the same way
(I
> > don't, as yet, have a box using it.) should there be a bugzilla either
> > complaining that the switch doesn't actually do what it says (e.g.,
skipping
> > to the next package if this one is broken instead of only being able to
pull
> > it out of the transaction if the signature (I think it is.) doesn't
match.)
> > or requesting that it be renamed to something more appropriate, with the
> > current switch being left as an alias for the correct one to keep
scripts
> > from breaking.  I'm neutral on the subject, although I'd prefer that
> > something be done to keep people from wasting time trying in cases
where it
> > doesn't apply.
>
> Thanks, Joe. I have just tried
>
> yum-complete-transaction
>
> but with no success: the error message ("/lib64/libidn.so.11: file too
short").
>
> Paul
> --
>

Fix whatever is dropping you into rescue mode, *then* do package updates.
One problem at a time, or you will get lost in the overlap.

--Pete
-- 
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

Re: After a power cut my machine cannot boot

[dwoody5654]

On 09/09/2015 01:58 PM, Paul Smith wrote:

On Wed, Sep 9, 2015 at 7:26 PM, Joe Zeff  wrote:

on a F21 machine, there occured a power cut. And now I cannot boot the
machine, and when I use the rescue mode and try to run again

yum update


I know I'm coming in late, and judging from other replies this probably
won't work, but have you tried yum-complete-transaction?  I'd suggest using
--skip-broken, but that only checks for certain errors in the files rather
than doing what the name implies.

Going off-topic for a moment, and presuming that dnf acts the same way (I
don't, as yet, have a box using it.) should there be a bugzilla either
complaining that the switch doesn't actually do what it says (e.g., skipping
to the next package if this one is broken instead of only being able to pull
it out of the transaction if the signature (I think it is.) doesn't match.)
or requesting that it be renamed to something more appropriate, with the
current switch being left as an alias for the correct one to keep scripts
from breaking.  I'm neutral on the subject, although I'd prefer that
something be done to keep people from wasting time trying in cases where it
doesn't apply.

Thanks, Joe. I have just tried

yum-complete-transaction

but with no success: the error message ("/lib64/libidn.so.11: file too short").

Paul
Can you copy /lib64/libidn.so.11 from another computer via network 
connection or flash drive?


David
--
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

Re: After a power cut my machine cannot boot

[Heinz Diehl]

On 09.09.2015, Paul Smith wrote: 

> "/lib64/libidn.so.11: file too short".

Have you repaired your crashed filesystems already?
If you have, try "dnf reinstall libidn libidn2".




-- 
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

Re: After a power cut my machine cannot boot

[Paul Smith]

On Wed, Sep 9, 2015 at 6:43 PM, Heinz Diehl  wrote:
>
>> "/lib64/libidn.so.11: file too short".
>
> Have you repaired your crashed filesystems already?
> If you have, try "dnf reinstall libidn libidn2".

Thanks for your reply, Heinz.

What can I do to repair the filesystem?

I did

yum reinstall libidn libidn2

but got again

"/lib64/libidn.so.11: file too short".

Paul
-- 
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

Re: After a power cut my machine cannot boot

[Dave Stevens]

On Wed, 9 Sep 2015 18:46:59 +0100
Paul Smith  wrote:

> On Wed, Sep 9, 2015 at 6:43 PM, Heinz Diehl  wrote:
> >
> >> "/lib64/libidn.so.11: file too short".
> >
> > Have you repaired your crashed filesystems already?
> > If you have, try "dnf reinstall libidn libidn2".
> 
> Thanks for your reply, Heinz.
> 
> What can I do to repair the filesystem?

first run (as root) fdisk -l and paste the output here.

Dave

> 
> I did
> 
> yum reinstall libidn libidn2
> 
> but got again
> 
> "/lib64/libidn.so.11: file too short".
> 
> Paul



-- 
There is a very nasty proposal afoot to pollute the air
in Smithers even more than it is now. Various objections 
to this have been registered to no effect. Check out issues at
http://ohnopro.ca
-- 
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

Re: After a power cut my machine cannot boot

[Joe Zeff]

On 09/09/2015 10:36 AM, Paul Smith wrote:

on a F21 machine, there occured a power cut. And now I cannot boot the
machine, and when I use the rescue mode and try to run again

yum update


I know I'm coming in late, and judging from other replies this probably 
won't work, but have you tried yum-complete-transaction?  I'd suggest 
using --skip-broken, but that only checks for certain errors in the 
files rather than doing what the name implies.


Going off-topic for a moment, and presuming that dnf acts the same way 
(I don't, as yet, have a box using it.) should there be a bugzilla 
either complaining that the switch doesn't actually do what it says 
(e.g., skipping to the next package if this one is broken instead of 
only being able to pull it out of the transaction if the signature (I 
think it is.) doesn't match.) or requesting that it be renamed to 
something more appropriate, with the current switch being left as an 
alias for the correct one to keep scripts from breaking.  I'm neutral on 
the subject, although I'd prefer that something be done to keep people 
from wasting time trying in cases where it doesn't apply.

--
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

Re: After a power cut my machine cannot boot

[Joe Zeff]

On 09/09/2015 11:58 AM, Paul Smith wrote:

Thanks, Joe. I have just tried

yum-complete-transaction

but with no success: the error message ("/lib64/libidn.so.11: file too short").


I kind of thought so, but I figured that it was worth a try.
--
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

Re: After a power cut my machine cannot boot

[Joe Zeff]

On 09/09/2015 11:56 AM, Paul Smith wrote:

Thanks, Dave. Unfortunately, I cannot paste any output here, as I do
not have a graphical console on the problematic machine -- it cannot
boot in graphical mode.


Use this, then:

fdisk -l | tee fdisk.txt

That will both show you the results of fdisk and put them in the file 
fdisk.txt.  Then, if you can copy it to another machine, possibly by 
ftp, you can paste the output into an email.

--
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

Re: After a power cut my machine cannot boot

[Dave Stevens]

On Wed, 9 Sep 2015 19:56:02 +0100
Paul Smith  wrote:

> On Wed, Sep 9, 2015 at 7:08 PM, Dave Stevens 
> wrote:
> >> >
> >> >> "/lib64/libidn.so.11: file too short".
> >> >
> >> > Have you repaired your crashed filesystems already?
> >> > If you have, try "dnf reinstall libidn libidn2".
> >>
> >> Thanks for your reply, Heinz.
> >>
> >> What can I do to repair the filesystem?
> >
> > first run (as root) fdisk -l and paste the output here.
> 
> Thanks, Dave. Unfortunately, I cannot paste any output here, as I do
> not have a graphical console on the problematic machine -- it cannot
> boot in graphical mode.
> 
> Paul

ok, but the point is to know what fs needs repair; fdisk must show the
filesystem type, yes? then fsck can address that fs specifically, using
fsck -t 

D




-- 
There is a very nasty proposal afoot to pollute the air
in Smithers even more than it is now. Various objections 
to this have been registered to no effect. Check out issues at
http://ohnopro.ca
-- 
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

Re: After a power cut my machine cannot boot

[Tom Rivers]

On 9/9/2015 13:36, Paul Smith wrote:

I have already tried to get the libidn rpm from a repo, but
again I get the same error with wget ("/lib64/libidn.so.11: file too
short").



Have you tried downloading the file from another system and transferring 
it using a USB flash drive?  You may also be able to boot from a live 
DVD/USB flash drive version of F21 on the broken system and use its 
functioning OS to download the file and place it on the hard drive so 
you can manually repair the file in question when you boot up normally.



Tom
--
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

Re: After a power cut my machine cannot boot

[Heinz Diehl]

On 09.09.2015, Paul Smith wrote: 

> What can I do to repair the filesystem?

Go to http://www.sysresccd.org and download the sysresccd image to
another machine. Then burn in onto a CD and boot from it. If you have
the syslinux tools installed, you can run

 isohybrid sysresccd.iso

and then copy this image to an USB-stick: cat image.iso > /dev/sdX
and boot from it.

After that, you can use "lsblk -f" to see what kind of filesystems you
have on your damaged machine and the respective blockdevices. The
sysresccd holds all the tools you need to repair most fs: fsck,
xfs_repair and more.

ext3/4 can be repaired using "fsck.ext3 /dev/sdX" or fsck.ext4
respectively.

For XFS, "xfs_repair -v /dev/sdX" will do it.

A DOS Partition can be repaired this way:
dosfsck -w -r -l -a -v -t /dev/sdX

After repairing, boot your machine, delete the defective libidn.so.11
and reinstall that package. Most probably, this lib got truncated by a
fs crash and became thus unusable.

-- 
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