Skip to contentSkip to conversation

Raid failing, which command to remove the bad drive?

DISCUSSION Timothy D. Lenz 7 participants 18 messages Aug 26, 2011 – Sep 12, 2011 MD RAID

lore
Share & tools
lore
#0 lore raw

I have 4 drives set up as 2 pairs. The first part has 3 partitions on it and it seems 1 of those drives is failing (going to have to figure out which drive it is too so I don't pull the wrong one out of the case)

It's been awhile since I had to replace a drive in the array and my notes are a bit confusing. I'm not sure which I need to use to remove the drive:

	sudo mdadm --manage /dev/md0 --fail /dev/sdb
	sudo mdadm --manage /dev/md0 --remove /dev/sdb
	sudo mdadm --manage /dev/md1 --fail /dev/sdb
	sudo mdadm --manage /dev/md1 --remove /dev/sdb
	sudo mdadm --manage /dev/md2 --fail /dev/sdb
	sudo mdadm --manage /dev/md2 --remove /dev/sdb

or

sudo mdadm /dev/md0 --fail /dev/sdb1 --remove /dev/sdb1 sudo mdadm /dev/md1 --fail /dev/sdb2 --remove /dev/sdb2 sudo mdadm /dev/md2 --fail /dev/sdb3 --remove /dev/sdb3

I'm not sure if I fail the drive partition or whole drive for each.

-------------------------------------
The mails I got are:
-------------------------------------
A Fail event had been detected on md device /dev/md0.

It could be related to component device /dev/sdb1.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]

      4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[1] sda3[0]

      459073344 blocks [2/2] [UU]

md3 : active raid1 sdd1[1] sdc1[0]

      488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]

      24418688 blocks [2/1] [U_]

unused devices: <none>
-------------------------------------
A Fail event had been detected on md device /dev/md1.

It could be related to component device /dev/sdb2.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]

      4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[1] sda3[0]

      459073344 blocks [2/2] [UU]

md3 : active raid1 sdd1[1] sdc1[0]

      488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]

      24418688 blocks [2/1] [U_]

unused devices: <none>
-------------------------------------
A Fail event had been detected on md device /dev/md2.

It could be related to component device /dev/sdb3.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]

      4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[2](F) sda3[0]

      459073344 blocks [2/1] [U_]

md3 : active raid1 sdd1[1] sdc1[0]

      488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]

      24418688 blocks [2/1] [U_]

unused devices: <none>
-------------------------------------

#1 lore raw
Quoted 93 lines · Timothy D. Lenz

I have 4 drives set up as 2 pairs.  The first part has 3 partitions on it and it seems 1 of those drives is failing (going to have to figure out which drive it is too so I don't pull the wrong one out of the case)

It's been awhile since I had to replace a drive in the array and my notes are a bit confusing. I'm not sure which I need to use to remove the drive:

       sudo mdadm --manage /dev/md0 --fail /dev/sdb sudo mdadm --manage /dev/md0 --remove /dev/sdb sudo mdadm --manage /dev/md1 --fail /dev/sdb sudo mdadm --manage /dev/md1 --remove /dev/sdb sudo mdadm --manage /dev/md2 --fail /dev/sdb sudo mdadm --manage /dev/md2 --remove /dev/sdb

or

sudo mdadm /dev/md0 --fail /dev/sdb1 --remove /dev/sdb1 sudo mdadm /dev/md1 --fail /dev/sdb2 --remove /dev/sdb2 sudo mdadm /dev/md2 --fail /dev/sdb3 --remove /dev/sdb3

I'm not sure if I fail the drive partition or whole drive for each.

-------------------------------------
The mails I got are:
-------------------------------------
A Fail event had been detected on md device /dev/md0.

It could be related to component device /dev/sdb1.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]
     4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[1] sda3[0]
     459073344 blocks [2/2] [UU]

md3 : active raid1 sdd1[1] sdc1[0]
     488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]
     24418688 blocks [2/1] [U_]

unused devices: <none>
-------------------------------------
A Fail event had been detected on md device /dev/md1.

It could be related to component device /dev/sdb2.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]
     4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[1] sda3[0]
     459073344 blocks [2/2] [UU]

md3 : active raid1 sdd1[1] sdc1[0]
     488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]
     24418688 blocks [2/1] [U_]

unused devices: <none>
-------------------------------------
A Fail event had been detected on md device /dev/md2.

It could be related to component device /dev/sdb3.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]
     4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[2](F) sda3[0]
     459073344 blocks [2/1] [U_]

md3 : active raid1 sdd1[1] sdc1[0]
     488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]
     24418688 blocks [2/1] [U_]

Quoted 7 lines

unused devices: <none>
-------------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Looks like your sda is failing, that's the smartctl -a /dev/sda output?

/Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#2 lore raw

um, no, that was the email that mdadm sends I thought. And it says problem is sdb in each case. Though I was wondering why each one said [U_] instead of [_U]. Here is the smartctl for sda and below that will be for sdb

======================================================================

vorg@x64VDR:~$ sudo smartctl -a /dev/sda
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-2.6.34.20100610.1] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===

