And when you click on the Double dots you dont see your other LV000x? What happens if you go to the one that you do see and keep digging into it do you see it? If not you may have had a hardware issue and if so it might be a good idea to send in the logs to support.
i can go in test (the directory i created). I can go back to the root of LV0000 but not upper.
and considering that this unit, is the second i created, then shouldnt it b LV0001 ?
the RAID controller is new, there is 3 new disks... what else could it be ? which logfile could be the good one ?
there is an option in the CLI that i didnt try "restore LVM VG (volume group) configuration"
do you think it might help ?
If you dont see your other logical volumes from the raid, I would say your raid repair was unsuccessful.
Does the other volume group show up in the webGUI, and do you see logical volumes created from it?
Ok, so i kept digging.
it seems that my new VG (vg01) didnt have a LV created, so i could create one.
now i have the LV0100 attached to vg01 (my new disk alone)
and LV0000 my old LV attached to vg00(my old RAID6 disks, + the 2 news)
on this LV0000 i created a "test" share, but i dont see any of my old shares.
if in the CLI, i set the vg00 as default, each time i boot, i get the message "ERROR: No system volume found! System services can't work without system volume !"
in the WEBinterface, when i want to access my share :i have aswell : "Warning No system volume found."
there is an option in the CLI that i didnt try "restore LVM VG (volume group) configuration"
do you think it might help ?
This maybe more complicated from the RAID array, you may need to contact the RAID vendor and provide them logs and explain the sequence of what happened.
Member
Posting Permissions
Reply With Quote