kernel refuses devices mdadm -E accepts

linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed

* kernel refuses devices mdadm -E accepts
@ 2015-01-19 23:01 Wesley W. Terpstra
  2015-01-19 23:52 ` Roger Heflin
  2015-01-20 18:28 ` Phil Turmel
  0 siblings, 2 replies; 7+ messages in thread
From: Wesley W. Terpstra @ 2015-01-19 23:01 UTC (permalink / raw)
  To: linux-raid

I have a raid5 array for which every disk, when examined with "mdadm
-E /dev/sd[abcd]4" shows a Version: 1.2 superblock with a valid
checksum.

However, when I try:
mdadm -A /dev/md/backing /dev/sd[abcd]4
mdadm says:
mdadm: failed to add /dev/sdc4 to /dev/md/backing: Invalid argument
mdadm: failed to add /dev/sdb4 to /dev/md/backing: Invalid argument
mdadm: failed to add /dev/sda4 to /dev/md/backing: Invalid argument
mdadm: failed to add /dev/sdd4 to /dev/md/backing: Invalid argument
mdadm: /dev/md/backing assembled from 0 drives - need all 4 to start
it (use --run to insist)
The kernel says:
md: sdc4 does not have a valid v1.2 superblock, not importing!
md: md_import_device returned -22
md: sdb4 does not have a valid v1.2 superblock, not importing!
md: md_import_device returned -22
md: sda4 does not have a valid v1.2 superblock, not importing!
md: md_import_device returned -22
md: sdd4 does not have a valid v1.2 superblock, not importing!
md: md_import_device returned -22

I was in the middle of a reshape of this 4-disk raid5 when something
rebooted the computer. The system seems otherwise fine, and I suspect
someone in the house.

What is the correct next step? Should I try --run ? I would obviously
prefer not to lose the data on this array. I expect that the reshape
was NOT complete, so just recreating the array will probably corrupt
its contents.

Kernel version 3.17.8 and mdadm version 3.3.2.

Thanks for any help. If I lose this array, I am going to face a lot of grief...

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: kernel refuses devices mdadm -E accepts
  2015-01-19 23:01 kernel refuses devices mdadm -E accepts Wesley W. Terpstra
@ 2015-01-19 23:52 ` Roger Heflin
  2015-01-20 18:28 ` Phil Turmel
  1 sibling, 0 replies; 7+ messages in thread
From: Roger Heflin @ 2015-01-19 23:52 UTC (permalink / raw)
  To: Wesley W. Terpstra; +Cc: Linux RAID

cat /proc/mdstat

if the device is in use mdadm -E will work but you cannot create a
device because one already has it.

On Mon, Jan 19, 2015 at 5:01 PM, Wesley W. Terpstra <wesley@terpstra.ca> wrote:
> I have a raid5 array for which every disk, when examined with "mdadm
> -E /dev/sd[abcd]4" shows a Version: 1.2 superblock with a valid
> checksum.
>
> However, when I try:
> mdadm -A /dev/md/backing /dev/sd[abcd]4
> mdadm says:
> mdadm: failed to add /dev/sdc4 to /dev/md/backing: Invalid argument
> mdadm: failed to add /dev/sdb4 to /dev/md/backing: Invalid argument
> mdadm: failed to add /dev/sda4 to /dev/md/backing: Invalid argument
> mdadm: failed to add /dev/sdd4 to /dev/md/backing: Invalid argument
> mdadm: /dev/md/backing assembled from 0 drives - need all 4 to start
> it (use --run to insist)
> The kernel says:
> md: sdc4 does not have a valid v1.2 superblock, not importing!
> md: md_import_device returned -22
> md: sdb4 does not have a valid v1.2 superblock, not importing!
> md: md_import_device returned -22
> md: sda4 does not have a valid v1.2 superblock, not importing!
> md: md_import_device returned -22
> md: sdd4 does not have a valid v1.2 superblock, not importing!
> md: md_import_device returned -22
>
> I was in the middle of a reshape of this 4-disk raid5 when something
> rebooted the computer. The system seems otherwise fine, and I suspect
> someone in the house.
>
> What is the correct next step? Should I try --run ? I would obviously
> prefer not to lose the data on this array. I expect that the reshape
> was NOT complete, so just recreating the array will probably corrupt
> its contents.
>
> Kernel version 3.17.8 and mdadm version 3.3.2.
>
> Thanks for any help. If I lose this array, I am going to face a lot of grief...
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: kernel refuses devices mdadm -E accepts
  2015-01-19 23:01 kernel refuses devices mdadm -E accepts Wesley W. Terpstra
  2015-01-19 23:52 ` Roger Heflin
@ 2015-01-20 18:28 ` Phil Turmel
  2015-01-20 18:32   ` Phil Turmel
  2015-01-20 18:32   ` Wesley W. Terpstra
  1 sibling, 2 replies; 7+ messages in thread