Model Family:     Seagate Barracuda 7200.11
Device Model:     ST3500320AS
Serial Number:    9QM7M86S
LU WWN Device Id: 5 000c50 01059c636
Firmware Version: SD1A
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Fri Aug 26 15:23:41 2011 MST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error. Auto Offline Data Collection:
Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test
has ever
been run.
Total time to complete Offline
data collection: ( 650) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection
on/off support.
Suspend Offline collection upon new command.
Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode. Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 119) minutes.
Conveyance self-test routine

recommended polling time:        (   2) minutes.
SCT capabilities:              (0x103b) SCT Status supported.

SCT Error Recovery Control
supported.
SCT Feature Control supported. SCT Data Table supported.

SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   114   100   006    Pre-fail 

Always - 83309768
3 Spin_Up_Time 0x0003 094 094 000 Pre-fail
Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age
Always - 13
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail
Always - 0
7 Seek_Error_Rate 0x000f 071 060 030 Pre-fail
Always - 13556066
9 Power_On_Hours 0x0032 094 094 000 Old_age
Always - 5406
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail
Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age
Always - 13
184 End-to-End_Error 0x0032 100 100 099 Old_age Always
- 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always
- 0
188 Command_Timeout 0x0032 100 100 000 Old_age Always
- 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always
- 0
190 Airflow_Temperature_Cel 0x0022 067 065 045 Old_age Always
- 33 (Min/Max 30/35)
194 Temperature_Celsius 0x0022 033 040 000 Old_age Always
- 33 (0 21 0 0)
195 Hardware_ECC_Recovered 0x001a 058 033 000 Old_age Always
- 83309768
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always
- 0

198 Offline_Uncorrectable   0x0010   100   100   000    Old_age Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always 

- 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1

 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing

Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay

Quoted 1 line · Mathias Burén

smartctl -a /dev/sda

======================================================================

vorg@x64VDR:~$ sudo smartctl -a /dev/sdb
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-2.6.34.20100610.1] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

Vendor: /1:0:0:0
Product:

User Capacity:        600,332,565,813,390,450 bytes [600 PB]
Logical block size:   774843950 bytes
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
Quoted 1 line
Quoted 1 line

Terminate command early due to bad response to IEC mode page

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. --
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#5 lore raw
In reply to Timothy D. Lenz
Quoted 9 lines · On Fri, 26 Aug 2011 13:13:01 -0700 "Timothy D. Lenz" <[email protected]> wrote:

I have 4 drives set up as 2 pairs. The first part has 3 partitions on it and it seems 1 of those drives is failing (going to have to figure out which drive it is too so I don't pull the wrong one out of the case)

It's been awhile since I had to replace a drive in the array and my notes are a bit confusing. I'm not sure which I need to use to remove the drive:

Quoted 6 lines
	sudo mdadm --manage /dev/md0 --fail /dev/sdb
	sudo mdadm --manage /dev/md0 --remove /dev/sdb
	sudo mdadm --manage /dev/md1 --fail /dev/sdb
	sudo mdadm --manage /dev/md1 --remove /dev/sdb
	sudo mdadm --manage /dev/md2 --fail /dev/sdb
	sudo mdadm --manage /dev/md2 --remove /dev/sdb

sdb is not a member of any of these arrays so all of these commands will fail.

The partitions are members of the arrays.

Quoted 5 lines

or

sudo mdadm /dev/md0 --fail /dev/sdb1 --remove /dev/sdb1 sudo mdadm /dev/md1 --fail /dev/sdb2 --remove /dev/sdb2

sd1 and sdb2 have already been marked as failed so there is little point in marking them as failed again. Removing them makes sense though.

Quoted 1 line

sudo mdadm /dev/md2 --fail /dev/sdb3 --remove /dev/sdb3

sdb3 hasn't been marked as failed yet - maybe it will soon if sdb is a bit marginal.
So if you want to remove sdb from the machine this the correct thing to do. Mark sdb3 as failed, then remove it from the array.

Quoted 2 lines

I'm not sure if I fail the drive partition or whole drive for each.

You only fail things that aren't failed already, and you fail the thing that mdstat or mdadm -D tells you is a member of the array.

NeilBrown

Quoted 77 lines

-------------------------------------
The mails I got are:
-------------------------------------
A Fail event had been detected on md device /dev/md0.

It could be related to component device /dev/sdb1.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]

       4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[1] sda3[0]

       459073344 blocks [2/2] [UU]

md3 : active raid1 sdd1[1] sdc1[0]

       488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]

       24418688 blocks [2/1] [U_]

unused devices: <none>
-------------------------------------
A Fail event had been detected on md device /dev/md1.

It could be related to component device /dev/sdb2.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]

       4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[1] sda3[0]

       459073344 blocks [2/2] [UU]

md3 : active raid1 sdd1[1] sdc1[0]

       488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]

       24418688 blocks [2/1] [U_]

unused devices: <none>
-------------------------------------
A Fail event had been detected on md device /dev/md2.

It could be related to component device /dev/sdb3.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]

       4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[2](F) sda3[0]

       459073344 blocks [2/1] [U_]

md3 : active raid1 sdd1[1] sdc1[0]

       488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]

       24418688 blocks [2/1] [U_]

unused devices: <none>
-------------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#3 lore raw
In reply to Timothy D. Lenz
Quoted 141 lines · Timothy D. Lenz

um, no, that was the email that mdadm sends I thought. And it says problem is sdb in each case. Though I was wondering why each one said [U_] instead of [_U]. Here is the smartctl for sda and below that will be for sdb

======================================================================

