LÉVAI Dániel @ 2017-06-20T10:22:27 +0200:
> Joel Sing @ 2017-06-19T18:14:30 +0200:
[...]
Hit reply too fast.
> > > You in fact gave the advice at a so lucky time, that I was about to
> > > return the disk for a warranty replacement -- had I done that, I could
> > > not have been able to repair
Joel Sing @ 2017-06-19T18:14:30 +0200:
> On Friday 16 June 2017 10:11:20 LÉVAI Dániel wrote:
> > Karel Gardas @ 2017-06-15T09:07:39 +0200:
> > > On Thu, Jun 15, 2017 at 7:04 AM, LEVAI Daniel wrote:
> > [...]
> >
> > > > Strangest thing is, if I boot with the 'bad' (=failing)
On Friday 16 June 2017 10:11:20 LÉVAI Dániel wrote:
> Karel Gardas @ 2017-06-15T09:07:39 +0200:
> > On Thu, Jun 15, 2017 at 7:04 AM, LEVAI Daniel wrote:
> [...]
>
> > > Strangest thing is, if I boot with the 'bad' (=failing) drive as
> > > part of the array, softraid brings the
Karel Gardas @ 2017-06-15T09:07:39 +0200:
> On Thu, Jun 15, 2017 at 7:04 AM, LEVAI Daniel wrote:
[...]
> > Strangest thing is, if I boot with the 'bad' (=failing) drive as
> > part of the array, softraid brings the volume online (albeit
> > degraded) and I can even decrypt/mount
> Have you had the same problem, in that softraid wouldn't assemble the
> RAID volume with a missing disk? How did you "remove" the failed device
> from the RAID array (ie. you 'add' the new disk with -R during rebuild,
> but how do you 'remove' the failed/offline drive with eg. bioctl)?
No, in
Karel Gardas @ 2017-06-15T09:07:39 +0200:
> On Thu, Jun 15, 2017 at 7:04 AM, LEVAI Daniel wrote:
> > Thanks Karel for pointing this out, you are in fact right, and
> > nothing is wrong with the logging, I just forgot that I'm decrypting
> > that device 'automatically' in
On Thu, Jun 15, 2017 at 7:04 AM, LEVAI Daniel wrote:
> Thanks Karel for pointing this out, you are in fact right, and nothing is
> wrong with the logging, I just forgot that I'm decrypting that device
> 'automatically' in rc.local. And the kernel log was from before this,
From: Karel Gardas -- Sent: 2017.06.14 - 19:25
> On Wed, Jun 14, 2017 at 5:23 PM, LÉVAI Dániel wrote:
>> sd8 at scsibus4 targ 2 lun 0: SCSI2 0/direct fixed
>> sd8: 155872MB, 512 bytes/sector, 319227056 sectors
>
> Here
On Wed, Jun 14, 2017 at 5:23 PM, LÉVAI Dániel wrote:
> sd8 at scsibus4 targ 2 lun 0: SCSI2 0/direct fixed
> sd8: 155872MB, 512 bytes/sector, 319227056 sectors
Here is sd8 as crypto.
> So the system disks (RAID1) are there, sd7l is decrypted as sd8 (so
Hi!
One of the disks of my softraid array of a four disk RAID5 has failed,
so I went on and replaced it with an identical make/model, and now I'm
trying to rebuild the RAID5 array:
So far I've replaced the HDD, fdisk/disklabeled it exactly the same as the
other drives:
# fdisk sd4 <--- one
10 matches
Mail list logo