From: Phil Turmel @ 2015-01-20 18:28 UTC (permalink / raw)
  To: Wesley W. Terpstra, linux-raid

Hi Wesley,

On 01/19/2015 06:01 PM, Wesley W. Terpstra wrote:

> I was in the middle of a reshape of this 4-disk raid5 when something
> rebooted the computer. The system seems otherwise fine, and I suspect
> someone in the house.
> 
> What is the correct next step? Should I try --run ? I would obviously
> prefer not to lose the data on this array. I expect that the reshape
> was NOT complete, so just recreating the array will probably corrupt
> its contents.
> 
> Kernel version 3.17.8 and mdadm version 3.3.2.

There have been many bug fixes to mdadm since that kernel was retired.
You should temporarily boot a current liveCD (my favorite is
systemrescuecd) and do "mdadm -Afv /dev/mdX /dev/sdX ..."

Show us the output of that if it doesn't work (it should resume your
reshape).

When it is done reshaping/recovering, consider upgrading your kernel.

> Thanks for any help. If I lose this array, I am going to face a lot of grief...

I shouldn't have to say this, but RAID is for availability, not for data
security.  You still need a backup system for any important data.

Phil

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: kernel refuses devices mdadm -E accepts
  2015-01-20 18:28 ` Phil Turmel
@ 2015-01-20 18:32   ` Phil Turmel
  2015-01-20 18:43     ` Wesley W. Terpstra
  2015-01-20 18:32   ` Wesley W. Terpstra
  1 sibling, 1 reply; 7+ messages in thread
From: Phil Turmel @ 2015-01-20 18:32 UTC (permalink / raw)
  To: Wesley W. Terpstra, linux-raid

Woops!

On 01/20/2015 01:28 PM, Phil Turmel wrote:
> Hi Wesley,
> 
> On 01/19/2015 06:01 PM, Wesley W. Terpstra wrote:
> 
>> I was in the middle of a reshape of this 4-disk raid5 when something
>> rebooted the computer. The system seems otherwise fine, and I suspect
>> someone in the house.
>>
>> What is the correct next step? Should I try --run ? I would obviously
>> prefer not to lose the data on this array. I expect that the reshape
>> was NOT complete, so just recreating the array will probably corrupt
>> its contents.
>>
>> Kernel version 3.17.8 and mdadm version 3.3.2.
> 
> There have been many bug fixes to mdadm since that kernel was retired.
> You should temporarily boot a current liveCD (my favorite is
> systemrescuecd) and do "mdadm -Afv /dev/mdX /dev/sdX ..."

I misread that kernel version.  It's relatively current.  Hmmm.

I'd still try a liveCD with 3.18.x or 3.19.

> Show us the output of that if it doesn't work (it should resume your
> reshape).

This still holds. :-)

