Beiträge von Togna Balogna

Sweet. Adding the pi user to the SSH group was super easy. I appreciate the advice from both of you. If I would have read the guide you posted, I wouldn't have even had this problem. Generally, I'm a bit better with software like this, but most of Linux is new to me, so I'll be asking more questions AFTER doing some reading about this. The main thing was that this wasn't an issue with my Pi 3 for some reason and I didn't even run into this until this installation from the past few days. Now that it's configured, it's just going to live in my entertainment center along with the attached hard drive. Thanks again for the help everyone!

Ahhh ok. I would be creating that user within the OMV web interface then, yeah? I don't remember this happening when I installed on my Pi 3, so this totally threw me off.

Good afternoon,

I've recently installed OMV 5 on a new Pi that I recently purchased and have experienced something that I didn't run into with my last installation. I went for the Debian Buster Lite image and put that on a 32GB Samsung Evo Select micro SD card. After creating a blank file called 'SSH' on the root, I connected the pi to my network via ethernet and was able to use PuTTY to establish a connection to it. I immediately entered the 'passwd' command to change my password, and tested it after exiting to ensure that I knew what the password was at least. After exiting and re-entering the Pi via SSH, I ran the following command 'wget -O - https://github.com/OpenMediaVa…Script/raw/master/install | sudo bash' in order to install OMV. At this point, I rebooted the Pi and tried to SSH into it again. At this point, I am unable to SSH into my Pi for any kind of maintenance, and I'm not sure what is causing this issue. I didn't prompt the system to change the password, and I've tried the default 'raspberry' as well as 'openmediavault' just for the hell of it. This is the 3rd time I've reinstalled the OS and started over in the last 24 hours, and I really just want to set this up and be done with it. All this Pi is going to do is function as a NAS. I only did it so many times because I wanted to identify the exact point where the password changes. Any help would be greatly appreciated.

I haven't checked documentation of the drive, but I totally understand that it's more specific to the drive. That was my bad for not being specific and checking what that particular indicator might mean for the drive. I've installed OMV onto a Pi 4 and it seems like it works just fine with that. I had to setup the share again, but the drive was fine. I also had tested the drive with other device. While I wasn't able to read the data from the drive, I could feel the drive spin up and didn't hear any clicking or anything. I'm going to chalk it up to a power delivery issue, since it worked on another device with more power delivery. Thank you for your help! Your suggestions were very helpful.

Good morning everyone,

I'm pretty new to the whole Raspberry Pi scene, but I have understood enough to get OMV running and all that. I've been using a Seagate 250GB external USB hard drive and it has worked as intended for the last few weeks. Recently, I've noticed that the white LED on my HDD is blinking, indicating some kind of issue. I've gone into the "disks" section of OMV and scanned for devices, and it's just not able to pick this up. I feel like the drive isn't even in a state where it would be able to be picked up if there is a blinking indicator on the drive. I also have a flash drive that I've used with OMV and after connecting that again, the connection was made just fine and it was detected by OMV. Anyone run into this issue before and know what the resolution might be? Any help would be greatly appreciated. Also, I'm relatively new to Linux, but this has been a great learning experience. That being said, please keep the comments friendly.