Nicolas Kovacs
2018-Dec-04 22:31 UTC
[CentOS] Accidentally nuked my system - any suggestions ?
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 : https://blog.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32
Stephen John Smoogen
2018-Dec-04 22:50 UTC
[CentOS] Accidentally nuked my system - any suggestions ?
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 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. -- Stephen J Smoogen.
Gordon Messmer
2018-Dec-04 22:55 UTC
[CentOS] Accidentally nuked my system - any suggestions ?
On 12/4/18 2:31 PM, Nicolas Kovacs wrote:> Unfortunately that didn't work. The boot process stops here: > [OK] Reached target Basic System. > Now what ?Remove "rhgb quiet" from the kernel boot args and see if you get any more information about what's happening.? "Reached target Basic System." is recorded twice in the boot logs on a system I checked a moment ago, so I'm not really sure where yours is stalling.
Nicolas Kovacs
2018-Dec-05 05:37 UTC
[CentOS] 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 like I'm making big progress. The system booted again, though it feels a bit sluggish. Here's the current state of things. [root at alphamule:~] # cat /proc/mdstat Personalities : [raid1] md125 : active raid1 sdb2[1] sda2[0] 512960 blocks super 1.0 [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk md126 : inactive sda1[0](S) 16777216 blocks super 1.2 md127 : active raid1 sda3[0] 959323136 blocks super 1.2 [2/1] [U_] bitmap: 8/8 pages [32KB], 65536KB chunk unused devices: <none> Now how can I make my RAID array whole again? For the record, /dev/sda is intact, and /dev/sdb is the faulty disk. How can I force synchronization with /dev/sda? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32