Oh it's a dockstar, sorry i didn't mention that. I've got 2 dockstars and 1 sheevaplug. I keep thinking if something goes wrong, I've got an immediate redundancy. But it's been what, 10 years? My dockstar shows no signs of giving up the ghost. Now that I see this issue isn't indicative of doom or anything. The exterior is the only part of it in bad shape! Its oncby Nematocyst - Debian
It's been a while since I installed it. but it's basically a straight debian stretch install. I d/l the armv5 uInitd and uInitrd, tftp booted, and ran the installer using serial console, iirc. It's currently running 4.9.0-8-marvell (4.9.130-2, 2018-10-27). and ofc, rootfs was generated during install. this is the same install that I had issues running out of memory a year or soby Nematocyst - Debian
I get this a lot. I recently messed with my server to consolidate drives and backup the rootfs and noticed this is happening every boot. It doesn't happen when I run blkid but it happens when I attach a USB device. I get: [156624.656218] __nand_correct_data: uncorrectable ECC error [156624.661674] blk_update_request: I/O error, dev mtdblock0, sector 2040 [156624.668905] __nand_correcby Nematocyst - Debian
DonCharisma Wrote: ------------------------------------------------------- > I got this also during dist-upgrade Jessie -> Stre > tch on GoFlexNet. Yeah, it seemed to be a stretch issue. I didn't have this on jessie. > A semi-permanent fix...is to add this to /etc/fstab : > tmpfs /run tmpfs nosuid,noexec,size=18M,nr_inodes= 4096 0 0 I haven't tried it. Myby Nematocyst - Debian
Yes, it is the /run mount. The reason rebooting works fine is that systemd isn't trying to reload anything, simply start the services. I can work around the problem by stopping each service and then starting it as such: 'restart' works too. the issue is 'systemctl daemon-reload' which isn't called during a reboot [● root@deimos /home/eric] systemctl stop smbby Nematocyst - Debian
No, not short on disk space. I rebooted and all services appear to be working fine. The bolded item is my rootfs. The red item is where the problem lies, I believe. eric@deimos:~$ df -h Filesystem Size Used Avail Use% Mounted on udev 59M 0 59M 0% /dev tmpfs 13M 2.2M 10M 18% /run /dev/sda5 585G 2.9G 553G 1% / tmpfs 61Mby Nematocyst - Debian
My dockstar server running debian stretch complains when doing updates. I got this a couple months ago, didn't get any useful hits on the problem, and avoided it since the server appeared to still do everything fine. I updated just now and got several errors like this: Warning: smbd.service changed on disk. Run 'systemctl daemon-reload' to reload units. Failed to reload daeby Nematocyst - Debian
I looked at my home server setup and found a troubling problem. It's running squeeze in NAND and works basically fine. But Debian no longer gives security updates (for i386 and amd64 it does still), and suggests: Users of other architectures are encouraged to upgrade to Debian 7 ("wheezy") This is problematic because wheezy is substantially larger than squeeze. For raw numberby Nematocyst - Debian
Do you know if uboot fixes that in more recent versions? yes, it does... downloading the correct one as of this date solves the ability to decompress the same files. note: doing so changed the device offset in /etc/fw_env.config from 0x60000 to 0xc0000. also it required a slight ubifsmount syntax change. instead ofubifsmount rootfsI neededubifsmount ubi0:rootfs For now, I added chattrby Nematocyst - Debian
Ok, I fixed it. Suspecting there might be a problem with u-boot's decompression, I disabled compression on that file. chattr -c /boot/uImage cp /boot/uImage /tmp/uImage cp /tmp/uImage /boot/uImage lsattr /boot/uImage 1) disable compression 2) copy it elsewhere 3) copy over the existing one since step 1) only changes the attributes, not the contents 4) verify it is still uncompresby Nematocyst - Debian
Holy cow. After reformatting, I get... exactly the same problem. How on earth is that possible? UBIFS: mounted UBI device 0, volume 0, name "rootfs" UBIFS: mounted read-only UBIFS: file system size: 511064064 bytes (499086 KiB, 487 MiB, 3961 LEBs) UBIFS: journal size: 9033728 bytes (8822 KiB, 8 MiB, 71 LEBs) UBIFS: media format: w4/r0 (latest is w4/r0) UBIFS: defby Nematocyst - Debian
There are solutions I can do that sort of ignore the details. Like I could set up uboot to use tftp. or I could copy the filesystem to a flash drive, and then reformat and copy back. Those would probably both work. Just then I wouldn't know what is going on and thus have no idea if it's gonna happen again, possibly to a more sensitive part of the filesystem. But given the behavioby Nematocyst - Debian
basically followed the instructions here: http://www.blaicher.com/2012/07/installing-debian-on-a-sheevaplug-into-flash/ eg: ubiformat /dev/mtd2 -s 512 ubiattach /dev/ubi_ctrl -m 2 ubimkvol /dev/ubi0 -N rootfs -m mkfs.ubifs --compr=zlib /dev/ubi0_0 mount -t ubifs ubi0:rootfs /mnt and then mkdir /tmp/rootfs mount -o bind / /tmp/rootfs/ cp -a /tmp/rootfs/* /mnt/ cp -a /boot /mnt/ to cby Nematocyst - Debian
I have debian installed on a UBIFS volume, and I get this error when booting: Loading file '/boot/uImage' to addr 0x00800000 with size 2082196 (0x001fc594)... UBIFS error (pid 0): read_block: bad data node (block 508, inode 51788) UBIFS error (pid 0): do_readpage: cannot read page 508 of inode 51788, error -22 Error reading file '/boot/uImage' /boot/uImage not found! thby Nematocyst - Debian
I got two dockstars in Oct 2010, both have been operating flawlessly since then. One acts as a home server, providing: Exim, Samba, mediatomb, ftp, http, and tftp. The rootfs is on a flash drive running Wheezy. The other is a print server connected via WiFi. It plays chess 24/7 at http://www.freechess.org. It runs squeeze from NAND and includes an updated G++ (4.8) in order to keep the eby Nematocyst - Off-Topic
I've been just using stuff like:ssh -c blowfish -X user@192.168.2.4 firefox ssh -c blowfish -X user@192.168.2.4 gnome-terminal Isn't using VNC or other similiar service less accurate and more overhead? Cygwin/X is a reasonable free X server for windows if that's the hangup. Seems like all I give up is a desktop.by Nematocyst - Debian
Worst thing about my dockstar-- works perfectly. Get it set up and forget it, come to this forum just to see what's up, and it's populated with lots of drug ads. Kinda the internet equivalent of cobwebs, I guess. Heh.by Nematocyst - Debian
I did an apt-get upgrade and had some nasty looking stuff appear: ... Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-5-kirkwood cryptsetup: WARNING: failed to detect canonical device of /dev/root cryptsetup: WARNING: could not determine root device from /etc/fstab find: `/lib/modules/2.6.32-5-kirkwood/kernel/arch/': No such file or directory find: `by Nematocyst - Debian
This really isn't a Debian issue, but I'm hoping someone here might have some insight about why my kirkwood devices aren't as fast as I expected. (I have 2 dockstars and 1 sheevaplug) I like running chess engines on all manner of embedded devices. One device is a TRENDnet TEW-652BRP. It has a 400 Mhz MIPS 24Kc V7.4 CPU, 32 MB RAM, 4 MB flash, and runs OpenWrt. I was surpby Nematocyst - Debian
Nematocyst Wrote: ------------------------------------------------------- > ygator Wrote: > > At the u-boot prompt do the following: > > setenv usb_init "usb reset; usb start" > > saveenv > > > I tried that. Unfortunately, it didn't work on > the USB device(s) I had trouble with. I've been messing with this issue a bit and haveby Nematocyst - uBoot
I see several threads with booting issues. Mostly I think UBoot is the issue, but I don't have any real evidence. But I think this issue, whatever the cause, leads to other problems. People try to fix the boot problem and end up making things worse. I see a few support threads where that is clearly the case. I don't know what causes the booting problems, but I can say much of tby Nematocyst - Debian
$22.98 shipped, today only at: http://www.1saleaday.com/by Nematocyst - Debian
ygator Wrote: > At the u-boot prompt do the following: > setenv usb_init "usb reset; usb start" > saveenv I tried that. Unfortunately, it didn't work on the USB device(s) I had trouble with. It's interesting in that if I 'reboot' from the pogo environment, it *always* goes into debian. And if I 'reboot' from debian, it *always* goes inby Nematocyst - uBoot
I've had some tempermental USB behavior. After installing debian, I did some minor config changes rebooted, and went to pogoplug environment. Continued reboots gave me continued entry into pogoplug instead of debian, so I thought I had borked the debian somehow. Well I was actually getting behavior similar to this thread where it would sometimes boot into debian and sometimes into pogopluby Nematocyst - uBoot