mett writes:
> Hi,
>
> I'm running Squeeze under raid 1 with mdadm.
> One of the raid failed and I replace it with space I had available on
> that same disk.
>
> Today, when rebooting I got an error cause the boot flag was still on
> both partitions(sdb1 and sdb3 below). I used the rescue part o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 26 Oct 2014 08:05:58 -0400
Gary Dale wrote:
> On 25/10/14 11:19 PM, mett wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Hi,
(snip)
> > -BEGIN PGP SIGNATURE-
> > Version: GnuPG v1.4.10 (GNU/Linux)
> >
> > iF4E
On 25/10/14 11:19 PM, mett wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I'm running Squeeze under raid 1 with mdadm.
One of the raid failed and I replace it with space I had available on
that same disk.
Today, when rebooting I got an error cause the boot flag was still on
both pa
On 10/25/2014 08:19 PM, mett wrote:
I'm running Squeeze under raid 1 with mdadm.
One of the raid failed and I replace it with space I had available on
that same disk.
I suggest that your read the SMART data, download the manufacturer's
diagnostics utility disk, and run the manufacturer's full
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I'm running Squeeze under raid 1 with mdadm.
One of the raid failed and I replace it with space I had available on
that same disk.
Today, when rebooting I got an error cause the boot flag was still on
both partitions(sdb1 and sdb3 below). I us
5 matches
Mail list logo