So i was having trouble getting this drive to work in ZM. The drive is a wd40purz (WD 4TB purple) BTW. so thinking i probably fed up some where so i just reinstalled my whole server. Ubuntu 18.04.4 LTS
To install Zm i used This Guide: https://zoneminder.readthedocs.io/en/st ... -04-bionic
And this one on the same page for a dedicated drive: https://zoneminder.readthedocs.io/en/st ... drive.html
Before i was using my software raid that i use for everything, just for testing. I remember just setting perms and then being good. But now with this drive it is freaking out and cant see it apparently. what am i missing?
Terminal and log: https://imgur.com/c03j6Rt
New Dedicated drive does not exist.
Re: New Dedicated drive does not exist.
Better install instructions: https://wiki.zoneminder.com/Ubuntu_Serv ... der_1.34.x The Read The Docs instructions are, still, not up to date.
is your 4 TB drive the main (and only) drive in your server?
If you are using an older PC for a server the BIOS may not recognize the 4 TB drive.
If you are using one drive for the OS and the 4 TB for storage you need to install Ubuntu so the 4 TB drive is mounted correctly.
You may want to step up to Ubuntu 20.04. A server version is recommended although I use a mini.iso net install to end up with a minimal server without all the junk the live server image loads.
Instructions can be provided but are somewhere on this forum as your issue has been addressed several times before.
is your 4 TB drive the main (and only) drive in your server?
If you are using an older PC for a server the BIOS may not recognize the 4 TB drive.
If you are using one drive for the OS and the 4 TB for storage you need to install Ubuntu so the 4 TB drive is mounted correctly.
You may want to step up to Ubuntu 20.04. A server version is recommended although I use a mini.iso net install to end up with a minimal server without all the junk the live server image loads.
Instructions can be provided but are somewhere on this forum as your issue has been addressed several times before.
Re: New Dedicated drive does not exist.
Secondary drives must be compatible filesystem (FAT32 won't work).
See
https://wiki.zoneminder.com/Using_a_ded ... Hard_Drive
See
https://wiki.zoneminder.com/Using_a_ded ... Hard_Drive
Re: New Dedicated drive does not exist.
OK I installed Ubuntu 20.04 server and ZM via the instructions you linked.
The 4TB purple is the 10th physical drive in the system
1: 1Tb Nvme ssd is my main drive
7: 2TB sas drives in a raid 6
1: 4Tb Drive sneaker data transfer
1: 4Tb Drive for Zm
It is a 1900x so i would be really surprised if the bios was that old
"If you are using one drive for the OS and the 4 TB for storage you need to install Ubuntu so the 4 TB drive is mounted correctly."
would you explain what you mean here. what i did was click the mount button and it mounted where i wanted it actually. with my raid 6 i had to do the whole mount/md/0 /media/sauron/Erebor and edit the fstab.
I have once again down chown -R www-data:www-data /media/sauron/Bara-dur/Events, and am still getting the same errors.
I posted sooner but for some reason it isn't showing up, so now i am responding again.
The 4TB purple is the 10th physical drive in the system
1: 1Tb Nvme ssd is my main drive
7: 2TB sas drives in a raid 6
1: 4Tb Drive sneaker data transfer
1: 4Tb Drive for Zm
It is a 1900x so i would be really surprised if the bios was that old
"If you are using one drive for the OS and the 4 TB for storage you need to install Ubuntu so the 4 TB drive is mounted correctly."
would you explain what you mean here. what i did was click the mount button and it mounted where i wanted it actually. with my raid 6 i had to do the whole mount/md/0 /media/sauron/Erebor and edit the fstab.
I have once again down chown -R www-data:www-data /media/sauron/Bara-dur/Events, and am still getting the same errors.
I posted sooner but for some reason it isn't showing up, so now i am responding again.
Re: New Dedicated drive does not exist.
first thing I would do is cutnpaste from logs and do ls -l /whatever the path is
Maybe try a path with a - in it? I wouldn't expect that to be a problem, but you never know.
Maybe try a path with a - in it? I wouldn't expect that to be a problem, but you never know.
Re: New Dedicated drive does not exist.
Did you ever get this to work?
I had the exact same problem as you; it took me a full day to figure it out. I'm pretty tech savvy, even with terminal, but it still took 5 or 6 full disc formattings to get it to work.
Frank
I had the exact same problem as you; it took me a full day to figure it out. I'm pretty tech savvy, even with terminal, but it still took 5 or 6 full disc formattings to get it to work.
Frank
Re: New Dedicated drive does not exist.
On a new Ubuntu or Debian install I get the drive for storage mounted and formatted at install.
When you get to the drive format area choose manual setup. (this is for legacy BIOS boot.)
The drive for the OS, partition the whole drive, select "/" as the mount point and EXT4 format The drive for Zoneminder storage partition the entire drive, Manually create a mount of "/zmstore" and format EXT4. Continue the install.
On first boot. create an events folder in /zmstore (mkdir /zmstore/events). Install LAMP or LEMP. change ownership of the /zmstore (chown -R www-data /zmstore)
Next see: https://wiki.zoneminder.com/Using_a_ded ... Hard_Drive
You can also use systemd mount. See: https://wiki.zoneminder.com/Common_Issu ... ive_or_NAS
When you get to the drive format area choose manual setup. (this is for legacy BIOS boot.)
The drive for the OS, partition the whole drive, select "/" as the mount point and EXT4 format The drive for Zoneminder storage partition the entire drive, Manually create a mount of "/zmstore" and format EXT4. Continue the install.
On first boot. create an events folder in /zmstore (mkdir /zmstore/events). Install LAMP or LEMP. change ownership of the /zmstore (chown -R www-data /zmstore)
Next see: https://wiki.zoneminder.com/Using_a_ded ... Hard_Drive
You can also use systemd mount. See: https://wiki.zoneminder.com/Common_Issu ... ive_or_NAS