Koozali.org: home of the SME Server

RAID1 BAD How to know wich disk !

Offline Snoopyski

  • *
  • 141
  • +0/-0
    • http://www.serviceinfosg.com
RAID1 BAD How to know wich disk !
« on: January 27, 2007, 02:46:54 PM »
Hello Everyone,

I got those message:

Quote

This is an automatically generated mail message from mdadm
running on serveur

A Fail event had been detected on md device /dev/md2.

Faithfully yours, etc.
---
This is an automatically generated mail message from mdadm running on serveur.actionvoyages.com.

A Fail event has been detected on md device /dev/md1.
---
This is an automatically generated mail message from mdadm running on serveur.actionvoyages.com.

A Fail event has been detected on md device /dev/md2.
---
This is an automatically generated mail message from mdadm
running on serveur

A Fail event had been detected on md device /dev/md1.

Faithfully yours, etc.
---
Jan 22 01:12:35 serveur kernel: raid1: Disk failure on sda1, disabling device.
Jan 22 01:12:35 serveur kernel:    Operation continuing on 1 devices
Jan 27 08:20:15 serveur console: unused devices: <none>
Jan 27 08:20:15 serveur console: devices: $VAR1 = '/dev/md2';

Quote

Jan 27 08:20:15 serveur console: État actuel du RAID :
Jan 27 08:20:15 serveur console:
Jan 27 08:20:15 serveur console: Personalities : [raid1]
Jan 27 08:20:15 serveur console: md2 : active raid1 sdb2[1] sda2[2](F)
Jan 27 08:20:15 serveur console:       245007232 blocks [2/1] [_U]
Jan 27 08:20:15 serveur console:      
Jan 27 08:20:15 serveur console: md1 : active raid1 sdb1[1] sda1[2](F)
Jan 27 08:20:15 serveur console:       104320 blocks [2/1] [_U]
Jan 27 08:20:15 serveur console:      
Jan 27 08:20:15 serveur console: unused devices: <none>
Jan 27 08:20:15 serveur console:
Jan 27 08:20:15 serveur console:
Jan 27 08:20:15 serveur console: devices: $VAR1 = '/dev/md2';
Jan 27 08:20:15 serveur console: $VAR2 = {
Jan 27 08:20:15 serveur console:           'PreferredMinor' => '2',
Jan 27 08:20:15 serveur console:           'RaidLevel' => 'raid1',
Jan 27 08:20:15 serveur console:           '2' => '       2       8        2       -1      faulty   /dev/sda2
Jan 27 08:20:15 serveur console: ',
Jan 27 08:20:15 serveur console:           'State' => 'clean, degraded',
Jan 27 08:20:15 serveur console:           'DeviceSize' => '245007232 (233.66 GiB 250.89 GB)',
Jan 27 08:20:15 serveur console:           '1' => '       1       8       18        1      active sync   /dev/sdb2
Jan 27 08:20:15 serveur console: ',
Jan 27 08:20:15 serveur console:           'SpareDevices' => '0',
Jan 27 08:20:15 serveur console:           'RaidDevices' => '2',
Jan 27 08:20:15 serveur console:           'FailedDevices' => '1',
Jan 27 08:20:15 serveur console:           'UpdateTime' => 'Sat Jan 27 08:20:12 2007',
Jan 27 08:20:15 serveur console:           'ArraySize' => '245007232 (233.66 GiB 250.89 GB)',
Jan 27 08:20:15 serveur console:           'UUID' => '3678cb68:3edbb859:47ddbf20:2095dc2a',
Jan 27 08:20:15 serveur console:           'CreationTime' => 'Wed May 17 05:19:39 2006',
Jan 27 08:20:15 serveur console:           'WorkingDevices' => '1',
Jan 27 08:20:15 serveur console:           'Persistence' => 'Superblock is persistent',
Jan 27 08:20:15 serveur console:           'UsedDisks' => [
Jan 27 08:20:15 serveur console:                            'sdb',
Jan 27 08:20:15 serveur console:                            'sda'
Jan 27 08:20:15 serveur console:                          ],
Jan 27 08:20:15 serveur console:           'Version' => '00.90.01',
Jan 27 08:20:15 serveur console:           'Events' => '0.10008631',
Jan 27 08:20:15 serveur console:           'TotalDevices' => '2',
Jan 27 08:20:15 serveur console:           'ActiveDevices' => '1'
Jan 27 08:20:15 serveur console:         };
Jan 27 08:20:15 serveur console: $VAR3 = '/dev/md1';
Jan 27 08:20:15 serveur console: $VAR4 = {
Jan 27 08:20:15 serveur console:           'PreferredMinor' => '1',
Jan 27 08:20:15 serveur console:           'RaidLevel' => 'raid1',
Jan 27 08:20:15 serveur console:           '2' => '       2       8        1       -1      faulty   /dev/sda1
Jan 27 08:20:15 serveur console: ',
Jan 27 08:20:15 serveur console:           'State' => 'clean, degraded',
Jan 27 08:20:15 serveur console:           'DeviceSize' => '104320 (101.88 MiB 106.82 MB)',
Jan 27 08:20:15 serveur console:           '1' => '       1       8       17        1      active sync   /dev/sdb1
Jan 27 08:20:15 serveur console: ',
Jan 27 08:20:15 serveur console:           'SpareDevices' => '0',
Jan 27 08:20:15 serveur console:           'RaidDevices' => '2',
Jan 27 08:20:15 serveur console:           'FailedDevices' => '1',
Jan 27 08:20:15 serveur console:           'UpdateTime' => 'Mon Jan 22 01:13:13 2007',
Jan 27 08:20:15 serveur console:           'ArraySize' => '104320 (101.88 MiB 106.82 MB)',
Jan 27 08:20:15 serveur console:           'UUID' => '4ce16395:44ee2eb2:b963f2ba:48714857',
Jan 27 08:20:15 serveur console:           'CreationTime' => 'Wed May 17 05:21:25 2006',
Jan 27 08:20:15 serveur console:           'WorkingDevices' => '1',
Jan 27 08:20:15 serveur console:           'Persistence' => 'Superblock is persistent',
Jan 27 08:20:15 serveur console:           'UsedDisks' => [
Jan 27 08:20:15 serveur console:                            'sdb',
Jan 27 08:20:15 serveur console:                            'sda'
Jan 27 08:20:15 serveur console:                          ],
Jan 27 08:20:15 serveur console:           'Version' => '00.90.01',
Jan 27 08:20:15 serveur console:           'Events' => '0.442',
Jan 27 08:20:15 serveur console:           'TotalDevices' => '2',
Jan 27 08:20:15 serveur console:           'ActiveDevices' => '1'
Jan 27 08:20:15 serveur console:         };
Jan 27 08:20:15 serveur console:
Jan 27 08:20:15 serveur console: used_disks: $VAR1 = 'sda';
Jan 27 08:20:15 serveur console: $VAR2 = 2;
Jan 27 08:20:15 serveur console: $VAR3 = 'sdb';
Jan 27 08:20:15 serveur console: $VAR4 = 2;
Jan 27 08:20:15 serveur console:
Jan 27 08:20:15 serveur console: unclean: /dev/md2 => clean, degraded /dev/md1 => clean, degraded
Jan 27 08:20:15 serveur console: recovering:
Jan 27 08:20:15 serveur console: free_disks:
Jan 27 08:20:37 serveur last message repeated 13 times
Jan 27 08:21:06 serveur su(pam_unix)[22150]: session closed for user admin
Jan 27 08:21:42 serveur last message repeated


