similar to: rescue boot - udev question

What does it take to make a disk bootable on a system with UEFI and a GPT on the boot disk? I used a default disk layout in the initial install on a 600Gb drive (on a box that also contained a larger raid). and it used a GPT. ReaR won't work to back up/restore this system, complaining about the UEFI. I cloned the drive to a different server with clonezilla-live which completed without

If I boot a 5.7 install disk with 'linux rescue selinux=0', let it start the network and detect the installed system, ssh seems to work, but rsync fails with "rsync: connection unexpectedly closed (0 bytes received so far) [receiver]). Shouldn't it work as long as the underlying ssh connection works? It doesn't prompt for the ssh password and using -essh doesn't change

On earlier versions of Centos, I could boot the install CD in rescue mode, let it find and mount the installed system on the HD even when it was just one disk of RAID1 partitions (type=FD). When booting from the centos5 disk the attempt find the system gives a box that says 'You don't have any Linux partitions'. At the bottom of the screen there is something that says:

I boot from the installation DVD, with an already existing CentOS 5.5 system on my hard disks. I have separate boot, root, and home partitions. I have moved the boot partition and now I need to re-initialize grub from rescue mode. Attempting to use 'rescue mode" to automatically mount my system under /mnt/sysimage eventally fails with an error message, which essentially says

If I boot C5 from DVD in rescue mode, chroot to /mnt/sysimage, and try to do a grub-install /dev/sda it will fail because the /dev folder is empty (in the chroot environment). Until now I've then created the missing nodes manually, but is there a smarter way of doing this? Some devfs that needs to be mounted on top of /dev? Mogens -- Mogens Kjaer, Carlsberg A/S, Computer Department Gamle

doing that grub-install /dev/sda will give me the "corresponding BIOS device" error. But now I fixed it by doing a manual grub install. first boot with cd1 and type linux rescue at the prompt when you're at the linux prompt after detecting and mounting the partitions, do a "chroot /mnt/sysimage" then # grub --batch #grub> root (hd0,0) Filesystem type is ext2fs,

Booting from the CentOS 5.2 Installation DVD (or the first Installation CD), one can type "linux rescue" and then "chroot /mnt/sysimage" and have full root access to the OS on the HD. For future reference, I would like to know what I did wrong, the past couple of days, when trying to use the CentOS 5.2 i386 Live CD, for rescue. From a terminal, "su -" did not seem to

so, Just chroot to mountpoint: http://www.cyberciti.biz/faq/unix-linux-chroot-command-examples-usage-syntax/ chroot /mounted/path /bin/bash and then .. mkinitrd (see man page for documentation) 2016-10-30 22:57 GMT+02:00 Eero Volotinen <eero.volotinen at iki.fi>: > A bit hard to say. Try chrooting into environment and rebuilding initrd? > > -- > Eero > > 2016-10-30

Booting to CentOS 5.5 works and I am able to login with all my devices mounted. When I boot from the install DVD and type "linux rescue" I eventually get the message, after attempting to have one of the screens mount my partitions in read/write mode: "An error occurred trying to mount some or all of your system. Some of it may be mounted under /mnt/sysimage." But nothing

How much is likely to break if you keep a locally installed /boot partition with it's anaconda-crafted module set in the initrd, but wipe and completely replace / and any other partitions with a copy from a machine that has somewhat different hardware? Assume both machines are running the same kernel versions and the change is done while running from the rescue CD or other livecd boot.

A bit hard to say. Try chrooting into environment and rebuilding initrd? -- Eero 2016-10-30 22:53 GMT+02:00 Paul R. Ganci <ganci at nurdog.com>: > On 10/30/2016 12:26 PM, Paul R. Ganci wrote: > >> <snip>I am thinking of putting the CentOS iso out and then booting the VM >> into it just to poke around the file system. Otherwise my other option is >> to just

Is there some new trick to making raid devices on Centos5? # mdadm --create /dev/md3 --level=1 --raid-devices=2 /dev/sdc1 /dev/sdc1 mdadm: error opening /dev/md3: No such file or directory I thought that worked on earlier versions. Do I have to do something udev related first? -- Les Mikesell lesmikesell at gmail.com

Hi, I've been using an CentOS4.4 version. All was well till 2 days back. Suddenly when the PC was booted-up, it wouldn't bootup. It gets stuck displaying the following message. exec of init (/sbin/init) failed !!!: 80 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! I entered the rescue mode and attempted chroot /mnt/sysimage It spitted an error

> ------------------------------ > > Message: 11 > Date: Fri, 13 Jun 2008 14:01:14 -0500 > From: Les Mikesell <lesmikesell at gmail.com> > Subject: Re: [CentOS] Network FS w/o user setup > To: CentOS mailing list <centos at centos.org> > Message-ID: <4852C3FA.6040901 at gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > >

On 10/30/2016 12:26 PM, Paul R. Ganci wrote: > <snip>I am thinking of putting the CentOS iso out and then booting the > VM into it just to poke around the file system. Otherwise my other > option is to just clone a twin VM on another server and then just > change the networking IPs/hostname. Anybody have any other ideas as to > how to debug this problem? So I booted off

--autosysroot option uses suggestions to user on how to mount filesystems and change root suggested by --suggest option in virt-rescue. Commands are passed on kernel command line in format guestfs_command=command;. Command ends with a semicolon and there can be multiple commands specified. These are executed just before bash starts. On successfull run user is presented directly with bash in

> -----Original Message----- > From: Les Mikesell [mailto:lesmikesell at gmail.com] > Sent: Tuesday, October 29, 2013 5:25 PM > To: CentOS mailing list > Subject: Re: [CentOS] How should I reinstall CentOS? > > On Tue, Oct 29, 2013 at 3:47 PM, Michael Hennebry > <hennebry at web.cs.ndsu.nodak.edu> wrote: > > <SNIP> > > > I'm not willing to

On Mon, Feb 9, 2015 at 2:06 PM, Les Mikesell <lesmikesell at gmail.com> wrote: > On Mon, Feb 9, 2015 at 3:42 PM, Valeri Galtsev > <galtsev at kicp.uchicago.edu> wrote: >> > >> Still, there are many knowledgeable people on the list, they may give >> different recommendation, which will create some pool of choices. I asked >> John and Jonathan, I'd

On Mon, Apr 27, 2015 at 4:52 PM, Les Mikesell <lesmikesell at gmail.com> wrote: > On Mon, Apr 27, 2015 at 4:34 PM, Matthew Miller <mattdm at mattdm.org> wrote: >> On Mon, Apr 27, 2015 at 04:04:41PM -0500, Les Mikesell wrote: >>> Interesting, but it seems to _only_ show groups that weren't included >>> in the anaconda install. For example where the

Less, You are 100% right. Of course I brought up my eth0 - but, like you said, with no IP. Meanwhile, I brought up eth0.48 with 192.168.48.100. However, until I would bring up eth0 with an IP address (any in the network) I would have no connection. Why? That's what I fail to understand. Boris. On Fri, Jan 23, 2015 at 6:45 PM, Les Mikesell <lesmikesell at gmail.com> wrote: > On