Phil


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: kernel refuses devices mdadm -E accepts
  2015-01-20 18:32   ` Phil Turmel
@ 2015-01-20 18:43     ` Wesley W. Terpstra
       [not found]       ` <FCB084A5-816F-4954-971E-1C69C707F213@blub.net>
  0 siblings, 1 reply; 7+ messages in thread
From: Wesley W. Terpstra @ 2015-01-20 18:43 UTC (permalink / raw)
  To: Phil Turmel; +Cc: linux-raid

An email race condition. ;-)

On Tue, Jan 20, 2015 at 7:32 PM, Phil Turmel <philip@turmel.org> wrote:
> Woops!
> I'd still try a liveCD with 3.18.x or 3.19.

Right. I am considering ordering one of these new 8TB hard disks so I
can raw copy the raid partitions before I try anything drastic.
Unfortunately even 8TB won't fit 4x3TB of data. :-/ I am fairly
certain my data is still good since all disks have a clean bill of
health and other partitions on them worked with bonnie. So, I figure
my biggest risk right now, is doing something else stupid.

The system remains bootable as the uefi+boot+root filesystems were on
RAID1 x4 arrays and not the data RAID5 array. I'm hesitant to take
action until I find away to store the raw partitions, but installing
3.19 and booting that from my existing root partition sounds harmless
enough.

The system does not have a CD-ROM and has insufficient SATA connectors
to attach one. I could try booting via a USB drive, though.

^ permalink raw reply	[flat|nested] 7+ messages in thread

[parent not found: <FCB084A5-816F-4954-971E-1C69C707F213@blub.net>]

* Re: kernel refuses devices mdadm -E accepts
       [not found]       ` <FCB084A5-816F-4954-971E-1C69C707F213@blub.net>
