Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Mar 2000 21:31:57 +0400 (MSD)
From:      grg@philol.msu.ru
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   kern/17643: 3.4 to 4.0 upgrade: ATAPI drivers damage the filesystem
Message-ID:  <200003281731.VAA01315@koch2.pikenet.ru>

next in thread | raw e-mail | index | archive | help


>Number:         17643
>Category:       kern
>Synopsis:       3.4 to 4.0 upgrade: ATAPI drivers damage the filesystem
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar 28 09:40:01 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     Grigoriy Strokin
>Release:        FreeBSD 3.4-STABLE i386
>Organization:
Moscow University
>Environment:

>Description:

 I have CVSuped the 4.0-STABLE sources on Mar 20.
 I have upgraded one 3.4-STABLE machine without any problems,
 and today wanted to upgrade another.
 I've made buildworld, buildkernel, installkernel.

 During the boot I've seen:

 Mar 28 17:48:56 koch2 /kernel: ata0: at 0x1f0 irq 14 on atapci0
 Mar 28 17:48:56 koch2 /kernel: ata0: at 0x1f0 irq 14 on atapci0
 Mar 28 17:49:07 koch2 /kernel: ed0: <Longshine LCS-8634P Ethernet Card
 Mar 28 17:49:07 koch2 /kernel: > at port 0x240-0x25f iomem 0xc0000-0xc003f irq 11 on isa0
 Mar 28 17:49:07 koch2 /kernel: ed0: supplying EUI64: 08:00:00:ff:fe:00:10:37
 Mar 28 17:49:07 koch2 /kernel: ed0: address 08:00:00:00:10:37, type NE2000 (16 bit) 
 ...
 Mar 28 17:49:07 koch2 /kernel: ed0: starting DAD for fe80:0001::0a00:00ff:fe00:1037
 Mar 28 17:49:07 koch2 /kernel: ed0: DAD complete for fe80:0001::0a00:00ff:fe00:1037 - no duplicates found
 Mar 28 17:49:07 koch2 /kernel: ed0: device timeout
 Mar 28 17:49:07 koch2 /kernel: ed0: device timeout
 Mar 28 17:49:07 koch2 /kernel: ad0: WRITE command timeout - resetting
 Mar 28 17:49:07 koch2 /kernel: ata0: resetting devices .. done
 Mar 28 17:49:11 koch2 /kernel: ed0: device timeout
 Mar 28 17:49:26 koch2 last message repeated 2 times
 Mar 28 17:49:48 koch2 /kernel: ad0: WRITE command timeout - resetting
 Mar 28 17:49:48 koch2 /kernel: ata0: resetting devices .. done
 Mar 28 17:50:23 koch2 /kernel: ed0: device timeout

Two strange thing here: ed0 timeout and ad0 timeout.

The booting process continued. 

Despite that fact that ed0 was detected,
"ifconfig ed0" gave "interface does not exist"
(also, note the 'ed0 device timeout' messages above)

Then I shut down the machine
and turned it off and on again, just in case there were
real minor problem with hardware.

Second boot:

fsck says about /usr "UNEXPECTED INCONSISTENCY, RUN FSCK MANUALLY".

After running fsck -y several times quite a few files
have been either deleted or moved to lost+found.
/usr/local and my home directory disappeared.

Then I rebooted again in order to turn 'UDMA' off in BIOS.

And again I've seen 'ad0: WRITE command timeout - resetting'
messages, and again /usr became damaged, which resulted
in loss of many other files and directories. About
2/3 of /usr is lost.

I restored parts of /usr and now this machine is again
on 3.4, without any hardware problems neither with 
HDD nor network card.

>How-To-Repeat:


>Fix:

I think I don't know where to look for source of the problem.


>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003281731.VAA01315>