similar to: Accidentally nuked my system - any suggestions ?

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

Nicolas Kovacs wrote: > > My workstation is running CentOS 7 on two disks (sda and sdb) in a > software RAID 1 setup. > > It looks like I accidentally nuked it. I wanted to write an installation > ISO file to a USB disk, and instead of typing dd if=install.iso > of=/dev/sdc I typed /dev/sdb. As soon as I hit <Enter>, the screen froze. > > I tried a hard reset, but

Le 04/12/2018 ? 23:10, Gordon Messmer a ?crit : > The system should boot normally if you disconnect sdb. Have you > tried that? Unfortunately that didn't work. The boot process stops here: [OK] Reached target Basic System. Now what ? -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Site : https://www.microlinux.fr Blog :

On 05/12/2018 05:37, Nicolas Kovacs wrote: > 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. >

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

'--no-degraded' flag in the first mdadm call inhibits the startup of array unless all expected drives are present. This will prevent starting arrays in degraded state. Second mdadm call (after LVM is scanned) will scan unused yet devices and make an attempt to run all found arrays even they are in degraded state. Two new tests are added. This fixes rhbz1527852. Here is boot-benchmark

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

On Tue, 4 Dec 2018 at 17:30, Nicolas Kovacs <info at microlinux.fr> wrote: > > Le 04/12/2018 ? 23:10, Gordon Messmer a ?crit : > > The system should boot normally if you disconnect sdb. Have you > > tried that? > > Unfortunately that didn't work. The boot process stops here: > > [OK] Reached target Basic System. > > Now what ? > > In the rescue

Hi, In my daily work I'm mainly using USB keys for work : one with CentOS 7, one with OpenSUSE Leap 15.1, one with Slax Live for data recovery purposes, one with Ghost4Linux and one with FreeDOS which I use for flashing the odd BIOS. Last week I bought a set of three flashy colored USB keys in a local shop. To my surprise, none of them seem to be able to boot anything. When I write a

Somewhere, mdadm is cacheing information. Here is my /etc/mdadm.conf file: more /etc/mdadm.conf # mdadm.conf written out by anaconda DEVICE partitions MAILADDR root ARRAY /dev/md0 level=raid1 num-devices=4 metadata=0.90 UUID=55ff58b2:0abb5bad:42911890:5950dfce ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=315eaf5c:776c85bd:5fa8189c:68a99382 ARRAY /dev/md2 level=raid1 num-devices=2

On 12/4/18 2:01 PM, Nicolas Kovacs wrote: > I tried a hard reset, but of course, the boot process would stop short > very early in the process. The system should boot normally if you disconnect sdb.? Have you tried that?

Right, that's my problem. a drive is unplugged... while the system is not running mdadm will not reassemble the array on boot. Red Hat Bugzilla ? Bug 1451660 Write that Fixed In Version:dracut-033-546.el7 I have drucat version 033-554.el7 and this bag don't fixed! >I believe you are hitting this bug: > > ? https://bugzilla.redhat.com/show_bug.cgi?id=1451660 > >That is,

(Resend: message didn't show, was my original message too big? Posted one of the output files to a website to see) The point of RAID1 is to allow for continued uptime in a failure scenario. When I assemble servers with RAID1, I set up two HDDs to mirror each other, and test by booting from each drive individually to verify that it works. For the OS partitions, I use simple partitions and

Just rebuilt a C6 box last week as C7. Four drives, and sda and sdb for root, with RAID-1 and luks encryption. Layout: lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 931.5G 0 disk ??sda1 8:1 0 200M 0 part /boot/efi ??sda2

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 Niki, md127 apparently only uses 81.95GB per disk. Maybe one of the partitions has the wrong size. What's the output of lsblk? Regards Michael ----- Urspr?ngliche Mail ----- Von: "Niki Kovacs" <info at microlinux.fr> An: "CentOS mailing list" <CentOS at centos.org> Gesendet: Mittwoch, 18. Februar 2015 08:09:13 Betreff: [CentOS] CentOS 7: software RAID 5

Hi, I just had the weirdest of system crashed. Here goes. I wanted to install a desktop step by step, as I usually do. First the base system, then the X Window System, then the WindowMaker window manager. Everything went OK, then I installed kmod-nvidia from ELRepo. Yum informed me that the driver conflicted with x11-glamor (something like that), so I removed the corresponding package.

Hi I have read instructions for udev, I also found many example on how to do this. I want to lock in the SDA/SDB/SDC for my drives and I came up with a rule like this KERNEL=="sd?", SUBSYSTEM=="block", ENV{ID_SERIAL}=="ST500DM002-1BC142_W2A56H8A", NAME="sda", RUN+="/usr/bin/logger ID_SERIAL=$ENV{ID_SERIAL} set to /dev/sda ",

Hi everyone. This isn't specifically a CentOS question, since it could apply for any distro but I hope someone can answer it anyway. I took the following steps but was puzzled by the outcome of the test at the end: 1. Create a RAID1 array called md3 with two 750GB drives 2. Create a RAID1 array called md9 with two 500GB drives 3. Initialise md3 then md9 as physical volumes (pvcreate) 4.

I am running software RAID1 on a somewhat critical server. Today I noticed one drive is giving errors. Good thing I had RAID. I planned on upgrading this server in next month or so. Just wandering if there was an easy way to fix this to avoid rushing the upgrade? Having a single drive is slowing down reads as well, I think. Thanks. Feb 7 15:28:28 server smartd[2980]: Device: /dev/sdb