Sam Smith wrote:
> But I still need to swap the first drive (sda) and I don't really want
> to have to reboot this time. So what can I do to ensure that once I pull
> the old drive and put in the new one that it comes back up as "sda"? Or
> does that even matter? (seems like it would..)
As Andy S
On 05/18/2017 12:30 PM, Dan Ritter wrote:
It doesn't matter that much. Use this:
mdadm --fail /dev/md0 /dev/sda1
mdadm --remove /dev/md0 /dev/sda1
mdadm --add /dev/md0 /dev/whatever1
then check on progress with cat /proc/mdstat
-dsr-
Ok, I just went ahead and yanked the drive and stuck th
Hi Sam,
It doesn't matter what your devices are called. In fact you are best
advised to avoid use of the /dev/sd* names where possible as these
names may change for reasons other than drives being hotplugged. For
example if your storage controller needs a module to detect drives,
then order of mod
On Thu, May 18, 2017 at 11:49:11AM -0500, Sam Smith wrote:
> Hi,
>
> I recently upgraded my home server to an HP ml30 tower server. It came with
> a 4 drive hotplug SATA cage. I loaded two old unused drives in it and
> installed Debian Stretch on it putting the drives in a software raid1 via
> the
Hi,
I recently upgraded my home server to an HP ml30 tower server. It came
with a 4 drive hotplug SATA cage. I loaded two old unused drives in it
and installed Debian Stretch on it putting the drives in a software
raid1 via the debian installer. My plan was once I got the new box up
and runni
5 matches
Mail list logo
