![]() ![]() ![]() ![]() If you installed SME Server /var/log/messages.If the existing system has lvs already installed and has a volume group called "main" there may be issues.dev/md8 main lvm2 a- 1.88G activate all known volume groups in the vgchange main -a nĠ logical volume(s) in volume group "main" now vgchange main -a yĢ logical volume(s) in volume group "main" now we should be able to mount the mount /dev/main/root good so let’s show where our files cd dirĪoup boot etc lib mnt proc selinux sys varĪer command home lost+found opt root service tmpīin dev initrd media package sbin srv you have successfully assembled your array and able to recover your data. Mdadm -AR /dev/md8 /dev/sdb2 /dev/sdd2 /dev/sde3 If you are running other then raid1, you may need to include additional members from other drives: ![]() Next write a DVD-ROM using the ISO file as an ISO image or install SystemRescue from the ISO image to an USB stick. What we will do now is assemble and run the array: Once you have downloaded the ISO image file, check the checksum. So we have now found which md device we can use and for our example we will use “md8” You need to make sure you are using an md device that isn't already in use, to check what isn’t being used type: You can also use any md device to assemble the array. With it being a raid 1 we only need 1 member to start it. What “mdadm -E /dev/sdb1” command shows it is a part of a raid array, what level, how many members, mdadm -E /dev/sdb2 Let’s try starting the raid and see what we get: Now you have successfully mounted your LVM and you are able to read your data on /mnt/recover, you can save them on a usb disk with the file browser for example. If you have a name of logical volume who is not /dev/main/root, you can type this command for knowing all your logical volume, and adapt this to your configuration. Now you have successfully mounted your LVM and you are able to read your data in a chroot environment, you can save them on a usb disk set to continue the question about how the system is mounted in /mnt/sysimage.set to no the start of network interfaces.start the system with your official SME Server CDROM.I presume that your SME Server is on a RAID over LVM, otherwise you will have to adapt this HOWTO. Method with the official SME Server CDROM If your issue concerns a grub issue, you should look to this wiki page You have several methods below, but all are done on a default Raid over LVM, therefore you might need to adapt to your configuration, if necessary. The purpose of this howto is to give to you the abilities to access to your data if the SME Server 8 is broken and can't start in a normal way. 1.1 Method with the official SME Server CDROM.1 Recovering SME Server with lvm drives.Sed -i -e 's/scandelay=1/scandelay=5/g' /mnt/usbstick/isolinux/syslinux. Mv /mnt/usbstick/isolinux/isolinux.cfg /mnt/usbstick/isolinux/syslinux.cfg Use following commands to copy files to USB.Download latest system rescue CD image and mount it on /mnt/cdrom using ' mount -o loop /mnt/cdrom'.Remove all files: ' rm -rf /mnt/usbstick/*'.Mount USB (Fat32) partition: ' mount -t vfat /dev/sdf1 /mnt/usbstick'.Create folder for USB - ' mkdir /mnt/usbstick'.Automated steps to install from linux using shell script do not work. Steps for installing system rescue CD on USB are mentioned on. Home > System Rescue CD > Installing System Rescue CD on USB disk or drive ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |