similar to: server fails reboot - GRUB

On 10/12/14 18:13, Jeff Boyce wrote: > Greetings - > > The short story is that got my new install completed with the > partitioning I wanted and using software raid, but after a reboot I > ended up with a grub prompt, and do not appear to have a grub.cfg file. > So here is a little history of how I got here, because I know in order > for anyone to help me they would

Greetings - The short story is that got my new install completed with the partitioning I wanted and using software raid, but after a reboot I ended up with a grub prompt, and do not appear to have a grub.cfg file. So here is a little history of how I got here, because I know in order for anyone to help me they would subsequently ask for this information. So this post is a little long, but

Hi all, I've installed CentOS 4.4 in a box which previously had dual boot (XP SP2 and Ubuntu) I can run CentOS without problem but I can't boot XP SP2. When I try it the system simply hangs... [root at seth ~]# fdisk -l Disco /dev/hdb: 40.0 GB, 40020664320 bytes 255 cabezas, 63 sectores/pista, 4865 cilindros Unidades = cilindros de 16065 * 512 = 8225280 bytes Disposit. Boot Start

I am running rsync throuhg cygwin and trying to "mirror" two hard drives (hd1 -> hd2). HD1 have tons of hard links (I will say about 2 millions) because I do monthly backups and have about 13 folders and maybe about 150,000 files. Every month when I make a new snapshot I would also want to mirror HD1 to HD2. I tried running rsync -aH --progress -vv /cygdrive/d/ /cygdrive/e/ I though

When I use my kickstart file (which works on 5.1 x86_64) with 5.2 I get the following error. I put my kickstart file at the end. Do I have something incomaptible in the file? jerry -------------------------------------- Traceback (most recent call first): File "/usr/lib/anaconda/network.py", line 341, in lookupHostname ret = isys.pumpNetDevice(dev.get('device'),

Dear all Recently, i did some work to test small files performance for gnfsv3 transport. Following is my scenario. #####environment##### ==2 cluster nodes(nodeA/nodeB)== each is equipped with E5-2650*2, 128G memory and 10GB*2 netcard nodeA: 10.254.3.77 10.128.3.77 nodeB: 10.254.3.78 10.128.3.78 ==2 stress nodes(clientA/clientB)== each is equipped with E5-2650*2, 128G memory and 10GB*2

Earlier this evening, I had the interesting experience of shutting down my machine (because of that lp out-of-sync problem, discussed elsewhere), and watching it not come back up. I admit that I changed out one of my DVD writers for another one, but I don't understand how that could have had any effect on this: When I restarted the machine, it came up to the point where it normally shows:

I'm still having conceptual trouble with this one. I have two PATA and two SATA disks in my home system. When the system comes up, these are, espectively, /dev/hda, /dev/hdb, /dev/sda and /dev/sdb. I have the boot order of the drives in the boot PROM set to boot from /dev/sda (hard drive 2), then /dev/hda (hd 0), and usually that works fine. /dev/sda is properly set up with the MBR and

On Thu, Aug 6, 2015 at 3:19 PM, Chris Murphy <lists at colorremedies.com> wrote: > On Thu, Aug 6, 2015 at 2:59 PM, Gordon Messmer <gordon.messmer at gmail.com> wrote: >> On 08/05/2015 10:23 AM, Chris Murphy wrote: >>> >>> Nothing about hd0 or hd1 gets baked into the bootloader code. It's an >>> absolute reference to a physical drive at the moment

I am trying to backup my /home directory. A friend helped me with this script: #!/bin/sh #backup friday #"Spinning up backup drive and mounting it .." cd / mount /mnt/hd2 #"Starting backup procedures" rsync -avx --exclude="/home/gary/.thumbnails/" --exclude="/home/gary/tmp/" --delete --ignore-errors /home/gary /mnt/hd2/2010 umount /mnt/hd2 #END It backs

On 08/05/2015 10:23 AM, Chris Murphy wrote: > Nothing about hd0 or hd1 gets baked into the bootloader code. It's an > absolute reference to a physical drive at the moment in time the > command is made. Is that true? If I have a system with two disks, where device.map labels one as hd0 and the other as hd1, and I swap those numbers, the resulting boot sector will differ by one bit.

> If I understand the syntax correct, it is: > (hdX,Y)/path/to/file", where X is disk number and Y is partition number. > As far as I understand X and Y are zero based. > > I've tested it with qemu and 2 disks: > - the first with bootloader > - the second with kernel+rootfs > > I've used the following configuration file label: > > label MULTIFS >

HI i'm so new to centos , Where can get it ? thank you centos-request at centos.org wrote: Send CentOS mailing list submissions to centos at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos or, via email, send a message with subject or body 'help' to centos-request at centos.org You can reach the person

HI i'm so new to centos , Where can get it ? thank you centos-request at centos.org wrote: Send CentOS mailing list submissions to centos at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos or, via email, send a message with subject or body 'help' to centos-request at centos.org You can reach the person

Dears, i setting a samba with shared server in me enviroment but i do not knew enable trash for this. What setting i need for enable trash in me samba? I search links in google for enable trash in samba4 but i do not give help. Below my smb.conf: [global] # Substituir xxxxxx pelo nome do domínio desejado caso necessário workgroup = oduvaldocozzi # Substituir xxxxxx pelo nome do servidor

Is there a way to tell WINE that question marks in directory names are okay? WINE fails whenever I ask it to access a file from within a directory with a question mark in its name. Specifically, my HTPC marks all commercials using WINE and Comskip. Whenever the schedule includes a tv show with a question mark in its title, WINE fails. Here are the logs that illustrate the failure. Script log

Hi, I want to slowly migrate from Debian to CentOS, so I setup a multiboot on my main machine. There's a Debian Etch install on /dev/hda, and GRUB is also installed on the Debian side. On /dev/hdb, I have CentOS 5. I fdisked the drive manually, then chose manual partitioning during install. The setup for CentOS is: hdb1 -> swap hdb2 -> /boot, ext2 hdb3 -> / , ext3 After

On Fri, 2020-07-31 at 22:35 +1200, Alan McRae via CentOS wrote: > I am running an Intel x64 machine using UEFI to boot an SSD. > > Installing the latest yum update which includes grub2 and kernel > 4.18.0-193.14.2.el8_2.x86_64 renders the machine unbootable, blank > screen where grub should be, no error messages, just hangs. > > After some hours I managed to modify another

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,

On Wed, Aug 5, 2015 at 11:11 AM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: > On 8/5/2015 1:00 PM, Chris Murphy wrote: >> >> On Wed, Aug 5, 2015 at 10:52 AM, Bowie Bailey <Bowie_Bailey at buc.com> >> wrote: >>> >>> How would I go about pointing it at the partition? >>> >>> What I am currently doing is this: >>> device