Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
What mounting?
After you created those nodes for SSD, did fdisk -l see the drive? You are sure you got the minor numbers right?
There is the kernel driver for controller, and controller deals with drive. When the drive is detected a node is created in /dev/. There may be a timing issue, the SSD may respond too fast for PATA driver for instance. No telling without enabling debug for PATA in kernel if this is the case.
mknod is probably used by udev, certainly not the other way around.
When you create a node the major and minor number will point to that specific piece of hardware. I have two drives, when I run
it wiil create the node for sdc. I could remove udev completely from my system and still, if I plug in another drive I will be able to access it as sdc using the node I created. Of course, if i have a partition on it I'd need to create a node for it.
It might be the PATA driver problem then which is not written with SSD hooked up to an IDE port in mind. Probably cannot be solved without kernel hacking then. Can you pastebin the whole dmesg from Stretch? Just for kicks.