So how did the boot drive (USB Flash) to which I had 9.3 and 9.10 installed offer me multiple boot options so that I could go back to earlier versions?No, FreeNAS uses an entire drive. You cannot use partitions.
So how did the boot drive (USB Flash) to which I had 9.3 and 9.10 installed offer me multiple boot options so that I could go back to earlier versions?No, FreeNAS uses an entire drive. You cannot use partitions.
I have an AMD system (see my test rig) just itching for FreeNAS 10 to be installed on it but first I need to clean up my computer room. I don't have enough hard drives to make a full featured NAS but it should be fine for operational checks. Maybe later today. If there is something specific a person wants me to test, throw it out there.I never said that, I just wanted to poke a stick at AMD users a bit. :)
See https://bugs.freenas.org/issues/17336
So how did the boot drive (USB Flash) to which I had 9.3 and 9.10 installed offer me multiple boot options so that I could go back to earlier versions?
It's datasets and snapshots. I'm not sure how they interact.Snapshots I think.
[root@nas] ~# zfs list | grep freenas-boot NAME USED AVAIL REFER MOUNTPOINT freenas-boot 1.70G 26.4G 31K none freenas-boot/ROOT 1.66G 26.4G 25K none freenas-boot/ROOT/9.10-STABLE-201604261518 71.5K 26.4G 463M / freenas-boot/ROOT/9.10-STABLE-201605021851 61.5K 26.4G 481M / freenas-boot/ROOT/9.10-STABLE-201605240427 66.5K 26.4G 483M / freenas-boot/ROOT/9.10-STABLE-201606270534 49K 26.4G 595M / freenas-boot/ROOT/9.10.1 1.66G 26.4G 615M / freenas-boot/ROOT/Initial-Install 1K 26.4G 494M legacy freenas-boot/ROOT/default 33K 26.4G 494M legacy freenas-boot/grub 37.9M 26.4G 6.33M legacy [root@nas] ~# zfs list -t snapshot | grep freenas-boot NAME USED AVAIL REFER MOUNTPOINT freenas-boot/ROOT/9.10.1@2016-04-30-13:09:28 2.69M - 494M - freenas-boot/ROOT/9.10.1@2016-04-30-14:26:07 2.46M - 494M - freenas-boot/ROOT/9.10.1@2016-05-04-06:24:55 94.1M - 463M - freenas-boot/ROOT/9.10.1@2016-05-26-22:31:40 92.5M - 481M - freenas-boot/ROOT/9.10.1@2016-07-16-18:09:43 109M - 483M - freenas-boot/ROOT/9.10.1@2016-08-04-17:30:27 253M - 595M - freenas-boot/grub@Pre-Upgrade-9.10-STABLE-201604261518 6.32M - 6.33M - freenas-boot/grub@Pre-Upgrade-9.10-STABLE-201605021851 6.32M - 6.33M - freenas-boot/grub@Pre-Upgrade-9.10-STABLE-201605240427 6.32M - 6.33M - freenas-boot/grub@Pre-Upgrade-9.10-STABLE-201606270534 6.32M - 6.34M - freenas-boot/grub@Pre-Upgrade-9.10.1 6.32M - 6.33M -
That is correct: https://forums.freenas.org/index.php?threads/freenas-10-beta-is-now-available.45755/I'm pretty sure there is not a supported "upgrade" from 9.10.x to 10 right now. (I think I read that in this thread actually? Can't remember.) So that mechanism you refer too won't work at present.
What I meant by "FreeNAS uses an entire drive. You cannot use partitions." is that the installer does not let you use partitions, only entire drives. The best way to use 9.10.1 and 10 on the same machine is to use different boot drives. However, I do not believe hopping back and forth between these 2 would be a good idea if you value the data in your pool. 10 is still experimental and changing frequently. Switching back and forth between a stable and an experimental version could have bizarre consequences. This is why I have a separate system for playing with 10. Then again I'm just speculating and you could be totally fine :DSo how did the boot drive (USB Flash) to which I had 9.3 and 9.10 installed offer me multiple boot options so that I could go back to earlier versions?
I tried using alternate boot drives (but 10Beta only with the power to the "main" drives switched off, and just one "spare" drive connected), but even when I set the BIOS to have the USB flash drive with 10Beta as the first drive, it seemed to "pass control" to the SSD with 9.10; if I wanted to use 10Beta, I had to open the case and disconnect the SSD.It's datasets and snapshots. I'm not sure how they interact.
Code:[root@nas] ~# zfs list | grep freenas-boot NAME USED AVAIL REFER MOUNTPOINT freenas-boot 1.70G 26.4G 31K none freenas-boot/ROOT 1.66G 26.4G 25K none freenas-boot/ROOT/9.10-STABLE-201604261518 71.5K 26.4G 463M / freenas-boot/ROOT/9.10-STABLE-201605021851 61.5K 26.4G 481M / freenas-boot/ROOT/9.10-STABLE-201605240427 66.5K 26.4G 483M / freenas-boot/ROOT/9.10-STABLE-201606270534 49K 26.4G 595M / freenas-boot/ROOT/9.10.1 1.66G 26.4G 615M / freenas-boot/ROOT/Initial-Install 1K 26.4G 494M legacy freenas-boot/ROOT/default 33K 26.4G 494M legacy freenas-boot/grub 37.9M 26.4G 6.33M legacy [root@nas] ~# zfs list -t snapshot | grep freenas-boot NAME USED AVAIL REFER MOUNTPOINT freenas-boot/ROOT/9.10.1@2016-04-30-13:09:28 2.69M - 494M - freenas-boot/ROOT/9.10.1@2016-04-30-14:26:07 2.46M - 494M - freenas-boot/ROOT/9.10.1@2016-05-04-06:24:55 94.1M - 463M - freenas-boot/ROOT/9.10.1@2016-05-26-22:31:40 92.5M - 481M - freenas-boot/ROOT/9.10.1@2016-07-16-18:09:43 109M - 483M - freenas-boot/ROOT/9.10.1@2016-08-04-17:30:27 253M - 595M - freenas-boot/grub@Pre-Upgrade-9.10-STABLE-201604261518 6.32M - 6.33M - freenas-boot/grub@Pre-Upgrade-9.10-STABLE-201605021851 6.32M - 6.33M - freenas-boot/grub@Pre-Upgrade-9.10-STABLE-201605240427 6.32M - 6.33M - freenas-boot/grub@Pre-Upgrade-9.10-STABLE-201606270534 6.32M - 6.34M - freenas-boot/grub@Pre-Upgrade-9.10.1 6.32M - 6.33M -
That is correct: https://forums.freenas.org/index.php?threads/freenas-10-beta-is-now-available.45755/
What I meant by "FreeNAS uses an entire drive. You cannot use partitions." is that the installer does not let you use partitions, only entire drives. The best way to use 9.10.1 and 10 on the same machine is to use different boot drives. However, I do not believe hopping back and forth between these 2 would be a good idea if you value the data in your pool. 10 is still experimental and changing frequently. Switching back and forth between a stable and an experimental version could have bizarre consequences. This is why I have a separate system for playing with 10. Then again I'm just speculating and you could be totally fine :D
I have an AMD system (see my test rig) just itching for FreeNAS 10 to be installed on it but first I need to clean up my computer room. I don't have enough hard drives to make a full featured NAS but it should be fine for operational checks. Maybe later today. If there is something specific a person wants me to test, throw it out there.
EDIT: Got FreeNAS 10 running on the AMD system, no issues so far and I plan to keep it running. I don't have much on it yet, just trying to do the basic configuration right now. Also, I removed the Intel NIC so I'm running on the motherboard RealTek NIC, this is just for testing purposes. I cannot saturate the LAN but it's close. Now to see how stable things are.
I know devs dont read this much but getting a shutdown/reboot confirmation popup would be nice.
There is no "emulated flavor" of Linux or translation involved. It's an actual Linux distribution (boot2docker) that runs the Docker containers.I'm not familiar with Docker (I'm a Windows guy, mainly)... does the Plex installation under Docker in the state of the union video effectively run in a full VM? (i.e. is it running a fully emulated flavor of Linux or some translation of Linux->BSD API calls)?
Better yet a video https://www.youtube.com/watch?v=isvHJ51YRBkI am also a windows person and I am wanting a to break away from running my windows server and try freenas. Is there a guide to help me with things. Thanks
ok thanks I am looking forward to the release and a guide to help people like meStick with 9.10 there loads of videos on what to do and when 10 becomes release in a few months you shall know what to do then.
10 evolving quite a bit so anything you ;learn now may not be valid in a month.
Can I lose my Data?
Thank you Matt, guess I have to wait a little longer since that doesn't sound encouraging.. cheers! :)You probably won't lose data.
We've had a FreeNAS 10 up and running for three months. Our production server (FreeNAS 9.10) is using FreeNAS 10 as a replication target. Lots of data is being pumped through 10 and we are confident with its ability to perform as a basic NAS (which is how we use FreeNAS - no jails, VMs or any other craziness).
That said, the FreeNAS 10 interface is atrocious. We'll give it another shot when the final release is out but, at this time, we don't see us going to FreeNAS 10 unless it becomes an absolute requirement. The usability of the web interface is a giant leap backwards.
Cheers,
Matt
Well, I guess that's why we're all a diverse nation and world - differences of opinion. :DThat said, the FreeNAS 10 interface is atrocious. We'll give it another shot when the final release is out but, at this time, we don't see us going to FreeNAS 10 unless it becomes an absolute requirement. The usability of the web interface is a giant leap backwards.