search for: irrecoverably

In article <E02FA554-9D6D-4E7D-8A78-5FBDE1DE939D at kicp.uchicago.edu>, Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: > > > > On Sep 26, 2020, at 8:05 AM, Jerry Geis <jerry.geis at gmail.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

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

> On Sep 26, 2020, at 8:05 AM, Jerry Geis <jerry.geis at gmail.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,

@tonymountifield Does this still hold true? https://superuser.com/a/1075837 On Sun, Sep 27, 2020 at 7:21 AM Tony Mountifield <tony at softins.co.uk> wrote: > In article <E02FA554-9D6D-4E7D-8A78-5FBDE1DE939D at kicp.uchicago.edu>, > Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: > > > > > > > On Sep 26, 2020, at 8:05 AM, Jerry Geis

...herefore, I set up pci passthrough for the Atheros device (worked), compiled some domU madwifi kernel modules (worked), loaded the modules (worked), and presto everything should be fine (not quite). Two problems: 1) Saving or pausing a VM that has madwifi drivers loaded crashes dom0 and domU irrecoverably without dropping a line to log or console. 2) Say I unload the modules, checkpoint, and restore the VM. Then, when I attempt to modprobe ath_pci, I see this lovely little bit[0]. Modules are loaded, no interfaces seen through ifconfig/iwconfig. Furthermore, I''ve tried re...

Hi all, a user contacted me about a segfault when installing WGCNA package dowloaded from CRAN. I also see a segfault like that on certain installs of R. The package passes all CRAN checks, so presumably this has something to do with the R installation or environment. The R versions here are not the newest but I would guess that this is not an R version issue. I'm attaching two

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

Interesting, yesterday I had exactly this problem, but today I solved it (see the R-pkg-devel list) by _installing_ R-devel and > update.packages(checkBuilt = TRUE) I also tried it on Martin's Fedora 26 example below. Worked fine (had to install some packages...) On ubuntu 16.04. G?ran Brostr?m On 2017-12-06 11:29, Martin Maechler wrote: >>>>>> Pearce, Robert

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

Dear everyone, I have maintained JL Schafer's package 'pan' for a while and recently been contacted for the possibility 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,

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

>>>>> Pearce, Robert <Pearce.Robert at epa.gov> >>>>> on Tue, 5 Dec 2017 21:31:09 +0000 writes: > 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). There is no such message (as you cite below) in the R-devel archives:

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

I'm having a strange problem compiling R4.4.0 on an AlmaLinux9 box. I've compiled previous versions OK on the same hardware/software (last was R4.3.2) but 4.4.0 is repeatedly failing. Configuration works OK. ./configure --prefix=/bi/apps/R/4.4.0 --enable-R-shlib R is now configured for x86_64-pc-linux-gnu Source directory: . Installation directory: /bi/apps/R/4.4.0

> Perhaps, but then you need to assume that the jitterbuffer can just > throw away the data, and that limits how you can use it. In object- > oriented terms, you might want to pass objects to the JB, and then > call a destructor on them. In C terms, you may want to allocate > frames via malloc(), and then call free() on them later. You might > want to pass in

Robert, To expand a bit on Goran's point, is it possible that you have an old library with packages installed that your R-devel is hitting. The R headers changes relatively recently, so any packages with compiled code that were built long enough ago (I don't have the exact date off the top of my head) need to be rebuilt before they can be safely used. If this is happening in a state

On May 3, 2006, at 9:54 PM, Jean-Marc Valin wrote: >> Perhaps, but then you need to assume that the jitterbuffer can just >> throw away the data, and that limits how you can use it. In object- >> oriented terms, you might want to pass objects to the JB, and then >> call a destructor on them. In C terms, you may want to allocate >> frames via malloc(), and then call

Hi all, I seem to be getting segfaults when attempting to build R 4.4.0 on RHEL 9.1 (5.14.0-162.23.1.el9_1.x86_64). Interestingly, it seems to build ok on Rocky 9.1 and 9.3. This is the trace: make[3]: Entering directory '/home/esteva.m/R/R-4.4.0/src/library/grDevices' building package 'grDevices' make[4]: Entering 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