+- Forum (http://forum.xbian.org)
+-- Forum: Software (/forum-6.html)
+--- Forum: Configuration (/forum-17.html)
+--- Thread: Mount LVM? (/thread-1063.html)
Mount LVM? - Segfault - 30th Jun, 2013 02:09 PM
I have two HDD's from my old media server (motherboard shorted) attached from my raspberry pi but I'm having trouble mounting them because I used an LVM. I've tried
Code:
apt-get install lvm2Terminal
Setting up lvm2 (2.02.95-7+rpi1) ...
[....] Setting up LVM Volume Groups... Couldn't find device with uuid 7rHCnY-MQy7-f1QP-A0lv-B3CJ-IvkI-rgIv5I.
Couldn't find device with uuid 7rHCnY-MQy7-f1QP-A0lv-B3CJ-IvkI-rgIv5I.
Refusing activation of partial LV Media. Use --partial to override.
failed.
update-initramfs: deferring update (trigger activated)
insserv: Service mountdevsubfs has to be enabled to start service lvm2
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing lvm2 (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for initramfs-tools ...
update-initramfs: Not updating initramfs.
Errors were encountered while processing:
lvm2
E: Sub-process /usr/bin/dpkg returned an error code (1)
[....] Setting up LVM Volume Groups... Couldn't find device with uuid 7rHCnY-MQy7-f1QP-A0lv-B3CJ-IvkI-rgIv5I.
Couldn't find device with uuid 7rHCnY-MQy7-f1QP-A0lv-B3CJ-IvkI-rgIv5I.
Refusing activation of partial LV Media. Use --partial to override.
failed.
update-initramfs: deferring update (trigger activated)
insserv: Service mountdevsubfs has to be enabled to start service lvm2
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing lvm2 (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for initramfs-tools ...
update-initramfs: Not updating initramfs.
Errors were encountered while processing:
lvm2
E: Sub-process /usr/bin/dpkg returned an error code (1)
Any help with this would be greatly appreciated.
RE: Mount LVM? - mk01 - 1st Jul, 2013 12:04 PM
Terminal
insserv -f /etc/init.d/mountdevsubfs.sh
dpkg --configure lvm2
RE: Mount LVM? - Segfault - 2nd Jul, 2013 01:08 AM
No dice.
Terminal
root@xbian:~# insserv -f /etc/init.d/mountdevsubfs.sh
root@xbian:~# dpkg --configure lvm2
Setting up lvm2 (2.02.95-7+rpi1) ...
[....] Setting up LVM Volume Groups... Couldn't find device with uuid 7rHCnY-MQy7-f1QP-A0lv-B3CJ-IvkI-rgIv5I.
Couldn't find device with uuid 7rHCnY-MQy7-f1QP-A0lv-B3CJ-IvkI-rgIv5I.
Refusing activation of partial LV Media. Use --partial to override.
failed.
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Not updating initramfs.
root@xbian:~# dpkg --configure lvm2
Setting up lvm2 (2.02.95-7+rpi1) ...
[....] Setting up LVM Volume Groups... Couldn't find device with uuid 7rHCnY-MQy7-f1QP-A0lv-B3CJ-IvkI-rgIv5I.
Couldn't find device with uuid 7rHCnY-MQy7-f1QP-A0lv-B3CJ-IvkI-rgIv5I.
Refusing activation of partial LV Media. Use --partial to override.
failed.
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Not updating initramfs.
Any other ideas? At this point I'm considering just wiping the drives using normal volumes.
RE: Mount LVM? - mk01 - 2nd Jul, 2013 02:28 AM
wait wait, you wanted lvm2 installed, you have it installed
and, what you have on screen is, that part of the LVM is there, but not all parts are available
RE: Mount LVM? - Segfault - 2nd Jul, 2013 03:39 AM
Yeah, I just figured it out. For some reason Xbian isn't reading my second hard drive. I have a powered sata port dock with two bays connected via a USB 2.0 cable. It only reads the first bay, not the second. Strange. Both are detected on my other computers.
RE: Mount LVM? - mk01 - 2nd Jul, 2013 03:56 AM
if you change the bays, reads the same disk, or same bay ?
RE: Mount LVM? - Segfault - 2nd Jul, 2013 08:09 AM
It's the bay that it reads. It did work in the older version of Xbian. I'm even having issues with Raspbian on my other flash drive. Perhaps something new in a more recent kernel, or an update?