Hello Gordon, yeah. it is really strange. from one boot to the next, everyhing is f** up.(2 months between). any idea? [root at quad live]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 1.8T 0 disk ??sda1 8:1 0 1.8T 0 part ??WDC_WD20EFRX-68AX9N0_WD-WMC1T2547260 253:3 0 1.8T 0 mpath ??WDC_WD20EFRX-68AX9N0_WD-WMC1T2547260p1 253:8 0 1.8T 0 part sdb 8:16 0 1.8T 0 disk ??sdb1 8:17 0 1.8T 0 part ??WDC_WD20EFRX-68AX9N0_WD-WMC301255087 253:4 0 1.8T 0 mpath ??WDC_WD20EFRX-68AX9N0_WD-WMC301255087p1 253:9 0 1.8T 0 part sdc 8:32 0 1.8T 0 disk ??sdc1 8:33 0 1.8T 0 part ??WDC_WD20EFRX-68EUZN0_WD-WCC4M2668622 253:5 0 1.8T 0 mpath ??WDC_WD20EFRX-68EUZN0_WD-WCC4M2668622p1 253:7 0 1.8T 0 part sdd 8:48 0 1.8T 0 disk ??sdd1 8:49 0 1.8T 0 part ??WDC_WD20EFRX-68EUZN0_WD-WMC4M2878723 253:2 0 1.8T 0 mpath ??WDC_WD20EFRX-68EUZN0_WD-WMC4M2878723p1 253:6 0 1.8T 0 part sde 8:64 0 119.2G 0 disk ??sde1 8:65 0 500M 0 part /boot ??sde2 8:66 0 118.8G 0 part ??centos-swap 253:0 0 2G 0 lvm [SWAP] ??centos-root 253:1 0 50G 0 lvm / ??centos-home 253:10 0 66.8G 0 lvm /home On Fri, Aug 18, 2017 at 11:56 PM, Gordon Messmer <gordon.messmer at gmail.com> wrote:> On 08/18/2017 12:35 PM, Mr Typo wrote: >> >> mdadm: /dev/sda1 is busy - skipping >> mdadm: /dev/sdb1 is busy - skipping >> mdadm: /dev/sdc1 is busy - skipping >> mdadm: /dev/sdd1 is busy - skipping > > > > That's plenty strange. The output of "lsblk" might tell you why those > devices are busy. > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos
On 08/19/2017 12:06 PM, Mr Typo wrote:> sda 8:0 0 1.8T 0 disk > ??sda1 8:1 0 1.8T 0 part > ??WDC_WD20EFRX-68AX9N0_WD-WMC1T2547260 253:3 0 1.8T 0 mpath > ??WDC_WD20EFRX-68AX9N0_WD-WMC1T2547260p1 253:8 0 1.8T 0 partYou haven't said anything about multipath hardware yet, and you've been referring to "sda1", etc, which makes me think that you probably don't have multipath hardware. If that's true, then the problem is probably that someone installed the multipath software on this system after the last time it booted successfully. One fix could be to boot from install media and use rescue mode to get a shell. Inside the rescue environment, remove the multipath software. If you did have multipath hardware, you'd be assembling the multipath targets, like WDC_WD20EFRX-68AX9N0_WD-WMC1T2547260p1, rather than sda1.
hello Gardon, thank you for the tip. I had an eye on multipathd during my debugging, but i ignored it, because i had installed it for years now. (and a stop of the service still gave me the device busy stuff). i assume that another rpm has enabled the multipath service and this was fiddling around. disabling the multipath stuff helped. thank you for your hint again! got my kudos .) regards Andreas On Sun, Aug 20, 2017 at 8:08 PM, Gordon Messmer <gordon.messmer at gmail.com> wrote:> On 08/19/2017 12:06 PM, Mr Typo wrote: >> >> sda 8:0 0 1.8T 0 disk >> ??sda1 8:1 0 1.8T 0 part >> ??WDC_WD20EFRX-68AX9N0_WD-WMC1T2547260 253:3 0 1.8T 0 mpath >> ??WDC_WD20EFRX-68AX9N0_WD-WMC1T2547260p1 253:8 0 1.8T 0 part > > > > You haven't said anything about multipath hardware yet, and you've been > referring to "sda1", etc, which makes me think that you probably don't have > multipath hardware. > > If that's true, then the problem is probably that someone installed the > multipath software on this system after the last time it booted > successfully. One fix could be to boot from install media and use rescue > mode to get a shell. Inside the rescue environment, remove the multipath > software. > > If you did have multipath hardware, you'd be assembling the multipath > targets, like WDC_WD20EFRX-68AX9N0_WD-WMC1T2547260p1, rather than sda1. > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos