On Fri, Jun 18, 2010 at 9:11 AM, Huang, Tao deb...@huangtao.me wrote:
On Fri, Jun 18, 2010 at 6:02 PM, Tom H tomh0...@gmail.com wrote:
[snip]
mdadm assembles an array according to data in the superblock so it
shouldn't matter whether the kernel recognizes sda and sdb as sdb and
sda
On 17/06/2010 14:08, Huang, Tao wrote:
On Thu, Jun 17, 2010 at 4:17 PM, Michal mic...@ionic.co.uk wrote:
This is a better way then disconnecting the drive and checking which
drive was disconnected like I did, but I would still put a very easy to
read label on the drive to say /dev/sdX. It
On Fri, Jun 18, 2010 at 4:27 AM, Michal mic...@ionic.co.uk wrote:
On 17/06/2010 14:08, Huang, Tao wrote:
On Thu, Jun 17, 2010 at 4:17 PM, Michal mic...@ionic.co.uk wrote:
This is a better way then disconnecting the drive and checking which
drive was disconnected like I did, but I would still
But how can this be correct when each raid partion is linked to the
HDD/Partions
# cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4]
md3 : active raid1 sda2[0] sdb2[1]
716796096 blocks [2/2] [UU]
md2 : active raid1 sda5[0] sdb5[1]
51199040 blocks [2/2] [UU]
On Fri, Jun 18, 2010 at 6:02 PM, Tom H tomh0...@gmail.com wrote:
[snip]
mdadm assembles an array according to data in the superblock so it
shouldn't matter whether the kernel recognizes sda and sdb as sdb and
sda respectively should you plug them in differently.
so they's recognized with data
On Thu, Jun 17, 2010 at 09:08:41PM +0800, Huang, Tao wrote:
On Thu, Jun 17, 2010 at 4:17 PM, Michal mic...@ionic.co.uk wrote:
This is a better way then disconnecting the drive and checking which
drive was disconnected like I did, but I would still put a very easy to
read label on the drive
On Wed, June 16, 2010 17:30, Michal wrote:
Sorry I really didnt explain my self propely;
Yes I mean /dev/sde and by lable I mean get a lable machine (or
somehting similar) to put a physical lable on the drive, like a sticker
with text saying /dev/sde
I did this in one machine and simply
On Wed, June 16, 2010 17:30, Michal wrote:
Sorry I really didnt explain my self propely;
Yes I mean /dev/sde and by lable I mean get a lable machine (or
somehting similar) to put a physical lable on the drive, like a sticker
with text saying /dev/sde
I did this in one machine and simply
On 16/06/2010 19:00, Håkon Alstadheim wrote:
Steven skrev:
How to identify which drive has failed in an array?
I have 6 disks, 4 are used in raid (mdadm), the other 2 contain /boot, /
and /home.
/dev/sdc
/dev/sdd
/dev/sde
/dev/sdf
Each have 1 partition.
/dev/md0 (raid 1) consists of
On Thu, June 17, 2010 10:17, Michal wrote:
On 16/06/2010 19:00, Håkon Alstadheim wrote:
Just do ls -l /dev/disk/by-id/. The disks will have factory labels
with serial-numbers to match.
This is a better way then disconnecting the drive and checking which
drive was disconnected like I did,
also sprach Michal mic...@ionic.co.uk [2010.06.17.1017 +0200]:
This is a better way then disconnecting the drive and checking which
drive was disconnected like I did, but I would still put a very easy to
read label on the drive to say /dev/sdX. It would be far easier then
checking a long
On Thu, Jun 17, 2010 at 4:17 PM, Michal mic...@ionic.co.uk wrote:
This is a better way then disconnecting the drive and checking which
drive was disconnected like I did, but I would still put a very easy to
read label on the drive to say /dev/sdX. It would be far easier then
checking a long
Hope some one finds this helpful :-)
--Siju
Rebuilding RAID 1 Array in Linux with a new hard disk after a disk fault.
=
** Actual screen shot from terminal of steps taken during rebuild on
10-June-2010 on Debian Lenny (
also sprach Siju George sgeorge...@gmail.com [2010.06.16.1313 +0200]:
2) Create identical partitions on the new disk using 'fdisk'.
sfdisk -d /dev/sda | sfdisk /dev/sdb
--
.''`. martin f. krafft madd...@d.o Related projects:
: :' : proud Debian developer
On Wed, Jun 16, 2010 at 4:48 PM, martin f krafft madd...@debian.org wrote:
also sprach Siju George sgeorge...@gmail.com [2010.06.16.1313 +0200]:
2) Create identical partitions on the new disk using 'fdisk'.
sfdisk -d /dev/sda | sfdisk /dev/sdb
oh thanks :-)
I did it manually using fdisk
also sprach Siju George sgeorge...@gmail.com [2010.06.16.1322 +0200]:
sfdisk -d /dev/sda | sfdisk /dev/sdb
oh thanks :-)
I did it manually using fdisk
Manually is for Mac users. ;)
--
.''`. martin f. krafft madd...@d.o Related projects:
: :' : proud Debian developer
On Wed, Jun 16, 2010 at 5:06 PM, martin f krafft madd...@debian.org wrote:
also sprach Siju George sgeorge...@gmail.com [2010.06.16.1322 +0200]:
sfdisk -d /dev/sda | sfdisk /dev/sdb
oh thanks :-)
I did it manually using fdisk
Manually is for Mac users. ;)
these days every one has left
also sprach Siju George sgeorge...@gmail.com [2010.06.16.1402 +0200]:
Manually is for Mac users. ;)
these days every one has left windows and are picking on Mac ? :-)
Reinstalling is for Windows users.
--
.''`. martin f. krafft madd...@d.o Related projects:
: :' : proud Debian
On Wed, June 16, 2010 13:13, Siju George wrote:
Hope some one finds this helpful :-)
--Siju
Rebuilding RAID 1 Array in Linux with a new hard disk after a disk fault.
=
Thanks, this might prove useful.
However I do
Thanks, this might prove useful.
However I do have a question... which might be just as important.
How to identify which drive has failed in an array?
I have 6 disks, 4 are used in raid (mdadm), the other 2 contain /boot, /
and /home.
/dev/sdc
/dev/sdd
/dev/sde
/dev/sdf
Each have
On Wed, June 16, 2010 13:13, Siju George wrote:
Hope some one finds this helpful :-)
--Siju
Rebuilding RAID 1 Array in Linux with a new hard disk after a disk fault.
=
Thanks, this might prove useful.
However I do
On Wed, June 16, 2010 15:47, Michal wrote:
One way is to label the disks themselves so you simply do;
cat /proc/mdstat which might say /dev/sd3 is down. Open the case, look
for the disk labled /dev/sde and replace it. If you have LED's like
servers have (probably not) they can be a fiddle
On 16/06/2010 15:50, Steven wrote:
On Wed, June 16, 2010 15:47, Michal wrote:
One way is to label the disks themselves so you simply do;
cat /proc/mdstat which might say /dev/sd3 is down. Open the case, look
for the disk labled /dev/sde and replace it. If you have LED's like
servers have
Use smartctl from the smartmontools package. If mdadm says that /dev/sdc (or
cat /proc/mdstat) is at fault then use smartctl -a /dev/sdc and it will print
out all kinds of info on the drive including its serial number which should be
on a sticker on the case of the drive.
The programs
Steven skrev:
How to identify which drive has failed in an array?
I have 6 disks, 4 are used in raid (mdadm), the other 2 contain /boot, /
and /home.
/dev/sdc
/dev/sdd
/dev/sde
/dev/sdf
Each have 1 partition.
/dev/md0 (raid 1) consists of /dev/sdc1 and /dev/sdd1
/dev/md1 (raid 1) consists of
25 matches
Mail list logo
