rebuild the initramfs, with mkinitrd, so the old drivers are not present at (re)boot time.remove the NVIDIA driver packages, with zypper (OpenSUSE package manager).Unfortunately, the video driver packages did not work, at all. A "set" of NVIDIA video drivers were installed, in an attempt to get "external LCD monitor support" working. In this case, a Lenovo Thinkpad W530s is running OpenSUSE 12.3. cd /mntįor fs in usr var boot do umount /mnt/$fs doneģ Rescue Scenario: broken video 3.1 The Rescue Plan When that is done, reboot the system and remove the Rescue CD / USB drive! exit # "exit" from the chrootįor fs in proc sysfs bind dev/pts dev do umount $fs doneĪnd so, un-mounts are also done for the "real" filesystems. When the Rescue attempt is complete, all the chroot filesystems must be unmounted.īasically, it is necessary to (just) reverse the order of the above mounts, with umount. sudo chroot /mnt # opens a new shell, within the chroot Mount -t devpts -o rw,nosuid,noexec,gid=5,mode=620,ptmxmode=000 devpts dev/ptsįinally, "change root" to the filesystem in the chroot, to begin running Rescue commands. # if a "gnome-terminal cannot get permission" occurs, use this 'devpts' mount Now, mount the Linux "special" filesystems, in the chroot. Mount /dev/sysvg00/root /mnt # mount the root filesystem, first! # list all logical-volumes determine "role" (root, usr. Then mount all other necessary filesystems - usually var and usr, if these are separate filesystems from root. Next, mount the root and boot filesystems (if boot is separate). When this is complete, we "change root" into this mount-directory, and an operate as if this is the current, booted filesystem - including running commands for Rescue purposes.Īctivate any LVM volume-groups and logical volumes, first. The plan is to create a Linux chroot, mounted under /mnt. This is modified, from the Arch Linux rescue-doc above. 2 Prepare for the Rescue 2.1 Mount filesystems to a chroot However, that particular distro may not have all the toolset included with the System Rescue CD. Sudo mount -o loop,exec /path/to/systemrescuecd-x86-x.y.z.iso /tmp/cdromĪ fallback is a Linux distro's Rescue mode. How to copy to a USB drive, for System Rescue CD: mkdir -p /tmp/cdrom A USB thumb drive will boot and operate much faster than a CD, and will also work on Ultrabooks (desktop) and servers, without a DVD drive. System Rescue CD can be burned to CD media, or easily copied via dd to USB thumb drive. Usually, the Linux system Rescue process is not Linux distro-specific, except perhaps in the usage of a particular distro's Rescue boot, from a Live-CD, for example. It's a good idea to read several Blogs or Linux articles that have solved various Rescue issues. However, it tends to focus on a particular Rescue task, such as recovering a lost root password. Linux Recovery and Rescue documentation is available, as seen above. Go to the homepage at – – for lots of really useful ideas on how to fix things for both Linux and Windows.Īny version after 6.1 you also need to stop the firewall stopping access to SSHD.1 Getting Started 1.1 Review the documentation Simply connect to the machine running SystemRescue with ssh -X As I say it only works on Xwindows but if you have a Linux desktop you can use SSH to run programs from one machine to another so this works too. This allows you easily to modify partitions including allocating more space to partitions as long as they are Ext3 or Ext4. One very useful tool that only runs on the supplied Xwindows desktop is gparted. For windows networks the CD can run a Samba share (just look at the /etc/smb.conf for more information.īeing a Linux based CD you can run chroot on a mounted disk to sometimes run a service from the broken install if it too is Linux based. Often it is a case of mounting the disk, and using rsync to copy everything off. From there you have full access to command line tools to try and fix or recover files from the machine. Boot from the CD, choose a keymap (or take the default), set the root password withĪnd finally find the IP address you have been given withĬonnect to it as root. Importantly it works well on VM’s that you can boot from CD It works happily on workstations and laptops even if they do not run Linux. I have used this disk to work on servers thousands of miles away. Imagine it is in a different office even a different country! You can SSH in and try and fix it. Imagine you need to fix a machine that is in a difficult place to work. Why? As well as lots handy tools the key feature I have used countless times is that it easily runs a SSH server. The one I have used for the last 12 years is System Rescue CD. There are lots of good rescue CD’s out there.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |