Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    Strange Problem Here!

    Reply
    Page 1 of 2 | 1   2   | Next
    seanmcken | # 1 | 2013-05-13, 13:05 | Report

    /home/user # apt-get upgrade
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages will be upgraded:
    theme-customizer
    1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    Need to get 0B/293kB of archives.
    After this operation, 20.5kB of additional disk space will be used.
    Do you want to continue [Y/n]? Y
    (Reading database ... dpkg: unrecoverable fatal error, aborting:
    unable to open files list file for package `theme-customizer': Stale NFS file handle
    E: Sub-process /usr/bin/dpkg returned an error code (2)
    /home/user #

    Edit | Forward | Quote | Quick Reply | Thanks

     
    anthonie | # 2 | 2013-05-13, 13:24 | Report

    You'll need to do a FS check in order to remove those stale handles.

    Sometimes it is enough to simply (forced) rm those files/folders, sometimes you' ll need to get into either an alternative OS that has access to that file system (inn case you have Nitdroid or something like that installed), or you could try getting rid of it in recovery mode.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to anthonie For This Useful Post:
    seanmcken

     
    seanmcken | # 3 | 2013-05-13, 14:08 | Report

    @anthonie
    can u plz give me those codes watever to do on x terminal to recover this problem?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    cddiede | # 4 | 2013-05-13, 14:53 | Report

    A reboot often helps stale NFS handles.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to cddiede For This Useful Post:
    seanmcken

     
    seanmcken | # 5 | 2013-05-13, 15:27 | Report

    tried reboot but no luck

    Edit | Forward | Quote | Quick Reply | Thanks

     
    willi6868 | # 6 | 2013-05-13, 15:36 | Report

    Does this not mean that you have not working repositories...?! Try to disable your added repos.

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by willi6868; 2013-05-13 at 16:03.
    The Following User Says Thank You to willi6868 For This Useful Post:
    seanmcken

     
    cddiede | # 7 | 2013-05-13, 18:29 | Report

    Worst case senario: uninstall/remove the `theme-customizer' package and do an apt-get autoclean

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to cddiede For This Useful Post:
    seanmcken

     
    anthonie | # 8 | 2013-05-13, 19:23 | Report

    Sean,

    I am not at home so I can't share my notes I scribbled down the last time I bumped into these troubles.

    I would try a remove (sudo gainroot -> rm -f <stale handle>). Probably that will not work, so the next step would be to boot into an alternative, if you have that installed, like Nitdroid or so. Next option would be ssh or Rob1n's backupmenu. Apart from that there is also a recovery console, but that requires bootmenu to be installed.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to anthonie For This Useful Post:
    seanmcken

     
    seanmcken | # 9 | 2013-05-14, 02:28 | Report

    Thanks Everybody, Problem is Solved Now, Thank You Very Musch For Your Replies

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Acurus_ | # 10 | 2013-05-14, 05:54 | Report

    How did you manage it?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Page 1 of 2 | 1   2   | Next
vBulletin® Version 3.8.8
Normal Logout