search for: irrecoverable

...flagging errors, attempting to rescue the data. > > > > I tried dd first - if gets about 117G of 320G disk and stops incrementing > > the save image any more. > > did you try > > dd conv=noerror ??? > > this flag makes dd not stop on input error. Whatever is irrecoverable is irrecoverable, but this way you will get stuff > beyond failure point. You need conv=noerror,sync so that unreadable sectors get replaced by zeros instead of not being written out at all. Without sync, the filesystem geometry on the destination image will be wrong after the first error. You...

I have a disk that is flagging errors, attempting to rescue the data. I tried dd first - if gets about 117G of 320G disk and stops incrementing the save image any more. Now I'm trying ddrescue and it also stops about the same point Thoughts on how to continue past that point ? Thanks, Jerry

...com> wrote: > > I have a disk that is flagging errors, attempting to rescue the data. > > I tried dd first - if gets about 117G of 320G disk and stops incrementing > the save image any more. did you try dd conv=noerror ? this flag makes dd not stop on input error. Whatever is irrecoverable is irrecoverable, but this way you will get stuff beyond failure point. Valeri > > Now I'm trying ddrescue and it also stops about the same point > > Thoughts on how to continue past that point ? > Thanks, > > Jerry > _______________________________________________...

...ata. > > > > > > I tried dd first - if gets about 117G of 320G disk and stops > incrementing > > > the save image any more. > > > > did you try > > > > dd conv=noerror ? > > > > this flag makes dd not stop on input error. Whatever is irrecoverable is > irrecoverable, but this way you will get stuff > > beyond failure point. > > You need conv=noerror,sync so that unreadable sectors get replaced by > zeros instead of not being written out at all. > Without sync, the filesystem geometry on the destination image will be >...

Hi list, The crux of my setup is given in the Subject: field. I''m using Xen 3.0.3 (release) on a VIA Nehemiah chipset with Linux 2.6.16.29 in both dom0 and domU. Because the documentation on PCI passthrough is a bit sparse, I''m turning to the mailing list.. hopefully you guys have some input. My goal is to set up a system where: * 1 domU VM runs at a time. * The VM can be

...ALLOW_WGCNA_THREADS=32 * * before running R. Other operating systems or shells will * have a similar command to achieve the same aim. * ========================================================================== *** caught segfault *** address (nil), cause 'memory not mapped' An irrecoverable exception occurred. R is aborting now ... Segmentation fault ERROR: loading failed * removing ?/mnt/mfs/cluster/bin/R-3.4/library/WGCNA? *** caught segfault *** address (nil), cause 'memory not mapped' Traceback: 1: q("no", status = status, runLast = FALSE) 2: do_exit(status...

Hi, I have a win10 guest on a fedora32 system and have some questions as I explore using external snapshots as a form of backup in case of a Windows failure (as in, it won't boot or is completely irrecoverable) as well as revision control (to be able to rollback changes after a failed app install, etc). The first hit on Google for external snapshots involves a RHEL7 document that talks about how it's not officially supported. The current RHEL8 docs don't include any references to snapshots....

..."weave", engine = engine)}, error = function(e) { stop(gettextf("processing vignette '%s' failed with diagnostics:\n%s", file, conditionMessage(e)), domain = NA, call. = FALSE)}) > 17: tools::buildVignettes(dir = ".", tangle = TRUE) > An irrecoverable exception occurred. R is aborting now ... > [nfslocal at lynne tmp]$ > ------------------------------------------------------------------------ > > > I've seen this (segfault, triggered from stringr stuff) before, > occasionally and always thought it was a consequence...

I am resubmitting this bug report but with additional information. I am running this with windows 10: w64-mingw32 with R Under development (unstable) (2017-12-04 r73829). I build 'httk' from the command prompt using 'R CMD build httk' after installing the required packages. Then when the vignettes are being created, it crashes. Today I installed the latest versions of Rtools,

Hello, I'm seeking the solution to live storage migration using blockcopy. Previously, the "virsh undefine" is required before blockcopy. https://www.redhat.com/archives/libvirt-users/2015-October/msg00027.html QEMU has "block-dirty-bitmap-*" operations now, are there steps for the live storage migration using blockcopy without undefine? By the way, why's the purpose

