similar to: ThinkStation with BIOS RAID and disk error messages in gparted

> My ThinkStation runs CentOS 7 which I installed on a BIOS RAID 0 setup > with two identical 256 Gb SSDs after removing Windows. It runs fine but I > just discovered in gparted something that does not seem right: > > - Launching gparted it complains "invalid argument during seek for red on > /dev/md126" and when I click on Ignore I get another error "The backup

Once upon a time, Simon Matter <simon.matter at invoca.ch> said: > I'm a bit confused what you have here. Did you mix pseudo hardware RAID > (BIOS RAID 0) with software RAID here? Because /dev/md126 clearly is part > of a software RAID. IIRC the old dmraid support for motherboard RAID has been phased out, but mdraid has grown support for Intel (and maybe some other?) common

On 10/23/2020 10:07 AM, Chris Adams wrote: > Once upon a time, Simon Matter <simon.matter at invoca.ch> said: >> I'm a bit confused what you have here. Did you mix pseudo hardware RAID >> (BIOS RAID 0) with software RAID here? Because /dev/md126 clearly is part >> of a software RAID. > IIRC the old dmraid support for motherboard RAID has been phased out, > but

On C6 (latest) I wanted to add an extra partition, number 14, to a 1TB GPT disk. It failed repeatedly. The error message is:- ~~~~~~~ GParted 0.19.1 Libparted 2.1 Create Primary Partition #1 (ext4, 33.00 MiB) on /dev/sda 00:00:01 ( ERROR ) calibrate New Partition #1 00:00:00 ( SUCCESS ) path: /dev/sda-1 start: 613591359 end: 1953525134 size: 1339933776 (638.93 GiB) create empty

I just upgraded my home KVM server to CentOS 6.0 CR to make use of the latest libvirt and now my RAID array with my VM storage is missing. It seems that the upgrade to mdadm-3.2.2 is the culprit. This is the output from mdadm when scanning that array, # mdadm --detail --scan ARRAY /dev/md0 metadata=imsm UUID=734f79cf:22200a5a:73be2b52:3388006b ARRAY /dev/md126 metadata=imsm

Hi, I just replaced Slackware64 14.1 running on my office's HP Proliant Microserver with a fresh installation of CentOS 7. The server has 4 x 250 GB disks. Every disk is configured like this : * 200 MB /dev/sdX1 for /boot * 4 GB /dev/sdX2 for swap * 248 GB /dev/sdX3 for / There are supposed to be no spare devices. /boot and swap are all supposed to be assembled in RAID level 1 across

hi all! back in Aug several of you assisted me in solving a problem where one of my drives had dropped out of (or been kicked out of) the raid1 array. something vaguely similar appears to have happened just a few mins ago, upon rebooting after a small update. I received four emails like this, one for /dev/md0, one for /dev/md1, one for /dev/md125 and one for /dev/md126: Subject: DegradedArray

Hi, I have a 24TB RAID6 disk with a GPT partition table on it. I need to partition it into 2 partitions one of 16TB and 1 of 8TB to put ext4 filesystems on both. But I really need to do this remotely. ( if I can get to the site I could use gparted ) Now fdisk doesn't understand GPT partition tables and pat

Hi, somebody knows how to get gparted for centos-5? Regards Joachim Backes <joachim.backes at rhrk.uni-kl.de> University of Kaiserslautern,Computer Center [RHRK], Systems and Operations, High Performance Computing, D-67653 Kaiserslautern, PO Box 3049, Germany -------------------------------------------------- Phone: +49-631-205-2438, FAX: +49-631-205-3056

Hi, I am looking for the rpm for gparted. I don't want the live CD, just the rpm to install on my system. I frequently have to format drives [mostly usb drives]. Any suggestion? -- Thanks http://www.911networks.com When the network has to work

On Mon, 2015-06-15 at 21:41 -0500, Robert Nichols wrote: > Non-GPT partitions do not have a UUID. The _content_ (filesystem, > LVM physical volume, non-encrypted swap space, etc.) of such a > partition could have a UUID, but the partition itself does not. ON Centos 5, using GPARTED I created partitions for filing systems ext3 and ext4. 4 primary and unlimited (except by space) extended

I plan to upgrade an existing C7 computer which currently has one 256 GB SSD to use mdadmin software RAID1 after adding two 4 TB M2. SSDs, the rest of the system remaining the same. The system also has one additional internal and one external harddisk but these should not be touched. The system will continue to run C7. If I remember correctly, the existing SSD does not use a M2. slot so they

First let me say I am not a true expert, but I am experienced. If this machine you purchased was some name brand, you must be speaking about hardware raid, true? If this is true, it normally presents you with what looks like a standard drive (/dev/sda) for every 2 drives configured as raid-1. Also, most name brand servers give you a bootable machine day one. If you are using software raid,

Good day, Gparted is not available on my installation. Which patition tool is available in centos 5.5 please. Thanks Johan

On 05/13/16 23:08, Always Learning wrote: > On C6 (latest) I wanted to add an extra partition, number 14, to a 1TB > GPT disk. > > It failed repeatedly. The error message is:- > > ~~~~~~~ > > GParted 0.19.1 > > Libparted 2.1 > > Create Primary Partition #1 (ext4, 33.00 MiB) on /dev/sda 00:00:01 > ( ERROR ) > calibrate New Partition #1 00:00:00 (

On Fri, 2016-05-13 at 23:17 -0453, William A. Mahaffey III wrote: > Is the disk or 1 of its partitions mounted ? If so, can it be > unmounted Hi William, its the only HDD on that machine. All the partitions are mounted. The error message refers to the HDD, not to any of the mounted partitions. > > WARNING: the kernel failed to re-read the partition table > > on /dev/sda

On Tue, 2015-06-16 at 11:30 +0100, John Hodrien wrote: > On Tue, 16 Jun 2015, Always Learning wrote: > > > ON Centos 5, using GPARTED I created partitions for filing systems ext3 > > and ext4. 4 primary and unlimited (except by space) extended partitions. > > That suggests those partitions are not GPT but old fashioned M$DOS > > If it is old fashioned MSDOS, you can

Le 04/12/2018 ? 23:50, Stephen John Smoogen a ?crit?: > In the rescue mode, recreate the partition table which was on the sdb > by copying over what is on sda > > > sfdisk ?d /dev/sda | sfdisk /dev/sdb > > This will give the kernel enough to know it has things to do on > rebuilding parts. Once I made sure I retrieved all my data, I followed your suggestion, and it looks

After switching to version 6.2, I am having a problem to use chain.c32 to boot a local disk. My settings: ====================== label local MENU LABEL Local operating system in hard drive kernel chain.c32 append hd0 ====================== It gave me "Error: Couldn't read the first disk sector" If I change the settings as ====================== label local MENU LABEL

Le 18/02/2015 09:24, Michael Volz a ?crit : > Hi Niki, > > md127 apparently only uses 81.95GB per disk. Maybe one of the partitions has the wrong size. What's the output of lsblk? [root at nestor:~] # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 232,9G 0 disk ??sda1 8:1 0 3,9G 0 part ? ??md126 9:126 0 3,9G 0 raid1 [SWAP] ??sda2 8:2