Search the Community

Trying to make a few different, ISOLATED, NAS on the same machine Have a Dell r320 server. 4 drives in the front connected to H310 mini HBA in IT mode, internal 2.5 ssd with OS Plan to add a JBOD / disk shelf with SAS cable to an HBA r320 has 2 pcie slots. 1 for an HBA for JBOD, second for a 4 port nic (or SFP+ 10G in future) ------- Goal: Have 2+ NAS running on the same machine, but isolated from eachother for security Each VM has its own disks and its own ethernet port and be on its own segmented network Each VM is independent and easily migrated (not using docker) Plan: Install XCP-ng hypervisor on the hardware (install on internal ssd) Create 2+ ubuntu VM's that are each on their own network (via different ports on the nic) Hardware passthrough the drives with IT mode and passthrough in XCP-ng so the VMs can only access certain drives (I believe you can do this in XCP-ng center) I have (currently) 5 isolated networks, created using pfsense running on a watchguard XTM5, I use physical separation (NOT vlan tags) and 5 separate gigabit switches Layout: 1 VM using internal H310 HBA and just the 4 10TB drives in the caddys - backup server for VMs running on the rest of my rack. Orchestra can do scheduled delta backups 1 VM for files share server using pcie HBA and connected JBOD - network accessible file share using samba (potential) 1 VM for jellyfin media server, running on JBOD - host VM will live on another hardware but just network attach this storage (optional) 1 VM for ISO library for creating other VMs with - samba share - live on management network Software: I plan on using some sort of software raid/ file system running on ubuntu, but have not figured out what yet leaning toward ZFS or trueNAS core or scale, maybe snapRAID. Each has downsides, still researching Unraid probably off the table since i want to have multiple installs, and unraid spendy and has its own downsides ------- This setup will not be used for running applications or services, just as network attached storage I have plenty of other compute servers that run everything I need ------- Thoughts? Feedback? Better ideas? I am trying to figure out as much as i can ahead of time Thanks! :]

I would like to have 2 parity drives but I don't know if i did it correctly. snapraid.conf # Example configuration for snapraid # Defines the file to use as parity storage # It must NOT be in a data disk # Format: "parity FILE_PATH" parity /mnt/parity1/snapraid.parity 2-parity /mnt/parity2/snapraid.parity # Defines the files to use as content list # You can use multiple specification to store more copies # You must have least one copy for each parity file plus one. Some more don't hurt # They can be in the disks used for data, parity or boot, # but each file must be in a different disk # Format: "content FILE_PATH" content /var/snapraid.content content /mnt/disk1/snapraid.content content /mnt/disk2/snapraid.content # Defines the data disks to use # The order is relevant for parity, do not change it # Format: "disk DISK_NAME DISK_MOUNT_POINT" disk data1 /mnt/disk1/ disk data2 /mnt/disk2/ disk data3 /mnt/disk3/ disk data4 /mnt/disk4/ disk data5 /mnt/disk5/ disk data6 /mnt/disk6/ # Excludes hidden files and directories (uncomment to enable). #nohidden # Defines files and directories to exclude # Remember that all the paths are relative at the mount points # Format: "exclude FILE" # Format: "exclude DIR/" # Format: "exclude /PATH/FILE" # Format: "exclude /PATH/DIR/" exclude /.lost+found/

