Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: Error: corrupted orphan linked list

  1. #1

    Default Error: corrupted orphan linked list

    I have openSUSE 11.4 (64-bit version) installed,
    but since getting an error, I have begun
    just using the LIVE_CD 11.4 to work around it.

    Within the ++++++ delimiters below I have
    posted the startup notices as they appear on
    the monitor until the login is sought. The
    /dev/sda9 mentioned is a sub-drive on an
    extended partition of my laptop's HDD. My
    question is this:
    If I wait two weeks and install openSUSE
    12.1, will this problem just take care of
    itself as the new version is applied? Or do
    I need to do the fix of my current version
    11.4 before beginning the upgrade to 12.1?

    I have searched the forums with the phrase
    "corrupted orphan linked list" but the con-
    versations elicited in the four threads
    which turn up do not seem to apply to my
    specific question.

    Thank you for thinking about my predicament.

    ++++++++++++++++++++++++++++++++++++++++++

    . . . .
    mounting mandatory file systems . . . done
    done
    Starting udevd: ok

    Loading drivers, configuring devices: done
    Loading required kernal modules done
    Activating swap-devices in /etc/fstab. . . done
    Set system Time to the current Hardware ClockSat Oct 15 08:34:23 2011 -0.734700 seconds
    done
    Activating device mapper. . . done
    Checking file systems. . . done
    fsck from util-linux 2.19
    /dev/sda9 contains a file system with errors, check forced.
    /dev/sda9:
    Inodes that were part of a corrupted orphan linked list found.

    /dev/sda9: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.
    (i.e., without -a or -p options) failed

    fsck failed for at least one filesystem (not /).
    Please repair manually and reboot.
    The root file system is already mounted read-write.

    Attention: Only CONTROL-D will reboot the system in this
    maintenance mode. shutdown or reboot will not work

    Give root password for login:
    Login incorrect.
    Give root password for login:

    ++++++++++++++++++++++++++++++++++++++++++

  2. #2
    Join Date
    Apr 2010
    Location
    Chicago, IL
    Posts
    171

    Default Re: Error: corrupted orphan linked list

    Run fsck manually and see if that works. If not, post the output of fsck here.

    Your error says that running fsck manually will fix it, and if it doesn't then fsck's output will help to figure out why it's not working.

  3. #3
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: Error: corrupted orphan linked list

    On 11/02/2011 05:06 AM, 3bitsShortOfaByte wrote:
    > If I wait two weeks and install openSUSE
    > 12.1, will this problem just take care of
    > itself as the new version is applied?


    probably not...it is probably not a problem with 11.4 or any software
    you run...

    you are seeing the result of a file system inconsistency...that might be
    caused by a hardware problem (disk dying)....or, it might be caused by
    unclean shutdowns (like pulling the power, or using the power switch to
    shut down), or situations in which the software is allowed to be in such
    an unstable state that it crashes and leaves bad juju on the disk..

    this problem _may_ be rather easy to fix with fsck....or, it _may_
    require a new hard drive....but, it is highly unlikely to be fixed by
    simply instaling 12.1

    --
    DD
    http://tinyurl.com/DD-Caveat
    openSUSE®, the "German Automobiles" of operating systems

  4. #4
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Error: corrupted orphan linked list

    On 2011-11-02 05:06, 3bitsShortOfaByte wrote:

    > Within the ++++++ delimiters below I have


    You should use code tags instead. Advanced editor, #.


    > ++++++++++++++++++++++++++++++++++++++++++
    > /dev/sda9 contains a file system with errors, check forced.
    > /dev/sda9:
    > Inodes that were part of a corrupted orphan linked list found.
    >
    > /dev/sda9: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.
    > (i.e., without -a or -p options) failed
    >
    > fsck failed for at least one filesystem (not /).
    > Please repair manually and reboot.
    > The root file system is already mounted read-write.
    >
    > Attention: Only CONTROL-D will reboot the system in this
    > maintenance mode. shutdown or reboot will not work
    >
    > Give root password for login:
    > Login incorrect.
    > Give root password for login:
    >
    > ++++++++++++++++++++++++++++++++++++++++++



    The system is telling you what to do: fsck on sda9. Do it.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.4 x86_64 "Celadon" at Telcontar)

  5. #5

    Default Re: Error: corrupted orphan linked list

    Thank you to all three of you good folks for responding. I do think my problem was, as DenverD suggests, a bad shutdown on my part. The rest of my hard drive has worked fine in every other way (except booting right!) under the LIVE-CD of 11.4. I am going to do the fsck, as you all agree I should. Because I'm a little overcautious, I'm working on completely backing up the Linux partition of the hard drive before I execute fsck. I probably won't get done with that backup part until tomorrow. I just wanted to give you an update and let you know that I appreciate your good ideas. I'll let you know how it ends.

  6. #6
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: Error: corrupted orphan linked list

    On 11/03/2011 04:26 AM, 3bitsShortOfaByte wrote:
    >
    > I'll let you know how it ends.


    -backup is always GOOD
    -and type "man fsck" at a command line and read read read
    -don't forget the error said to run it "without -a or -p options"
    -if after reading you have questions: Ask them _before_ running fsck

    --
    DD
    openSUSE®, the "German Automobiles" of operating systems

  7. #7
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Error: corrupted orphan linked list

    On 2011-11-03 04:26, 3bitsShortOfaByte wrote:

    > Because I'm a little overcautious, I'm working on completely
    > backing up the Linux partition of the hard drive before I execute fsck.


    Bad timing. You can not do a backup of a partition that needs doing an
    fsck, because you can not mount it. You can backup an image, but that image
    will be corrupt and needs an fsck itself.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.4 x86_64 "Celadon" at Telcontar)

  8. #8

    Default Re: Error: corrupted orphan linked list

    It worked. fsck fixed the problem. It reported to me:
    Inode 1525002 was part of the orphaned mode list. FIXED

    My hesitation in applying fsck was just to know that I had backed up my personal data and checked that it was accurate in the backup. That took extra time. I was not imagining that the backuped system material would be corrected. I just wanted to protect the other data. All is well. My system is back to normal and I look forward to trying out 12.1 in a few more days!

    Thanks to you good folks for your encouragement and excellent advice.

  9. #9
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: Error: corrupted orphan linked list

    On 11/05/2011 03:24 AM, 3bitsShortOfaByte wrote:
    >
    > I was not imagining that the backuped system material would
    > be corrected.


    whatever data you backed up from sda9 now needs to be backup again
    (because the backup you have of it is corrupt)...its always good to have
    a recent backup of important data _before_ 'disaster' strikes..

    and, if you don't have SMART installed and active you should probably
    consider doing that....drives _do_ fail and SMART will usually give you
    some indication prior to . . .

    --
    DD
    openSUSE®, the "German Automobiles" of operating systems

  10. #10

    Default Re: Error: corrupted orphan linked list

    Thanks, DenverD,

    I understand what you said "whatever data you backed up from sda9 now needs to be backup again
    (because the backup you have of it is corrupt)" and I understood it before as well. What I meant by saying
    "I was not imagining that the backuped system material would be corrected" was that I was really happy
    that the personal data on other partitions was untouched by the problem. I do not change configuration
    details frequently, so I thought that if fsck did not fix sda9 [which now, of course, it did], I would not have
    to change a lot from a previous backup of sda9 done a few months ago. I will now do a proper backup of
    the current sda9. I will also look into SMART. I'm not familiar with it, so a I appreciate your reference to
    it for me.

    Thank you again.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •