> Did you chroot into it to install kernel? Yes, I did. > Did you use Ext3 or Ext4 for the format? I used ext3 for the bad USB stick. I am also surprised that it didn't recover but I don't know how else to explain it. Everything is running well enough so no use spending any more time on 'what happened?'. I've been a lurker for several years and would likby sparks - uBoot
I did as you suggested. I even added the 'c' option for fsck. The check did modify the filesystem. I reinstalled the kernel to create a new initrd.img... and then recreated uInitrd. No joy. I went and made a new usb boot drive from the Debian image and copied non-boot files from the bad drive. It works but apt-get and dpkg are a little wonky. They don't recognize some packages as iby sparks - uBoot
While I was away on holidays, my home suffered a power outage. When I came home and tried to access my GoFlexHome (that I usually turn off when going away), I couldn't. The NC Console showed me this: Found bootable drive on usb 0 Bootargs = console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) init=/bin/systemd loading uImageby sparks - uBoot
I had a similar problem on my Seagate FreeAgent. I came across this thread looking for an answer. Taking Bodhi's lead I looked for shell solution. What I ended up doing is stopping /etc/network/if-up.d/nptdate from running and added ntpdate to the ntp start script. To /etc/network/if-up.d/nptdate I added an exit statement thus: Quote #!/bin/sh exit 0 blah blah blah... It effectivelyby sparks - Debian