NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
IcyK
Dec 02, 2012Tutor
Q: change raid0 volume name?
Hi all, I have an Ultra 2 with 2 x Raid0 drives, single volumes, volumes /dev/c and /dev/d. Today, I tried to updrade one of the disks: pulled out the left disk (/dev/c), put in a new one, made a ...
IcyK
Dec 09, 2012Tutor
Well, I almost nailed it.
For future refetence, this is what I did:
with only original disk [d] to copy:
-> only one volume appeared
reboot 2x
shutdown
Insert new disk [d]
create new volume [d] (in frontview)
start
reboot 2x
copy contents from original [d] (now [c]) to new [d]
reboot
shutdown
remove original disk [d] which is now disk [c]
start + reboot
shutdown
insert original disk [c]
start
-> new disk [d] not recognized
Now new volume [d] gets mounted.
Only when I reboot, the mount is lost and I have to do it manually.
So the remaining question is: how to get drive / volume [d] to mount at boot?
For future refetence, this is what I did:
with only original disk [d] to copy:
root ~ # vgs
VG #PV #LV #SN Attr VSize VFree
d 1 1 0 wz--n- 1.81T 5.00G
root ~ # lvs
LV VG Attr LSize Origin Snap% Move Log Copy%
d d -wi-a- 1.81T
-> only one volume appeared
vgchange -a n
vgrename /dev/d /dev/c
lvrename /dev/c/d /dev/c/c
reboot 2x
shutdown
Insert new disk [d]
create new volume [d] (in frontview)
start
reboot 2x
copy contents from original [d] (now [c]) to new [d]
rsync -av --stats /c/recordings/* /d/recordings
reboot
shutdown
remove original disk [d] which is now disk [c]
start + reboot
shutdown
insert original disk [c]
start
-> new disk [d] not recognized
root ~ # mdadm --examine --scan
ARRAY /dev/md/2 metadata=1.2 UUID=060d371f:28bca8e5:bed47ae0:4a196b61 name=E091F58AD37A:2
ARRAY /dev/md/0 metadata=1.2 UUID=2f7dfbb0:adfa39f9:bb6da5bf:c85762bf name=E091F58AD37A:0
ARRAY /dev/md/1 metadata=1.2 UUID=da6a5053:e8870122:3644d00c:1346d084 name=E091F58AD37A:1
ARRAY /dev/md/2 metadata=1.2 UUID=cbed02fd:fb7d7142:ffbc8472:21cde62c name=E091F58AD37A:2
root ~ # mdadm --assemble --scan
mdadm: /dev/md/E091F58AD37A:2 has been started with 1 drive.
mdadm: /dev/md/E091F58AD37A:1_0 has been started with 1 drive (out of 2).
mdadm: /dev/md/E091F58AD37A:0_0 has been started with 1 drive (out of 2).
root ~ # lvm pvscan
PV /dev/md127 VG d lvm2 [1.81 TB / 5.00 GB free]
PV /dev/md2 VG c lvm2 [461.25 GB / 10.00 GB free]
Total: 2 [2.27 TB] / in use: 2 [2.27 TB] / in no VG: 0 [0 ]
root ~ # lvm vgscan
Reading all physical volumes. This may take a while...
Found volume group "d" using metadata type lvm2
Found volume group "c" using metadata type lvm2
root ~ # vgchange -a y
1 logical volume(s) in volume group "d" now active
1 logical volume(s) in volume group "c" now active
root ~ # ls -al /dev/mapper
total 0
drwxr-xr-x 2 root root 100 2012-12-09 11:43 .
drwxr-xr-x 16 root root 3560 2012-12-09 11:43 ..
brw-rw---- 1 root disk 253, 0 2012-12-09 11:32 c-c
crw-rw---- 1 root root 10, 236 2012-12-09 11:32 control
brw-rw---- 1 root disk 253, 1 2012-12-09 11:43 d-d
root / # mount /dev/d/d /d
Now new volume [d] gets mounted.
Only when I reboot, the mount is lost and I have to do it manually.
So the remaining question is: how to get drive / volume [d] to mount at boot?
Related Content
- Dec 25, 2018Retired_Member
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!