[19:09] hello. i got the problem that my internal devices aren't recognized when i use the dd command... is there something like a limitation for drives to be detected, maybe on the kernel side during a dd command execution? [19:10] i'm talking about a bay with changeable devices on the sata-port [19:12] I doubt it would be dd, not mounted or wrong mount point? [19:12] last time it seemed that the drives wheren't recognized anymore at all, even after reboot. had to rewrite my whole uefi-system to get it back working [19:13] if i write to an usb-device with dd and put a removable sata-ssd into the internal bay, the drive is not more recognized. [19:14] last time i got strange messages: [19:15] mtd device must be supplied (device name is empty) [19:16] since i rewrote the uefi, this message is gone [19:16] or does this have nothing to do with dd? [19:19] dmesg gave also some strange lines: [19:19] unknown parameter 'windows_names' [19:20] ata6: sata link down (sstatus 0 scontrol 300) [19:20] ata6.00: disabled [19:21] ata6.00: detaching (SCSI 5:0:0:0) [19:21] sd 5:0:0:0 [sdc] stopping disk [19:22] sd 5:0:0:0 [sdc] start/stop unit failed: result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_=K [19:22] sd 5:0:0:0 [sdc] start/stop unit failed: result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [19:22] what can this be? [19:27] important to mention: after every reboot the drive was recognized again, but not at hotswap. [19:28] i already thought the hotswap-module in my uefi was broken... [19:28] or sata-module (or whatever) [19:30] and after i reused dd again, i tested to put in an ssd into the bay, but it wasn't recognized for the time dd was running (and the time after, until reboot) [19:33] (after i rewrote the uefi) [19:33] could this be something like maybe a kernel-bug? [19:34] or bug in dd? [20:03] dd-flags were: bs=4M oflag=nocache,sync status=noxfer