vorg@x64VDR:~$ sudo smartctl -a /dev/sda
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-2.6.34.20100610.1] (local
build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.11
Device Model:     ST3500320AS
Serial Number:    9QM7M86S
LU WWN Device Id: 5 000c50 01059c636
Firmware Version: SD1A
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show] ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Fri Aug 26 15:23:41 2011 MST
SMART support is: Available - device has SMART capability. SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection:
Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                       without error or no self-test has ever
                                       been run.
Total time to complete Offline
data collection:                (  650) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support.
                                       Suspend Offline collection upon new command.
                                       Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:            (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:        (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 119) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x103b) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
 1 Raw_Read_Error_Rate     0x000f   114   100   006    Pre-fail Always
-       83309768
 3 Spin_Up_Time            0x0003   094   094   000    Pre-fail Always
-       0
 4 Start_Stop_Count        0x0032   100   100   020    Old_age Always
-       13
 5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail Always
-       0
 7 Seek_Error_Rate         0x000f   071   060   030    Pre-fail Always
-       13556066
 9 Power_On_Hours          0x0032   094   094   000    Old_age Always
-       5406
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail Always
  -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age Always
-       13
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always
  -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always
  -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always
  -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always
  -       0
190 Airflow_Temperature_Cel 0x0022   067   065   045    Old_age   Always
  -       33 (Min/Max 30/35)
194 Temperature_Celsius     0x0022   033   040   000    Old_age   Always
  -       33 (0 21 0 0)
195 Hardware_ECC_Recovered  0x001a   058   033   000    Old_age   Always
  -       83309768
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always
  -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age Offline
 -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always
  -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
   1        0        0  Not_testing
   2        0        0  Not_testing
   3        0        0  Not_testing
   4        0        0  Not_testing
   5        0        0  Not_testing
Selective self-test flags (0x0):
 After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay

Quoted 2 lines · Mathias Burén

smartctl -a /dev/sda

======================================================================

vorg@x64VDR:~$ sudo smartctl -a /dev/sdb
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-2.6.34.20100610.1] (local
build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

Vendor:               /1:0:0:0
Product:
User Capacity:        600,332,565,813,390,450 bytes [600 PB] Logical block size:   774843950 bytes
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46

Quoted 4 lines
Quoted 1 line
Quoted 1 line

Terminate command early due to bad response to IEC mode page

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

Indeed, sorry. 600 PB... where did you get that drive? ;)

/M

#4 lore raw
Quoted 143 lines · Mathias Burén
Quoted 142 lines · Timothy D. Lenz

um, no, that was the email that mdadm sends I thought. And it says problem is sdb in each case. Though I was wondering why each one said [U_] instead of [_U]. Here is the smartctl for sda and below that will be for sdb

======================================================================

vorg@x64VDR:~$ sudo smartctl -a /dev/sda
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-2.6.34.20100610.1] (local
build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===

Model Family:     Seagate Barracuda 7200.11
Device Model:     ST3500320AS
Serial Number:    9QM7M86S
LU WWN Device Id: 5 000c50 01059c636
Firmware Version: SD1A
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Fri Aug 26 15:23:41 2011 MST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error. Auto Offline Data Collection:
Enabled.
Self-test execution status: ( 0) The previous self-test routine
completed
without error or no self-test has
ever
been run.
Total time to complete Offline
data collection: ( 650) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off
support.
Suspend Offline collection upon new command.
Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode. Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 119) minutes.
Conveyance self-test routine

recommended polling time:        (   2) minutes.
SCT capabilities:              (0x103b) SCT Status supported.

SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported.

SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 114 100 006 Pre-fail Always

(quoted diff) +0 -7
-       83309768
  3 Spin_Up_Time            0x0003   094   094   000    Pre-fail Always
-       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age Always
-       13
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail Always
-       0
  7 Seek_Error_Rate         0x000f   071   060   030    Pre-fail Always
-       13556066
  9 Power_On_Hours          0x0032   094   094   000    Old_age Always
-       5406
  10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail Always
   -       0
  12 Power_Cycle_Count       0x0032   100   100   020    Old_age Always
-       13

184 End-to-End_Error 0x0032 100 100 099 Old_age Always
- 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always
- 0
188 Command_Timeout 0x0032 100 100 000 Old_age Always
- 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always
- 0
190 Airflow_Temperature_Cel 0x0022 067 065 045 Old_age Always
- 33 (Min/Max 30/35)
194 Temperature_Celsius 0x0022 033 040 000 Old_age Always
- 33 (0 21 0 0)
195 Hardware_ECC_Recovered 0x001a 058 033 000 Old_age Always
- 83309768
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always
- 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline
- 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always
- 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS

    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing

Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay

Quoted 2 lines · Mathias Burén

smartctl -a /dev/sda

======================================================================

vorg@x64VDR:~$ sudo smartctl -a /dev/sdb
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-2.6.34.20100610.1] (local
build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

Vendor: /1:0:0:0
Product:

User Capacity:        600,332,565,813,390,450 bytes [600 PB]
Logical block size:   774843950 bytes
scsiModePageOffset: response length too short, resp_len=47 offset=50

bd_len=46

Quoted 1 line
Quoted 1 line

Terminate command early due to bad response to IEC mode page

Quoted 8 lines
Quoted 3 lines

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

Indeed, sorry. 600 PB... where did you get that drive? ;)