...ty to fix a crash but it turned to be elusive -- I am wondering what is the best to resolve this. First, the error message is as follows, *** caught segfault *** address 0x1b0000001b3, cause 'memory not mapped' Traceback: 1: pan(test$Y1, test$ID, X, 1:4, 4, prior, seed = m, iter = 100) An irrecoverable exception occurred. R is aborting now ... and I gather this is to do with R/fortran mismatch nevertheless the tricky thing is that it works fine with the documentation data and even with this data there were times it could be tweaked to work (therefore PAN.txt, test.rda and test.log were as intend...

On 1/19/2016 2:24 PM, Warren Young wrote: > It?s dying. Replace it now. agreed > On a modern hard disk, you should*never* see bad sectors, because the drive is busy hiding all the bad sectors it does find, then telling you everything is fine. thats not actually true. the drive will report 'bad sector' if you try and read data that the drive simply can't read. you

...t(name, by = "weave", engine = engine)}, error = function(e) { stop(gettextf("processing vignette '%s' failed with diagnostics:\n%s", file, conditionMessage(e)), domain = NA, call. = FALSE)}) 17: tools::buildVignettes(dir = ".", tangle = TRUE) An irrecoverable exception occurred. R is aborting now ... [nfslocal at lynne tmp]$ ------------------------------------------------------------------------ I've seen this (segfault, triggered from stringr stuff) before, occasionally and always thought it was a consequence of a messup (different R versio...

https://bugs.freedesktop.org/show_bug.cgi?id=96836 Bug ID: 96836 Summary: Kernel unaligned access at TPC[105d9fb4] nvkm_instobj_wr32+0x14/0x20 [nouveau] Product: xorg Version: unspecified Hardware: SPARC OS: Linux (All) Status: NEW Severity: normal Priority: medium

...urce = keep.source, keep.parse.data = keep.parse.data, partial = TRUE)) 16: code2LazyLoadDB(package, lib.loc = lib.loc, keep.source = keep.source, keep.parse.data = keep.parse.data, compress = compress, set.install.dir = set.install.dir) 17: tools:::makeLazyLoading("grDevices") An irrecoverable exception occurred. R is aborting now ... make[4]: *** [../../../share/make/lazycomp.mk:9: ../../../library/grDevices/R/grDevices.rdb] Error 139 I can reproduce the error directly by running make in /bi/apps/R/R-4.4.0/src/library/grDevices. Nothing strange is in my environment, I'm using the...

...at happens if it gets into asterisk and a lot > of real-world broken streams get thrown at it :) Of course, I'm always interested in more testing. However, I've already (voluntarily and especially involuntarily) abused it nonsensical data and I have yet to see it fail (i.e. go into an irrecoverable state). > What really would help in the long run is if we had some kind of test > harness to run these things in, and good test data culled from real- > world situations. I had some hacky tools like this I used when I > built my implementation, but nothing really good. Sure. I...

...t; engine)}, error = function(e) { stop(gettextf("processing vignette '%s' >> failed with diagnostics:\n%s", file, conditionMessage(e)), domain = >> NA, call. = FALSE)}) >> 17: tools::buildVignettes(dir = ".", tangle = TRUE) >> An irrecoverable exception occurred. R is aborting now ... >> [nfslocal at lynne tmp]$ >> ----------------------------------------------------------- >> ------------- >> >> >> I've seen this (segfault, triggered from stringr stuff) before, >> occasionally and alwa...

...sterisk and a lot >> of real-world broken streams get thrown at it :) > > Of course, I'm always interested in more testing. However, I've > already > (voluntarily and especially involuntarily) abused it nonsensical data > and I have yet to see it fail (i.e. go into an irrecoverable state). > >> What really would help in the long run is if we had some kind of test >> harness to run these things in, and good test data culled from real- >> world situations. I had some hacky tools like this I used when I >> built my implementation, but nothing really...

...e = keep.source, keep.parse.data = keep.parse.data, partial = TRUE)) 16: code2LazyLoadDB(package, lib.loc = lib.loc, keep.source = keep.source, keep.parse.data = keep.parse.data, compress = compress, set.install.dir = set.install.dir) 17: tools:::makeLazyLoading("grDevices") An irrecoverable exception occurred. R is aborting now ... make[4]: *** [../../../share/make/lazycomp.mk:9: ../../../library/grDevices/R/grDevices.rdb] Error 139 make[4]: Leaving directory '/home/esteva.m/R/R-4.4.0/src/library/grDevices' make[3]: *** [Makefile:28: all] Error 2 make[3]: Leaving directory...

Hi all, I know this is the EXT3 list, and my problem is with an EXT2 filesys, but I cannot seem to find a more suitable list on this server, and I have seen a lot of knowledge go by on this list and in the archives, so I thought I'd give it a try anyway... Here goes nothing: I am in a terrible problem: My data disk on my Linux server has gone bad, with approx 18 GB of data on it, and I