Hello,
When issuing the shutdown via the management console, the drive powered down automatically and then OMV finished the NAS shutdown on the Raspberry Pi. Nothing new, nothing failing, and all appeared normal.
I have two Raspberry Pi's setup. One for OMV and the other for Kodi. Kodi is working fine but for some reason when I went to boot up the NAS, there is something that is not making the shared drive accessible. Also, I would always receive the shared resource named 'SMB CIFS' within the finder on my MacBook Pro. I'm perfectly certain there is nothing wrong with Kodi on the Pi or my Mac.
Unfortunately, I cannot provide any diagnostic information as I can't even connect to the management console. I can't even SSH into the OMV instance.
- the build I used to install OMV was OMV_3_0_88_RaspberryPi_2_3_4.9.41.img.xz, with updates applied approximately a month ago. None of the updates created any issues at all as the NAS has been rebooted a few times since the updates were applied. If I recall correctly the drive was formatted EXT4.
- I have powered off and on the OMV on the Pi simply because I couldn't connect.
- The IP address for the Pi's OMV is shown as not connected to the local network, presumably because OMV is not totally initialized.
- I have rebooted the modem which is connected to the OMV instance on the Pi via Ethernet. None of the other ethernet connections are presenting any issues, so I don't see any issues there.
- Since I don't see the shared storage device in the finder, I tried accessing the files via Kodi and it couldn't find them.
- BTW, I am using a Seagate 4TB Backup Plus Hub.
- The access to the various folders on the Seagate drive are all via SMB.
I know this isn't much of any diagnostic information to go by but is my only option to re-install OMV and configure everything from scratch? Hopefully I will not need to go that route. Even if that is my only option, will the folders on the drive still be accessible with the existing data retained?
Thanks in advance.