Sid is/was crazy

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Sid is/was crazy

Alejandro Bonilla Beeche
Hi,

Every some hours my Debian Sid box goes wild and I can't do anything.
Not even being root.

Is crazy. I can't even do apt-get update to try fixing this problem...

Err http://http.us.debian.org unstable/main xpdf-common 3.01-2
  Could not open file
/var/cache/apt/archives/partial/xpdf-common_3.01-2_all.deb - open (30
Read-only file system) [IP: 64.50.236.52 80]
Err http://http.us.debian.org unstable/main yelp 2.10.0-3
  Could not open file
/var/cache/apt/archives/partial/yelp_2.10.0-3_i386.deb - open (30
Read-only file system) [IP: 204.152.191.7 80]
39% [Waiting for headers]
debian:~# whoami
root
debian:~# screen
mkfifo /var/run/screen/S-root/5922.pts-0.debian failed

dmesg:

SCSI error : <0 0 0 0> return code = 0x8000002
sda: Current: sense key: Aborted Command
    Additional sense: Scsi parity error
end_request: I/O error, dev sda, sector 147753830
Buffer I/O error on device sda3, logical block 1572865
lost page write due to I/O error on sda3
ATA: abnormal status 0xD0 on port 0xEC07
ATA: abnormal status 0xD0 on port 0xEC07
ATA: abnormal status 0xD0 on port 0xEC07
ata1: command 0x25 timeout, stat 0xd0 host_stat 0x21
ata1: status=0xd0 { Busy }
SCSI error : <0 0 0 0> return code = 0x8000002
sda: Current: sense key: Aborted Command
    Additional sense: Scsi parity error
end_request: I/O error, dev sda, sector 144346022
EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode
block - inode=571367, block=1146889
Remounting filesystem read-only
ATA: abnormal status 0xD0 on port 0xEC07
ATA: abnormal status 0xD0 on port 0xEC07
ATA: abnormal status 0xD0 on port 0xEC07
ata1: command 0x25 timeout, stat 0x50 host_stat 0x21
EXT3-fs error (device sda3) in ext3_reserve_inode_write: IO failure


This like a 1 month old apt-get upgrade.

.Alejandro


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Sid is/was crazy

Carlos C Soto
Hi Alejandro.

Looks like your ext3 partition has errors and the system remount it in
readonly mode.
Not every problem get corrected by apt, I mean apt rocks but this is not
a package problem.
Try to check your partition with fsck (man fsck, man fsck.ext3) maybe
you need will to execute a livecd ( from man fsck.ext3: "...in  general
it is not safe to run e2fsck on mounted filesystems...")

Maybe you want to enter some IRC Channel to get some quickly and in
spanish answers.

Cheers
eclipxe

Alejandro Bonilla Beeche wrote:

> Hi,
>
> Every some hours my Debian Sid box goes wild and I can't do anything.
> Not even being root.
>
> Is crazy. I can't even do apt-get update to try fixing this problem...
>
> Err http://http.us.debian.org unstable/main xpdf-common 3.01-2
>  Could not open file
> /var/cache/apt/archives/partial/xpdf-common_3.01-2_all.deb - open (30
> Read-only file system) [IP: 64.50.236.52 80]
> Err http://http.us.debian.org unstable/main yelp 2.10.0-3
>  Could not open file
> /var/cache/apt/archives/partial/yelp_2.10.0-3_i386.deb - open (30
> Read-only file system) [IP: 204.152.191.7 80]
> 39% [Waiting for headers]
> debian:~# whoami
> root
> debian:~# screen
> mkfifo /var/run/screen/S-root/5922.pts-0.debian failed
>
> dmesg:
>
> SCSI error : <0 0 0 0> return code = 0x8000002
> sda: Current: sense key: Aborted Command
>    Additional sense: Scsi parity error
> end_request: I/O error, dev sda, sector 147753830
> Buffer I/O error on device sda3, logical block 1572865
> lost page write due to I/O error on sda3
> ATA: abnormal status 0xD0 on port 0xEC07
> ATA: abnormal status 0xD0 on port 0xEC07
> ATA: abnormal status 0xD0 on port 0xEC07
> ata1: command 0x25 timeout, stat 0xd0 host_stat 0x21
> ata1: status=0xd0 { Busy }
> SCSI error : <0 0 0 0> return code = 0x8000002
> sda: Current: sense key: Aborted Command
>    Additional sense: Scsi parity error
> end_request: I/O error, dev sda, sector 144346022
> EXT3-fs error (device sda3): ext3_get_inode_loc: unable to read inode
> block - inode=571367, block=1146889
> Remounting filesystem read-only
> ATA: abnormal status 0xD0 on port 0xEC07
> ATA: abnormal status 0xD0 on port 0xEC07
> ATA: abnormal status 0xD0 on port 0xEC07
> ata1: command 0x25 timeout, stat 0x50 host_stat 0x21
> EXT3-fs error (device sda3) in ext3_reserve_inode_write: IO failure
>
>
> This like a 1 month old apt-get upgrade.
>
> .Alejandro
>
>


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Sid is/was crazy

Bernd Eckenfels
In reply to this post by Alejandro Bonilla Beeche
In article <[hidden email]> you wrote:
> /var/cache/apt/archives/partial/yelp_2.10.0-3_i386.deb - open (30
> Read-only file system) [IP: 204.152.191.7 80]
> debian:~# screen
> mkfifo /var/run/screen/S-root/5922.pts-0.debian failed

your /var is mounted read only mode because your kernel had an hardware IO error.

>    Additional sense: Scsi parity error

this could be a failing device electronics, broken wiring, thermal or power
problems - less likely is a failing drive but also possible.

Backup your data as long as you can.

Gruss
Bernd


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Sid is/was crazy

Henrique de Moraes Holschuh
On Wed, 19 Oct 2005, Bernd Eckenfels wrote:

> In article <[hidden email]> you wrote:
> > /var/cache/apt/archives/partial/yelp_2.10.0-3_i386.deb - open (30
> > Read-only file system) [IP: 204.152.191.7 80]
> > debian:~# screen
> > mkfifo /var/run/screen/S-root/5922.pts-0.debian failed
>
> your /var is mounted read only mode because your kernel had an hardware IO error.
>
> >    Additional sense: Scsi parity error
>
> this could be a failing device electronics, broken wiring, thermal or power
> problems - less likely is a failing drive but also possible.
>
> Backup your data as long as you can.

And, considering the type of problem you had and that you were unable to
figure it out immediately, I'd strongly suggest that you switch to Etch or
Sarge, instead of Sid.

You will have a happier Debian experience, then.  Eventually one of the real
badass sid breakages would hit you, and cause you quite a lot of grief.

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]