linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: o1bigtenor <o1bigtenor@gmail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Advice requested
Date: Mon, 2 Nov 2015 23:47:32 -0500	[thread overview]
Message-ID: <56383C64.2070807@turmel.org> (raw)
In-Reply-To: <CAPpdf5-DMFrKRiBXjstJkvqQU1KzqJoL=hfNVqTGjy2HfMcALQ@mail.gmail.com>

On 11/02/2015 11:28 PM, o1bigtenor wrote:
> gdisk
> 
> n 1 2048 1923518592
> 
> Will that change any of the data on the sectors?
> 
> Please - - - is there any way of getting specific commands?

gdisk /dev/md0

{Yes, you put /dev/md0 on the gdisk command line.}

then select 'n' for new partition.  It should offer to create partition
#1.  It should offer 2048 as the starting sector.  It should offer the
last legal sector as the ending sector.  It will probably assign type
8300 by default too.  All good.  Just make sure it *does* get the
starting sector right (2048).

When it gives you its prompt again, select 'p' to print it out so you
can double check.  Then select 'w' to write the new partition table.  It
will warn you, but yes you are sure (as long as the start sector is 2048).

You will end up back at the shell prompt.  You may or may not have seen
a partition device name in the messages.  If not, use "partprobe /dev/md0".

Finally, use "dmesg |tail" to see the last few kernel messages -- the
new device name should show up there.  Or use "blkid" to see all known
partition names.

Whatever name it is, fsck it with the '-n' option.

Then mount it.

Then make backups.

Phil

  reply	other threads:[~2015-11-03  4:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-31 11:55 Advice requested o1bigtenor
2015-11-01 20:55 ` Phil Turmel
     [not found]   ` <CAPpdf5_PUpR7GhBHUaQfWb8Q+7FZenxXgFqbaN3f3r0r6NQNDA@mail.gmail.com>
2015-11-02 15:41     ` Phil Turmel
     [not found]       ` <CAPpdf59MFX1oVwLC-bmQBaQp9K_9-+h0v64OGMnV1-k=eCzO0w@mail.gmail.com>
     [not found]         ` <5637BCE4.8000006@turmel.org>
2015-11-02 23:49           ` o1bigtenor
2015-11-03  0:11             ` Phil Turmel
2015-11-03  0:44               ` o1bigtenor
2015-11-03  0:57                 ` Phil Turmel
2015-11-03  1:02                   ` o1bigtenor
2015-11-03  1:55                     ` Phil Turmel
2015-11-03  4:03                       ` o1bigtenor
2015-11-03  4:09                         ` Phil Turmel
2015-11-03  4:28                           ` o1bigtenor
2015-11-03  4:47                             ` Phil Turmel [this message]
2015-11-03 12:45                               ` o1bigtenor
2015-11-03 13:09                                 ` Phil Turmel
2015-11-03 13:36                                   ` o1bigtenor
2015-11-03 15:49                                     ` Adam Goryachev
2015-11-03 16:08                                     ` Phil Turmel
     [not found]                                       ` <CAPpdf59o0kf1-mgB29AcgH2cpdwBrhazf3NeQUYNa6m9+c6C+A@mail.gmail.com>
2015-11-04  4:05                                         ` o1bigtenor
2015-11-04  4:31                                           ` Brad Campbell
2015-11-03 18:02       ` Phil Turmel
2015-11-03 19:06         ` o1bigtenor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56383C64.2070807@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=o1bigtenor@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).