Going to be setting up a low cost nas from spare parts I have collected over the years. Mostly data storage, but I plan on it doing at least one transcode over network to kodi or chromecast devices if I go down the plex route, pull data off it for adobe editing, and dumping obs streams over network to it. I have two ideas to do, the first is a bit strange but could be interesting to see if it works. Idea 1(lazy windows server): -Windows 10 -throw all my random drives into a JBOD style span volume -keep an archival drive that is larger than span that will act as a clone -set automated backup to archival drive -in event of failure in JBOD span, simply replace drive, add additional replacement drive to span, then move lost data back to spanned volume from archival drive(replacement will be same size or larger) Pros: -spanned drives and archival drive are readable by any windows machine and can be migrated to another machine in event of hardware failures without data loss -windows is easy, set up will be done quickly -adding drives to span is easy, and once I outgrow archival drive I can span that as well to increase it's size -these volumes aren't tied to hardware config of the server Cons: -windows and the word uptime in the same sentence has always made me nervous -"rebuilds" from archival drive will take forever -potentially abysmal speeds because spanning drives and window's software raid implementation is a mixed bag I have read. -limited software choices, less open source options for other things this server may end up doing Idea 2: -debian linux -snapraid to span volumes -fwbackup to move data to archival disk -samba for file sharing over network, offsite back up, etc. Pros: -stability and historically good uptime -snapraid seems to have a better implementation to prevent errors and data degredation and has more spanning options -more control over scheduled backups -much more can be done cheaply on linux as far as creating your own "cloud", hosting my own email server, etc. Cons: -unsure of ability to migrate spanned volume to another linux box in the event of hardware failure -much longer set up -steeper learning curve I am morbidly curious as to how the first option could turn out, and I have been putting off the hassle of establishing idea 2 as I am a bit rusty with terminal work, linux has just gotten easier over time for normal things I rarely use the terminal except to install programs. I am familiar with freenas and unraid and have been hesitant to use them for something so small. Freenas I haven't used and it seems to have a steeper learning curve than unraid. I am not going for a headless server, it will be in my rack under my desk so I will have it as the second input on my monitor and I have been a longtime user of synergy because I hate the cable spaghetti of kvm switches. I also plan to eventually have offsite backup via a friends router running wrt with sftp enabled for a usb hard drive. hardware I will be using, boot drive will be a 64gb usb 3 flashdrive: -phenom II x4 3ghz , 12gb ddr3, antec bronze 600 watt, lian li 4u rack case. -3tb hgst ultrastar, 2x 1.5tb barracudas, 1 hgst deskstar, 1tb wd green, will be buying an 8tb archival drive soon I am curious to see if anyone is interested in seeing how idea 1 can fair and I am willing to experiment with it as all the data I will be moving to it is already on drives on 3 machines so I can field test and not lose data short term, wont trust this system till I have had it running a few months.

I am a noob. I was doing scrubbing of my pool for the first time and at 45% of the run there was an error of renaming the "content.tmp" to "content" I didn't touch the computer the moment this error had happened. What went wrong for me?

