From: Aniruddha on 26 Jul 2010 03:40 Hi, When I try to do a safe-upgrade on a Lenny system I get the following error: ------------------------------------------------------------------------ dpkg: error processing /var/cache/apt/archives/base-files_5lenny6_amd64.deb (--unpack): unable to stat `./mnt' (which I was about to install): No such device or address ------------------------------------------------------------------------ I'm thinking this might be caused a bad block or bad cabling. Anyone who knows what this is? Thanks in advance! Some more information: ------------------------------------------------------------------------ # ls /mnt ls: cannot access /mnt: No such device or address # cd /mnt # pwd /mnt # ls ls: cannot open directory .: No such device or address -------------------------------------------------------------------------- From the syslog ----------------------------------------------------------------------- Jul 25 17:02:47 server kernel: [4684955.154845] ide-cd: cmd 0x3 timed out Jul 25 17:02:47 server kernel: [4684955.154884] hda: lost interrupt Jul 25 17:03:47 server kernel: [4685015.281517] hda: lost interrupt Jul 25 17:04:47 server kernel: [4685075.638334] ide-cd: cmd 0x3 timed out Jul 25 17:04:47 server kernel: [4685075.638334] hda: lost interrupt Jul 25 17:05:47 server kernel: [4685135.767911] ide-cd: cmd 0x3 timed out Jul 25 17:05:47 server kernel: [4685135.767950] hda: lost interrupt ---------------------------------------------------------------------- -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4C4D3B54.70309(a)gmail.com
From: Boyd Stephen Smith Jr. on 26 Jul 2010 05:10 On Monday 26 July 2010 02:37:56 Aniruddha wrote: > ------------------------------------------------------------------------ > dpkg: error processing > /var/cache/apt/archives/base-files_5lenny6_amd64.deb (--unpack): > unable to stat `./mnt' (which I was about to install): No such device > or address > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------ > # ls /mnt > ls: cannot access /mnt: No such device or address > # cd /mnt > # pwd > /mnt > # ls > ls: cannot open directory .: No such device or address > -------------------------------------------------------------------------- > > From the syslog > > ----------------------------------------------------------------------- > Jul 25 17:02:47 server kernel: [4684955.154845] ide-cd: cmd 0x3 timed out > Jul 25 17:02:47 server kernel: [4684955.154884] hda: lost interrupt > Jul 25 17:03:47 server kernel: [4685015.281517] hda: lost interrupt > Jul 25 17:04:47 server kernel: [4685075.638334] ide-cd: cmd 0x3 timed out > Jul 25 17:04:47 server kernel: [4685075.638334] hda: lost interrupt > Jul 25 17:05:47 server kernel: [4685135.767911] ide-cd: cmd 0x3 timed out > Jul 25 17:05:47 server kernel: [4685135.767950] hda: lost interrupt > ---------------------------------------------------------------------- Maybe something mounted your optical media on /mnt, and the disk / drive is no longer available but the filesystem is still mounted. umount -f and umount -l could help here. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss(a)iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
|
Pages: 1 Prev: pick invalid ones from package list Next: Error during safe-upgrade: unable to stat `./mnt' |