From owner-freebsd-current Sun Dec 5 10:23:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id A242814DFB for ; Sun, 5 Dec 1999 10:23:25 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA18354; Sun, 5 Dec 1999 19:23:13 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Jeroen C. van Gelderen" Cc: current@FreeBSD.ORG Subject: Re: Mount problems after lockup In-reply-to: Your message of "Sun, 05 Dec 1999 14:09:27 -0400." <384AAA57.CF98083F@vangelderen.org> Date: Sun, 05 Dec 1999 19:23:12 +0100 Message-ID: <18352.944418192@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is really a good idea to read the current mailing list if you run current on your machine. copy MAKEDEV from src/etc/MAKEDEV to /dev, and run it to recreate your disk devices. Poul-Henning In message <384AAA57.CF98083F@vangelderen.org>, "Jeroen C. van Gelderen" writes : >Hi, > >I'm having some problems with my -CURRENT box. The problem as >described has happened twice already but I cannot reproduce >it reliably yet (have to wait for X to lock up). > >My system locked up solidly (no ping response) while in X so I >had to reboot the box. Upon fsck I got the following messages: > > WARNING: / was not properly dismounted > > WARNING: R/W mount of / denied. Filesystem is not clean - run fsck > >I then drop into single user mode to run fsck manually and it >simply succeeds, without any errors shown. If I subsequently >try to mount R/W I again get the the complaint about the >filesystem not being clean as seen above. > >I then tried fsck -b32 /, a couple of syncs and a reboot and the >machine is happy now, apart from some filesystem corruption. (I >had to boot an older kernel as /kernel was corrupt.) > >I ran a disk checker (the one provided in the Adaptec BIOS) and >it doesn't find any problems on the the disk. Also, all cables >are terminated properly and this configuration has worked for >months without problems. I've never seen any SCSI related errors >in my logs. > >Is this likely to be a hardware problem? If so, how come there is >no messages in syslog? Could it be that one of the IDE drives has >gone bad and this confuses the kernel?? I'd appreciate any clues >as to how to approach this correctly. > >Cheers, >Jeroen > >FreeBSD grolsch.ai 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Wed Dec 1 >08:27:42 GMT 1999 > >gelderen@grolsch.ai:/usr/src/sys/compile/DESKTOP i386 >Copyright (c) 1992-1999 The FreeBSD Project. >Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights >reserved. >FreeBSD 4.0-CURRENT #0: Wed Dec 1 08:27:42 GMT 1999 > gelderen@mises.ai:/usr/src/sys/compile/DESKTOP >Timecounter "i8254" frequency 1193182 Hz >CPU: Pentium II/Xeon/Celeron (450.46-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x651 Stepping = 1 > >Features=0x183fbff >real memory = 268423168 (262132K bytes) >avail memory = 257310720 (251280K bytes) >Preloaded elf kernel "kernel" at 0xc02fc000. >ccd0-3: Concatenated disk drivers >Pentium Pro MTRR support enabled >npx0: on motherboard >npx0: INT 16 interface >pcib0: on motherboard >pci0: on pcib0 >pcib1: at device 1.0 on >pci0 >pci1: on pcib1 >vga-pci0: irq 11 at device 0.0 on >pci1 >isab0: at device 4.0 on pci0 >isa0: on isab0 >ata-pci0: at device 4.1 on pci0 >ata-pci0: Busmastering DMA supported >ata0 at 0x01f0 irq 14 on ata-pci0 >ata1 at 0x0170 irq 15 on ata-pci0 >pci0: UHCI USB controller (vendor=0x8086, dev=0x7112) at 4.2 irq 10 >chip1: at device 4.3 on pci0 >ahc0: irq 10 at device 6.0 on >pci0 >ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs >fxp0: irq 10 at device 9.0 on >pci0 >fxp0: Ethernet address 00:90:27:88:b2:dc >fxp0: supplying EUI64: 00:90:27:ff:fe:88:b2:dc >atkbdc0: at port 0x60-0x6f on isa0 >atkbd0: irq 1 on atkbdc0 >psm0: irq 12 on atkbdc0 >psm0: model Generic PS/2 mouse, device ID 0 >vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on >isa0 >sc0: on isa0 >sc0: VGA <16 virtual consoles, flags=0x200> >sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 >sio0: type 16550A >sio1 at port 0x2f8-0x2ff irq 3 on isa0 >sio1: type 16550A >sio2: not probed (disabled) >sio3: not probed (disabled) >ad0: ATA-4 disk at ata0 as master >ad0: 6204MB (12706470 sectors), 13446 cyls, 15 heads, 63 S/T, 512 B/S >ad0: 16 secs/int, 1 depth queue, UDMA33 >ad1: ATA-4 disk at ata0 as slave >ad1: 6204MB (12706470 sectors), 13446 cyls, 15 heads, 63 S/T, 512 B/S >ad1: 16 secs/int, 1 depth queue, UDMA33 >ad2: ATA-3 disk at ata1 as master >ad2: 8693MB (17803296 sectors), 17662 cyls, 16 heads, 63 S/T, 512 B/S >ad2: 16 secs/int, 1 depth queue, UDMA33 >ad3: ATA-3 disk at ata1 as slave >ad3: 8693MB (17803440 sectors), 17662 cyls, 16 heads, 63 S/T, 512 B/S >ad3: 16 secs/int, 1 depth queue, UDMA33 >Mounting root from ufs:/dev/da0s1a >da0 at ahc0 bus 0 target 0 lun 0 >da0: Fixed Direct Access SCSI-2 device >da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing >Enabled >da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) >fxp0: starting DAD for fe80:0001::0290:27ff:fe88:b2dc >fxp0: DAD complete for fe80:0001::0290:27ff:fe88:b2dc - no duplicates >found > ># Device Mountpoint FStype Options Dump >Pass# >/dev/da0s1b none swap sw 0 >0 >/dev/da0s1a / ufs rw 1 >1 > ^^^^^^ > not running soft updates. the others do. >/dev/da0s1f /tmp ufs rw 2 >2 >/dev/da0s1g /usr ufs rw 2 >2 >/dev/da0s1e /var ufs rw 2 >2 >/dev/wcd0c /cdrom cd9660 ro,noauto 0 >0 >/dev/ccd0c /mnt/ccd0 ufs rw 0 >2 >/dev/wd2s1e /mnt/wd2 ufs rw 0 >2 >/dev/wd3s1e /mnt/wd3 ufs rw,sync 0 >2 >proc /proc procfs rw 0 >0 >-- >Jeroen C. van Gelderen - jeroen@vangelderen.org >Interesting read: http://www.vcnet.com/bms/ JLF > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message