Joey, 1. If the disk is high capacity, Ext3 will take a long time. 2. It must be sdb1 (sdb is the whole disk). sdb1 is the partition to be formatted. mkfs.ext3 -L JoeyUSB3 /dev/sdb1 Or you can try ext4. Ext4 will be very fast (it only partially formats the partition, and will slowly perform a background task to complete). mkfs.ext4 -L JoeyUSB3 /dev/sdb1 ----- BTW, my USB-molexby bodhi - Off-Topic
nielsek, Yes it will work the same way whether it's Dockstar, GoFlex, or Zyxel. Here is the layout. This header has a unique layout where the missing pin (2nd from right) can be used as the reference point . Zyxel NAS326 Serial Pinouts (same as NSA325 and NSA310S/320S) GND RX TX +----+----+ | | | +----+----+----+----+----+ |3.3V|by bodhi - Debian
nielsek, > Should I do that or is it safe to t > ry something else? I'm a bit scared changing (bac > k) the uboot env's to stock mode. Below my envs f > or booting and information about mtd's. One is wi > th a bad block. You are right to be careful. No, it is not safe to change u-boot envs to something else if you don't have serial console, becauseby bodhi - Debian
Joey, > > Do you have log of fdisk /dev/sdb ? > > I don't think so and don't know the code. This tim > e I've un-formatted the USB stick and here's some > results: You did already! here: > root@DebianPlug:~# fdisk /dev/sdb > > Welcome to fdisk (util-linux 2.25.2). > Changes will remain in memory only, until you deci > de to wby bodhi - Off-Topic
Do you have log of fdisk /dev/sdb ?by bodhi - Off-Topic
> > root@DebianPlug:~# mkdir -p /media/JoeyUSB3 > root@DebianPlug:~# mount /dev/sdb1 /media/JoeyUSB3 > mount: /dev/sdb1: can't read superblock > root@DebianPlug:~# > > Joey, This is a low level file system software error, not hardware. So your process to partition and format might have been faulty. At the shell commandline (root@DebianPlug:~#): umounby bodhi - Off-Topic
Well, you did not follow the instructions! http://forum.doozan.com/read.php?2,28710,33189#msg-33189 > You can see the tarball didn't extract the first t > ime, that was just because I still had the file in > my /Downloads instead of on the card. So it did extract OK now? > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. This likelyby bodhi - Debian
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > Wow, that thought never occurred to me. I could tr > y a higher power supply, maybe an eCigarette charg > er or maybe you have a cellphone USB charger... Sure, that would be better than power it up after.by bodhi - Off-Topic
Erik, It should be set to 0xc0000. As stated in the instruction. has the offset to be 0xc0000 --> __nand_correct_data: uncorrectable ECC error This error is expected, you can't access this location until after you install new u-boot. Stock u-boot defined envs at a different location.by bodhi - uBoot
Wes, Your rootfs will not work. As I mentioned often, when you install either u-boot or rootfs, you should run the commands from the instruction exactly as it stated. Don't try to change to something you think is compatible. If for whatever reason, the commands are not working, then you should post that log, and I will help explain why! Here is the installation instruction (I remby bodhi - Debian
It looks like we don't have enough power. The card must be drawing too much power upon power up. I'll to try either plugging in after booted, or with a separate power source (such as USB charger) for the USB power connector end.by bodhi - Off-Topic
Erik, If you are extra careful, you should adjust the mtdparts in bootargs so that it looks like this in Debian: # cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "u-boot" mtd1: 00400000 00020000 "uImage" mtd2: 02000000 00020000 "rootfs" mtd3: 0db00000 00020000 "data" Note that this definition will not allow you to run stby bodhi - uBoot
Erik, It looks OK. mtd0 is where it is important. As long as it is correct then you can install u-boot. These NAND ECC errors are shown in some boxes before installating u-boot (old u-boot wrote the envs differently, and you are using newer fw_printenv from the rootfs). Your bad blocks are OK (in different region away from mtd0): [ 1.843066] Scanning device for bad blocks [ 1.87by bodhi - uBoot
Erik Wrote: ------------------------------------------------------- > Hi Bodhi, > > I have found the error in this code: > > > setenv usb_set_bootargs 'setenv bootargs console=$ > (console) root=$(usb_root) root=LABEL=rootfs' > > > It works when i change console=$(console) to $cons > ole > My usb_set_bootargs looks now like this: >by bodhi - uBoot
oleteacher Wrote: ------------------------------------------------------- > Your help solved the issue bodhi, thank you! > > Now I will have to read up on installing new uboot > and debian. Basically all I am wanting to do is se > tup PHP development area (and attached two USB dri > ves) so we can use it in classroom project. > > Thank you again, > > Suby bodhi - Debian
> So i think fw_tools are supported with kernel 4.4. > 0 and higher. > Question: Does kernel 4.4.0 support envir-tools? Yes it does. If you are not sure how to get through some error while instalingl u-boot, post the the entire log of what you did, and I will point out where the error is.by bodhi - uBoot
Last post moved here;: http://forum.doozan.com/read.php?3,33178by bodhi - uBoot
Wes, http://forum.doozan.com/read.php?2,12096 QuoteUpdated 20 Feb 2016: This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1. Basic minimal Debian Kirkwood rootfs for most Kirwood plugs: - tarball size: 137M - install size: 398M - a basic jessie rootfs. - The init system used in this rootfs is sysvinit . To bootby bodhi - Debian
No luck. I went ahead and I swap the Molex black and yellow wires before plugging it in, it would not start the box at all. Could be the connector is already correct. Back to the drawer for another day :)by bodhi - Off-Topic
Susan, Yours is an older version of u-boot. Again, posting the serial log from the u-boot banner would help telling me right away which version. For example, the log should begin here: QuoteU-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700) Pogoplug V4 But based on the envs, looks like 2014.xx version? Here is the problem: 1. You have chosen to boot with the DTB appended to uImageby bodhi - Debian
:) the problem is easy to solve if you do this: Quote1. Power up, interrupt serial console and printenv boot Please post the entire serial log, from u-boot banner until the initramfs prompt (this is where the rootfs could not be mounted, so the kernel throw you out to the temporary rootfs).by bodhi - Debian
youxiaojie, Quotepreboot_nc=run if_netconsole start_netconsole # wihout judge whether pc running nc or Hercules ready or not? u-boot netconsole is always running. That preboot_nc, which is executed by preboot, is just to check for netconsole server by pinging it, and then route the stdin/stdout/stderr to nc console. Quotepreboot_nc = setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleeby bodhi - uBoot
Susan, > Finally got around to gaining SSH using serial met > hod. All seemed to go well. > Used "Updated 24 Feb 2015" @ http://forum.doozan.c > om/read.php?2,12096 to create on SD card. Is this the Pogo V4 box? That's the 3.18.5 rootfs. Not the latest, but it should be OK. > > Looking at serial console everything seems to go g > ood until:by bodhi - Debian
Joey, Not yet! but I will try later today or tomorrow.by bodhi - Off-Topic
Erik, Yes I would recommend installing new u-boot and its default envs. After that, you will not need to change envs to boot with multiple drives attached. No need to run envs script either.by bodhi - uBoot
drdos5, I will add this config to my next kernel relase.by bodhi - Debian
Wes, Your box is in good shape with new u-boot installed. Now your problem is the SD card. You will need a Linux box or Linux VM to untar the rootfs Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 to it as root user. Using Windows will never work.by bodhi - Debian
Erik, I totally forgot that you are running stock u-boot :) with stock u-boot, the envs need to be sightly different: setenv usb_set_bootargs 'setenv bootargs console=$(console) root=$(usb_root) root=LABEL=rootfs' But once you install new u-boot, the syntax will work either way. So I'd recommend doing that after you have running Debian, and want to boot with multiple drby bodhi - uBoot
Rolandcharcker, > I have a goflex home and all of a sudden the start > up LED contines to blink, regardless of how long l > leave it on. I have checked power, hard drive moun > ting, ethernet cable changed etc. If you are running stock FW, the only thing that could get your box fixed is: - Do the FW reset as the support website instructed. - If the FW reset does not worby bodhi - Debian
helge, If the bootargs is that simple and we could not get it to run, most likely the DTB is wrong one. These have the same SoCs: NSA310S NSA320S Pogo V4 So perhaps we want to try all 3.by bodhi - Debian