Who to to change the good one (SATA disk) (Master, Slave) ???

Thanks,

Snoopyski

Offline Gaston94

  • *****
  • 184
  • +0/-0
RAID1 BAD How to know wich disk !
« Reply #1 on: January 27, 2007, 03:22:30 PM »
Hi,
your faulty drive is sda
Quote
Jan 27 08:20:15 serveur console: '2' => ' 2 8 2 -1 faulty /dev/sda2
Jan 27 08:20:15 serveur console: '2' => ' 2 8 1 -1 faulty /dev/sda1



G.

Offline Snoopyski

  • *
  • 141
  • +0/-0
    • http://www.serviceinfosg.com
RAID1 BAD How to know wich disk !
« Reply #2 on: January 27, 2007, 03:50:09 PM »
OK thanks,

So it's the "master" Primary port drive...

Thanks,

Snoopyski

Offline Snoopyski

  • *
  • 141
  • +0/-0
    • http://www.serviceinfosg.com
RAID1 BAD How to know wich disk !
« Reply #3 on: January 27, 2007, 03:54:16 PM »
Hello again,

So do I need to put my secondary drive on master port now... And put my new drive on the secondary port ?

OR JUST CHANGE THE MASTER DRIVE ?

Thanks,

Snoopyski

Offline Gaston94

  • *****
  • 184
  • +0/-0
RAID1 BAD How to know wich disk !
« Reply #4 on: January 28, 2007, 02:47:54 PM »
Hi
You should only have to replace your master drive
Recreate the disk layout, and join it back to the RAID array. Do not forget the grub part of the operation.
Usage of http://forums.contribs.org/search.php , key word sfdisk and Gaston94 should help you too ;)

G

Offline bpivk

  • *
  • 908
  • +0/-0
    • http://www.bezigrad.com
RAID1 BAD How to know wich disk !
« Reply #5 on: January 28, 2007, 03:26:40 PM »
I just inserted the new disk when i had problems like this and computer set the partition and everything else.
"It should just work" if it doesn't report it. Thanks!

Offline pfloor

  • *****
  • 889
  • +1/-0
RAID1 BAD How to know wich disk !
« Reply #6 on: January 28, 2007, 04:51:58 PM »
It should work automagically.

-Shut down the machine
-Replace the drive
-Boot up
-Log on as admin to get to the admin console
-Go to #5 Manage disk redundency

It should tell you there if the drives are syncing up. Don't turn off the server until the sync is complete or it will start from the beginning again. When it is done syncing it will show a good working raid1.
In life, you must either "Push, Pull or Get out of the way!"