> Is the filesystem mounted when it tries to find the firmware? I thought it was, but having another look at dmesg, it looks like that's not the case.
proxy linux # dmesg | grep eth0 [ 0.897559] r8169 0000:02:00.0: eth0: RTL8168d/8111d at 0xffffc90000360000, 1c:6f:65:20:3f:c6, XID 083000c0 IRQ 41 [ 70.453673] r8169 0000:02:00.0: eth0: unable to load firmware patch rtl_nic/rtl8168d-2.fw (-2) [ 70.461027] r8169 0000:02:00.0: eth0: link down [ 70.461050] r8169 0000:02:00.0: eth0: link down [ 70.461444] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 72.851287] r8169 0000:02:00.0: eth0: link up [ 72.851846] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready proxy linux # dmesg | grep btrfs [ 1.647953] btrfs: use lzo compression [ 2.129807] VFS: Mounted root (btrfs filesystem) on device 0:13. > In other words, are you perhaps using a ramdisk? > > If you have this drives as a module, can you try removing it (rmmod > <driver> and then reloading it (modprobe <driver>)? > > If it isn't a module, can you rebuild your kernel to have the relevant > driver as a module? Its not a module - i'll make it one and see how that goes.
