Everything looks normal. Except for that Ext2/Ext3 mounting. It doesn't hurt to run it that way, but it's best to change usbrootfs_type to Ext3 to get the journal going so it will be resilient to unexpected power outage. The HDD was assigned as /dev/sda and the rootfs partition is sda1, so it is normal too. HDD used to be assigned has hda/hda1.. , but the kernel has changed the way tby bodhi - Debian
Yes, you should change your uBoot env for usbrootfs_type to ext3. And pls post the full dmesg log.by bodhi - Debian
If apt-get upgrade caused this file to be updated: /boot/initrd.img-3.11.1-kirkwood-tld-1 then the uInitrd should be regenerated.by bodhi - Debian
dinjo Wrote: ------------------------------------------------------- > Thanks I'll look into your netconsole thread you > mentioned sometime back if i do a apt-update and > upgrade i dont need to do flash the kernel so does > that mean i just add netconsole module command in > conf file ? It's in the instruction: modify the modules file, update initramfs file, anby bodhi - Debian
I'm eager to find some free time this weekend to try the Emdebian install. Thanks!by bodhi - Debian
dinjo Wrote: ------------------------------------------------------- > Thanks booting from SATA drive now.I have some > final questions. > > 1. When I issue a shutdown command the LAN light > on router does not goes off I guess that because the GoFlex Net power is still on (it's normal). Power is not off completely on these plugs. But you've shutdowned so the oby bodhi - Debian
I would use a swap file. It is much more flexible (e.g. you can turn on/off swap in /etc/rc.local). Yes, the instruction for creating the rootfs on USB thumb drive specified one partition. That was to simplify the booting process only. You can use as many partition as you need, as long as only the rootfs partition is labeled rootfs. There are plenty of space on the HDD, so the rootfs should beby bodhi - Debian
dinjo, Ext3 rootfs should be very reliable. I think it is best that you move the files out and reformat. Upgrade from Ext3 to Ext4 is straight forward, but downgrade is a pain. You udev rules is too complicated. I can't judge it easily!. You should worry about booting with HDD first, udev rules can come after.by bodhi - Debian
lewy1 Wrote: ------------------------------------------------------- > Thanks bodhi. > I ttok a look at the post you linked to. Just to > make sure I get it right, how do I check if my > uboot requires ext2 or ext3? Also after installing > the rootfs what's the next step? Sorry I'm not a > linux expert and have forgotten some of what I > knew. It's beeby bodhi - Debian
dinjo, This looks good for booting with USB, and SATA in this order (if the rootfs is on USB then it will boot, if not then boot SATA): Can you verify these are the commands i need to run to boot from sata fw_setenv sata_boot 'ide reset; mw 0x800000 0 1; ext2load ide 0:1 0x800000 /boot/uImage; if ext2load ide 0:1 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0xby bodhi - Debian
dinjo, Looks great :) this ubifs error is expected, can safely be ignored. It's really depend how you use the GF Net. If you want to mount NTFS HDD so that you can unplug it and connect it on Windows, then I would boot with USB, but more setup step needed to make sure you don't wear out the USB thumb. The safest and best way is to boot with HDD rootfs. A few uBoot envs need toby bodhi - Debian
The server side is your Pogo E02? should be 192.168.1.104 Your GoFlex Net should be 192.168.1.110 (verify it with ifconfig like you did) Server side has to be running these 2 nc commands first. And then reboot the GoFlex Net. And remember to backup your GoFlex Net rootfs, since you are going to modify it quite a bit with apt-get upgrade.by bodhi - Debian
dinjo Wrote: ------------------------------------------------------- > Whats the difference between flashing kernel and > doing apt upgrade ? I flash kernel then do a > upgrade or other way around or both are > independent They are independent: apt-get upgrade only updates the current packages to latest version in wheezy. So don't worry about kernel. Kernel update sometby bodhi - Debian
No need to, you've already running my latest kernel and latest rootfs. This rootfs has kernel 3.11.1 and the apt source is wheezy (look in /etc/apt/sources.list). So from now on, from time to time when you want to get the latest package versions, then: apt-get update apt-get upgrade You don't really need to update the kernel, if you don't need the latest changes. But if youby bodhi - Debian
dinjo, Congrats! you are all set. I would not bother with rescue system. If you set up netconsole, and test it to make sure it is working, you don't need rescue system at all. If you encounter any problem in the future, then just use netconsole to monitor uBoot, get into uBoot prompt and recover. Rescues system also had caused some problems lately for some users, so if you can do withoutby bodhi - Debian
lewy1, Currently, Jeff's Wheezy script has problem with debootstrap. You should run the installation again with the Squeeze script and then after booting into Debian, upgrade to Wheezy. If even the Squeeze script does not work then try this rootfs 3.11.1 (you've already installed uBoot successfully). http://forum.doozan.com/read.php?2,12096by bodhi - Debian
While in Debian, pls get the output of dmesg fw_printenv mount and post here.by bodhi - Debian
dinjo Wrote: ------------------------------------------------------- > I have done that exactly the same way > New USB stick formatted with Ext3: meaning using fdisk to delete all existing partitions, and create one and only one Ext3 partition. Also, in fdisk, make sure that the stick is MBR not GPT. > Could changing URL_BOOTSTRAP have caused some > issue ? Does not affecby bodhi - Debian
OK, let state the instruction from this thread http://forum.doozan.com/read.php?2,12096 once more time. Updated 01 Oct 2013: Rootfs 3.11.1 was uploaded. This rootfs is to keep in sync with kernel Linux-3.11.1-kirkwood-tld-1 (and its new features). ..... Installation: - format a new ext3 USB drive, and label it rootfs (this means only one Ext3 partition on this USB stick). - cdby bodhi - Debian
I think it's likely running out of RAM. When you run Debian on the Pro, a big junk of memory is taken already. It's best to have swap on USB, even though you don't intent to use it in normal operation. Use a swapfile so it can be turned on/off easily in rc.local.by bodhi - Debian
dinjo1 Wrote: ------------------------------------------------------- > I'll reach home and try again but i'm confused > since the rootfs is 3.11.1 kernel compatible and > device is flashed with 2.6 kernel is it expected > to boot ? > > Serial Cable and how to open and connect the > device ? The device is not flashed with kernel. The script only flashedby bodhi - Debian
Jeff's Squeeze script flashes kernel 2.6.3x.xx to the USB drive. The only thing that's changed in NAND is mtd0 for uBoot. Since your uBoot installation was good (according to the log), the problem is with the USB rootfs that you're using. So that's why I think it's worth trying to create USB boot drive using my uploaded rootfs. If you can post the log of how you create tby bodhi - Debian
Ah! then I am not sure. Because it works fine on GoFlex Net. I might have to check the ALARM patch to see if they have updated it since I extracted the patch a while ago. The new patch to the 3 files I mentioned above should work the same way on GoFlex Net and NSA320. @pbg4, Did this patch work in your build?by bodhi - Debian
dinjo Wrote: ------------------------------------------------------- > SInce the script has several issues in it i had to > run some times and I have seen there were no > issues installing uboot, the log is mentioned in > first post itself I see. uBoot installation does look good in this: # Validating existing uBoot... Block size 131072, page size 2048, OOB size 64 Dumpby bodhi - Debian
Thanks Warhead. Yeah, understood. There is no backplate to remove then!by bodhi - Debian
Guys, Does it look like the back plate of this Nsa320 can be removed ? I saw only 2 top screws. I would get this box if I can run it without the fan. Thanksby bodhi - Debian
Do you have the log when you run dockstar.debian-squeeze.sh the first time? It shows how uBoot was installed, and anything abnormal occurred during that step. Blinking green and never got to solid green means that either the kernel (uImage) and initrd (uInitrd) were not loaded successfully. But it does not mean the box is bricked. If you have installed uBoot (part of the squeeze script) succesby bodhi - Debian
dinjo Wrote: ------------------------------------------------------- > I don't know which kernel did the squeeze script > flashed hence i was asking this ,i tried your > rootfs too blinking green and then lights goes > off. To prepare the rootfs, log on to another Linux box as root user, format a USB stick as Ext3, and follow the rest of the instruction to extract the roby bodhi - Debian
dinjo, Read the instruction! the rootfs has 3.11.1 kernel. Meaning the rootfs kernel is later than 3.9.x, 3.10.x.... :)by bodhi - Debian
gaogao, Did you try to turn on/off each HDD LED with echo? what do you see with these (in various order): echo default_on > nsa320:green:hdd1 echo default_on > nsa320:green:hdd2 echo none > nsa320:green:hdd2 echo none > nsa320:green:hdd2by bodhi - Debian