@ 2015-01-21 12:37         ` Wesley W. Terpstra
  0 siblings, 0 replies; 7+ messages in thread
From: Wesley W. Terpstra @ 2015-01-21 12:37 UTC (permalink / raw)
  To: Valentijn Sessink; +Cc: linux-raid

[-- Attachment #1: Type: text/plain, Size: 956 bytes --]

On Wed, Jan 21, 2015 at 12:28 AM, Valentijn Sessink <valentyn@blub.net> wrote:
> Make a snapshot using dmsetup.

Thanks for the tip. I did not know the blockdev --setro command.

I've attached the output of smartctl -A in smartctl.log, mdadm -E in
mdadm.log, and mdstat in mdstat.log.

The mdstat needs some explanation, perhaps
sd[a-d] are 3TB hard disks
sd[e-f] are SSDs
md121, md122, md125 : swap disks
md123, md124: uefi, boot
md126: PV with LV root
md125: bcache cache disk

what is missing is a raid5 on /dev/sd[a-d]4 which is the bcache backing device

Try: madam -A -o --run --force --freeze-reshape /dev/md120 /dev/sd[a-d]4
It failed the same as before. Logs in mdadm-a.log and dmesg.log

The system was in the middle of a reshape to move the data-offset from
5120 to 8192. No disks were added or removed. All disks are healthy. I
believe the system was rebooted mid-reshape.

Could this be a bug? That madam won't continue a data-offset reshape?

[-- Attachment #2: dmesg.log --]
[-- Type: application/octet-stream, Size: 669 bytes --]

[    5.520447] md: sdc4 does not have a valid v1.2 superblock, not importing!
[    5.520457] md: md_import_device returned -22
[    5.536177] md: sdb4 does not have a valid v1.2 superblock, not importing!
[    5.536203] md: md_import_device returned -22
[    5.536328] md: sda4 does not have a valid v1.2 superblock, not importing!
[    5.536337] md: md_import_device returned -22
[    5.536441] md: sdd4 does not have a valid v1.2 superblock, not importing!
[    5.536449] md: md_import_device returned -22
[    5.544142] md: sdc4 does not have a valid v1.2 superblock, not importing!
[    5.544155] md: md_import_device returned -22
[    5.544176] md: md120 stopped.

[-- Attachment #3: mdadm-a.log --]
[-- Type: application/octet-stream, Size: 308 bytes --]

mdadm: failed to add /dev/sdc4 to /dev/md128: Invalid argument
mdadm: failed to add /dev/sdb4 to /dev/md128: Invalid argument
mdadm: failed to add /dev/sda4 to /dev/md128: Invalid argument
mdadm: failed to add /dev/sdd4 to /dev/md128: Invalid argument
mdadm: failed to RUN_ARRAY /dev/md128: Invalid argument

[-- Attachment #4: mdadm.log --]
[-- Type: application/octet-stream, Size: 3746 bytes --]

/dev/sda4:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 4f83a72f:c52aa18b:59d48798:d706483b
           Name : pumpkin:backing  (local to host pumpkin)
  Creation Time : Sat Nov 30 13:48:44 2013
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 5842897920 (2786.11 GiB 2991.56 GB)
     Array Size : 8764342272 (8358.33 GiB 8974.69 GB)
  Used Dev Size : 5842894848 (2786.11 GiB 2991.56 GB)
    Data Offset : 8192 sectors
   Super Offset : 8 sectors
   Unused Space : before=8104 sectors, after=0 sectors
          State : clean
    Device UUID : 65262ece:4cc1be5b:51627b0b:89b74d71

    Update Time : Mon Jan 19 20:53:07 2015
  Bad Block Log : 512 entries available at offset 72 sectors
       Checksum : 5558443c - correct
         Events : 795592

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 3
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdb4:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 4f83a72f:c52aa18b:59d48798:d706483b
           Name : pumpkin:backing  (local to host pumpkin)
  Creation Time : Sat Nov 30 13:48:44 2013
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 5842897920 (2786.11 GiB 2991.56 GB)
     Array Size : 8764342272 (8358.33 GiB 8974.69 GB)
  Used Dev Size : 5842894848 (2786.11 GiB 2991.56 GB)
    Data Offset : 8192 sectors
   Super Offset : 8 sectors
   Unused Space : before=8104 sectors, after=0 sectors
          State : clean
    Device UUID : 62b10c04:5207bada:02ca566e:3df26814

    Update Time : Mon Jan 19 20:53:07 2015
  Bad Block Log : 512 entries available at offset 72 sectors
       Checksum : 1028b7a3 - correct
         Events : 795592

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 2
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdc4:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 4f83a72f:c52aa18b:59d48798:d706483b
           Name : pumpkin:backing  (local to host pumpkin)
  Creation Time : Sat Nov 30 13:48:44 2013
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 5842897920 (2786.11 GiB 2991.56 GB)
     Array Size : 8764342272 (8358.33 GiB 8974.69 GB)
  Used Dev Size : 5842894848 (2786.11 GiB 2991.56 GB)
    Data Offset : 8192 sectors
   Super Offset : 8 sectors
   Unused Space : before=8112 sectors, after=0 sectors
          State : clean
    Device UUID : 86bfac3b:c4c39510:1b75d729:8c8b8e9f

    Update Time : Mon Jan 19 20:53:07 2015
       Checksum : c442c656 - correct
         Events : 795592

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 1
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdd4:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 4f83a72f:c52aa18b:59d48798:d706483b
           Name : pumpkin:backing  (local to host pumpkin)
  Creation Time : Sat Nov 30 13:48:44 2013
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 5842897920 (2786.11 GiB 2991.56 GB)
     Array Size : 8764342272 (8358.33 GiB 8974.69 GB)
  Used Dev Size : 5842894848 (2786.11 GiB 2991.56 GB)
    Data Offset : 8192 sectors
   Super Offset : 8 sectors
   Unused Space : before=8112 sectors, after=0 sectors
          State : clean
    Device UUID : 68fa16c1:47652504:c49b4591:9399790e

    Update Time : Mon Jan 19 20:53:07 2015
       Checksum : 1395d76b - correct
         Events : 795592

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 0
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)

[-- Attachment #5: mdstat.log --]
[-- Type: application/octet-stream, Size: 686 bytes --]

Personalities : [raid1] 
md121 : active raid1 sdb3[1] sda3[0]
      8388608 blocks super 1.2 [2/2] [UU]
      
md122 : active raid1 sdc3[0] sdd3[1]
      8388608 blocks super 1.2 [2/2] [UU]
      
md123 : active raid1 sdc1[2] sdb1[1] sda1[0] sdd1[3]
      204800 blocks super 1.0 [4/4] [UUUU]
      
md124 : active raid1 sdc2[2] sda2[0] sdb2[1] sdd2[3]
      204800 blocks super 1.2 [4/4] [UUUU]
      
md125 : active raid1 sde3[0] sdf3[1]
      83886080 blocks super 1.2 [2/2] [UU]
      
md126 : active raid1 sde2[0] sdf2[1]
      20975616 blocks super 1.2 [2/2] [UU]
      
md127 : active raid1 sde1[1] sdf1[0]
      8388608 blocks super 1.2 [2/2] [UU]
      
unused devices: <none>

[-- Attachment #6: smartctl.log --]
[-- Type: application/octet-stream, Size: 7661 bytes --]

smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.17.7] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   146   145   021    Pre-fail  Always       -       9658
  4 Start_Stop_Count        0x0032   056   056   000    Old_age   Always       -       44077
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   076   076   000    Old_age   Always       -       17882
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       101
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       51
193 Load_Cycle_Count        0x0032   158   158   000    Old_age   Always       -       127271
194 Temperature_Celsius     0x0022   121   086   000    Old_age   Always       -       31
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.17.7] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   148   145   021    Pre-fail  Always       -       9591
  4 Start_Stop_Count        0x0032   055   055   000    Old_age   Always       -       45623
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   076   076   000    Old_age   Always       -       18209
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       97
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       49
193 Load_Cycle_Count        0x0032   161   161   000    Old_age   Always       -       117768
194 Temperature_Celsius     0x0022   120   088   000    Old_age   Always       -       32
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.17.7] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   176   173   021    Pre-fail  Always       -       6183
  4 Start_Stop_Count        0x0032   095   095   000    Old_age   Always       -       5666
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   082   082   000    Old_age   Always       -       13432
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       65
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       38
193 Load_Cycle_Count        0x0032   001   001   000    Old_age   Always       -       702407
194 Temperature_Celsius     0x0022   121   094   000    Old_age   Always       -       29
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.17.7] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   150   147   021    Pre-fail  Always       -       9491
  4 Start_Stop_Count        0x0032   094   094   000    Old_age   Always       -       6520
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   094   094   000    Old_age   Always       -       4958
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       120
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       63
193 Load_Cycle_Count        0x0032   197   197   000    Old_age   Always       -       9745
194 Temperature_Celsius     0x0022   121   097   000    Old_age   Always       -       31
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: kernel refuses devices mdadm -E accepts
  2015-01-20 18:28 ` Phil Turmel
  2015-01-20 18:32   ` Phil Turmel
@ 2015-01-20 18:32   ` Wesley W. Terpstra
  1 sibling, 0 replies; 7+ messages in thread
