similar to: How NOT to have a disk recognized by grub?

Hi... I've seen several posting regarding assertion failure (I also have that problem since rh 7.2 and 7.3!!). Is it a bug or something? This failure can happen although we have run fsck. The failure msg can sometimes just pop-up from the screen when the computer is idling. Sometimes low-level format needs to be done if we want to do reinstallation because otherwise during formatting the

> On 30.06.2016 19:41, Erwan Velu via Syslinux wrote: > > The exisiting label= option offer to boot on a gpt partition that have > > a particular label. > > The existing guuid= option offer to boot on a disk or partition with a > > particular label. > > > > This new option offer to boot the disk that have a partition which > > have a given label. >

Hi, I do have an iscsi storage with two raidsets. I'm logged in to the target and get two devices: /dev/sdb and /dev/sdc. After formatting the devices with ext4 I realised, that I had used a wrong label, so I tried to relabel the devices. But now I'm confused: doing a e2label /dev/sdb or /dev/sdc returns always the same label name for both devices. so I did "e2label /dev/sdb

Hi all, I am a non-technical guy (in some ways) & I did read the man pages but became no wiser. My main aim is to do backups between my hdd & an external 80 GB EIDE hdd. The filesystem is ext3 both on the hdd as well as have made ext3 partitions to the hdd. I have 2 use-cases really :- 1. take an image of my /home/shirish the first time (without the .something files) all the

The exisiting label= option offer to boot on a gpt partition that have a particular label. The existing guuid= option offer to boot on a disk or partition with a particular label. This new option offer to boot the disk that have a partition which have a given label. The label is so just a way to detect a disk to boot. A typical use is for making an intelligent localboot like : label

Hello, I need help with grub. I've a PC that I've assembled by my self and the configuration is listed below. AMD Athlon 3600+ 1GB Kingstone RAM 80GB SATA & 40 GB PATA MSI Motherboard And the problem that I'm having is with my two Linux distros. Ive installed CentOS & Windows in my SATA HDD and I've used my complete 40GB PATA HDD for Ubuntu. Well all OS's

I have change my disk from hdc to hda. I need to change the LABEL information in grub.conf so hda is / and not hdc. Where is that. Thanks, jerry

I have VMPlayer 12 running a CentOS 7 disk. Works fine. However I wish to change the disk from UUID booting (fstab) to the old style LABEL. (so I can export it and use on another machine). fdisk -l /dev/sda Disk /dev/sda: 21.5 GB, 21474836480 bytes, 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes

Hi, I'm trying to implement this: I have: - A windows 2000 server - A centos 4 server - Monday, Tuesday, Wednesday, Thursday, Friday, Monthly. The tape drive in the windows server died recently and I decided to switch to USB external drives. However, the USB controller in the windows server is only 1.1, so it is very slow. I didn't want to install a 2.0 USB controller in the

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:

Quote everywhere that we reference wwid in o-c-storage, o-c-boot and ovirt-functions. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-boot | 6 +- scripts/ovirt-config-storage | 178 +++++++++++++++++++++--------------------- scripts/ovirt-functions | 38 +++++----- 3 files changed, 111 insertions(+), 111 deletions(-) diff --git

Hi, somehow after a power failure i can't mount my ext3 partition :( mount /dev/hdd2 /mnt/gentoo/ mount: you must specify the filesystem type fdisk /dev/hdd The number of cylinders for this disk is set to 484521. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2)

I ran into a problem when using grub-install experimentally in what is obviously a foolish way, since I was unable to boot the machine afterwards. I got round the problem, as I shall explain, but I'm still interested to know why the problem arose. Having added a second hard disk to my CentOS-6.5 server, as an experiment I gave the command grub-install /dev/sdb after checking (with fdisk)

This lays the groundwork for setting Root and RootBackup onto individual partitions for multiple disk installations in the future. Install, removal, upgrade testing has been performed and all seems to work at this point. --- scripts/ovirt-config-boot | 15 ++++++++------- scripts/ovirt-config-storage | 28 +++++++++++++++------------- scripts/ovirt-config-uninstall | 2 ++

I am trying to create a CF card that boots 686 CentOS 6.3 On boot I get a message about /dev/disk/by-label/\x2f where \x2f is "/" cannot be found. Adding rdshell to the boot line and booting up sure enough the /dev/disk directory does not exist. What "creates" that early on in the boot process? My CF card was changed from UUID to LABEL. So I edited grub.conf and make

Use findfs LABEL=ABC and mount LABEL=ABC instead. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-boot | 29 ++++++++++++++++------------- scripts/ovirt-config-storage | 2 -- scripts/ovirt-functions | 18 ++++++++++-------- 3 files changed, 26 insertions(+), 23 deletions(-) diff --git a/scripts/ovirt-config-boot b/scripts/ovirt-config-boot index

Hi, Didier Spaier wrote: > The issue is the inability of booting of a *physical* (not virtual) optical > media, like for instance a DVD or a CD, using syslinux.efi. Actually firmware cannot find any UEFI specified booting starting points in an ISO 9660 filesystem that was created with mkisofs -b and -hard-disk-boot, but without a boot image which was marked as EFI System Partition. The

Previous implementation had staticly defined partitions to remove. This would break in the case of split Root and HostVG devices. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-boot | 11 +-------- scripts/ovirt-config-uninstall | 48 ++++++++++++++++++++++++--------------- scripts/ovirt-functions | 33 +++++++++++++++++++++++++++ 3 files

We should use the existing function from specific fs, if not, move it to specific fs files. Chen Hanxiao (4): labels: move e2label to ext2.c and call it directly labels: move ntfslabel to ntfs.c labels: use existing do_xfs_admin for xfslabel labels: return ENOTSUP if could not set label for specific fs daemon/daemon.h | 2 ++ daemon/ext2.c | 23 ++++++++++++-----

Greetings. I have just successfully updated a RH-9 file server to CentOS-3.1. I'm VERY impressed. I have a client who has 4 Redhat servers (1 x 7.3 and 3 x 9.0) that I would like to migrate to CentOS-3.1. Question: My client is willing to send a donation for these boxes but they just want to send you (caosity.org) a check that will cover the next couple of years. Who do we make the