search for: ad8e

Hi, after one month with gmirror and gjournal running on a 7.0-RELEASE #p2 amd64 (built from latest CVS source), the box hung a couple of times when on high disk load. Finally, while building some port it won't boot for no reason obvious to me. This is what I get with kernel.geom.mirror.debug=2: ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad4: 476940MB <SAMSUNG HD501LJ

I have a zpool that consists for a two-drive mirror. The two times I took the zpool offline, I had to resilver one of the drives (the same drive both times) when I imported it back. All drives in the pool show no read, write, or checksum errors and are new, so I'm looking to a software problem before hardware. Both drives are encrypted geli devices. I tried to reproduce the error with 1GB

I am attempting to install 7.1-BETA2 (from CD) onto a PC with a Promise SX4060 RAID controller and two Seagate 120GB ATA disk drives. The boot from CD keeps repeating the following (error) messages: (I'm retyping here) ============================================================================ ================== ad4: WARNING - SETFEATURES SET TRANSFER MODE task queue timeout - completing

Hello I have this problem: Yesterday server with FreeBSD 6.0 was self restarted . In messages was this: Mar 8 20:03:11 mail kernel: ar1: WARNING - mirror protection lost. RAID1 array in DEGRADED mode Mar 8 20:03:11 mail kernel: ar1: writing of Intel MatrixRAID metadata is NOT supported yet Mar 8 20:03:11 mail kernel: subdisk8: detached Mar 8 20:03:11 mail kernel: ar1: writing of Intel

I made a bad judgment and now my raidz pool is corrupted. I have a raidz pool running on Opensolaris b85. I wanted to try out freenas 0.7 and tried to add my pool to freenas. After adding the zfs disk, vdev and pool. I decided to back out and went back to opensolaris. Now my raidz pool will not mount and got the following errors. Hope someone expert can help me recover from this error.

Hi all! According to www.freebsd.org/releases/5.1R/hardware-i386.html#AEN63 FreeBSD doesnt seem to support the PDC20378 chipset. Anyway, output of dmesg, atapci0: <Promise PDC20378 SATA150 controller> port 0xdc00-0xdc7f,0xdfa0-0xdfaf,0xdf00-0xdf3f mem 0xfeac0000-0xfeadffff,0xfeafe000-0xfeafefff irq 11 at device 4.0 on pci2 more dmesg output: ar0: ERROR - array broken

I have previously written about a mountroot prompt, here are some details. I have a system with an asus m3a78-emh hdmi board, a 74 gig raptor drive, and a dual core amd am2 cpu. I have had this result with both the amd64 and i386 systems. My steps were all conducted today as follows. install 7.0 release run freebsd-update get src tree build world build and install kernel reboot and be greeted

Say I have a raidz of 3 disks: ad4 ad6 ad8 I want to tell zfs that I am pulling ad4 and replacing it with a new disk on the same controller, but I can''t get it to release its hold on ad4. [0138][root at ztest:/home/matt]# zpool offline pond ad4 Bringing device ad4 offline [0140][root at ztest:/home/matt]# zpool replace pond ad4 cannot replace ad4 with ad4: ad4 is busy

I've tested both 6.3 and 7.0-RC2, amd64 architecture, and have found the occurrence of an interrupt storm using an ASUS A8N-SLI Premium (nForce 4) motherboard with an AMD Opteron 175. Relevant dmesg output: atapci0: <nVidia nForce CK804 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0 ata0: <ATA channel 0> on atapci0 ata1: <ATA

...> I have already done it but I can't really tell what I 'm supposed to > see in the log > > this is a line for a message without matching rule : > > Jan 09 23:07:48 lda(xxxx at xxxxxx.xxx): Info: sieve: > msgid=<849d7f91-fdd3-4c07-8039-9e00acfefd2e_2961dc3c-f238-4f72-ad8e-02b1c779e6b5 at SYSTEM5.de.local>: > stored mail into mailbox 'INBOX' > > and this with a working rule: > > Jan 10 01:00:04 lda(xxxx at xxxxxx.xxx): Info: sieve: > msgid=<20180109230004.1BC1344773 at xxx.xxxxx.xxx>: stored mail into > mailbox 'INBOX/Postfix...

On 11.01.2018 11:45, CP wrote: > Hello list, > > I'm trying to setup sieve on a Debian 9 install with virtual users. > Perhaps I'm getting old, but I can't figure out why managesieve is > not working for virtual users. I have about 20 v users on this machine > and only one has also a real unix account. The sieve rules work for this > single unix account? but not

Hi all, I have some problems with my gvinum setup after the system panic'ed. Afterwards the system fails finding the plexes to the subdisks (or at least that is what I can understand after having searched the gvinum source code for the error string in the DMESG log..) The machine is an IBM Netfinity 5000 and the internal HW self tests does not find any errors in the hw. Luckily my root is

Hi I just did a system update and after I've rebooted it doesn't boot up any more. All I'm getting is a blank screen with a curser blinking at the top left corner of the screen. This system was running 7.0-STABLE Any ideas as to how I can get it back up? Regards Reinhold

...rules remotely. > > Aki I have already done it but I can't really tell what I 'm supposed to see in the log this is a line for a message without matching rule : Jan 09 23:07:48 lda(xxxx at xxxxxx.xxx): Info: sieve: msgid=<849d7f91-fdd3-4c07-8039-9e00acfefd2e_2961dc3c-f238-4f72-ad8e-02b1c779e6b5 at SYSTEM5.de.local>: stored mail into mailbox 'INBOX' and this with a working rule: Jan 10 01:00:04 lda(xxxx at xxxxxx.xxx): Info: sieve: msgid=<20180109230004.1BC1344773 at xxx.xxxxx.xxx>: stored mail into mailbox 'INBOX/Postfix' both are with lda deliv...

I've got an Asus P5E3WSPro with 8 SATA ports and 8 disks attached. 6 disks are on one controller (and work perfectly) and 2 are on a second Marvell controller. FreeBSD sees the controller, but not the disks. If I move a working disk to the Marvell controller I can boot off it up to the stage of mounting root where it fails to see the disk. atacontrol shows: ATA channel 2: Master:

Hello, Arne. I try to build storage server for my home (I have a LOT of media files) with FreeBSD 7, 5xHDD (WD 500Gb) and geom_raid5 ("simple" version from perforce, beacuse http://home.tiscali.de/cmdr_faako/geom_raid5.tbz is not patched for FreeBSD7). Array & FS were created with default arguments: # graid5 label storage ad6 ad8 ad10 ad12 ad14 # newfs -O2 -U /dev/raid5/storage

I recently had a hard drive die on my 6 drive raidz2 array (4+2). Unfortunately, now that the dead drive didn''t register anymore, Linux decided to rearrange all of the drive names around such that zfs couldn''t figure out what drives went where. After much hair pulling, I gave up on Linux and went to OpenSolaris, but it wouldn''t recognize my SATA controller, so

Hey folks, So what's the word on AHCI and bios drive geometry? I'm having a real pain of a time trying to get some 750gb sata drives running on my FreeBSD7 box in AHCI mode. It doesn't seem to matter what disk geometry I suggest to sysinstall, something complains of an invalid disk upon booting it. Actually, in AHCI mode the bios screen doesn't report any information on

Thomas, Have spoken to Soren, from my bootlog he believes that the problem is in atapicam causing the system to lock up. He is happy to answer some questions but doesnt have time to delve into atapicam himself. Did you author atapicam, I have seen your name on the sourcecode, can you help me further? Whats next? Thanks Adam. -------------- next part -------------- An embedded message was

...it but I can't really tell what I 'm supposed to >> see in the log >> >> this is a line for a message without matching rule : >> >> Jan 09 23:07:48 lda(xxxx at xxxxxx.xxx): Info: sieve: >> msgid=<849d7f91-fdd3-4c07-8039-9e00acfefd2e_2961dc3c-f238-4f72-ad8e-02b1c779e6b5 at SYSTEM5.de.local>: >> stored mail into mailbox 'INBOX' >> >> and this with a working rule: >> >> Jan 10 01:00:04 lda(xxxx at xxxxxx.xxx): Info: sieve: >> msgid=<20180109230004.1BC1344773 at xxx.xxxxx.xxx>: stored mail into >&gt...