Would really appreciate some help with unpicking what might have happened here. I have a 4 drive (12TB) array that all of a sudden went read-only & has now "crashed" so that it isn't mouting any file system.
Device was running DSM 6 when the volume was created and migrated to DSM 7 successfully a few months ago.
While I have backups of the critical bits I'd like to work through what might be possible to bring it back to at least a read-only state to take more complete backups.
Given that there hasn't been a drive failure (all seem happy in SMART - but know that isn't perfect) or a PSU/power failure issue to spark corruption I'm hoping I might be able to kick things a bit back into life.
I've opened a ticket to Synology but as I have a background in computer stuff wanted to try and understand what might have happened. I'm also being cautious after a Qnap failure years ago where I made things worse!
Any pointers for picking through what might be wrong much appreciated.
VGDisplay:
:/$ sudo vgdisplay --verbose
Using volume group(s) on command line.
--- Volume group ---
VG Name vg1
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 8
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 1
Max PV 0
Cur PV 1
Act PV 1
VG Size 32.73 TiB
PE Size 4.00 MiB
Total PE 8579626
Alloc PE / Size 8579587 / 32.73 TiB
Free PE / Size 39 / 156.00 MiB
VG UUID ox16tw-smba-XftF-ckPN-7aO6-tPaz-OFKU35
--- Logical volume ---
LV Path /dev/vg1/syno_vg_reserved_area
LV Name syno_vg_reserved_area
VG Name vg1
LV UUID 15s7wM-Mp1w-o2qw-UV95-qp3u-8NKX-MZlNK2
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 0
LV Size 12.00 MiB
Current LE 3
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 768
Block device 252:0
--- Logical volume ---
LV Path /dev/vg1/volume_1
LV Name volume_1
VG Name vg1
LV UUID FpSGKA-76kU-3RsJ-rfwx-pona-3ydg-I4pII1
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 1
LV Size 32.73 TiB
Current LE 8579584
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 768
Block device 252:1
--- Physical volumes ---
PV Name /dev/md2
PV UUID d55Kcs-wujY-TVXZ-Fcyz-8jqd-J2ts-Id5iFv
PV Status allocatable
Total PE / Free PE 8579626 / 39
LVDisplay:
:/$ sudo lvdisplay --verbose
Using logical volume(s) on command line.
--- Logical volume ---
LV Path /dev/vg1/syno_vg_reserved_area
LV Name syno_vg_reserved_area
VG Name vg1
LV UUID 15s7wM-Mp1w-o2qw-UV95-qp3u-8NKX-MZlNK2
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 0
LV Size 12.00 MiB
Current LE 3
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 768
Block device 252:0
--- Logical volume ---
LV Path /dev/vg1/volume_1
LV Name volume_1
VG Name vg1
LV UUID FpSGKA-76kU-3RsJ-rfwx-pona-3ydg-I4pII1
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 1
LV Size 32.73 TiB
Current LE 8579584
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 768
Block device 252:1
Question
Bibbleq
Would really appreciate some help with unpicking what might have happened here. I have a 4 drive (12TB) array that all of a sudden went read-only & has now "crashed" so that it isn't mouting any file system.
Device was running DSM 6 when the volume was created and migrated to DSM 7 successfully a few months ago.
While I have backups of the critical bits I'd like to work through what might be possible to bring it back to at least a read-only state to take more complete backups.
Given that there hasn't been a drive failure (all seem happy in SMART - but know that isn't perfect) or a PSU/power failure issue to spark corruption I'm hoping I might be able to kick things a bit back into life.
I've opened a ticket to Synology but as I have a background in computer stuff wanted to try and understand what might have happened. I'm also being cautious after a Qnap failure years ago where I made things worse!
Any pointers for picking through what might be wrong much appreciated.
VGDisplay:
:/$ sudo vgdisplay --verbose Using volume group(s) on command line. --- Volume group --- VG Name vg1 System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 8 VG Access read/write VG Status resizable MAX LV 0 Cur LV 2 Open LV 1 Max PV 0 Cur PV 1 Act PV 1 VG Size 32.73 TiB PE Size 4.00 MiB Total PE 8579626 Alloc PE / Size 8579587 / 32.73 TiB Free PE / Size 39 / 156.00 MiB VG UUID ox16tw-smba-XftF-ckPN-7aO6-tPaz-OFKU35 --- Logical volume --- LV Path /dev/vg1/syno_vg_reserved_area LV Name syno_vg_reserved_area VG Name vg1 LV UUID 15s7wM-Mp1w-o2qw-UV95-qp3u-8NKX-MZlNK2 LV Write Access read/write LV Creation host, time , LV Status available # open 0 LV Size 12.00 MiB Current LE 3 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 768 Block device 252:0 --- Logical volume --- LV Path /dev/vg1/volume_1 LV Name volume_1 VG Name vg1 LV UUID FpSGKA-76kU-3RsJ-rfwx-pona-3ydg-I4pII1 LV Write Access read/write LV Creation host, time , LV Status available # open 1 LV Size 32.73 TiB Current LE 8579584 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 768 Block device 252:1 --- Physical volumes --- PV Name /dev/md2 PV UUID d55Kcs-wujY-TVXZ-Fcyz-8jqd-J2ts-Id5iFv PV Status allocatable Total PE / Free PE 8579626 / 39
LVDisplay:
:/$ sudo lvdisplay --verbose Using logical volume(s) on command line. --- Logical volume --- LV Path /dev/vg1/syno_vg_reserved_area LV Name syno_vg_reserved_area VG Name vg1 LV UUID 15s7wM-Mp1w-o2qw-UV95-qp3u-8NKX-MZlNK2 LV Write Access read/write LV Creation host, time , LV Status available # open 0 LV Size 12.00 MiB Current LE 3 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 768 Block device 252:0 --- Logical volume --- LV Path /dev/vg1/volume_1 LV Name volume_1 VG Name vg1 LV UUID FpSGKA-76kU-3RsJ-rfwx-pona-3ydg-I4pII1 LV Write Access read/write LV Creation host, time , LV Status available # open 1 LV Size 32.73 TiB Current LE 8579584 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 768 Block device 252:1
Link to comment
Share on other sites
21 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.