JustinChase Posted May 3, 2014 Author Share Posted May 3, 2014 in my archVM.cfg file disk = [ 'phy:/mnt/appdisk/ArchVM/arch.img,xvda,w', 'phy:/mnt/appdisk/ArchVM/data.img,xvdb,w' ] the data.img is just a 100g image file for storage since the default arch.img is like only 15g if I remember correctly. Okay, that makes sense. I'll have to find again the instructions on how to create a new, blank 100GB image file. I am not using my cache drive, I have a 240g ssd mounted outside the array for my VM stuff. I'll get around to setting that up also one of these days this data.img is mounted as the 2nd drive when the vm started, I then mount this drive That's a little confusing; you mount it when the vm starts, then you mount it? Maybe that will make more sense as I move thru this. and have told sab and plex to use this drive for its database/download stuff as whats left of 15g will not hole alot of sab downloads at one time I agree that's not enough space for downloads, 100GB should be plenty, since most get automatically processed quickly anyway. /dev/xvdb1 on /mnt/data type ext4 (rw,relatime,data=ordered) is my data.img that is mount on /mnt/data for useage Where do I enter this? Does that go in the fstab setup stuff? I assume it needs to be entered someplace that will 'stick'. in my sab config for folder section I have: Default Base Folder: /opt/sabnzbd Temporary Download Folder /mnt/data/sab-downloads/incomplete Completed Download Folder /mnt/data/sab-downloads/complete Permissions for completed downloads 777 Post-Processing Scripts Folder /opt/sabnzbd/scripts I made the sab-downloads folder to keep them seperate from my plex stuff which is in Library - both are located in /mnt/data also in my VM i did a chmod -R 777 * in my /mnt folder for the unraid mounts [root@IronicsArchVM_v4 mnt]# ls -la total 12 drwxr-xr-x 12 root root 4096 Apr 21 13:34 . drwxr-xr-x 19 root root 4096 Feb 4 07:58 .. drwxrwxrwx 2 root root 0 Jul 21 2013 Adult drwxrwxrwx 2 root root 0 Apr 28 03:04 BDMovies drwxrwxrwx 4 root root 4096 Apr 19 00:11 data drwxrwxrwx 2 root root 0 Apr 20 09:21 DVDMovies drwxrwxrwx 2 root root 0 Dec 16 22:55 eBooks drwxrwxrwx 2 root root 0 Sep 20 2013 HDMisc drwxrwxrwx 2 root root 0 Apr 28 03:04 Music drwxrwxrwx 2 root root 0 Apr 20 08:46 Pictures drwxrwxrwx 2 root root 0 Apr 29 03:00 SortThru drwxrwxrwx 2 root root 0 May 2 04:04 TV in the vm they are owned by root.root, but in unraid they are nobody.users, the extra params in the fstab i posted earlier takes care of the ownership prob this way it does not matter what sab is running as - sabnzbd i think if i remember correctly, and sickbeard as sickbeard also Everything has been running like this for almost 2 months now Myk After doing the chmod -R 777 * command, should I also do a chown -R root:root, or will they already be that way from the fstab stuff you showed earlier? Finally, I believe you are using cifs (SMB?), but I've been trying to use NFS, for reasons I mentioned earlier. Does it really matter? Is the benefit of NFS worth the hassle of trying to manage both file types? Thanks again for all your help. Quote Link to comment
MyKroFt Posted May 3, 2014 Share Posted May 3, 2014 ok disk = [ 'phy:/mnt/appdisk/ArchVM/arch.img,xvda,w', 'phy:/mnt/appdisk/ArchVM/data.img,xvdb,w' ] when the vm starts these images are like hd1 and hd2 once hd2 is formatted and a file structure put on it, itsjust like a blank hd I stayed with smb because of the nfs problem in pre 6 beta 3 in the /etc/fstab I mount the 2nd .img filesystem with: /dev/xvdb1 /mnt/data ext4 defaults 0 1 the /dev/xvdb comes from the disk section of the .cfg i needed to make the /data in the /mnt dir 1st before mounting it Myk Quote Link to comment
JustinChase Posted May 3, 2014 Author Share Posted May 3, 2014 Just another quick question. Earlier you said this data.img is mounted as the 2nd drive when the vm started, I then mount this drive /dev/xvdb1 on /mnt/data type ext4 (rw,relatime,data=ordered) is my data.img that is mount on /mnt/data for useage then you said in the /etc/fstab I mount the 2nd .img filesystem with: /dev/xvdb1 /mnt/data ext4 defaults 0 1 So, my question is, which one of these should I put in the fstab file? They look very similar, but the first one has more detail. I'm not sure if that syntax is necessary, or if the short version is enough. I used the short version, and will reboot soon. Quote Link to comment
JustinChase Posted May 3, 2014 Author Share Posted May 3, 2014 Okay, I'm not winning I've created the 100G data.img file in /mnt/cache/domains/archVM/ root@media:/mnt/cache/domains/archVM# ls -l total 14765153 -rw-rw-rw- 1 nobody users 0 Apr 23 19:26 README.md- -rw-rw-rw- 1 nobody users 399 May 3 10:42 arch.cfg -rw-rw-rw- 1 nobody users 449 Apr 23 19:26 arch.cfg- -rw-rw-rw- 1 nobody users 15000000000 May 3 11:36 arch.img -rw-rw-rw- 1 root root 107374182400 May 3 11:29 data.img *I'm not sure whether everything should be nobody:users or root:root. I'm guessing nobody:users I've amended my arch.cfg file like so... name = "archVM" bootloader = "pygrub" memory = '2048' maxmem = '4096' vcpus = '2' disk = [ 'phy:/mnt/cache/domains/archVM/arch.img,xvda,w', 'phy:/mnt/cache/domains/archVM/data.img,xvdb,w' ] vif = [ 'mac=00:16:3e:a2:b2:c2,bridge=br0' ] I've edited my /etc/fstab file to include /dev/xvdb1 /mnt/data ext4 defaults 0 1 I then shutdown the VM, then restarted it using the unRAID GUI. The GUI shows it's started, but I can't connect to the VM via putty. I then tried to xl console archVM and got... root@media:/mnt/cache/domains/archVM# xl console archVM [ 0.000000] e820: cannot find a gap in the 32bit address range [ 0.000000] e820: PCI devices with unassigned 32bit BARs may break! [ 0.195863] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) :: running early hook [udev] :: running hook [udev] :: Triggering uevents... :: performing fsck on '/dev/xvda1' /dev/xvda1: clean, 75281/915712 files, 600438/3661853 blocks ********************** WARNING ********************** * * * The root device is not configured to be mounted * * read-write! It may be fsck'd again later. * * * ***************************************************** :: mounting '/dev/xvda1' on real root :: running cleanup hook [udev] Welcome to Arch Linux! Expecting device dev-hvc0.device... [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Remote File Systems. [ OK ] Reached target Paths. [ OK ] Reached target Encrypted Volumes. [ OK ] Set up automount Arbitrary Executable File Formats F...utomount Point. [ OK ] Reached target Swap. Expecting device dev-xvdb1.device... [ OK ] Created slice Root Slice. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Listening on Device-mapper event daemon FIFOs. [ OK ] Listening on Delayed Shutdown Socket. [ OK ] Listening on LVM2 metadata daemon socket. [ OK ] Created slice User and Session Slice. [ OK ] Listening on udev Kernel Socket. [ OK ] Listening on udev Control Socket. [ OK ] Listening on Journal Socket. [ OK ] Created slice System Slice. Starting File System Check on Root Device... [ OK ] Created slice system-systemd\x2dfsck.slice. Mounting POSIX Message Queue File System... Mounting Debug File System... Starting Apply Kernel Variables... Starting Create list of required static device nodes...rrent kernel... Starting Load Kernel Modules... Mounting Huge Pages File System... [ OK ] Created slice system-getty.slice. [ OK ] Created slice system-serial\x2dgetty.slice. Starting Setup Virtual Console... Starting udev Coldplug all Devices... Starting Journal Service... [ OK ] Started Journal Service. [ OK ] Reached target Slices. Mounting Temporary Directory... [ OK ] Started Apply Kernel Variables. [ OK ] Started Create list of required static device nodes ...current kernel. Starting Create Static Device Nodes in /dev... [ OK ] Started udev Coldplug all Devices. [ OK ] Started Setup Virtual Console. [ OK ] Mounted Huge Pages File System. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Mounted Temporary Directory. [ OK ] Mounted Debug File System. [ OK ] Started Create Static Device Nodes in /dev. Starting udev Kernel Device Manager... [ OK ] Started udev Kernel Device Manager. [ OK ] Started Load Kernel Modules. Mounting Configuration File System... [ OK ] Mounted Configuration File System. [ 3.583989] systemd-fsck[85]: /dev/xvda1: clean, 75281/915712 files, 600438/3661853 blocks [ OK ] Started File System Check on Root Device. Starting Remount Root and Kernel File Systems... [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Reached target Local File Systems (Pre). Mounting RPC Pipe File System... Starting Load/Save Random Seed... [ OK ] Mounted RPC Pipe File System. [ OK ] Started Load/Save Random Seed. [ OK ] Found device /dev/hvc0. [ TIME ] Timed out waiting for device dev-xvdb1.device. [DEPEND] Dependency failed for /mnt/data. [DEPEND] Dependency failed for Local File Systems. [DEPEND] Dependency failed for File System Check on /dev/xvdb1. [ OK ] Stopped Getty on tty1. [ OK ] Stopped Serial Getty on hvc0. [ OK ] Stopped target Graphical Interface. [ OK ] Stopped target Multi-User System. [ OK ] Stopped NFS Mount Server Daemon. [ OK ] Stopped SickBeard Daemon. [ OK ] Stopped NFS v2/3 Network Status Monitor Daemon. [ OK ] Stopped Automounts filesystems on demand. [ OK ] Stopped dhcpcd on all interfaces. [ OK ] Stopped NFS v4 ID-Name Mapping Daemon. [ OK ] Stopped NFS Server Daemon. [ OK ] Stopped RPC Bind. [ OK ] Reached target RPC Port Mapper. [ OK ] Stopped OpenSSH Daemon. [ OK ] Stopped SSH Key Generation. [ OK ] Stopped Plex Media Server for Linux. [ OK ] Stopped SABnzbd binary newsreader. [ OK ] Reached target Network. [ OK ] Stopped NZBGet. [ OK ] Stopped Login Service. [ OK ] Stopped Permit User Sessions. Starting Trigger Flushing of Journal to Persistent Storage... [ OK ] Reached target Login Prompts. [ OK ] Stopped D-Bus System Message Bus. [ OK ] Stopped target Basic System. [ OK ] Closed D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. [ OK ] Reached target Timers. [ OK ] Stopped target System Initialization. Starting Create Volatile Files and Directories... Starting Emergency Shell... [ OK ] Started Emergency Shell. [ OK ] Reached target Emergency Mode. [ OK ] Started Create Volatile Files and Directories. Starting Update UTMP about System Boot/Shutdown... [ OK ] Started Trigger Flushing of Journal to Persistent Storage. [ OK ] Started Update UTMP about System Boot/Shutdown. Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode. Give root password for maintenance (or press Control-D to continue): Obviously something isn't right now, but I'm not sure what went wrong. Also, I'm not sure if I'll need to do this... mount via fstab and make a cronjob that mount -a ; df -h every 5 min (takes care of stale handles), on the VM chmod all the mount dirs 777 Finally, I've amended your earlier instructions, but I'm not sure where to enter this info either... //media/backup /mnt/backup cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 //media/documents /mnt/documents cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 //media/music /mnt/music cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 //media/photos /mnt/photos cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 //media/video /mnt/video cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 //media/adult /mnt/adult cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 I really do feel like an incompetent idiot at this point. Quote Link to comment
MyKroFt Posted May 3, 2014 Share Posted May 3, 2014 your getting close, before you can mount the 2nd data .img in the fstab, it needs to be partitioned and formatted, then add it to the fstab to be auto mounted at bootup the /dev/xvdb1 on /mnt/data type ext4 (rw,relatime,data=ordered) came from a 'mount' command to show you its device and where it was mounted to, sorry for the confusion you can use fdisk /dev/xvdb and create a primary partition with the default values, then when coming back to the command line then use mke4fs -t ext4 /dev/xvdb1 to format the partition. you should be good to go. add the line for the xvdb1 device, then you can 'mount -a' to have everything in the fstab mounted - you should then see your extra data drive on whatever mount you made. make sure the directory you are going to mount it to exists 1st myk Quote Link to comment
MyKroFt Posted May 3, 2014 Share Posted May 3, 2014 also does your VM see //meda as your unraid server? mine didnt, and I added a entry into /etc/hosts to point my //tower to its static ip address Myk Quote Link to comment
MyKroFt Posted May 3, 2014 Share Posted May 3, 2014 you might not not have to do the conjob anymore with b5a - I need to take mine out and see if any of my unraid network connections go stale anymore Myk Quote Link to comment
JustinChase Posted May 3, 2014 Author Share Posted May 3, 2014 your getting close...you can use fdisk /dev/xvdb and create a primary partition with the default values Okay, I commented out the new line in fstab, so now it looks like this... # # /etc/fstab: static file system information # # <file system> <dir> <type> <options> <dump> <pass> # /dev/xvda1 UUID=93ec2c22-36c1-487c-a888-adde602a16fe / ext4 $ #/dev/xvdb1 /mnt/data ext4 defaults 0 1 the /dev/xvda1 line was already commented out. I have no idea what the UUID= line is there for, but assume it's correct. Then I rebooted the VM. Then I opened the archVM console again, and did this... [root@IronicsArchVM_v4 ~]# fdisk /dev/xvdb Which gave me this... Welcome to fdisk (util-linux 2.24.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Device does not contain a recognized partition table. Created a new DOS disklabel with disk identifier 0x0c1d39cf. Command (m for help): Which I assumed was what you meant by when coming back to the command line then use mke4fs -t ext4 /dev/xvdb1 to format the partition. you should be good to go. So, I entered it and got this... Command (m for help): mke4fs -t ext4 /dev/xvdb1 Help: DOS (MBR) a toggle a bootable flag b edit nested BSD disklabel c toggle the dos compatibility flag Generic d delete a partition l list known partition types n add a new partition p print the partition table t change a partition type v verify the partition table Misc m print this menu u change display/entry units x extra functionality (experts only) Save & Exit w write table to disk and exit q quit without saving changes Create a new label g create a new empty GPT partition table G create a new empty SGI (IRIX) partition table o create a new empty DOS partition table s create a new empty Sun partition table Which doesn't look like it accepted/used my command above, but I typed w - to write table and exit, in case it did work, and got this... Command (m for help): w The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. Maybe that's correct, but it's ambiguous at best. You go on to suggest this... add the line for the xvdb1 device, then you can 'mount -a' to have everything in the fstab mounted - you should then see your extra data drive on whatever mount you made. make sure the directory you are going to mount it to exists 1st but I'm not sure where you want me to "add the line for the xvb1 device", but I assume you mean in fstab, is that correct? when you then tell me to 'mount -a', I assume that's from the command line to get the fstab to 'execute' Finally, I'm still not sure where I need to put this information to get my mounts all taken care of... //media/backup /mnt/backup cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 //media/documents /mnt/documents cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 //media/music /mnt/music cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 //media/photos /mnt/photos cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 //media/video /mnt/video cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 //media/adult /mnt/adult cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 I sure hope all this documentation helps others in the future!! Quote Link to comment
JustinChase Posted May 3, 2014 Author Share Posted May 3, 2014 also does your VM see //meda as your unraid server? mine didnt, and I added a entry into /etc/hosts to point my //tower to its static ip address yes, but only because I also added the entry to /etc/hosts previously. you might not not have to do the conjob anymore with b5a - I need to take mine out and see if any of my unraid network connections go stale anymore please let me know if this is still needed. I'd rather not have to add more stuff, but will if necessary. Quote Link to comment
JustinChase Posted May 3, 2014 Author Share Posted May 3, 2014 add the line for the xvdb1 device, then you can 'mount -a' to have everything in the fstab mounted - you should then see your extra data drive on whatever mount you made. make sure the directory you are going to mount it to exists 1st I un-commented the fstab line with the xvdb1 device, like so, and saved # /etc/fstab: static file system information # # <file system> <dir> <type> <options> <dump> <pass> # /dev/xvda1 UUID=93ec2c22-36c1-487c-a888-adde602a16fe / ext4 $ /dev/xvdb1 /mnt/data ext4 defaults 0 1 then typed mount -a and got this... [root@IronicsArchVM_v4 ~]# mount -a mount: special device /dev/xvdb1 does not exist I'm guessing I didn't get this part right above... mke4fs -t ext4 /dev/xvdb1 time for a drink; or 4 Quote Link to comment
JustinChase Posted May 3, 2014 Author Share Posted May 3, 2014 closer? I did this... [root@IronicsArchVM_v4 ~]# fdisk /dev/xvdb Welcome to fdisk (util-linux 2.24.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Device does not contain a recognized partition table. Created a new DOS disklabel with disk identifier 0xad33588c. Command (m for help): w The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. Then this... [root@IronicsArchVM_v4 ~]# mke4fs -t ext4 /dev/xvdb1 -bash: mke4fs: command not found did some searching, and ended up doing this instead... [root@IronicsArchVM_v4 ~]# mkfs.ext4 /dev/xvdb1 mke2fs 1.42.9 (28-Dec-2013) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 6553600 inodes, 26214144 blocks 1310707 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=4294967296 800 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872 Allocating group tables: done Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done That seemed like it worked, so I did this... [root@IronicsArchVM_v4 ~]# mount -a which didn't give any error, so I followed up with... [root@IronicsArchVM_v4 ~]# cd /mnt [root@IronicsArchVM_v4 mnt]# ls data tmp [root@IronicsArchVM_v4 mnt]# cd data [root@IronicsArchVM_v4 data]# ls -l total 16 drwx------ 2 root root 16384 May 3 18:33 lost+found That seems like it might have worked. Now, I need to go back and look into the chmod stuff you mentioned earlier, and try to figure out where to put the mounting stuff to assign my unRAID shares to the archVM mounts, then check what permissions and ownership might still need changed. I sure hope this fixes my issues, as if not, I'm not sure I could unwind it all, and will probably just have to start from scratch. Sadly, if it comes to that, I'm afraid I'll just go back to the plugins, which didn't cause me this much grief Wish me luck. Quote Link to comment
JustinChase Posted May 3, 2014 Author Share Posted May 3, 2014 hmmm... [root@IronicsArchVM_v4 mnt]# mount -a mount error(13): Permission denied Refer to the mount.cifs( manual page (e.g. man mount.cifs) [root@IronicsArchVM_v4 mnt]# cd / [root@IronicsArchVM_v4 /]# cd /mnt [root@IronicsArchVM_v4 mnt]# chmod -R 777 * chmod: changing permissions of ‘backup’: Permission denied chmod: changing permissions of ‘backup/JRMC’: Permission denied why might that be? I'm logged in as root. Quote Link to comment
JustinChase Posted May 9, 2014 Author Share Posted May 9, 2014 This still does not work correctly, and I'm out of ideas on how to 'fix' it. Here is as much information as I think is necessary to diagnose what I've done wrong. This is the /opt/sabnzbd folder permissions... [root@IronicsArchVM_v4 download]# cd /opt/sabnzbd [root@IronicsArchVM_v4 sabnzbd]# ls -la total 304 drwxr-xr-x 18 sabnzbd sabnzbd 4096 May 1 15:33 . drwxr-xr-x 6 root root 4096 Apr 29 16:19 .. -rw-r--r-- 1 sabnzbd sabnzbd 2088 Mar 27 10:52 ABOUT.txt -rwxr-xr-x 1 sabnzbd sabnzbd 125 Mar 27 10:52 addnzb.sh drwxr-xr-x 3 sabnzbd sabnzbd 4096 May 9 13:01 admin drwxr-xr-x 3 sabnzbd sabnzbd 4096 Apr 29 15:22 autoProcessTV -rw-r--r-- 1 sabnzbd sabnzbd 27198 Mar 27 10:52 CHANGELOG.txt drwxr-xr-x 5 sabnzbd sabnzbd 4096 Apr 23 20:59 cherrypy -rw-r--r-- 1 sabnzbd sabnzbd 1532 Mar 27 10:52 COPYRIGHT.txt drwxr-xr-x 3 sabnzbd sabnzbd 4096 May 1 12:44 Downloads drwxr-xr-x 2 sabnzbd sabnzbd 4096 Mar 27 10:52 email drwxr-xr-x 2 sabnzbd sabnzbd 4096 Apr 23 20:59 gntp -rw-r--r-- 1 sabnzbd sabnzbd 17990 Mar 27 10:52 GPL2.txt -rw-r--r-- 1 sabnzbd sabnzbd 35147 Mar 27 10:52 GPL3.txt drwxr-xr-x 2 sabnzbd sabnzbd 4096 Mar 27 10:52 icons -rw-r--r-- 1 sabnzbd sabnzbd 5841 Mar 27 10:52 INSTALL.txt drwxr-xr-x 8 sabnzbd sabnzbd 4096 Mar 27 10:52 interfaces -rw-r--r-- 1 sabnzbd sabnzbd 4465 Mar 27 10:52 ISSUES.txt drwxr-xr-x 2 sabnzbd sabnzbd 4096 Mar 27 10:52 licenses drwxr-xr-x 12 sabnzbd sabnzbd 4096 Mar 27 10:52 locale drwxr-xr-x 2 sabnzbd sabnzbd 4096 Apr 23 19:53 logs -rw-r--r-- 1 sabnzbd sabnzbd 2913 Mar 27 10:52 nzb-2.png -rw-r--r-- 1 sabnzbd sabnzbd 286 Mar 27 10:52 PKG-INFO drwxr-xr-x 5 sabnzbd sabnzbd 4096 Mar 27 10:52 po -rw-r--r-- 1 sabnzbd sabnzbd 3240 Mar 27 10:52 README.txt -rw-r--r-- 1 sabnzbd sabnzbd 2745 Mar 27 10:52 sab2_64.png -rw-r--r-- 1 sabnzbd sabnzbd 5317 Mar 27 10:52 SABHelper.py drwxr-xr-x 3 sabnzbd sabnzbd 4096 Apr 23 20:59 sabnzbd -rw-r--r-- 1 sabnzbd sabnzbd 4397 May 9 12:47 sabnzbd.ini -rw-r--r-- 1 sabnzbd sabnzbd 4397 May 9 12:47 sabnzbd.ini.bak -rwxr-xr-x 1 sabnzbd sabnzbd 65947 Mar 27 10:52 SABnzbd.py -rw-r--r-- 1 sabnzbd sabnzbd 464 Mar 27 10:52 Sample-PostProc.cmd -rwxr-xr-x 1 sabnzbd sabnzbd 481 Mar 27 10:52 Sample-PostProc.sh drwxr-xr-x 2 sabnzbd sabnzbd 4096 Mar 27 10:52 solaris drwxr-xr-x 2 sabnzbd sabnzbd 4096 Mar 27 10:52 tools drwxr-xr-x 2 sabnzbd sabnzbd 4096 Mar 27 10:52 util -rwxrwx--- 1 sabnzbd sabnzbd 365 Mar 27 10:52 x-nzb.xml The autoProcessTV folder was copied from /opt/sickbeard in an effort to 'fix' my inability to set the folder in the sab settings GUI. ========================================= This is the data.img permissions for the drive I created to put all my downloads into, to keep it within the VM, instead of the unRAID array. I don't know how or why the lost+found folder got created, nor if I need to keep it. [root@IronicsArchVM_v4 data]# cd /mnt/data [root@IronicsArchVM_v4 data]# ls -la total 28 drwxrwxrwx 4 root root 4096 May 9 11:17 . drwxr-xr-x 9 root root 4096 May 4 09:40 .. drwxr-xr-x 3 root root 4096 May 9 11:18 downloads drwxrwxrwx 2 root root 16384 May 3 18:33 lost+found ========================================= Here is my /etc/fstab file... # # /etc/fstab: static file system information # # <file system> <dir> <type> <options> <dump> <pass> # /dev/xvda1 UUID=93ec2c22-36c1-487c-a888-adde602a16fe / ext4 rw,relatime,data=ordered 0 1 /dev/xvdb1 /mnt/data ext4 defaults 0 1 #//media/backup /mnt/backup cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 #//media/documents /mnt/documents cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 #//media/music /mnt/music cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 #//media/photos /mnt/photos cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 #//media/video /mnt/video cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 #//media/adult /mnt/adult cifs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 //media:/mnt/user/backup /mnt/backup nfs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 //media:/mnt/user/documents /mnt/documents nfs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 //media:/mnt/user/music /mnt/music nfs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 //media:/mnt/user/photos /mnt/photos nfs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 //media:/mnt/user/video /mnt/video nfs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 //media:/mnt/user/adult /mnt/adult nfs rw,guest,username=nobody,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 I've commented out the cifs shares, trying to get it to work only with NFS shares. Not sure if this is at all correct, I pieced it together from stuff I've seen/read elsewhere. ========================================= Here is my archVM config file... name = "archVM" bootloader = "pygrub" memory = '2048' maxmem = '4096' vcpus = '2' disk = [ 'phy:/mnt/cache/domains/archVM/arch.img,xvda,w', 'phy:/mnt/cache/domains/archVM/data.img,xvdb,w' ] vif = [ 'mac=00:16:3e:a2:b2:c2,bridge=br0' ] ========================================= Here is my /net/media/mnt permissions... [root@IronicsArchVM_v4 /]# cd /net/media/mnt [root@IronicsArchVM_v4 mnt]# ls -la total 0 dr-xr-xr-x 4 root root 0 May 9 12:47 . dr-xr-xr-x 3 root root 0 May 9 12:47 .. drwxr-xr-x 2 root root 0 May 9 12:47 cache dr-xr-xr-x 12 root root 0 May 9 12:47 user I'm not sure why or how the cache and user directories have different permissions, or if it matters. Not sure if I should change them to match, or to something else entirely. ========================================= Here is the permissions for /net/media/mnt/user... [root@IronicsArchVM_v4 mnt]# cd user [root@IronicsArchVM_v4 user]# ls -la total 0 dr-xr-xr-x 12 root root 0 May 9 12:47 . dr-xr-xr-x 4 root root 0 May 9 12:47 .. drwxrwxrwx 1 nobody users 72 May 9 10:50 backup drwxr-xr-x 2 root root 0 May 9 12:47 BIN drwxr-xr-x 2 root root 0 May 9 12:47 documents drwxr-xr-x 2 root root 0 May 9 12:47 domains drwxr-xr-x 2 root root 0 May 9 12:47 download drwxr-xr-x 2 root root 0 May 9 12:47 JRiver drwxr-xr-x 2 root root 0 May 9 12:47 music drwxr-xr-x 2 root root 0 May 9 12:47 photos drwxr-xr-x 2 root root 0 May 9 12:47 plugins drwxr-xr-x 2 root root 0 May 9 12:47 video I'm not sure why the backup folder has different permissions than the rest, or if it matters. I had been using the download folder for the incomplete downloads, but kept getting weird errors in SAB, related to SAB losing the ability to see/write to this folder. Oddly enough, if I closed teh tab with the SAB gui, and just let it run in the background, it would run for days without errors, but if I opened the GUI, within an hour or so, usually less, I would start getting errors. I'm not sure what else I can provide to get to the bottom of the my issues, but I'm motivated to get this resolved, so I appreciate any help, and will provide answers and more information as quickly as possible to anyone that wants to help. Thanks again! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.