I just found that I have by accident overwritten the label rootfs setting. Now I have set it correct again and everything works perfecly. I can boot from SATA with any number of usb devices connected without failing. And if I insert the usb_rootfs it will boot from the usb stick. Thanks bohdi for your help and patience :)by amyren - uBoot
Thanks bodhi You think the new uboot envs will improve the usb issues? I have done a bit testing with different usb sticks connected. I had this 4 port usb hub connected earlier (before I got SATA boot working) and then this booted fine with one usb_rootfs stick and two other usb sticks (8GB + 16GB). I actually had them set up as a raid stipe, just for testing. After this I tested the folby amyren - uBoot
Thanks for the help so far:) I did add some of the lines from the first post. Now things are working almost as I want it. I am now able to boot both from USB and SATA disk. If USB is atatched, it will boot from it, otherwise from SATA. But if I boot with some other usb sticks attached, it will fail during boot. Her is my current env: # fw_printenv ethact=egiga0 bootdelay=3 baudrateby amyren - uBoot
All done updating then. Do I need to make any changes to make it boot from SATA? It still does not boot from my SATA hdd. I did make a 5G ext3 partition on the disk, made it bootable, labeled it rootfs, copied everything from the usb stick onto it, second partition is 512MB swap, and the third is EXT4 with the rest of the disk space. It boots fine with usb attached, as before. I tried toby amyren - uBoot
Doing the flashing by your instructions now. Doing it from SSH, I didnt wait long enaugh to see your serial console advice, I hope this will still be ok. In my case I got an error at making the nanddump backup (nanddump: command not found) But after doing "apt-get install mtd-utils" it was ok. But at 6. I get a slightly different output than you wrote: #flash_erase /dev/mtd0 0by amyren - uBoot
bodhi Wrote: > Which u-boot version you have installed? It looks like its 2011.12 # grep -a --null-data U-Boot /dev/mtd0ro U-Boot 2011.12 (Apr 18 2012 - 23:08:20) Seagate GoFlexNetU-Boot ** Invalid partition type "%.32s" (expect "U-Boot") U-Boot BUG at %s:%d! Edit: I notice that latest uboot is 2014.07, which makes my uboot very old. So I guess I should updaby amyren - uBoot
I have set up my goflex net to boot from label rootfs. I have set up a partition on the SATA, copied the rootfs from the sub stick onto, set the bootable flag, and labeled it rootfs, but it still doesnt boot up from the SATA drive. My goal is to have set this up so it can boot from both usb or SATA if the partition is labeled rootfs. Preferably it should boot from usb stick if both are present, bby amyren - uBoot
The solution was easier than expected. I did download the latest wheezy based rootfs (ver. 3.17.0) and installed it into an usb stick according to the instructions. After booting the goflex net with the stick, I performed this procedure: rm /etc/ssh/ssh_host* ssh-keygen -A echo "deb http://packages.openmediavault.org/public kralizec main" > /etc/apt/sources.list.d/openmeby amyren - Debian
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > Pardon my interruption, but OMV's own demo is > currently on the blank side as well: > http://demo.omv-extras.org/ > No idea why. At least their demo page source code is not blank:) I also did get a blank page earlier when I installed it on an older (squeeze) rootfs, and tried with OMV v0by amyren - Debian
Back to the OMV issue: I have made myself a sort of a "step by step guide" on how to get OMV installed without getting any dependency or broken packages errors. And everything looks good, exept for the problem that the webgui does not work (only a blank page is displayed) Start with fresh install with latest rootfs (3.18.5 and kernel update 4.2.0) rm /etc/ssh/ssh_host* sby amyren - Debian
bodhi Wrote: ------------------------------------------------------- > Quotemount: mounting /dev/disk/by-label/rootfs > on /root failed: Invalid argument > > This error points to the mismatch in bootargs > and/or fstab. Here is the problem > > usb_rootfstype=ext2 > > > Boot and interrupt serial console, remove this env > and then boot > > setby amyren - Debian
I think something is still not as it should be. The usb stick I'm using was made using the instructions on this forum, http://forum.doozan.com/read.php?2,12096 And I did format it as ext3, and edited the fstab file as well. This usb stick did work and I used that to try to install OMV. I do have an image file backup of this, and have restored this several times. But now, I use the samby amyren - Debian
Thanks for the quick reply. I did just unplug my usb and it booted right into rescue, so that makes me feel rather stupid.. First time I applied that boot rootfs it failed to boot anything, not even the rescue system. But I did do one change after this. Because when it failed to boot, I had to look for a serial adapter to connect to the box. Then I noticed that it was looking for ROOTFS (cby amyren - Debian
I just got my Goflex Net a couple of weeks ago, and at first I was thinking of putting openwrt on it. But after googling around I read that debian/openmediavault was a better choice. I have through some of the (outdated) guides out there, and had a few headaches along the way. .. getting the blinking orange led, making an usb_rescue and installed the rescue system to the flash. Started with squeby amyren - Debian