/M

What about those pre-fail messages on the other drive? are they something to worry about now?

Also, I ran the same thing on the 2 drives for md3 and got the same pre-fail messages for both of those, plus one had this nice little note:

==> WARNING: There are known problems with these drives, AND THIS FIRMWARE VERSION IS AFFECTED,
see the following Seagate web pages:
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207951

4 seagate drives in this computer, this will make 3 failures since I put them in. I think the drives are still in warrenty. last time I replaced one it was good till something like 2012 or 2013. But any new drives will be WD. --
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#6 lore raw
In reply to NeilBrown
Quoted 39 lines · NeilBrown
Quoted 9 lines · On Fri, 26 Aug 2011 13:13:01 -0700 "Timothy D. Lenz"<[email protected]> wrote:

I have 4 drives set up as 2 pairs. The first part has 3 partitions on it and it seems 1 of those drives is failing (going to have to figure out which drive it is too so I don't pull the wrong one out of the case)

It's been awhile since I had to replace a drive in the array and my notes are a bit confusing. I'm not sure which I need to use to remove the drive:

Quoted 6 lines
	sudo mdadm --manage /dev/md0 --fail /dev/sdb
	sudo mdadm --manage /dev/md0 --remove /dev/sdb
	sudo mdadm --manage /dev/md1 --fail /dev/sdb
	sudo mdadm --manage /dev/md1 --remove /dev/sdb
	sudo mdadm --manage /dev/md2 --fail /dev/sdb
	sudo mdadm --manage /dev/md2 --remove /dev/sdb

sdb is not a member of any of these arrays so all of these commands will fail.

The partitions are members of the arrays.

Quoted 5 lines

or

sudo mdadm /dev/md0 --fail /dev/sdb1 --remove /dev/sdb1 sudo mdadm /dev/md1 --fail /dev/sdb2 --remove /dev/sdb2

sd1 and sdb2 have already been marked as failed so there is little point in marking them as failed again. Removing them makes sense though.

Quoted 1 line

sudo mdadm /dev/md2 --fail /dev/sdb3 --remove /dev/sdb3

sdb3 hasn't been marked as failed yet - maybe it will soon if sdb is a bit marginal.
So if you want to remove sdb from the machine this the correct thing to do. Mark sdb3 as failed, then remove it from the array.

Quoted 1 line
Quoted 82 lines
Quoted 1 line

I'm not sure if I fail the drive partition or whole drive for each.

You only fail things that aren't failed already, and you fail the thing that mdstat or mdadm -D tells you is a member of the array.

NeilBrown

Quoted 73 lines

-------------------------------------
The mails I got are:
-------------------------------------
A Fail event had been detected on md device /dev/md0.

It could be related to component device /dev/sdb1.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]

        4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[1] sda3[0]

        459073344 blocks [2/2] [UU]

md3 : active raid1 sdd1[1] sdc1[0]

        488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]

        24418688 blocks [2/1] [U_]

unused devices:<none>
-------------------------------------
A Fail event had been detected on md device /dev/md1.

It could be related to component device /dev/sdb2.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]

        4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[1] sda3[0]

        459073344 blocks [2/2] [UU]

md3 : active raid1 sdd1[1] sdc1[0]

        488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]

        24418688 blocks [2/1] [U_]

unused devices:<none>
-------------------------------------
A Fail event had been detected on md device /dev/md2.

It could be related to component device /dev/sdb3.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]

        4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[2](F) sda3[0]

        459073344 blocks [2/1] [U_]

md3 : active raid1 sdd1[1] sdc1[0]

        488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]

        24418688 blocks [2/1] [U_]

unused devices:<none>
-------------------------------------

Got another problem. Removed the drive and tried to start it back up and now get Grub Error 2. I'm not sure if when I did the mirrors if something when wrong with installing grub on the second drive< or if is has to do with [U_] which points to sda in that report instead of [_U].

I know I pulled the correct drive. I had it labled sdb, it's the second drive in the bios bootup drive check and it's the second connector on the board. And when I put just it in instead of the other, I got the noise again. I think last time a drive failed it was one of these two drives because I remember recopying grub.

I do have another computer setup the same way, that I could put this remaining drive on to get grub fixed, but it's a bit of a pain to get the other computer hooked back up and I will have to dig through my notes about getting grub setup without messing up the array and stuff. I do know that both computers have been updated to grub 2

#7 lore raw
Quoted 143 lines · Timothy D. Lenz
Quoted 44 lines · NeilBrown
Quoted 9 lines · On Fri, 26 Aug 2011 13:13:01 -0700 "Timothy D. Lenz"<[email protected]> wrote:

I have 4 drives set up as 2 pairs.  The first part has 3 partitions on it and it seems 1 of those drives is failing (going to have to figure out which drive it is too so I don't pull the wrong one out of the case)

It's been awhile since I had to replace a drive in the array and my notes are a bit confusing. I'm not sure which I need to use to remove the drive:

Quoted 6 lines

       sudo mdadm --manage /dev/md0 --fail /dev/sdb sudo mdadm --manage /dev/md0 --remove /dev/sdb sudo mdadm --manage /dev/md1 --fail /dev/sdb sudo mdadm --manage /dev/md1 --remove /dev/sdb sudo mdadm --manage /dev/md2 --fail /dev/sdb sudo mdadm --manage /dev/md2 --remove /dev/sdb

sdb is not a member of any of these arrays so all of these commands will fail.

The partitions are members of the arrays.

Quoted 5 lines

or

sudo mdadm /dev/md0 --fail /dev/sdb1 --remove /dev/sdb1 sudo mdadm /dev/md1 --fail /dev/sdb2 --remove /dev/sdb2

sd1 and sdb2 have already been marked as failed so there is little point in
marking them as failed again.  Removing them makes sense though.

Quoted 1 line

sudo mdadm /dev/md2 --fail /dev/sdb3 --remove /dev/sdb3

sdb3 hasn't been marked as failed yet - maybe it will soon if sdb is a bit marginal.
So if you want to remove sdb from the machine this the correct thing to do.
Mark sdb3 as failed, then remove it from the array.

Quoted 1 line
Quoted 83 lines
Quoted 1 line

I'm not sure if I fail the drive partition or whole drive for each.

You only fail things that aren't failed already, and you fail the thing that
mdstat or mdadm -D tells you is a member of the array.

NeilBrown

Quoted 73 lines

-------------------------------------
The mails I got are:
-------------------------------------
A Fail event had been detected on md device /dev/md0.

It could be related to component device /dev/sdb1.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]
       4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[1] sda3[0]
       459073344 blocks [2/2] [UU]

md3 : active raid1 sdd1[1] sdc1[0]
       488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]
       24418688 blocks [2/1] [U_]

unused devices:<none>
-------------------------------------
A Fail event had been detected on md device /dev/md1.

It could be related to component device /dev/sdb2.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]
       4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[1] sda3[0]
       459073344 blocks [2/2] [UU]

md3 : active raid1 sdd1[1] sdc1[0]
       488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]
       24418688 blocks [2/1] [U_]

unused devices:<none>
-------------------------------------
A Fail event had been detected on md device /dev/md2.

It could be related to component device /dev/sdb3.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]
       4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[2](F) sda3[0]
       459073344 blocks [2/1] [U_]

md3 : active raid1 sdd1[1] sdc1[0]
       488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]
       24418688 blocks [2/1] [U_]

unused devices:<none>
-------------------------------------

Got another problem. Removed the drive and tried to start it back up and now get Grub Error 2. I'm not sure if when I did the mirrors if something when wrong with installing grub on the second drive< or if is has to do with [U_] which points to sda in that report instead of [_U].

I know I pulled the correct drive. I had it labled sdb, it's the second drive in the bios bootup drive check and it's the second connector on the board. And when I put just it in instead of the other, I got the noise again.  I think last time a drive failed it was one of these two drives because I remember recopying grub.

Quoted 5 lines

I do have another computer setup the same way, that I could put this remaining drive on to get grub fixed, but it's a bit of a pain to get the other computer hooked back up and I will have to dig through my notes about getting grub setup without messing up the array and stuff. I do know that both computers have been updated to grub 2

How did you install Grub on the second drive? I have seen some instructions on the web that would not allow the system to boot if the first drive failed or was removed.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#8 lore raw
Quoted 151 lines · Simon Matthews
Quoted 143 lines · Timothy D. Lenz
Quoted 44 lines · NeilBrown
Quoted 9 lines · On Fri, 26 Aug 2011 13:13:01 -0700 "Timothy D. Lenz"<[email protected]> wrote:

I have 4 drives set up as 2 pairs. The first part has 3 partitions on it and it seems 1 of those drives is failing (going to have to figure out which drive it is too so I don't pull the wrong one out of the case)

It's been awhile since I had to replace a drive in the array and my notes are a bit confusing. I'm not sure which I need to use to remove the drive:

Quoted 6 lines
        sudo mdadm --manage /dev/md0 --fail /dev/sdb
        sudo mdadm --manage /dev/md0 --remove /dev/sdb
        sudo mdadm --manage /dev/md1 --fail /dev/sdb
        sudo mdadm --manage /dev/md1 --remove /dev/sdb
        sudo mdadm --manage /dev/md2 --fail /dev/sdb
        sudo mdadm --manage /dev/md2 --remove /dev/sdb

sdb is not a member of any of these arrays so all of these commands will fail.

The partitions are members of the arrays.

Quoted 5 lines

or

sudo mdadm /dev/md0 --fail /dev/sdb1 --remove /dev/sdb1 sudo mdadm /dev/md1 --fail /dev/sdb2 --remove /dev/sdb2

sd1 and sdb2 have already been marked as failed so there is little point in
marking them as failed again. Removing them makes sense though.

Quoted 1 line

sudo mdadm /dev/md2 --fail /dev/sdb3 --remove /dev/sdb3

sdb3 hasn't been marked as failed yet - maybe it will soon if sdb is a bit marginal.
So if you want to remove sdb from the machine this the correct thing to do.
Mark sdb3 as failed, then remove it from the array.

Quoted 1 line
Quoted 83 lines
Quoted 1 line

I'm not sure if I fail the drive partition or whole drive for each.

You only fail things that aren't failed already, and you fail the thing that
mdstat or mdadm -D tells you is a member of the array.

NeilBrown

Quoted 73 lines

-------------------------------------
The mails I got are:
-------------------------------------
A Fail event had been detected on md device /dev/md0.

It could be related to component device /dev/sdb1.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]

        4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[1] sda3[0]

        459073344 blocks [2/2] [UU]

