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@xxxxxxxxx> 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@xxxxxxxxxx
> https://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
