I did the following today:Indeed, the /lib/udev/rules.d/60-persistent-storage.rules file does exist in the initramfs.
I tried "udevadm control --reload-rules", but there was no output that I can use. I also think I tried it with --debug, and I saw some info, but nothing helpful.
I decided to try to rebuild my 3.10-1 initramfs, to see if the newly build package would cause the same problems, and indeed it did. I have the old working initramfs, and now a broken one which gives the same behavior as the 3.10-3 version. So, it's not the kernel so much as it's something else being packaged on the initramfs. I'm thinking this is a udev problem thus far, but I really don't know that for certain yet.
I'll decompress the initramfs files tomorrow and look at the differences between them.
Unfortunately the host in question is important to me, and at a remote location, so I can't play with it right now. I will look into setting up a test system though and see if I can duplicate the problem locally.
On 10/12/13 11:58 PM, Jesse Molina wrote:
Okay, this is helpful. Unfortunately, I don't know a lot about Debian's initramfs scripts, and I'm fairly ignorant of udev beyond it's basic functions and rule files. So, advice on basic troubleshooting of udev would be helpful to me.I am going to go play with this system here shortly, so hopefully I can discover a little bit more which will be helpful to us.On 10/12/13 5:12 PM, Tom H wrote:Since the "by-id" links are being created, I assume that the answer to the following question will be "yes" but just in case: does "lib/udev/rules.d/60-persistent-storage.rules" exist in the initramfs? Can you add a line to "scripts/local" to retrigger the udevadm creation of the "by-uuid" links? I don't know the <deleted> syntax offhand, sorry. ("udevadm trigger ...)