Re: sata + vinum + Asus p4p800 = :(
On Monday, Oct 20, 2003, at 19:02 Europe/Budapest, Alexander Leidinger wrote: Greg 'groggy' Lehey schrieb: Provide a dump? Analyse the problem yourself? This *is* -CURRENT, after all. I can reproduce this here (same MB). I don't think it's a vinum problem, but vinum seems to be a good way to reproduce the bug. I set up a stripe over 2 SATA disks, newfs it, run iozone -a and BOOM. Well, my /etc dir is gone, and I have no other bootable device. Tomorrow my hardware guy will bring me a new be7s motherboard... Sorry guys, the rest is in your hands. -- jul ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sata + vinum + Asus p4p800 = :(
On Wednesday, Oct 15, 2003, at 01:24 Europe/Budapest, Greg 'groggy' Lehey wrote: On Tuesday, 14 October 2003 at 18:46:44 +0200, Balazs Nagy wrote: What can I do? Provide a dump? Analyse the problem yourself? This *is* -CURRENT, after all. Well... There is a tricky problem... I have two panics: %fsck -t ufs -B /mnt panic: ata_dmasetup: transfer active on this device! syncing disks, buffers remaining... 1015 1015 1015 1015 1015 1015 1015 1015 1015 1015 1015 1015 1015 1015 1015 1015 1015 1015 1015 1015 giving up on 949 buffers Uptime: 1m32s ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) ata2: resetting devices .. panic: free locked buf Uptime: 1m32s of course, no dump created. Besides, why my SATA interfaces are recognized as UDMA133? It sounds like this could be an issue with ATA compatibility issues with this mother board. You should be able to mount your root file system from the underlying UFS partition, thus disabling Vinum; at least that would help you track down the problem. It has ICH5R south bridge, with correct PCI ids. Film at 11, or when I go home to generate some crash dump. -- jul ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sata + vinum + Asus p4p800 = :(
On Wednesday, Oct 15, 2003, at 10:34 Europe/Budapest, Soren Schmidt wrote: First loose vinum from the mix, if we should have a chance finding the problem we need to lower the number of unknowns. Then tell us if and how it fails, dmesg from verbose booted system, backtrace etc, you know the drill if running -current. Lunchtime I went home just to reboot my box with no vinum config. Sadly it works seamlessly. -- jul ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
sata + vinum + Asus p4p800 = :(
Hi, I had a -CURRENT setting with an Abit BE7-S and two SATA disks with vinum configuration. It worked very well until a power failure, and the mainboard died. Yesterday I got a replacement mainboard, the only type met the requirements (eg. two SATA ports) in the store: an Asus P4P800. My only problem is with the disks. I can use all USB ports (8; what a server could do with eight USB ports?), the 3C940 Gigabit Ethernet port (I disabled the sound subsystem), and everything works until the first fsck, when the kernel paniced. Here is the dmesg: GEOM: create disk ad0 dp=0xc6b4bb70 ad0: 4028MB Maxtor 90422D2 [8184/16/63] at ata0-master UDMA33 acd0: CDROM GCR-8523B at ata0-slave PIO4 GEOM: create disk ad4 dp=0xc6b4b070 ad4: 117246MB Maxtor 6Y120M0 [238216/16/63] at ata2-master UDMA133 GEOM: create disk ad6 dp=0xc6b4b170 ad6: 117246MB Maxtor 6Y120M0 [238216/16/63] at ata3-master UDMA133 Mounting root from ufs:/dev/vinum/root panic: ata_dmasetup: transfer active on this device! I did further investigation: I booted from ata0-master, and mounted /dev/vinum/root as /mnt. A simple fsck -f -B /mnt killed the system. I did the same with /dev/ad4s1a (this is the boot hack partition from the handbook), then I switched off softupdates. No win. I tried to boot with safe mode either, but it hung with page fault. What can I do? Besides, why my SATA interfaces are recognized as UDMA133? -- jul ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
