From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Murphy Subject: Re: Inactive arrays Date: Mon, 12 Sep 2016 15:37:53 -0600 Message-ID: References: <57A07345.4040708@youngman.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: Sender: linux-raid-owner@vger.kernel.org To: Daniel Sanabria Cc: Wols Lists , Linux-RAID List-Id: linux-raid.ids On Mon, Sep 12, 2016 at 3:13 PM, Daniel Sanabria wrote: > Error: Invalid argument during seek for read on /dev/sdc > Retry/Ignore/Cancel? R > Error: Invalid argument during seek for read on /dev/sdc > Retry/Ignore/Cancel? I > Error: The backup GPT table is corrupt, but the primary appears OK, so > that will be used. > OK/Cancel? O > Model: ATA WDC WD30EZRX-00D (scsi) > Disk /dev/sdc: 3001GB > Sector size (logical/physical): 512B/4096B > Partition Table: unknown > Disk Flags: What version of parted? This looks like a problem due to the error, followed by "primary appears OK" but instead of using that like it says, it reports the Partition Table as unknown. Not expected. > Error: Invalid argument during seek for read on /dev/sde > Retry/Ignore/Cancel? C > Model: ATA WDC WD30EZRX-00D (scsi) > Disk /dev/sde: 3001GB > Sector size (logical/physical): 512B/4096B > Partition Table: unknown > Disk Flags: And the same thing with a second drive? What are the chances? Can you post a complete dmesg somewhere? Are these two drives on the same controller? smartctl -x for each drive? -- Chris Murphy