On Thu, 2020-05-21 at 06:15 +0800, Ed Greshko wrote:
> On 2020-05-21 05:16, Patrick O'Callaghan wrote:
> > Just an update on this. After faffing around trying to recover the
> > failing disk, I decided to replace it and start afresh.
> >
> > I formatted 2 1TB drives with ext4 and created a new md
On Wed, 2020-05-20 at 15:50 -0700, Samuel Sieb wrote:
> On 5/20/20 2:16 PM, Patrick O'Callaghan wrote:
> > I formatted 2 1TB drives with ext4 and created a new md volume as
> > RAID1. However they are taking many hours to sync, despite being empty.
> > Is this normal?
>
> This is somewhat unclear.
On Wed, 2020-05-20 at 22:16 +0100, Patrick O'Callaghan wrote:
> Also, I presume I should mount the md device, using an fstab entry like
>
> this:
>
>
>
> /dev/md0 /raid ext4defaults0 0
>
>
>
> but attempts to do that give an error:
>
>
>
> mount: /raid:
On 5/20/20 2:16 PM, Patrick O'Callaghan wrote:
I formatted 2 1TB drives with ext4 and created a new md volume as
RAID1. However they are taking many hours to sync, despite being empty.
Is this normal?
This is somewhat unclear. It sounds like you formatted the drives
before making the raid. I
On 2020-05-21 05:16, Patrick O'Callaghan wrote:
> Just an update on this. After faffing around trying to recover the
> failing disk, I decided to replace it and start afresh.
>
> I formatted 2 1TB drives with ext4 and created a new md volume as
> RAID1. However they are taking many hours to sync, d
On Sat, 2020-05-16 at 11:34 +0100, Patrick O'Callaghan wrote:
> On Fri, 2020-05-15 at 19:57 -0400, Todd Zullinger wrote:
> > George N. White III wrote:
> > > On Fri, 15 May 2020 at 18:41, Patrick O'Callaghan
> > > wrote:
> > >
> > > > On Fri, 2020-05-15 at 22:35 +0100, Patrick O'Callaghan wrote:
On Sat, 2020-05-16 at 17:18 +0100, Barry Scott wrote:
> > On 15 May 2020, at 11:53, Patrick O'Callaghan wrote:
> >
> > However gsmartcontrol reports that one of the HDDs has internal errors.
> > Would it be best to correct these using mdadm (assuming they can be
> > corrected), and if so, how? Or
> On 15 May 2020, at 11:53, Patrick O'Callaghan wrote:
>
> However gsmartcontrol reports that one of the HDDs has internal errors.
> Would it be best to correct these using mdadm (assuming they can be
> corrected), and if so, how? Or should I do an offline copy with the
> docking station's "clo
I intentionally partitioned my 3tb drives into 4x750G, and built 4
separate arrays out of it, and used LVM to make it one big device.
#1: it allowed me to use 2x1.5tb in place of a 3tb for a while (I had
the old 1.5tb ones) prior to me buying more 3tb ones, later on it
allowed me to use those 1.5t
Tim:
>> Though it can be surprising to find out how they've used a drive.
>> Such as a 4TB WD MyCloud that provides that 4TB using two 2TB
>> partitions on the *same* drive, using RAID to make them one 4TB. I
>> dunno why they'd do it that way.
George N. White III:
> If you control the hardware
On Fri, 15 May 2020 at 23:09, Tim via users
wrote:
> On Fri, 2020-05-15 at 10:28 -0700, Samuel Sieb wrote:
> > This is not so surprising when you realize that most NAS boxes run
> > Linux.
>
> Though it can be surprising to find out how they've used a drive. Such
> as a 4TB WD MyCloud that provi
On Fri, 2020-05-15 at 19:57 -0400, Todd Zullinger wrote:
> George N. White III wrote:
> > On Fri, 15 May 2020 at 18:41, Patrick O'Callaghan
> > wrote:
> >
> > > On Fri, 2020-05-15 at 22:35 +0100, Patrick O'Callaghan wrote:
> > > > > echo check > /sys/block/md127/md/sync_action
> > >
> > > That's
On Sat, 2020-05-16 at 08:21 +1000, Cameron Simpson wrote:
> On 15May2020 11:53, Patrick O'Callaghan wrote:
> > I recently had to throw out an old NAS I've been using for over 10
> > years. However I rescued the 2 HDDs and got a dual-slot USB SATA
> > docking station for them. To my astonishment Fe
On Fri, 2020-05-15 at 10:28 -0700, Samuel Sieb wrote:
> This is not so surprising when you realize that most NAS boxes run
> Linux.
Though it can be surprising to find out how they've used a drive. Such
as a 4TB WD MyCloud that provides that 4TB using two 2TB partitions on
the *same* drive, using
George N. White III wrote:
> On Fri, 15 May 2020 at 18:41, Patrick O'Callaghan
> wrote:
>
>> On Fri, 2020-05-15 at 22:35 +0100, Patrick O'Callaghan wrote:
echo check > /sys/block/md127/md/sync_action
>>
>> That's giving "permission denied" even with sudo, and with setenforce
>> set to 'off'.
On 5/15/20 3:21 PM, Cameron Simpson wrote:
On 15May2020 11:53, Patrick O'Callaghan wrote:
Are there any general recommendations for monitoring these beasties? I
don't want to change anything for the time being and will be using the
thing mainly for backup, but I see there is such a thing as mdm
On 15May2020 11:53, Patrick O'Callaghan wrote:
I recently had to throw out an old NAS I've been using for over 10
years. However I rescued the 2 HDDs and got a dual-slot USB SATA
docking station for them. To my astonishment Fedora recognised them
immediately as a RAID1 array (formatted with XFS)
On Fri, 15 May 2020 at 18:41, Patrick O'Callaghan
wrote:
> On Fri, 2020-05-15 at 22:35 +0100, Patrick O'Callaghan wrote:
> > > echo check > /sys/block/md127/md/sync_action
>
> That's giving "permission denied" even with sudo, and with setenforce
> set to 'off'.
>
This can happend if you run :
On Fri, 2020-05-15 at 14:56 -0700, Samuel Sieb wrote:
> On 5/15/20 2:41 PM, Patrick O'Callaghan wrote:
> > On Fri, 2020-05-15 at 22:35 +0100, Patrick O'Callaghan wrote:
> > > > echo check > /sys/block/md127/md/sync_action
> >
> > That's giving "permission denied" even with sudo, and with setenforc
On 5/15/20 2:41 PM, Patrick O'Callaghan wrote:
On Fri, 2020-05-15 at 22:35 +0100, Patrick O'Callaghan wrote:
echo check > /sys/block/md127/md/sync_action
That's giving "permission denied" even with sudo, and with setenforce
set to 'off'.
First, is that the right md number?
But also, you can'
On Fri, 2020-05-15 at 22:35 +0100, Patrick O'Callaghan wrote:
> > echo check > /sys/block/md127/md/sync_action
That's giving "permission denied" even with sudo, and with setenforce
set to 'off'.
poc
___
users mailing list -- users@lists.fedoraproject.or
On Fri, 2020-05-15 at 10:27 -0700, Samuel Sieb wrote:
> On 5/15/20 3:53 AM, Patrick O'Callaghan wrote:
> > However gsmartcontrol reports that one of the HDDs has internal errors.
> > Would it be best to correct these using mdadm (assuming they can be
> > corrected), and if so, how? Or should I do a
On Fri, 2020-05-15 at 10:28 -0700, Samuel Sieb wrote:
> On 5/15/20 3:53 AM, Patrick O'Callaghan wrote:
> > I recently had to throw out an old NAS I've been using for over 10
> > years. However I rescued the 2 HDDs and got a dual-slot USB SATA
> > docking station for them. To my astonishment Fedora
On 5/15/20 3:53 AM, Patrick O'Callaghan wrote:
I recently had to throw out an old NAS I've been using for over 10
years. However I rescued the 2 HDDs and got a dual-slot USB SATA
docking station for them. To my astonishment Fedora recognised them
immediately as a RAID1 array (formatted with XFS)
On 5/15/20 3:53 AM, Patrick O'Callaghan wrote:
However gsmartcontrol reports that one of the HDDs has internal errors.
Would it be best to correct these using mdadm (assuming they can be
corrected), and if so, how? Or should I do an offline copy with the
docking station's "clone" button?
It say
On Fri, 15 May 2020 at 09:59, Patrick O'Callaghan
wrote:
> On Fri, 2020-05-15 at 08:50 -0300, George N. White III wrote:
> > > I recently had to throw out an old NAS I've been using for over 10
> > > years. However I rescued the 2 HDDs and got a dual-slot USB SATA
> > > docking station for them.
On Fri, 2020-05-15 at 08:50 -0300, George N. White III wrote:
> > I recently had to throw out an old NAS I've been using for over 10
> > years. However I rescued the 2 HDDs and got a dual-slot USB SATA
> > docking station for them. To my astonishment Fedora recognised them
> > immediately as a RAID
On Fri, 15 May 2020 at 07:54, Patrick O'Callaghan
wrote:
> I recently had to throw out an old NAS I've been using for over 10
> years. However I rescued the 2 HDDs and got a dual-slot USB SATA
> docking station for them. To my astonishment Fedora recognised them
> immediately as a RAID1 array (fo
On Fri, May 15, 2020 at 12:44:32 +0100,
Patrick O'Callaghan wrote:
One other thing. On connecting the dock, I get this from dmesg:
[259115.502000] sd 7:0:0:0: [sdd] Attached SCSI disk
[259115.505730] sd 7:0:0:1: [sdf] Attached SCSI disk
[259115.820568] md127: Warning: Device sdf1 is misaligne
On Fri, May 15, 2020 at 12:32:03 +0100,
Patrick O'Callaghan wrote:
On Fri, 2020-05-15 at 06:20 -0500, Bruno Wolff III wrote:
That's not a good sign, but sometimes you can still get a lot of use out
of such a drive. If you don't want to spend effort figuring out where
the bad sectors are, you
On Fri, 2020-05-15 at 06:20 -0500, Bruno Wolff III wrote:
> On Fri, May 15, 2020 at 11:53:11 +0100,
> Patrick O'Callaghan wrote:
> > However gsmartcontrol reports that one of the HDDs has internal errors.
> > Would it be best to correct these using mdadm (assuming they can be
> > corrected), and
On Fri, 2020-05-15 at 06:20 -0500, Bruno Wolff III wrote:
> On Fri, May 15, 2020 at 11:53:11 +0100,
> Patrick O'Callaghan wrote:
> > However gsmartcontrol reports that one of the HDDs has internal errors.
> > Would it be best to correct these using mdadm (assuming they can be
> > corrected), and
On Fri, May 15, 2020 at 11:53:11 +0100,
Patrick O'Callaghan wrote:
However gsmartcontrol reports that one of the HDDs has internal errors.
Would it be best to correct these using mdadm (assuming they can be
corrected), and if so, how? Or should I do an offline copy with the
docking station's "
I recently had to throw out an old NAS I've been using for over 10
years. However I rescued the 2 HDDs and got a dual-slot USB SATA
docking station for them. To my astonishment Fedora recognised them
immediately as a RAID1 array (formatted with XFS) without me doing
anything.
However gsmartcontrol
34 matches
Mail list logo
