-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Sun, 26 Oct 2014 08:05:58 -0400 Gary Dale <garyd...@torfree.net> 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) > > > > iF4EAREIAAYFAlRMaDMACgkQGYZUGVwcQVJTNQEAtTFXt5o+TJUA6v7XQiUL1MCQ > > f24zTUpe7Zqrcz6XLi4BAJNEuPRx8QFZZeSHK9f1Qg/zAHhXBVTn3G21ODgEp+XQ > > =eaQS > > -----END PGP SIGNATURE----- > As I undertand your issue: > - you had RAID 1 arrays md0 (sda1+sdb1) and md1 (sda2+sdb2), > - sdb1 & sdb2 showed an error, so you removed them from the arrays > and added sdb3 & sdb4 from the same physical disk, > - you are now wondering what to do with two partitions on device sdb > (sdb1 & sdb2). - -->exactly > I'm guessing that sdb is nearly toast. Run smartctl -H /dev/sdb on > it. If it passes, remove it from the array and repartition it, then > add it back into the array. > > If it fails, remove if from your computer and replace it. Whatever > new drive you get will probably be larger than your current drives, > so partition it so that the sdb1 is larger than the current sd1a and > the rest of the space goes to sdb2. In this way, you can expand md1 > when you eventually have to replace sda (it will happen - disks > eventually fail). > > In general it is a really bad idea to keep a filing disk in your > system. It not only will fail sooner rather than later but will also > slow down your system due to i/o failures. > > I'll try that and update the results. Thanks a lot for both answers -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iF4EAREIAAYFAlRM/jIACgkQGYZUGVwcQVKtXwEAlWMQuEh3OITQpXIjxMe0ldQU XCYQZwsAgG1GUIm2DsYA/2fyJZ8jZsnVu2XFAFmR9SDkQUODn02wTeaSr58cLXmt =CqrV -----END PGP SIGNATURE-----