md3 : active raid1 sdd1[1] sdc1[0]

        488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]

        24418688 blocks [2/1] [U_]

unused devices:<none>
-------------------------------------
A Fail event had been detected on md device /dev/md1.

It could be related to component device /dev/sdb2.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]

        4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[1] sda3[0]

        459073344 blocks [2/2] [UU]

md3 : active raid1 sdd1[1] sdc1[0]

        488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]

        24418688 blocks [2/1] [U_]

unused devices:<none>
-------------------------------------
A Fail event had been detected on md device /dev/md2.

It could be related to component device /dev/sdb3.

Faithfully yours, etc.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md1 : active raid1 sdb2[2](F) sda2[0]

        4891712 blocks [2/1] [U_]

md2 : active raid1 sdb3[2](F) sda3[0]

        459073344 blocks [2/1] [U_]

md3 : active raid1 sdd1[1] sdc1[0]

        488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[2](F) sda1[0]

        24418688 blocks [2/1] [U_]

unused devices:<none>
-------------------------------------

Got another problem. Removed the drive and tried to start it back up and now get Grub Error 2. I'm not sure if when I did the mirrors if something when wrong with installing grub on the second drive< or if is has to do with [U_] which points to sda in that report instead of [_U].

I know I pulled the correct drive. I had it labled sdb, it's the second drive in the bios bootup drive check and it's the second connector on the board. And when I put just it in instead of the other, I got the noise again. I think last time a drive failed it was one of these two drives because I remember recopying grub.

Quoted 5 lines

I do have another computer setup the same way, that I could put this remaining drive on to get grub fixed, but it's a bit of a pain to get the other computer hooked back up and I will have to dig through my notes about getting grub setup without messing up the array and stuff. I do know that both computers have been updated to grub 2

Quoted 4 lines

How did you install Grub on the second drive? I have seen some instructions on the web that would not allow the system to boot if the first drive failed or was removed.

I think this is how I did it, at least it is what I had in my notes:

grub-install /dev/sda && grub-install /dev/sdb

And this is from my notes also. It was from an IRC chat. Don't know if it was the raid channel or the grub channel:

[14:02] <Jordan_U> Vorg: No. First, what is the output of grub-install --version?
[14:02] <Vorg> (GNU GRUB 1.98~20100115-1)
[14:04] <Jordan_U> Vorg: Ok, then run "grub-install /dev/sda && grub-install /dev/sdb" (where sda and sdb are the members of the array)

#9 lore raw
Quoted 12 lines · Timothy D. Lenz
Quoted 6 lines

How did you install Grub on the second drive? I have seen some instructions on the web that would not allow the system to boot if the first drive failed or was removed.

I think this is how I did it, at least it is what I had in my notes:

grub-install /dev/sda && grub-install /dev/sdb

Quoted 9 lines

And this is from my notes also. It was from an IRC chat. Don't know if it was the raid channel or the grub channel:

[14:02] <Jordan_U> Vorg: No. First, what is the output of grub-install --version?
[14:02] <Vorg>  (GNU GRUB 1.98~20100115-1)
[14:04] <Jordan_U> Vorg: Ok, then run "grub-install /dev/sda && grub-install /dev/sdb" (where sda and sdb are the members of the array)

Which is exactly my point. You installed grub on /dev/sdb such that it would boot off /dev/sdb. But if /dev/sda has failed, on reboot, the hard drive that was /dev/sdb is now /dev/sda, but Grub is still looking for its files on the non-existent /dev/sdb.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#10 lore raw
Quoted 23 lines · Simon Matthews
Quoted 12 lines · Timothy D. Lenz
Quoted 6 lines

How did you install Grub on the second drive? I have seen some instructions on the web that would not allow the system to boot if the first drive failed or was removed.

I think this is how I did it, at least it is what I had in my notes:

grub-install /dev/sda && grub-install /dev/sdb

Quoted 9 lines

And this is from my notes also. It was from an IRC chat. Don't know if it was the raid channel or the grub channel:

[14:02] <Jordan_U> Vorg: No. First, what is the output of grub-install --version?
[14:02] <Vorg>  (GNU GRUB 1.98~20100115-1)
[14:04] <Jordan_U> Vorg: Ok, then run "grub-install /dev/sda && grub-install /dev/sdb" (where sda and sdb are the members of the array)

Quoted 5 lines

Which is exactly my point. You installed grub on /dev/sdb such that it would boot off /dev/sdb. But if /dev/sda has failed, on reboot, the hard drive that was /dev/sdb is now /dev/sda, but Grub is still looking for its files on the non-existent /dev/sdb.

The way I do it is to run grub, then for each drive do:

    device (hd0) /dev/sdX
    root (hd0,0)
    setup (hd0)

That should set up each drive to boot up as the first drive.

Cheers,
Robin

Signature · 4 lines
     ___        
    ( ' }     |       Robin Hill        <[email protected]> |
   / / )      | Little Jim says ....                            |
  // !!       |      "He fallen in de water !!"                 |
#11 lore raw
Quoted 30 lines · Robin Hill
Quoted 23 lines · Simon Matthews
Quoted 12 lines · Timothy D. Lenz
Quoted 6 lines

How did you install Grub on the second drive? I have seen some instructions on the web that would not allow the system to boot if the first drive failed or was removed.

