Re: A partially failing disk in raid0 needs replacement

Hi Chris > > I don't see how you get an IO error in user space without the kernel > reporting the source of that IO error, whatever it is. > I totally agree, so I just retried the deletion. The only thing related I could see in /var/log/messages is this: Nov 30 07:29:57 box kernel: [368193.019160]

Re: A partially failing disk in raid0 needs replacement

On Wed, Nov 29, 2017 at 10:28 PM, Klaus Agnoletti wrote: > Hi Chris, > >> >> I assume when you get that, either when deleting the device or >> scrubbing, that you also see the device unrecoverable read error in >> dmesg, as originally reported. If the drive must have the

Re: A partially failing disk in raid0 needs replacement

Hi Chris, > > I assume when you get that, either when deleting the device or > scrubbing, that you also see the device unrecoverable read error in > dmesg, as originally reported. If the drive must have the information > on that lost sector, and you can't increase SCT ERC time (as well as > the

Re: A partially failing disk in raid0 needs replacement

On Wed, Nov 29, 2017 at 6:33 AM, Klaus Agnoletti wrote: > Hi list > > Can anyone give me any hints here? If not, my plan right now is to > start updating the server to latest debian stable (it's currently > running Jessie), to get access to a newer btrfs driver and tools, >

Re: A partially failing disk in raid0 needs replacement

Hi list Can anyone give me any hints here? If not, my plan right now is to start updating the server to latest debian stable (it's currently running Jessie), to get access to a newer btrfs driver and tools, hoping that decreases the risk of something screwing up, and then run btrfs check --repair

Re: A partially failing disk in raid0 needs replacement

Hi List I tried removing the disk roughly like Roman suggested; I copied data using ddrescue from /dev/sdd to new disk /dev/sda. That seemed to work fine. After that I physically removed the old /dev/sdd and put the new /dev/sda to replace it on the same controller. After that I tried removing

Re: A partially failing disk in raid0 needs replacement

On Tue, Nov 14, 2017 at 1:36 AM, Klaus Agnoletti wrote: > Btrfs v3.17 Unrelated to the problem but this is pretty old. > Linux box 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u5 (2017-09-19) Also pretty old kernel. > x86_64 GNU/Linux > klaus@box:~$ sudo btrfs --version >

Re: A partially failing disk in raid0 needs replacement

On Tue, Nov 14, 2017 at 5:48 AM, Roman Mamedov wrote: > On Tue, 14 Nov 2017 10:36:22 +0200 > Klaus Agnoletti wrote: > >> Obviously, I want /dev/sdd emptied and deleted from the raid. > > * Unmount the RAID0 FS > > * copy the bad drive using

Re: A partially failing disk in raid0 needs replacement

On Tue, Nov 14, 2017 at 5:38 AM, Adam Borowski wrote: > On Tue, Nov 14, 2017 at 10:36:22AM +0200, Klaus Agnoletti wrote: >> I used to have 3x2TB in a btrfs in raid0. A few weeks ago, one of the > ^ >> 2TB disks started giving me I/O

Re: A partially failing disk in raid0 needs replacement

Hi Roman, If you look at the 'show' command, the failing disk is sorta out of the fs, so maybe removing the 6TB disk again will divide the data already on the 6TB disk (which isn't more than 300something gigs) to the 2 well-functioning disks. Still, as putting the dd-image of the 2TB disk on the

Re: A partially failing disk in raid0 needs replacement

On Tue, 14 Nov 2017 15:09:52 +0100 Klaus Agnoletti wrote: > Hi Roman > > I almost understand :-) - however, I need a bit more information: > > How do I copy the image file to the 6TB without screwing the existing > btrfs up when the fs is not mounted? Should I remove it

Re: A partially failing disk in raid0 needs replacement

Am Tue, 14 Nov 2017 17:48:56 +0500 schrieb Roman Mamedov : > [1] Note that "ddrescue" and "dd_rescue" are two different programs > for the same purpose, one may work better than the other. I don't > remember which. :) One is a perl implementation and is the one working worse.

Re: A partially failing disk in raid0 needs replacement

Hi Austin Good points. Thanks a lot. /klaus On Tue, Nov 14, 2017 at 2:14 PM, Austin S. Hemmelgarn wrote: > On 2017-11-14 03:36, Klaus Agnoletti wrote: >> >> Hi list >> >> I used to have 3x2TB in a btrfs in raid0. A few weeks ago, one of the >> 2TB disks started giving me

Re: A partially failing disk in raid0 needs replacement

Hi Roman I almost understand :-) - however, I need a bit more information: How do I copy the image file to the 6TB without screwing the existing btrfs up when the fs is not mounted? Should I remove it from the raid again? Also, as you might have noticed, I have a bit of an issue with the entire

Re: A partially failing disk in raid0 needs replacement

On 2017-11-14 03:36, Klaus Agnoletti wrote: Hi list I used to have 3x2TB in a btrfs in raid0. A few weeks ago, one of the 2TB disks started giving me I/O errors in dmesg like this: [388659.173819] ata5.00: exception Emask 0x0 SAct 0x7fff SErr 0x0 action 0x0 [388659.175589] ata5.00:

Re: A partially failing disk in raid0 needs replacement

On 2017-11-14 07:48, Roman Mamedov wrote: On Tue, 14 Nov 2017 10:36:22 +0200 Klaus Agnoletti wrote: Obviously, I want /dev/sdd emptied and deleted from the raid. * Unmount the RAID0 FS * copy the bad drive using `dd_rescue`[1] into a file on the 6TB drive

Re: A partially failing disk in raid0 needs replacement

On 14 November 2017 at 09:36, Klaus Agnoletti wrote: > > How do you guys think I should go about this? I'd clone the disk with GNU ddrescue. https://www.gnu.org/software/ddrescue/ -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a

Re: A partially failing disk in raid0 needs replacement

On Tue, 14 Nov 2017 10:36:22 +0200 Klaus Agnoletti wrote: > Obviously, I want /dev/sdd emptied and deleted from the raid. * Unmount the RAID0 FS * copy the bad drive using `dd_rescue`[1] into a file on the 6TB drive (noting how much of it is actually unreadable --

Re: A partially failing disk in raid0 needs replacement

On Tue, Nov 14, 2017 at 10:36:22AM +0200, Klaus Agnoletti wrote: > I used to have 3x2TB in a btrfs in raid0. A few weeks ago, one of the ^ > 2TB disks started giving me I/O errors in dmesg like this: > > [388659.188988] Add. Sense: Unrecovered read error -