Ok, I purged all kinds of old kernel versions. I guess I should have been doing that with every new kernel? As expected (from my dry run), it failed to boot. See the continuation here. Thanks again, bodhi! -JTby renojim - Debian
I finally completed updating my kernel to v4.8.3 and my distribution to jessie (thanks, bodhi), but my Dockstar wouldn't complete the boot process. I traced it to an old fstab entry for a hard disk I no longer use, but may want to connect again in the future:UUID=FCF0061DF005DEB0 /media/500GB ntfs rw 0 0 Before the update/upgrade, this never caused a pby renojim - Debian
Thanks, I'll give it a try once the weekend is over. I haven't rebooted and I'm afraid to right now since I need a few things to keep working for the rest of the weekend. It got worse after I tried an apt-get upgrade:Setting up linux-image-4.8.3-kirkwood-tld-1 (1.0) ... Running depmod. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removby renojim - Debian
So I'm in the process of going from wheezy to jessie and I just noticed this pass across the screen:Selecting previously unselected package linux-image-3.16.0-4-kirkwood. Preparing to unpack .../linux-image-3.16.0-4-kirkwood_3.16.36-1+deb8u1_armel.deb ... Unpacking linux-image-3.16.0-4-kirkwood (3.16.36-1+deb8u1) ... I just updated to kernel 4.8.3, so why do I need linux-image-3.16.0? -by renojim - Debian
Thanks! Will update in the next couple of days. -JTby renojim - Debian
Just updated to kernel 4.8.3 (from 3.16.0, I believe) on my Dockstar and now I'm getting a ton of ECC errors on boot:[ 22.951509] __nand_correct_data: uncorrectable ECC error [ 22.956878] Buffer I/O error on dev mtdblock1, logical block 0, async page read [ 22.964449] __nand_correct_data: uncorrectable ECC error [ 22.970005] __nand_correct_data: uncorrectable ECC error [ 22.975by renojim - Debian
It's probably easiest to just create a swap file on another drive; there's no need to use an entire partition. I have mine on a 4TB hard drive that gets mounted to /media/WD4TB on my Dockstar. Here's how I did it: Create a 1GB file filled with zeroes (probably overkill on the size, but I have plenty of space): dd if=/dev/zero of=/media/WD4TB/swapfile bs=1k count=1M Mark the fby renojim - Debian
I was able to update both of them with apt-get with no problem, but I suppose that's not an option for you. -JTby renojim - Debian
So maybe the apt-key binary is corrupted? Can you run it with no parameters? It should print out some help. -JTby renojim - Debian
I just tried to upgrade apt myself and I believe I was successful. Here's my output:Preparing to replace apt 0.9.7.9+deb7u2 (using .../apt_0.9.7.9+deb7u7_armel.deb) ... Unpacking replacement apt ... Processing triggers for man-db ... Setting up apt (0.9.7.9+deb7u7) ... gpg: key B98321F9: "Squeeze Stable Release Key <debian-release@lists.debian.org>" not changed gpg: keyby renojim - Debian
I recently had another (cheap) flash drive fail and after restoring a backup I noticed a "UBIFS error" message in the netconsole output. For all I know it's always been there and after doing a little research I think it's because it's trying to load a UBIFS image from the internal flash and there's none there. I believe it's harmless and/or normal, but I'by renojim - Debian
bohdi, I have both, but I don't think I'll get another chance to do any debugging since I'm on the road now until after the holidays and I'll be leaving them with family members. From the dmsg output I posted above you can see that it appears to give the drive 15 seconds to respond. I tried to find some reference to a 15 second timeout period in the source, but I never foby renojim - Debian
Sorry for the delayed response. Thanks for the idea, but I think I tried a similar cable I made for an old laptop that wasn't supplying enough power for my external drive. I know I tried a powered Seagate FreeAgent Go Dock+ I bought years ago when I thought I was buying a Dockstar. I've now put both Fantom drives into old USB 2.0 enclosures and both the Pogoplug Mobile and Pogoplugby renojim - Debian
Just in case anyone else stumbles upon this thread, that "error -110" noted in the dmesg output is "timed out". -JTby renojim - Debian
A followup: I got the idea today to swap the 1TB Fantom drive from its USB 3.0 enclosure with an old Verbatim drive in a USB 2.0 enclosure. Both the Pogo Mobile and PogoPro boot just fine with the Fantom drive connected via the Verbatim USB 2.0 electronics, so it would appear that it's the USB 3.0 interface that's causing the problem with booting. -JTby renojim - Debian
Thanks for this. I wish I had seen it a few hours ago. I don't want to hijack this thread, but since it's kind of related, here goes. A few hours ago I was trying to use a bash script I found to update my no-ip host and had trouble with its use of wget. I'd get back:Resolving dynupdate.no-ip.com (dynupdate.no-ip.com)... 8.23.224.120 Connecting to dynupdate.no-ip.com (dynupdaby renojim - Debian
Thanks, Don. I had tried a powered hub with no change. For the record, the drive says it uses 500mA which would max out the current a USB 2.0 port/hub is required to support. But, there's no problem if I plug in the drive after Debian has booted. I've been meaning to post an update in case anyone else stumbles upon this thread. It took a while and a failed flash drive (which mayby renojim - Debian
Thanks, bohdi. Interesting reading. It doesn't sound like it was ever resolved. Any chance one of those quirks would work? I don't have the serial port connected at the moment, but I'll open it up again if you think it's worth a try. -JTby renojim - Debian
Thanks, bohdi. I think I've tried every port. Currently I have the flash boot drive in the bottom rear port just above the ethernet connector and the Fantom just above that. If I reverse them, it tries to boot from the Fantom, fails, and then boots from the flash drive, but the Fantom still doesn't get mounted. At one point I could swear that I could do a cold boot (everything conneby renojim - Debian
So I got a couple of Fantom Gforce/3 Mini drives on sale to go with the $5 Pogo Pro and Mobile I got to make a couple of poor man's NASs for family members. Everything works pretty well except that if I try to boot off a flash drive with the Fantom drive attached, it won't mount the Fantom drive. Here's the relative part of dmesg output:[ 14.399639] udevd[267]: starting versionby renojim - Debian
bodhi Wrote: ------------------------------------------------------- > So perhaps some next rootfs we'll switch to systemd? anybody have strong feeling about it? I have a strong feeling about it. I switched to Debian from Arch to get away from systemd. I couldn't even get it to set the freaking clock on boot. After spending a few days in systemd hell, I decided it's way,by renojim - Debian
Thanks bodhi. Will do when I get some free time. -JTby renojim - Debian
It looks like it just plugs into the Lightning connector that Apple's using now, so neither. -JTby renojim - Debian
/ on the Dockstar:/dev/sda1 on / type ext2 (rw,noatime,errors=remount-ro) The "barrier=1" and "data=ordered" attributes weren't accepted and the others didn't make any difference. I just can't seem to create a file with Unicode/UTF-8 characters in the name and have that name display properly (or as something other than a question mark) on any file system on tby renojim - Debian
On the command line, I've been able to view the characters 'Ã' and 'Æ' for quite a while (installing locales fixed that problem). It's when I do a directory listing that I don't see the proper characters. bodhi Wrote: ------------------------------------------------------- > JT, > > I think it might be your Windows file name already > encby renojim - Debian
Well guys, I really appreciate your help. but I think I give up. There's something strange going on here that I don't think I'll ever understand. TEN, convmv -t utf8 *nima.jpg mv "./Ænima.jpg" "./�nima.jpg" really makes a mess of things. I end up with a file named "./�nima.jpg". That's really not what I want. bohdi, I tby renojim - Debian
Thanks bohdi, but it didn't work. I had already done everything up to the installation of the fonts and installing the fonts didn't make a difference. I really don't think it's a font issue as I can display the characters, they just don't seem to be recognized/interpreted in a file name. -JTby renojim - Debian
Thanks, TEN, but I don't think convmv is going to help and the more I play with this the more I realize I don't understand a thing about character encoding. I'll try to give as much detail as possible because maybe something will make sense to someone. The "problem" file is on an NTFS formatted hard drive connected to my Dockstar. It's shared using Samba. Ifby renojim - Debian
Thank you! No rush. As I've seen someone else mention, I'm sure your time is valuable. -JTby renojim - Debian