I think this is how I did it, at least it is what I had in my notes:

grub-install /dev/sda && grub-install /dev/sdb

Quoted 9 lines

And this is from my notes also. It was from an IRC chat. Don't know if it was the raid channel or the grub channel:

[14:02] <Jordan_U> Vorg: No. First, what is the output of grub-install --version?
[14:02] <Vorg>  (GNU GRUB 1.98~20100115-1)
[14:04] <Jordan_U> Vorg: Ok, then run "grub-install /dev/sda && grub-install /dev/sdb" (where sda and sdb are the members of the array)

Quoted 5 lines

Which is exactly my point. You installed grub on /dev/sdb such that it would  boot off /dev/sdb. But if /dev/sda has failed, on reboot, the hard drive that was /dev/sdb is now /dev/sda, but Grub is still looking for its files on the non-existent /dev/sdb.

Quoted 7 lines

The way I do it is to run grub, then for each drive do:
   device (hd0) /dev/sdX
   root (hd0,0)
   setup (hd0)

That should set up each drive to boot up as the first drive.

How about (after installing grub on /dev/sda):
dd if=/dev/sda of=/dev/sdb bs=466 count=1

Simon
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#12 lore raw
Quoted 36 lines · Simon Matthews
Quoted 35 lines · Robin Hill
Quoted 23 lines · Simon Matthews
Quoted 12 lines · Timothy D. Lenz
Quoted 6 lines

How did you install Grub on the second drive? I have seen some instructions on the web that would not allow the system to boot if the first drive failed or was removed.

I think this is how I did it, at least it is what I had in my notes:

grub-install /dev/sda && grub-install /dev/sdb

Quoted 9 lines

And this is from my notes also. It was from an IRC chat. Don't know if it was the raid channel or the grub channel:

[14:02] <Jordan_U> Vorg: No. First, what is the output of grub-install --version?
[14:02] <Vorg>  (GNU GRUB 1.98~20100115-1)
[14:04] <Jordan_U> Vorg: Ok, then run "grub-install /dev/sda && grub-install /dev/sdb" (where sda and sdb are the members of the array)

Quoted 5 lines

Which is exactly my point. You installed grub on /dev/sdb such that it would  boot off /dev/sdb. But if /dev/sda has failed, on reboot, the hard drive that was /dev/sdb is now /dev/sda, but Grub is still looking for its files on the non-existent /dev/sdb.

The way I do it is to run grub, then for each drive do:
   device (hd0) /dev/sdX
   root (hd0,0)
   setup (hd0)

Quoted 5 lines
Quoted 2 lines

That should set up each drive to boot up as the first drive.

How about (after installing grub on /dev/sda):
dd if=/dev/sda of=/dev/sdb bs=466 count=1

ooops, that should be bs=446, NOT bs=466

Simon
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#15 lore raw
In reply to Robin Hill
Quoted 31 lines · Robin Hill
Quoted 23 lines · Simon Matthews
Quoted 12 lines · Timothy D. Lenz
Quoted 6 lines

How did you install Grub on the second drive? I have seen some instructions on the web that would not allow the system to boot if the first drive failed or was removed.

I think this is how I did it, at least it is what I had in my notes:

grub-install /dev/sda&& grub-install /dev/sdb

Quoted 9 lines

And this is from my notes also. It was from an IRC chat. Don't know if it was the raid channel or the grub channel:

[14:02]<Jordan_U> Vorg: No. First, what is the output of grub-install --version?
[14:02]<Vorg> (GNU GRUB 1.98~20100115-1)
[14:04]<Jordan_U> Vorg: Ok, then run "grub-install /dev/sda&& grub-install /dev/sdb" (where sda and sdb are the members of the array)

Quoted 5 lines

Which is exactly my point. You installed grub on /dev/sdb such that it would boot off /dev/sdb. But if /dev/sda has failed, on reboot, the hard drive that was /dev/sdb is now /dev/sda, but Grub is still looking for its files on the non-existent /dev/sdb.

The way I do it is to run grub, then for each drive do:

Quoted 8 lines
     device (hd0) /dev/sdX
     root (hd0,0)
     setup (hd0)

That should set up each drive to boot up as the first drive.

Cheers,
Robin

That is how I was trying to do it when I first set it up and was having problems with it not working. The grub people said not to do it that way because of a greater potential for problems.

The way I read the line I think I used, "&&" is used to put two commands on the same line, so it should have done both. But, If I did that from user vorg instead of user root, I would have needed sudo before both grub-install commands. I can't remember now what I did.

The second drive is teh one that died and was removed, but I guess if sda wasn't bootable, it could have been booting off of sdb the whole time.

#16 lore raw
In reply to Robin Hill
Quoted 6 lines · Robin Hill

The way I do it is to run grub, then for each drive do:
   device (hd0) /dev/sdX
   root (hd0,0)
   setup (hd0)

That should set up each drive to boot up as the first drive.

$me does the same way, it works.

Quoted 9 lines

Cheers,
   Robin
--
    ___

   ( ' }     |       Robin Hill        <[email protected]> |
  / / )      | Little Jim says ....                            |
 // !!       |      "He fallen in de water !!"                 |
Signature · 6 lines
Best regards,
[COOLCOLD-RIPN]
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#17 lore raw
In reply to Timothy D. Lenz
Quoted 10 lines · Timothy D. Lenz

