Again, I'm new at this, so please be patient with me.
I downloaded PuTTY and used SSH to get to my Raspberry Pi, but it's calling for a password, and the only password I know is the default admin password I use to get to the openmediavault web interface. It's not accepting that.
There's not another way to send that command to the Pi, is there?
when you installed omv3.x or 4.x, a root password was created.
You need to use those credintial to log in:
root / thepasswordyoucreated ( not admin/openmediavault, witch is the GUI password )
French, so forgive my english
Personal Rig: valid.x86.fr/v72uek as a test bench with Oracle VM.
And YES, my avatar is real, i am flying "parapentes" in St Hilaire du Touvet and at la coupe icare.
You have to enable SSH in the WebUI first. Then credentials for SSH are root/openmediavault.
OMV_3_0_88_RaspberryPi_2_3_4.9.41.img.xz - OMV Erasmus - Uses 4.9 kernel update to latest official version - not based on Raspbian but Debian/armhf (only compatible to RPi 2 and 3!) - SSH keys are regenerated on first boot but SSH login has to be enabled in web UI prior to usage: Services --> SSH --> Permit root login - Please immediately change default passwords! - A third partition for data use will be automatically resized on first boot but you have to format it manually with the fs of your choice! -
On first boot the installation will be finished. REMAIN PATIENT PLEASE
since this can take up to 30 minutes with a slow SD card and slow internet
connection (needs internet access to update all packages to latest version).
After one automatic reboot green activity led stops blinking and then your
Raspberry Pi is ready!
There are tons of threads here that deal with obscure problems on RPis and it's alway the result of not following this simple first step. The screenshot @mediagiant posted shows clearly a horribly outdated kernel version and pending security updates so this first step has never happened and so NTFS will never work (since drivers are missing, same with Wi-Fi and a lot of other stuff) and the whole installation is in a somewhat instable state.
Most simple solution: start from scratch this time following the readme. Maybe just to realize that Raspberry Pis are crap as a NAS at least with host powered disks since undervoltage is then a huge issue which leads to all sorts of strange problems and even filesystem corruption later. Everything outlined in detail in the thread that is referenced by the readme at the download page (the text no one is reading obviously).
As a rule of thumb: the best way to use OMV with a Raspberry Pi is to replace the RPi with something more suited for the job prior to attaching any disk(s). Then continue...
Not even remotely. Your screenshot clearly states that the necessary module is missing and that you're at kernel 4.9.41.
You failed to read the instructions that tell you that your RPi needs to be connected to the network at first boot and that you need to have patience since all packages will be updated on first boot and more importantly all the RPi support staff will then be installed. You somehow interfered with this and this problem can not be solved without the installation being finished.
Stop now, read the instructions and start over from scratch this time allowing to installation to be finished in first boot. Or search the forum, there it's explained how this can be fixed manually.
OK, so I started over with a fresh run of OMV. I actually got the new, blank drive to work.
BUT I'd still like to get the old drive that has all my files on it to work as well.
That drive is sdb1 now. I have the NTFS file system, and the drive is mounted. However, when I attempt to add a shared folder, I get an error message when I attempt to select a device. So, is this because there are files on this drive?
If I can't get this mounted, does anyone have any thoughts on how I might quickly move the files to the drive that IS mounted? We're talking about nearly 500 GB of data, so pushing all that over the network at once does not seem efficient.