Problem solved, it was the RAM.
Replaced the Patriot 1600 with some Corsair 1866 and it installed off the CD on the first try. After installing, I updated the kernel to the 3.2.0 backports kernel for the AMD 6 core support and all seems to be running well.
Thanks for the replies and suggestions!
Zitat von "ryecoaaron"Not that it really helps with OMV but does Debian Wheezy install and run ok on this machine? Also, does the system fully pass all the tests using memtest?
Good question. I was actually thinking the RAM might be bad out of the box. I'll exchange it tomorrow and give the Wheezy install a try.
Thanks for the replies,
I knew that using the other system to install was not going to be a solution, but I wanted to see both if the installer was good, as well as if the machine would even boot the system once it was installed in an attempt to narrow down where the problem is.
As for the Backports kernel, I have tried both the 3.2.4 kernel and the 2.6.83 kernel versions of Squeeze from here http://kmuto.jp/debian/d-i/ with the exact same kernel panic as the result.
Greetings,
I have been using OMV for about 2 years and it's always been rock solid, which is why I love it. Unfortunately, we were hit with some flooding in the midwest a month or so ago and my server that lived in my basement, went for a swim. Bad news was the server was a loss, but the data wasn't and insurance covered a new server build, which brings me here.
I just put together a brand new machine dedicated to running OMV based on a AMD FX-6300 6 core cpu, ASUS M5A78L-M LX PLUS Motherboard, 16GB of Patriot DDR3-1600, 30GB SSD boot drive and 5 3 TB Seagate SATA drives. Build went together smoothly but for the past 2 days I have been trying to get OMV to boot and install on this machine.
Both off the CD installer as well as a USB thumbdrive I get the same results, as soon as the machine trys to boot, I get "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(254,32)
I have tried about every bios combination I can think of that might have an effect on this and nothing makes a difference.
I even went so far as to try the install to the SSD in another machine, which installed fine off the same USB stick. I then swapped the drive into the new machine and it booted with a few warnings, but after setting up a share and test copying a few large files, the machine kernel panics every time.
I am at a loss and was wondering if anyone here had any suggestions, it would be greatly appreciated.
Greetings,
I am just getting started with OpenMediaVault and have got everything up and running on the LAN side of things, but would like to also set up Rsync to automatically download the files folder on my remote torrent seedbox.
I have SSH access to the remote machine, and it does have rsync installed. So far I have been able to ssh into the remote machine from both the OMV CLI as well as from Terminal in OSX and have confirmed that Rsync is up and running, but for some reason whenever I try it from within the Rsync Jobs on the WebUI in OMV, I get errors.
With the command: username@remotesever.com:873/filedirectory/ in the source server address, I get the following error when executing the job.
opening connection using: ssh -l username remoteserver.com rsync --server --sender -vvlogDtprSze.iLsf . 873/filedirectory/
Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,password).
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(601) [Receiver=3.0.7]
Like I said, I have logged into the remote machine via SSH in the CLI on the OMV machine and it has stored the password certificate, but it seems like it's not being accessed.
Any ideas?
