For some crazy reason I tried to update my Seagate Dockstar running squeeze to wheezy and in the process of finding all the web links from almost 3 years ago I either hosed something up, or the new scripts have bugs I didn't work around correctly. It was late. I was shall we say 'not wise'. Help appreciated.
Updating squeeze => wheezy via "apt-get dist-upgrade" gave me a spinning disk (a real Dockstar 500 GB disk) that doesn't boot. Eventually the dockstar seems to power itself down, as the light goes off, which surprised me a bit. Initially it 'used to' fail nicely to the NAND os so I could at least get in via ssh, but now I don't think it's getting there.
I 'think' what I did was answer yes to Jeff's question about slamming the uboot settings with reasonable defaults, but at this point I'm not certain. I did notice that the nc stuff wasn't there, which I put back via fw_setenv. I also noticed the usb_rootfs type was ext2 which I switched to ext3 to match the other (not broken (yet) dockstar that matched this one).
The box is not totally dead, I booted it on a gigabit switch and do get some nc console info (attached). I do not have a JTAG cable, but since it's talking at least somewhat on the network, would there be a network restore / update path that I might try ?
Lastly, not having updated the dockstar in a few years I'm a little lost knowing whose update script to run for the NAND os, whose to run to get wheezy installed, and which bugs I need to work around in the various scripts. Seems like there are a lot of scripts and images out there each with some nuances that seem to be tripping folks up.
I guess what I'd like to do is get it back one the network ok for ssh access, then update whatever uBoot stuff needs to be updated, then reinstall Debian cleanly ala an initial install.
I'd be thrilled to just reinstall squeeze and get it back where it was before. Getting to wheezy would be better. Any help/ideas/pointers definitely appreciated.
Here's the nc capture with 'no' disks etc. attached to the dockstar...
Updating squeeze => wheezy via "apt-get dist-upgrade" gave me a spinning disk (a real Dockstar 500 GB disk) that doesn't boot. Eventually the dockstar seems to power itself down, as the light goes off, which surprised me a bit. Initially it 'used to' fail nicely to the NAND os so I could at least get in via ssh, but now I don't think it's getting there.
I 'think' what I did was answer yes to Jeff's question about slamming the uboot settings with reasonable defaults, but at this point I'm not certain. I did notice that the nc stuff wasn't there, which I put back via fw_setenv. I also noticed the usb_rootfs type was ext2 which I switched to ext3 to match the other (not broken (yet) dockstar that matched this one).
The box is not totally dead, I booted it on a gigabit switch and do get some nc console info (attached). I do not have a JTAG cable, but since it's talking at least somewhat on the network, would there be a network restore / update path that I might try ?
Lastly, not having updated the dockstar in a few years I'm a little lost knowing whose update script to run for the NAND os, whose to run to get wheezy installed, and which bugs I need to work around in the various scripts. Seems like there are a lot of scripts and images out there each with some nuances that seem to be tripping folks up.
I guess what I'd like to do is get it back one the network ok for ssh access, then update whatever uBoot stuff needs to be updated, then reinstall Debian cleanly ala an initial install.
I'd be thrilled to just reinstall squeeze and get it back where it was before. Getting to wheezy would be better. Any help/ideas/pointers definitely appreciated.
Here's the nc capture with 'no' disks etc. attached to the dockstar...
U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported
** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 219 MiB
UBI: number of good PEBs: 1750
UBI: number of bad PEBs: 2
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 1729
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: ....... read_nand_cached: error reading nand off 0x9b2000 size 8192 bytes
. done.
read_nand_cached: error reading nand off 0x9b1800 size 8192 bytes
off = 0x9b11e0 magic 0x1985 type 0xe002 node.totlen = 1880
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...