On 8/26/2011 3:45 PM, NeilBrown wrote:

Got another problem. Removed the drive and tried to start it back up and now get Grub Error 2. I'm not sure if when I did the mirrors if something when wrong with installing grub on the second drive< or if is has to do with [U_] which points to sda in that report instead of [_U].

I know I pulled the correct drive. I had it labled sdb, it's the second drive in the bios bootup drive check and it's the second connector on the board. And when I put just it in instead of the other, I got the noise again. I think last time a drive failed it was one of these two drives because I remember recopying grub.

I do have another computer setup the same way, that I could put this remaining drive on to get grub fixed, but it's a bit of a pain to get the other computer hooked back up and I will have to dig through my notes about getting grub setup without messing up the array and stuff. I do know that both computers have been updated to grub 2

I like to check the table of device names vs. make/model/serno before going to far. I get the out of blkdevtrk to be sure.

Signature · 4 lines
Bill Davidsen<[email protected]>
  We are not out of the woods yet, but we know the direction and have
taken the first step. The steps are many, but finite in number, and if
we persevere we will reach our destination.  -me, 2010
#13 lore raw
In reply to Simon Matthews
Quoted 42 lines · Simon Matthews
Quoted 39 lines · Simon Matthews
Quoted 37 lines · Robin Hill
Quoted 23 lines · Simon Matthews
Quoted 11 lines · Timothy D. Lenz
Quoted 6 lines

How did you install Grub on the second drive? I have seen some instructions on the web that would not allow the system to boot if the first drive failed or was removed.

I think this is how I did it, at least it is what I had in my notes:

grub-install /dev/sda&& grub-install /dev/sdb

Quoted 10 lines

And this is from my notes also. It was from an IRC chat. Don't know if it was the raid channel or the grub channel:

[14:02]<Jordan_U> Vorg: No. First, what is the output of grub-install --version?
[14:02]<Vorg> (GNU GRUB 1.98~20100115-1)
[14:04]<Jordan_U> Vorg: Ok, then run "grub-install /dev/sda&& grub-install /dev/sdb" (where sda and sdb are the members of the array)

Quoted 6 lines

Which is exactly my point. You installed grub on /dev/sdb such that it would boot off /dev/sdb. But if /dev/sda has failed, on reboot, the hard drive that was /dev/sdb is now /dev/sda, but Grub is still looking for its files on the non-existent /dev/sdb.

The way I do it is to run grub, then for each drive do:

    device (hd0) /dev/sdX
    root (hd0,0)
    setup (hd0)
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines

That should set up each drive to boot up as the first drive.

How about (after installing grub on /dev/sda):
dd if=/dev/sda of=/dev/sdb bs=466 count=1

ooops, that should be bs=446, NOT bs=466

Which is why you use grub commands, because a typo can wipe out your drive. May or may not have in this case, but there's no reason to do stuff like that.

Signature · 4 lines
Bill Davidsen<[email protected]>
  We are not out of the woods yet, but we know the direction and have
taken the first step. The steps are many, but finite in number, and if
we persevere we will reach our destination.  -me, 2010
#14 lore raw
Quoted 41 lines · Bill Davidsen
Quoted 40 lines · Simon Matthews
Quoted 38 lines · Simon Matthews
Quoted 37 lines · Robin Hill
Quoted 23 lines · Simon Matthews
Quoted 14 lines · Timothy D. Lenz
Quoted 5 lines

How did you install Grub on the second drive? I have seen some instructions on the web that would not allow the system to boot if the
first drive failed or was removed.

I think this is how I did it, at least it is what I had in my notes:

grub-install /dev/sda&& grub-install /dev/sdb

And this is from my notes also. It was from an IRC chat. Don't know if it
was the raid channel or the grub channel:

Quoted 7 lines

[14:02]<Jordan_U> Vorg: No. First, what is the output of grub-install --version?
[14:02]<Vorg> (GNU GRUB 1.98~20100115-1)
[14:04]<Jordan_U> Vorg: Ok, then run "grub-install /dev/sda&& grub-install
/dev/sdb" (where sda and sdb are the members of the array)

Quoted 5 lines

Which is exactly my point. You installed grub on /dev/sdb such that it would boot off /dev/sdb. But if /dev/sda has failed, on reboot, the hard drive that was /dev/sdb is now /dev/sda, but Grub is still looking for its files on the non-existent /dev/sdb.

The way I do it is to run grub, then for each drive do:
device (hd0) /dev/sdX
root (hd0,0)
setup (hd0)

That should set up each drive to boot up as the first drive.

Quoted 8 lines
Quoted 3 lines
Quoted 2 lines

How about (after installing grub on /dev/sda):
dd if=/dev/sda of=/dev/sdb bs=466 count=1

ooops, that should be bs=446, NOT bs=466

Which is why you use grub commands, because a typo can wipe out your drive. May or may not have in this case, but there's no reason to do stuff like that.

Found the problem:

[13:06] <Jordan_U> Vorg: That error is from grub legacy.
[13:08] <Jordan_U> Vorg: Grub2 doesn't use error numbers. "grub error 2" is from grub legacy.

I had updated the boot drives to the new Grub. Checked in bios and it was set to boot from SATA 3, then SATA 4 AND THEN SATA 1 :(. The second pair are data drives and where never ment to have grub.