From owner-freebsd-stable Thu Mar 30 14:21:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73]) by hub.freebsd.org (Postfix) with ESMTP id 3C52337B95C for ; Thu, 30 Mar 2000 14:21:32 -0800 (PST) (envelope-from grg@isabase.philol.msu.ru) Received: (from grg@localhost) by isabase.philol.msu.ru (8.9.3/8.9.2) id CAA04123 for freebsd-stable@freebsd.org; Fri, 31 Mar 2000 02:21:30 +0400 (MSD) (envelope-from grg) Date: Fri, 31 Mar 2000 02:21:30 +0400 From: Grigoriy Strokin To: freebsd-stable@freebsd.org Subject: Re: New kernel with its ATA drivers damages the filesystem Message-ID: <20000331022130.A4045@isabase.philol.msu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [sorry --- this message has been recently posted with a wrong subject line] Hello, While the bug wiping out filesystems on machines with Apollo MVP3 when ATA driver is in UDMA mode is being fixed, I suppose there at least should be some note added to /usr/src/UPDATING, so that another users do not loss all their data and have to reinitialize /usr and restore it from backup, as I had to do? Something like that: If you use the Apollo MVP3 chipset, it is STRONGLY recommended that you disable the use of DMA mode in ATA drivers BEFORE you try to boot the system after `make installkernel'. Add the following line: /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio to the very beginning of your /etc/rc, ~root/.profile and ~root/.login. Be warned that if you don't disable the DMA mode, all your filesystems may be corrupted because of a bug in the driver that is still being fixed. > Hello, > > Three days ago I've performed my first upgrade to FreeBSD 4.0-STABLE from > 3.4 on one machine, via CVSUP. Observing the lack of any problems for 3 > days (except audio record) I decided to install it to another box, from the > same sources. > > Well, buildworld etc., then buildkernel (GENERIC), installkernel, > reboot. > > During the boot, I've seen: > > Mar 28 17:48:56 koch2 /kernel: ata0: at 0x1f0 irq 14 on atapci0 > ... > Mar 28 17:49:07 koch2 /kernel: ed0: 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: ad0: 8063MB [16383/16/63] at ata0-master using UDMA33 > Mar 28 17:49:07 koch2 /kernel: acd0: CDROM at ata0-slave using PIO4 > ... > 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: ata0: resetting devices .. done > Mar 28 17:49:48 koch2 /kernel: ad0: WRITE command timeout - resetting > Mar 28 17:49:48 koch2 /kernel: ata0: resetting devices .. done > > The booting process continued. Then I shut down the machine > and turned it off and on again, just in case there were > real problem with HDD. > > 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. > > Moreover, despite that fact that ed0 was detected, > "ifconfig ed0" gave "interface does not exist" > (also, note the 'ed0 device timeout' messages above) > > Now I think I don't know where to find the source of the problem. > -- === Grigoriy Strokin, Lomonosov University (MGU), Moscow === === contact info: http://isabase.philol.msu.ru/~grg/ === To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message