Ubuntu 13.04 (GNU/Linux 3.8.0-19-generic x86_64) here is my /etc/fstab # /etc/fstab: static file system information.## Use 'blkid' to print the universally unique identifier for a# device; this may be used with UUID= as a more robust way to name devices# that works even if disks are added and removed. See fstab(5).## <file system> <mount point> <type> <options> <dump> <pass># / was on /dev/sda6 during installationUUID=eccfb5b3-f6fd-461b-bdc1-74b71f618b1c / ext4 errors=remount-ro 0 1# swap was on /dev/sda5 during installationUUID=c76e45aa-6cdb-4152-b179-6150ceb0ff7a none swap sw 0 0#/dev/sda1UUID=5580a7c5-b59e-4523-bf9f-169c9193d8a8 /home/phil/harddrives/sda1 ext4 defaults 0 0# /dev/sdb1UUID=cbaa00c3-d1bb-4522-8523-c13b7b92a097 /home/phil/harddrives/sdb1 ext4 defaults 0 0#/dev/sdc1UUID=63baad7c-c12a-42b9-9ae2-f36ac90e7798 /home/phil/harddrives/sdc1 ext4 defaults 0 0#/dev/sdd1UUID=8c63d06b-31b4-4b8c-9ad5-7f1d31b06653 /home/phil/harddrives/sdd1 ext4 defaults 0 0#/dev/sde1UUID=e7ca4a1b-4675-4774-a983-06c4d7c98818 /home/phil/harddrives/sde1 ext4 defaults 0 0#/dev/sdf1UUID=0caec458-2264-4d2b-a9e0-32fc6c9316c7 /home/phil/harddrives/sdf1 ext4 defaults 0 0mhddfs#/home/phil/harddrives/sdb1,/home/phil/harddrives/sdc1,home/phil/harddrives/sdd1,/home/phil/harddrives/sde1 /home/phil/storagepool fuse defaults,allow_other 0 0 All drives appear to be mounted correctly, users phil and root can read & write to all drives listed. Here's the ls -l for the drives mounted to home/phil/hardrives total 24drwxr-xr-x 2 phil root 4096 Aug 3 20:47 sda1drwxr-xr-x 4 phil root 4096 Aug 7 16:23 sdb1drwxr-xr-x 4 phil root 4096 Aug 7 16:17 sdc1drwxr-xr-x 3 phil root 4096 Aug 7 00:19 sdd1drwxr-xr-x 4 phil root 4096 Aug 7 00:19 sde1drwxr-xr-x 2 phil root 4096 Aug 3 20:45 sdf1 I believe the filesystems provide the possibility to get their parameters correctly, because of my df -h output Filesystem Size Used Avail Use% Mounted on/dev/sda6 52G 2.5G 47G 6% /none 4.0K 0 4.0K 0% /sys/fs/cgroupudev 3.9G 4.0K 3.9G 1% /devtmpfs 797M 1.9M 796M 1% /runnone 5.0M 0 5.0M 0% /run/locknone 3.9G 0 3.9G 0% /run/shmnone 100M 0 100M 0% /run/user/dev/sda1 55G 52M 52G 1% /home/phil/harddrives/sda1/dev/sdb1 1.8T 1.6T 110G 94% /home/phil/harddrives/sdb1/dev/sdc1 1.8T 146M 1.7T 1% /home/phil/harddrives/sdc1/dev/sdd1 1.8T 146M 1.7T 1% /home/phil/harddrives/sdd1/dev/sde1 459G 148M 435G 1% /home/phil/harddrives/sde1/dev/sdf1 2.7T 1.6T 973G 63% /home/phil/harddrives/sdf1/home/phil/harddrives/sdb1;/home/phil/harddrives/sdc1;/home/phil/harddrives/sdd1;/home/phil/harddrives/sde1 5.9T 1.6T 4.0T 29% /home/phil/storagepool So what is strange is that anything I write in /storagepool, goes directly to /sdb1, rather than any of the other drives with more free space. I have tested this through the command-line with touch, over FTP, and also using samba. I also have snapraid doing snapshots at irregular intervals, though I doubt it's relevant, here's my snapraid.conf #Parity Format: "parity FILE_PATH"parity /home/phil/harddrives/sdf1/snapraidparity# q-Parity Format: "q-parity FILE_PATH"#q-parity /mnt/diskqar/q-parity# Content Format: "content FILE_PATH"content /home/phil/harddrives/sdb1/contentcontent /home/phil/harddrives/sdc1/contentcontent /home/phil/harddrives/sdd1/contentcontent /home/phil/harddrives/sde1/content# The order is relevant for parity, do not change it# Data Format: "disk DISK_NAME DISK_MOUNT_POINT"disk d1 /home/phil/harddrives/sdb1/disk d2 /home/phil/harddrives/sdc1/disk d3 /home/phil/harddrives/sde1/disk d4 /home/phil/harddrives/sdd1/# Excludes hidden files and directories (uncomment to enable).# nohidden# Defines files and directories to exclude# Remember that all the paths are relative at the mount points# Format: "exclude FILE"# Format: "exclude DIR/"# Format: "exclude /PATH/FILE"# Format: "exclude /PATH/DIR/"exclude *.bakexclude *.unrecoverableexclude /tmp/exclude /lost+found/include /raidredemption/# Defines the block size in kibi bytes (1024 bytes).# Default value is 256 -> 256 kibi bytes -> 262144 bytes# Format: "block_size SIZE_IN_KiB"block_size 256# Automatically save the state when synching after the specied amount# of GiB processed.# This option is useful to avoid to restart from scratch long 'sync'# commands interrupted by a machine crash.# The SIZE argument is specified in gibi bytes -> 1073741824 bytes# Default value is 0, meaning disabled.# Format: "autosave_size SIZE_IN_GiB"# autosize 500# Defines the pooling directory where the virtual view of the disk# array is created using the "pool" command.# The files are not really copied here, but just linked using# symbolic links.# This directory must be outside the array.# Format: "pool DIR"# pool I guess it's possible that the content files could be confusing mhddfs as they all have the same name, however that wouldn't explain why mhddfs is happy enough to write in /sdb1