It seems that you just have to create the inotify node in /dev manually in order for it to work Quotemknod /dev/inotify c 10 63 and then restart minidlna.by darkoo - Debian
Hey, This is an old thread, but I'm facing the same issue. Did you find a solution? When I built my own kernel, inotify config option was enabled, but it doesn't seems to be used in the end. Indeed, there is no such thing as /dev/inotify. Any ideas? Thanks!by darkoo - Debian
Yes many thanks to you varkey and kraqh3d!! Yesterday I finally managed to make it permanent by modifying usb_scan line. But this is cleaner with your solution kraqh3d. My device boots even with the SATA drive plugged in now! Thanks again.by darkoo - Debian
Oops, my mistake... Indeed it works like a charm! To make it permanent, I just have to use saveenv instead of setenv for command setenv usb_root LABEL=ROOTFS? Anyway, thanks for your help and reactivity! Edit: Ok, apparently you need to issue saveenv after setenv usb_root ... to write the variable to the NAND, but it doesn't seem to be permanent either...by darkoo - Debian
Thanks for your answers. I just tried this and it doesn't solve the issue unfortunately... When I run printenv bootargs I get exactly the same output than you do with cat /proc/cmdline kraqh3d (except that my rootfs is ext2): console=ttyS0,115200 root=LABEL=ROOTFS rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) Maybe there's a parametby darkoo - Debian
Hi everyone, I have the exact same problem with my GoFlex Net and a SATA hard drive: you have to wait till the end of boot, then you can plug the disk. That's annoying when you need to remotely reboot. I've checked the uBoot sequence and it seems that everything goes find, it even prints "Starting kernel" at the end. After booting, the led is green but the device is notby darkoo - Debian