Joey, > Right now I have no Mints installed on hard drives > , I was using live USB sticks. For the next few da > ys I'll be wrapping up maintenance on a few comput > ers and should have a spare hard drive after that. It's a good idea! Live USB is good enough, but you're not runing the same system I'm running (Mint 18.x Cinamon) so it is a little hard forby bodhi - Off-Topic
Erik, > if i do a > run scan_disk > run set_bootargs and > run bootcmd_exec > > than usb is starting correctly. Great! meaning you've resolve the problem with the envs. > > FW is not starting. To boot back to stock FW in NAND, further set up is needed. >There is a line in console abo > ut mtdparts, is this enough? The mtdparts shouldby bodhi - uBoot
> s-3.12.13-oxnas-tld-5, -n linux-3.12.13-oxnas-tld > -5? neither exist similar files before run nor aft > er. I see the "man mkimage",but not be clear about > this parameter. thanks. -n is the name of the image.by bodhi - Debian
Joey, Are you running Cinamon desktop on Mint? if not can you switch to that? And I'm not talking about Live. I meant do you have Mint with Cinamon Desktop on any of your laptop(s) or Thin Client(s)?by bodhi - Off-Topic
Joey, > Mint (at least the Live USB CinnoMint) wouldn't ge > t past root permissions You don't need root for this USB drive. It is for testing pupose, so data is good enough. Use the Mint menu (just like in Windows Start menu). Go to the Acessories submenu and format it as Ext2 or Ext4, does not matter. After you've formatted it, use the mouse/touchpad right buttonby bodhi - Off-Topic
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > It didn't probably connect but here's the exact re > sults just so you know: > > > root@DebianPlug:~# df -h > Filesystem Size Used Avail Use% Mounted on > udev 10M 0 10M 0% /dev > tmpfs 12M 400K 12M 4% /run > /dev/sda1 7.by bodhi - Off-Topic
OK. So it does not look like it's working. I guess I will need to set it up and see for myself if I got the same behavior!by bodhi - Off-Topic
Erik, If you have serial console then don't use nc. Connect serial console and power up. Interrupt netconsole and setenv preboot saveenv reset Let it boot.by bodhi - uBoot
SAMBA instruction will come later!by bodhi - Off-Topic
root@DebianPlug:~# mount /dev/sdb1 on /media/JoeyUSB3 type ext3 (rw,noatime,data=ordered) This is great so far! Now check capacity df -h Now just copy some files and measure the time: cd /media/JoeyUSB3 time cp -a /boot/vmlinu* . sync chekck the files sizes ls -lh vmlinu* Download a large file (this is the kernel source code): wget https://www.kernel.org/pub/linux/by bodhi - Off-Topic
Kernel linux-4.4.54-oxnas-tld-1 package was uploaded. Please see 1st post for download link.by bodhi - Debian
Wes, The envs is a wrong set! when you flashed the new u-boot, you did not do step 8 to flash the default envs image that came with it. Quote8. Flashing default u-boot envs image: As described in step 1, u-boot envs must be defined in etc/fw_env.config as # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000 A special seby bodhi - Debian
Erik, Glad that you have the new u-boot installed! Netconsole does not output more than what you saw. It always stops at Starting kernel ... There is no output after this. Unless you set it up further in Debian. So try to find the Stora in the network. Are you using DHCP (the 4.4 rootfs default settings for ethernet)? - ping debian.local - look for a new IP appear in the router orby bodhi - uBoot
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