On Wed, 25 Mar 2015 21:00:03 +0100, "Jim MacKenzie" <j...@photojim.ca> wrote: >If your SheevaPlug is already running Debian and you simply want to upgrade >it, you can upgrade to Debian 7 in-place. This requires a firmware upgrade >to the SheevaPlug (in some cases) as the Debian 7 kernel isn't compatible >with older versions of the SheevaPlug's boot loader. I just upgraded my two >SheevaPlugs a few weeks ago.
I've been running Debian on that device for about a year, and would like to upgrade to the latest stable kernel, and also either move the whole thing from the SD card (where I think it's living) to the NAND, or replace the current SD card with a new one, since dmesg isn't happy: ========= # dmesg | tail [42113305.934129] mmcblk0: error -110 transferring data, sector 1230482, nr 6, c md response 0x900, card status 0x0 [42113305.944295] end_request: I/O error, dev mmcblk0, sector 1230482 [42113306.123221] mmcblk0: error -110 transferring data, sector 1230480, nr 8, c md response 0x900, card status 0xb00 [42113306.133560] mmcblk0: retrying using single block read [42113306.306724] mmcblk0: error -110 transferring data, sector 1230480, nr 8, c md response 0x900, card status 0x0 [42113306.316885] end_request: I/O error, dev mmcblk0, sector 1230480 [42113306.490929] mmcblk0: error -110 transferring data, sector 1230481, nr 7, c md response 0x900, card status 0x0 [42113306.501094] end_request: I/O error, dev mmcblk0, sector 1230481 [42113306.676773] mmcblk0: error -110 transferring data, sector 1230483, nr 5, c md response 0x900, card status 0x0 [42113306.686937] end_request: I/O error, dev mmcblk0, sector 1230483 ========= How can I 1. Check what the NAND contains? I assume Uboot lives in the first block, and the other two are empty: ========= # cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "u-boot" mtd1: 00400000 00020000 "uImage" mtd2: 1fb00000 00020000 "root" ========= # mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=63463,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=51516k,mode=755) /dev/disk/by-uuid/b1767040-9366-43c0-9684-3a8ff83f6547 on / type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=146840k) /dev/mmcblk0p1 on /boot type ext2 (rw,relatime,errors=continue) ========= 2. Upgrade to the latest Debian, and replace the SD card? I was thinking of backing up user data to an other host, shutting it down, replacing the SD card, download a workable image through TFTP, perform a fresh install, and restore user files. >As for /tmp etc., you will extend the life of the SD card if you do that but >I haven't had great problems with SD card life as long as you buy >high-quality ones (cheap ones can be a problem though). Use the "noatime" >option in /etc/fstab to disable file access date recording; that will reduce >writing to the disk by avoiding writing to every file when it's read. I'll check it out. Currently, /etc/fstab says this: ========= UUID=b1767040-9366-43c0-9684-3a8ff83f6547 / ext4 barrier=0,errors=remount-ro 0 1 # /boot was on /dev/mmcblk0p1 during installation UUID=45b3b845-431e-4278-b97d-6d61328171fb /boot ext2 defaults 0 2 # swap was on /dev/mmcblk0p5 during installation UUID=36b91ac2-8b5f-4ec9-ac4b-4127407d8477 none swap sw 0 0 ========= Thank you. -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/dta6ha52kv7c4p03t7qkstiv8jrnuu9...@4ax.com