In case this is useful for anyone else, here's my notes on How to install pi-hole 5.0 on Seagate Dockstar running Debian 10 --------------------------------------------------------- This was performed on a fresh install of the standard install ( Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 ) install curl: # apt install curl Download pi-hole installscript. But firstby rsinklair - Debian
Update - flashing the newer u-boot went smoothly, thanks to the clear & detailed instructions, so my U-boot banner now shows 2017.07 :-) And boots from USB. Thanks again for your help bodhi. I would like to buy you a beer but it looks from your signature that a donation to MSF is preferred, so have donated the proceeds of my only sale today on eBay ( a pair of 15-year-old 18GB 10k rpm SCby rsinklair - Debian
Great , that did it thanks ! It has now booted up, gets an IP address from my DHCP server, and I can log in as root. Yippee! ( I had actually run the mkimage commands at the weekend when creating the USB stick, but then when setting up the TFTP server yesterday I just used the uImage file from the original tar.bz file , to save me walking downstairs to unplug the USB stick.. forgetting theby rsinklair - Debian
That's great thanks, it now boots nicely from tftp.:) However it gives an invalid dtb error - see below Elsewhere I saw the use of dtb_file=/boot/dts/kirkwood-dockstar.dtb however that file is on USB.. do we have to tftpboot the dtb file into a specific location on the NAND instead? BTW, is there a way to escape back to the bootloader prompt once it has failed to boot ? (by rsinklair - Debian
Here you go .. CE>> help ? - alias for 'help' base - print or set address offset boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcmd' bootext2 dev:boot_part1,boot_part2 addr boot_image linux_dev_name bootm - boot application image from memory bootp - boot image via network using BootP/TFTP protocolby rsinklair - Debian
Thanks for the fast response! When doing the setenv of the long usb_boot string, it gives a 'too many args' error, but I went ahead anyway, and it gave a 'Unknown command - usb ' , similar to yesterday. I subsequently tried splitting the long usb_boot into two shorter ones, usb_boot1 & usb_boot2 , but still get the same "Unknown command usb" - Hopefullyby rsinklair - Debian
Wow thanks for outlining detailed options! most helpful of you I will definitely go for option 1 as less risk of faffing around if unexpected problems encountered with bad NAND blocks etc I created a 8GB USB stick with the Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi untarred on it, and had a go at booting from USB but will definitely appreciate your help on the correct setenv commands please..by rsinklair - Debian
yippee, I now have serial comms ! My homemade cable wasn't connecting well to the GND pin on the Dockstar . Thanks for the pointer David So I now see the boot process : a Bad Data CRC error when it tries to boot the kernel - see full details further down.. From some research it looks like I now need to : 1. Restore the original kernel : Set up a tftp server, Download uboot.by rsinklair - Debian
Thanks for the prompt reply David. Glad to hear my dockstar is almost certainly good - that has made my day ! I omitted to mention in my original post that I already had my doubts about the Pi serial port setup when I saw no output from the Dockstar ( especially since the Pi has a LCD display HAT ('Displayotron') on top of it which offers up the UART pins as pass-through ) , so toby rsinklair - Debian
Hello, I recently found an old Seagate Dockstar which I would like to re-use as a network backup & monitoring server (since it is such a neat compact low-power unit), and would appreciate your advice on how feasible it would be to get it loaded with Debian or similar, given its current behaviour, outlined below :- I bought the unit new about 10 years ago, registered it on pogoplug.com, anby rsinklair - Debian