similar to: SMART errors

I finally fixed my drive error problem. This has been going on quite a while. I've posted before with no success on getting this fixed. I was getting these errors. Dec 4 04:03:10 bikesn4x4s kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Dec 4 04:03:10 bikesn4x4s kernel: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } And now for the amazing smartctl -a

My wife's box has a very intermittent problem, when booting from the Maxtor IDE hard drive. This has been going on for about 2 1/2 years.... The box is a Compaq EVO D300v for the Enterprise. When it boots, there is a SMART advisory from the BIOS that says failure is immenient. Occasionally, it will not boot, because the BIOS does not see the hard drive. I replaced the EIDE cable, but the

Hi... I really hope that somebody can help me to brainstorm this problem. Please let me describe my enviornment. Environment --------------- Fedora 16 x86_64(fully up-to-date) Wine 1.5.1 32bit and noarch binaries only Nvidia GPU - GTS 450 Nvidia Driver - 295.40 (including 32bit libraries) I've installed Perfectworld International under wine. Everything was running fine until the most recent

Hi All, I am fairly certain that this disk is failing in my server, and I am replacing it straight away anyway. However, I'd appreciate the views of the list just to be sure as I value your opinion(s). I got these errors, once only so far, in /var/log/messages. This disk has / on it. Oct 5 08:34:47 server1 kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0 Oct 5 08:34:47

Hi there. OS version: FreeBSD 4.7-Stable FreeBSD #3 I just added a disk to my box and after playing with fdisk and disklabel with this configuration: fdisk: **************************************************************** g c16383 h16 s63 p 1 165 0 39102336 **************************************************************** disklabel

Hi, We're using gmirror on our sun fire x2100 and FreeBSD 6.1-p10. Some days ago I found this in the logs: Apr 1 02:12:05 x2100 kernel: ad6: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=612960533 Apr 1 02:12:05 x2100 kernel: ad6: FAILURE - WRITE_DMA48 status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=612960533 Apr 1 02:12:05 x2100 kernel: GEOM_MIRROR:

On May 24, 2008, at 4:25 PM, Marcel Moolenaar wrote: > On May 24, 2008, at 12:12 PM, Bill Wendling wrote: >> Let us know if you would like extra eyes on the two PPC failures. >> Many >> of us have a lot of experience with C++. :-) Do you know where these >> allocations are? > > I don't mind if people help out, so here's some information: Nice!

On May 24, 2008, at 12:12 PM, Bill Wendling wrote: > Let us know if you would like extra eyes on the two PPC failures. Many > of us have a lot of experience with C++. :-) Do you know where these > allocations are? I don't mind if people help out, so here's some information: FAIL: /nfs/llvm/src/llvm/test/Transforms/PredicateSimplifier/ 2006-11-04-ReplacingZeros.ll Failed with

On May 24, 2008, at 11:43 AM, Marcel Moolenaar wrote: > All, > > So far I've tried LLVM on amd64, i386, ia64 and powerpc under FreeBSD > and aside for ia64, things look pretty good for a first try. There > are 2 unexpected failures for PowerPC, which appear to be caused by > uninitialized memory. I'm still working on a fix for that (need to > brush up on my C++

All, So far I've tried LLVM on amd64, i386, ia64 and powerpc under FreeBSD and aside for ia64, things look pretty good for a first try. There are 2 unexpected failures for PowerPC, which appear to be caused by uninitialized memory. I'm still working on a fix for that (need to brush up on my C++ skills). [sidenote: In FreeBSD -current, the memory allocator initializes memory with 0xa5

Hi, I get the following error when running libvirtd on MacOS as root: $ sudo libvirtd 2019-07-11 00:12:33.379+0000: 123145573953536: info : libvirt version: 5.5.0 2019-07-11 00:12:33.379+0000: 123145573953536: warning : virProcessGetStartTime:1070 : Process start time of pid 49746 not available on this platform 2019-07-11 00:12:33.379+0000: 123145573953536: error : virSysinfoReadDMI:1172 :

Hi. I am looking for an IPv6 capable CVSUP mirror. I found a discussion from one year ago where it was stated that CVSUP was not IPv6-capable. Does anyone know if this has changed? Sam -- Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/sam

Hello, I've got a (P)ATA disk in a special frame. The disk itself supports UDMA-100 (and has an 80-ribbon cable), but the frame isn't compatible with that. By default, FreeBSD negotiates UDMA-100, and the console starts to fill with ICRC errors. In the past, I used a patch to ata-all.c that enabled the following entry in loader.conf to force the disk to UDMA-33, so it worked fine:

You should probably exclude the .DUMPSTER folder from quota and FTS plugin { fts_autoindex_exclude = .DUMPSTER quota_ruleN = .DUMPSTER:ignore } Aki On 23.05.2018 13:29, Matt Bryant wrote: > So digging a little deeper it seems this maybe an issue between > fts/fts_lucene and lazy_expunge .. if I disable the fts plugin > > [root at stargate dovecot.rawlog]#? doveadm search -u >

The subject says ‘xpath_get_nodes()‘, but this function doesn't actually take a unit parameter, so it's better to drop ‘()’. On Thu, Oct 05, 2017 at 04:58:29PM +0200, Cédric Bosdonnat wrote: > + > +let xpath_get_nodes xpathctx expr = > + let obj = Xml.xpath_eval_expression xpathctx expr in > + let nodes = ref [] in > + for i = 0 to Xml.xpathobj_nr_nodes obj - 1 do > +

Hi. There's a rescue cd at ftp://ftp.pld.org.pl/people/areq/RescueCD/ that uses isolinux that don't work in my configuration. All I get is: --8<-- ISOLINUX 1.75 2002-06-14 isolinux: loading spec packet failed, trying to wing it... isolinux: extremly broken bios detected, last ditch attempt with drive=9F isolinux: disk error 80, ax=432E, drive 9F --8<-- My configuration is: VP_IDE:

Hi, I'm using a recent RELENG_6 under I386/SMP (Athlon X2 4800+). dmesg output is under http://people.freebsd.org/~mr/dmesg.log.gz Root is on gmirror volume (2 SATA disks), a backup FS is on graid3 (5 firewire disks). This server acts as an bacula server. During backup with bacula I discovered an complete system freeze (no keyboard, nfs, disk...) after the following lines on the screen: ...

Hello, SMART error (OfflineUncorrectableSector) detected on host: *************************************************************************** The following warning/error was logged by the smartd daemon: Device: /dev/hdb, 2 Offline uncorrectable sectors For details see host's SYSLOG (default: /var/log/messages). You can also use the smartctl utility for further investigation. No additional

On 2014-01-14 10:12, dstrr wrote: > Hello. > Trouble to communicate with APC SmartUPS via serial port. > UPS connected to the com1 port on windows host. > Communication witch hyperterm works well. > There is a log: > > YSM > ^ASmart-UPS SC1000 > n5S0713T63247 > m03/29/07 > L240.0 > B27.10 > > apcupsd also can communicate with the UPS and works well. >

Hello. Trouble to communicate with APC SmartUPS via serial port. UPS connected to the com1 port on windows host. Communication witch hyperterm works well. There is a log: YSM ^ASmart-UPS SC1000 n5S0713T63247 m03/29/07 L240.0 B27.10 apcupsd also can communicate with the UPS and works well. running apcsmart -a ups gives the following: com1: device reports different attributes than what were set