Posts by cadre

    sorry, here's the feedback.


    Code
    root@debian:~# cat /etc/apt/sources.list
    deb http://ftp.us.debian.org/debian wheezy main
    deb http://security.debian.org/ wheezy/updates main contrib non-free
    root@debian:~# ls /etc/apt/sources.list.d/
    .  ..  openmediavault.list  openmediavault-local.list
    root@debian:~#


    Also

    Code
    root@debian:/etc/apt/sources.list.d# cat openmediavault.list
    deb http://packages.openmediavault.org/public kralizec main
    root@debian:/etc/apt/sources.list.d# cat openmediavault-local.list
    deb file:/var/cache/openmediavault/archives /root@debian:/etc/apt/sources.list.d#


    Thanks for the help

    Thanks for the update, but should I be able to see the list of plug-ins via the web interface?


    Currently when I click on Plugins I get the same error message.



    If I'm logged in via SSH and issue "apt-get update" I get this error message.


    I've checked everything I know to check but obviously I'm still missing something. Any ideas?

    I'm currently running 0.6.0.16 krazilex on a pogoplug armel platform using the backported 3.14 kernel.


    I've installed the omv-extras.org plugin, but before I installed the plugin and afterwards; every time that I click on "Plugins" section via the web-interface I get the following error message.


    Code
    Error #6000: exception 'OMVException' with message 'The index of available plugins does not exist. Please re-synchronize the package index files from their sources.' in /usr/share/openmediavault/engined/rpc/pluginmgmt.inc:73 Stack trace: #0 [internal function]: OMVRpcServicePluginMgmt->enumeratePlugins(NULL, Array) #1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array) #2 /usr/share/openmediavault/engined/rpc/pluginmgmt.inc(117): OMVRpcServiceAbstract->callMethod('enumeratePlugin...', NULL, Array) #3 [internal function]: OMVRpcServicePluginMgmt->getList(Array, Array) #4 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array) #5 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('getList', Array, Array) #6 /usr/sbin/omv-engined(495): OMVRpc::exec('Plugin', 'getList', Array, Array, 1) #7 {main}


    Not sure if I've got an installation error or maybe there just isn't any plug-ins yet for the armel platform?


    Thanks

    I just did another fresh install with a Wheezy 7.5 amd64 net.iso and omv install from apt sources and I still get 502 Bad Gateway.


    I know this is pretty simple and straight forward (so much that there really isn't much to get wrong) but after four times with the same results, now I'd have to ask when is the last time that you could did a successful install of kralizec?

    Just an update. I know kralizec is still beta but I've tried to install it from apt three times in the last two days. One from the armel source and two from the amd64 sources.


    All three installs have gone the same but ending with "502 Bad Gateway, nginx" when trying to browse to the OMV web interface.


    Still doing some investigation, more curious if anyone else had seen this?

    Just a note, I'm trying to install kralizen on an Armv5 (Pogo-E02) platform.


    Interesting update, I tried to save some time by using bodhi's latest rootfs based in wheezy taken from http://forum.doozan.com/read.php?2,12096


    The installation was very quick and straight forward and I was running kernel 3.14 on wheezy in a matter of minutes.


    Running as root I updated everything and proceeded with the following installation sequence

    Code
    echo "deb http://packages.openmediavault.org/public kralizec main" > /etc/apt/sources.list.d/openmediavault.list
    apt-get update
    apt-get install openmediavault-keyring postfix
    apt-get update
    apt-get install openmediavault
    omv-initsystem


    This time there were no errors, but after the installation finished I tried to browse to the omv web interface. The webpage simply displayed "Bad gateway, ngnix"


    I did notice that the "locales" package wasn't installed, so I installed it and configured it to UTF-8.


    Reluctantly I rebooted in hopes of the problem being addressed but now that the system has rebooted, SSH is disabled and I currently don't have console access.


    So I'll try again from scratch, if not configure a working serial console first.

    unfortunately, it's the same as before.



    I don't want to waste your time. I'll start over from scratch and see what happens. Thanks

    Here's the output...


    Code
    root@debian:~# cat /etc/apt/sources.list.d/openmediavault.list
    deb http://packages.openmediavault.org/public kralizec main
    root@debian:~#

    I tried to remove and reinstall of openmediavault and these are the last few lines after issuing "apt-get install openmediavault" Again this isn't all of the output.



    If there is an easy way to completely scrub any OMV data or files I'd be happy to do that. Really just trying to avoid installing wheezy from scratch but if that's what it comes to so be it.


    Any ideas? Thanks for your time.

    I'll post the exact error message later today when I get back home. I did originally have OMV .4 installed but I completely removed it before upgrading to wheezy. I tried to purge any and all OMV related files or remnants before wheezy. Are there any usual suspects that I should check or remove?


    Upgrading to wheezy was smooth. I'll try to install OMV again tonight and will post my error messages if I have any. Thanks.

    Quick question, I tried to install OMV after installing Wheezy onto an armv5 (kirkwood) system but I've run into the same problems as s711.


    Is it possible that the php5-pam and php5-proctitle files in the repository aren't compatible with the armv5 cpu too?

    Any update on whem DNSMasq might be available? Really looking forward to having this one to use. Thank you for your time and efforts.

    Call it luck or whatever, but I've been running ubuntu minimal server install 12.04 LTS for over two years. Before the upgrade I was running 11.04 off a Sandisk Cruzer Professional 8gb key. Still running strong 24/7/365.


    http://www.amazon.com/dp/B00169R1H4


    Also use this running OMV for a pogoplug for over a year too.


    For $7 shipped I guess I'll press my luck...

    I've had one of these Intel ss4200 systems to do the same exact thing of reporting the CPU temp at 72C (which I knew wasn't true).


    In my case with no OS loaded, nor even hard drives attached; I could power the system on and go into the bios under Hardware Monitor and see that the CPU temp immediately reported 72C which also caused the fans to run at max speed.


    Ultimately the motherboard was replaced, but alternatively I could have manually set the speed of the two case fans in the bios because I know the system was not overheating.


    You need to connect a serial console or video card via a PCIe-1x extension cable to see what your system is reporting in the bios. See attached pictures, note the difference in fan speed too.

    Pogoplug POGO-E02 Debian / Openmediavault install notes


    I had multiple problems trying to install Debian (and OpenMediaVault) on my pogoplug and couldn't find all of the answers in one place, so this is my attempt to try and consolidate all of my steps that I took to accomplish this.


    I realize that some, if not most of these commands are not needed for the more veteran people, but this is geared towards the noobs...so bare with me.


    Preparing the drive


    I'm using an 8gb Sandisk Cruzer Professional usb drive, but I'll create partitions that would fit on a 4gb drive because I'll plan to use USB Image Tool to create "device" backups that I can compress (hopefully without data loss) and restore on other available USB drives if needed. Before I plugged it into the pogoplug, I put into a Win7 machine and started up diskpart to completely "clean" and erase the drive before use.


    Note: Realize what you're doing here, DON'T select the wrong drive to clean, or you'll be sorry!


    Start, Run, diskpart


    list disk


    select disk # (# = your usb drive)


    clean


    exit


    the usb drive is now completely erased and empty


    Installing Debian Squeeze


    Main project page is here
    http://projects.doozan.com/debian/


    Now, SSH to the pogoplug. Default login is root and default password is ceadmin


    just in case, kill all pogoplug call-home software with:


    Code
    killall hbwd


    plug in the usb drive into the usb port closest to the network port.


    We need to create partitions on the usb drive for debian.


    Code
    cd /tmp


    Code
    fdisk /dev/sda


    Create the primary Debian install partition


    n = new
    p = primary
    1 = 1st partition
    1 = 1st cylinder
    +2500M (your choice, I choose to create 2500Mb partition for Debain install)


    Create the swap file partition


    n = new
    p = primary
    2 = 2nd partition
    enter = choose default (continuing from the end of the 1st partition)
    +1000M = (your choice, I choose to create a 1000M partition for swap)


    change partition type for primary
    t = type
    1 = 1st partition
    83 = Linux
    change partition type for swap
    t = type
    2 = 2nd partition
    82 = Linux swap


    Set 1st partition to active for booting
    a = boot flag
    1 = 1st partition


    print partition tables to verify


    writes changes and exit Fdisk
    w


    Continue following Jeff's install for Debian Squeeze
    make sure you are in the /tmp folder, this is the only folder with read write access.

    Code
    cd /tmp


    Code
    wget http://projects.doozan.com/debian/dockstar.debian-squeeze.sh


    Code
    chmod +x dockstar.debian-squeeze.sh


    Code
    export PATH=$PATH:/usr/sbin:/sbin


    Code
    ./dockstar.debian-squeeze.sh


    After the install script finishes, it will ask if you want to Reboot now?


    Choose NO


    For whatever reason the install script doesn't seem to properly create the boot images needed to work properly so we have to manually create them.


    We need to mount the 1st partition (where Debian was installed) to the /tmp/debian folder.


    Code
    mount /dev/sda1 /tmp/debian


    Now we need to change directory to the /tmp/debian/usr/bin folder because that's where the executables files are.


    Code
    cd /tmp/debian/usr/bin


    Now issue these two commands to manually create the images needed to boot properly


    Code
    ./mkimage -A arm -O linux -T kernel  -C none -a 0x00008000 -e 0x00008000 -n Linux-2.6.32-5-kirkwood -d ../../boot/vmlinuz-2.6.32-5-kirkwood ../../boot/uImage


    Code
    ./mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-2.6.32-5-kirkwood -d ../../boot/initrd.img-2.6.32-5-kirkwood ../../boot/uInitrd


    You should have seen the Linux-2.6-32-5-kirkwood image created after the first command, and initramfs-2.6.32-5-kirkwood image created after the second command.


    We now should un-mount the usb drive before restarting


    Code
    cd /tmp


    Code
    umount /dev/sda1


    Setting up NetConsole
    http://forum.doozan.com/read.php?3,14,14


    Before rebooting the pogoplug, you might want to setup Netconsole to review the boot-up process in case trouleshooting is needed.
    This is not required at all, but optional.


    Configuring the pogoplug for your network with Netconsole


    on the pogoplug, change to the /usr/sbin directory where the fw_setenv and fw_printevn files reside


    From Jeff's post, you'll see we need to add 5 lines or variables, but substitute the "serverip" with your netconsole "server" or station to view the pogoplug boot process, and the "ipaddr" with the IP address that you'll assign to the pogoplug. Don't use an IP address that is currently in use or part of a DHCP pool for the pogoplug.


    My netconsole "server" IP will be 192.168.0.25, and I choose 192.168.0.90 for the pogoplug, so one line at a time, I entered the following.


    fw_setenv serverip 192.168.0.25
    fw_setenv ipaddr 192.168.0.90
    fw_setenv if_netconsole 'ping $serverip'
    fw_setenv start_netconsole 'setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;'
    fw_setenv preboot 'run if_netconsole start_netconsole'


    I'm using Windows so I downloaded the windows port.
    http://www.rodneybeede.com/Com…_Windows_using_MinGW.html


    I downloaded and extracted the file to a folder I created in the root of my system drive, just for quicker access from a command prompt.
    If your using Vista or Win 7, be sure to right click Command Prompt and choose "Run as administrator"
    change directory to where you extracted the files


    issue this command within the command prompt window
    nc -l -u -p 6666


    Expand the command prompt to cover the full height of your desktop


    Now on the pogoplug, we'll finally issue the reboot command.


    reboot


    Watch the netconsole window for the boot process.


    Finally, if the last line reads "Starting kernel..." then Debian squeeze sucessfully booted!


    *See attached picture*


    In my experience, the pogoplug plug booting and running Debian never uses the same IP address as before, so check you DHCP server to see what IP address was taken. Also, don’t worry about the status LED being orange, that’s normal for this version of kernel on the pogoplug.


    SSH to the new IP address.
    default login is root
    default passwor is root


    Note, if you can't SSH to it ( but know that Debian booted) then you may have to clear old SSHhostkeys from your computer.


    after logging in, check your kernel with


    Code
    uname -a


    Now at this point you're done with Debian Squeeze, and can install just about any packages you want to; but if you want to continue with installing Openmediavault read on....


    This is another area where I had many, many problems actually getting OMV to install and work, and again I could not find all of the answers in the same place.
    I know this is a little verbose for some, but this works for me...


    I'll be jumping straight to the current version of OMV which in currently the .4.x branch


    Update everything...


    Code
    apt-get update
    apt-get upgrade


    since this updates the kernel, I'll reboot here.


    Code
    reboot


    SSH back to the pogoplug


    Since the OMV .4.x branch has some dependencies we'll install those first, along with some other things...


    Code
    apt-get update
    apt-get install nano
    apt-get install sudo
    apt-get install lm-sensors
    apt-get install xmlstarlet
    wget http://ftp.us.debian.org/debian/pool/main/x/xmlstarlet/xmlstarlet_1.4.2-1_armel.deb
    dpkg -i xmlstarlet_1.4.2-1_armel.deb
    apt-get install postfix


    (during postfix installation I choose "no configuration")


    there are some things that we need to configure before and after installing OpenMediaVault to avoid errors during the install process, which I believe may apply to any existing Debian system?
    Anyway, during the OMV install, collectd will fail if it can't resolve the host name, so we need to add the current pogoplug IP address and host name to the /etc/hosts file


    currently my pogoplug is using IP 192.168.0.31 with a host name of debian, so I'll added a line of:
    192.168.0.31 debian to the /etc/hosts file


    Code
    nano /etc/hosts


    add line:
    192.168.0.31 debian
    after the "local host" entry


    Ctrl+O
    enter, to save changes
    Ctrl+X, to exit


    Also, since the default "user" account that OMV expects is admin which currently doesn't exist, we need to create it...


    Code
    adduser admin


    *note* whatever password that you give user "admin" this will also be the password for admin when logging into OMV web-interface after installation!


    Now we will reboot before installing OMV


    Code
    reboot


    SSH back to the pogoplug
    Now we'll add the OMV repository and perform the install


    We need to create /etc/apt/sources.list.d/openmediavault.list file


    Code
    nano /etc/apt/sources.list.d/openmediavault.list


    in the blank file, add...

    Code
    deb http://packages.openmediavault.org/public fedaykin main


    save and exit


    Code
    apt-get update
    apt-get install openmediavault-keyring
    apt-get update
    apt-get install openmediavault


    Configuring mdadm
    MD arrays needed for root file system, entered = none
    ProFTPd run from inetd
    Samba Server, input whatever your workgroup name is, or default


    after OMV finishes installing, we need to cleanup and configure some more things.


    we installed sudo earlier, but need to add user 'admin'


    Code
    visudo


    at the end of the file, add...


    Code
    admin ALL=(ALL) ALL


    save and exit


    we also need to add user 'admin' to the openmediavault group


    Code
    adduser admin openmediavault


    next, we need to give group openmediavalut permission to the /etc/shawdow file, for web authentication to work.


    first verify current permissions


    Code
    ls -la /etc/shadow


    if it reads
    -rw-r----- 1 root root, then we need to change it.

    Code
    chown root:openmediavault /etc/shadow


    verify the change with...

    Code
    ls -la /etc/shadow


    should include openmediavault now


    since we've changed some permissions around, we are going to re-initialize omv and restart apache


    Code
    omv-initsystem


    Code
    service apache2 restart


    pull up a web brower at the pogoplug IP address


    login = admin
    password = (the password you gave user admin during creation earlier)


    once logged in to OMV, first enable SSH, then let's set or change the system time, time zone, and configure Primary DNS under network, DNS Server tab


    after verifying that SSH is enabled, we'll reboot the system


    I don't believe that I've left anything out, but you should be all done now.


    I didn't solve any of these problems, but just couldn't all the solutions in the same place, so anyone trying to install debian squeeze or OpenMediaVault on a Pogoplug POGO-E02 I hope this can be your guide.

    1coyote1, I would say that you really need to setup netconsole and see what is being displayed.
    http://forum.doozan.com/read.php?3,14,14


    Also, if you're using putty.exe for SSH, depending on your DHCP scope or even your prior history; I would clear out all of your old SSHhostkeys from the registry.
    Look in the registry under HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys and delete those entries.


    Also to note, that while I have finally been able to install Debian Squeeze and successfully connect and configure this, I still have not been able to actually install OMV to it and login to it's webgui with default login credentials.


    Between the xmlstarlet, and collectd erroring out, and some file permissions not being applied properly; I'm still working on that.


    I think this has been solved in this thread.
    http://forums.openmediavault.o…83&p=5902&hilit=ARM#p5902

    Alright, anyone that has had trouble just installing Debian on a POGO-E02 Pogoplug like I have, I've found a solution after A LOT of searching and time.


    To recap I tried multiple USB sticks, even a 2.5" laptop drive in a USB dock, nothing ultimately worked, but each time I could see and verify that debian did install to the USB device during the installation script, but after rebooting the Pogoplug it never seemed to boot off the USB and would always boot off the Pogoplug software.


    Just to clarify, I followed this page for the Debian Squeeze.
    http://projects.doozan.com/debian/


    But in order to actually get Debain to boot off USB, I had to do the following in addition.


    After Jeff's script finishes running and asks you to reboot, choose NO.


    mount the /dev/sda1 partition (the first partition that Debian installed to) to the /tmp/debian folder

    Code
    mount /dev/sda1 /tmp/debian


    Code
    cd /tmp/debian/usr/bin


    issue these commands


    Code
    ./mkimage -A arm -O linux -T kernel  -C none -a 0x00008000 -e 0x00008000 -n Linux-2.6.32-5-kirkwood -d ../../boot/vmlinuz-2.6.32-5-kirkwood ../../boot/uImage
    ./mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-2.6.32-5-kirkwood -d ../../boot/initrd.img-2.6.32-5-kirkwood ../../boot/uInitrd


    Lastly I un-mounted the USB by...

    Code
    cd /tmp


    Code
    umount /dev/sda1


    reboot


    After reboot, I saw that the Pogoplug associated with a different IP address, so check your DHCP server.
    SSH to the new IP, login is root and password is root
    issue a uname -a to verify your kernel.


    Note, with this POGO-E02 on this version of kernel, the "status" light will remain orange, but that is normal.


    For reference and credit, I found this information at the links below.
    Your mileage may vary but this worked for me...


    Originally, Okigan's post on this thread
    http://forum.doozan.com/read.php?2,11396


    And David's help on this thread
    http://forum.doozan.com/read.php?2,12061

    Alright, I really hope someone here can advise as to what exactly my problem is trying to get debian squeeze to boot. I'm using a Pogo Plug E02 with a usb hard drive in a dock, followed the instructions as usual, but only boots into the pogoplug environment.


    I know that debian installed fine to /dev/sda1, because if I create /tmp/debain and mount it there I can see all of the files.


    I have increased bootdelay to 15, and usbrootdelay to 15; no differences. The output of my fw_printenv is almost identical to what 1coyote1 posted above.


    I have setup netconsole and can provide the following output during boot up?


    Here is the output shown by netconsole during boot (both cold and warm) didn't change a thing...



    U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
    Pogoplug E02
    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... 3 USB Device(s) found
    scanning bus for storage devices... 1 Storage Device(s) found
    Loading file "/rescueme" from usb device 0:1 (usbda1)
    ** File not found /rescueme
    reading /rescueme.txt


    ** Unable to read "/rescueme.txt" from usb 0:1 **
    Creating 1 MTD partitions on "nand0":
    0x000002500000-0x000008000000 : "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: 91 MiB
    UBI: number of good PEBs: 727
    UBI: number of bad PEBs: 1
    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: 716
    UBI: total number of reserved PEBs: 11
    UBI: number of PEBs reserved for bad PEB handling: 7
    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'!
    Loading file "/boot/uImage" from usb device 0:1 (usbda1)
    ** File not found /boot/uImage
    ** Block device usb 1 not supported
    ** Block device usb 2 not supported
    ** Block device usb 3 not supported
    Loading file "/boot/uImage" from usb device 0:1 (usbda1)
    ** File not found /boot/uImage
    Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
    ** File not found /boot/uInitrd
    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: .......... done.
    ### JFFS2 load complete: 524288 bytes loaded to 0x800000
    ## Starting application at 0x00800200 ...




    Then I get the green light, and I'm back at the pogoplug prompt.


    Anyone?