From: Wesley W. Terpstra @ 2015-01-20 18:32 UTC (permalink / raw)
  To: Phil Turmel; +Cc: linux-raid

On Tue, Jan 20, 2015 at 7:28 PM, Phil Turmel <philip@turmel.org> wrote:
>> Kernel version 3.17.8 and mdadm version 3.3.2.
> There have been many bug fixes to mdadm since that kernel was retired.

Really? I will give that a shot.

> Show us the output of that if it doesn't work (it should resume your
> reshape).

I will try that.

It was totally stupid reshape, I was changing the "data-offset" to
align it. Really unnecessary, and really slow, so I feel like an idiot
for starting it.

>> Thanks for any help. If I lose this array, I am going to face a lot of grief...
> I shouldn't have to say this, but RAID is for availability, not for data
> security.  You still need a backup system for any important data.

Sure. The really vital (and small) stuff I have backed up elsewhere,
but the sheer volume of raw video my girlfriend records is not
economically feasible to backup beyond raid+btrfs snapshots.

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2015-01-21 12:37 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-01-19 23:01 kernel refuses devices mdadm -E accepts Wesley W. Terpstra
2015-01-19 23:52 ` Roger Heflin
2015-01-20 18:28 ` Phil Turmel
2015-01-20 18:32   ` Phil Turmel
2015-01-20 18:43     ` Wesley W. Terpstra
     [not found]       ` <FCB084A5-816F-4954-971E-1C69C707F213@blub.net>
2015-01-21 12:37         ` Wesley W. Terpstra
2015-01-20 18:32   ` Wesley W. Terpstra

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).