4 ms·

I'm curious - has anyone here faced trouble with Corral? Did you revert? What were your experiences?

myrandomcomment 10y ago
See my post above. 1. Upgrade did not come back up with disk mounted. 2. Changed import of encryption key so it would not mount volumes without user doing it. 3. LAG did not come up on reboot, has to be created again. 4. 1000 snapshot on 8 core FreeNAS mini took 20 minutes to mount all the file systems. 5. SMB shows started but no shares. Have to restart it. 6. GUI to slow in Firefox, asked to kill the script. 7. GUI completely locked up Chrome page. Had to kill.
colechristensen 10y ago
I did and had a series of issues. * Docker containers failing after running for ~24 hours due to networking problems with boot2docker vm. * Failing to automatically import my zfs pools on upgrade * UI "freezing" or generally stopping correct functioning (requiring reboot) * UI login failing requiring reboot I reverted back and forth a few times, I will probably stay with Corral until the next 9.10 release.
awinder 10y ago
I ran into an issue on upgrade that required me to connect to a monitor to figure out what was going on. Basically I just had out of date drivers on a storage controller so I needed to upgrade that, once I did, everything was smooth sailing.
unethical_ban 10y ago
After several days of it working fine, I couldn't access the storage menu. I just couldn't get any data to load when I clicked on it. And the 'cli' command error'ed out on every subcmd. So I don't know what happened or when, but it broke. I am going to fall back to 9.10.2 and let a bunch of other people test 9.10.3 before I upgrade.
leonroy 10y ago
Works fine, but little bugs and regressions like lack of form entry validation on some config fields for instance mean you could create a completely invalid config. I didn't try and find out what happened with an invalid config but did report the bug. Another big issue was that Chrome was the only supported browser which is something you expect from a beta. On top of that all the excellent docs from 9.10 were not updated for Corral so literally all Corral had were a few Wiki pages on a new site with a request for contributors to help fill in the blank pages. Very odd behaviour for a release but clear why now. It's a real shame, I upgraded my backup (personal) NAS which will have to be manually downgraded once iX release a FreeBSD 11 backed version of FreeNAS.
ownagefool 10y ago
Yeah, I tried to create several virtual machines and docker containers with bridged connections using DHCP and they error'd and dissapeared, then it just stopped letting me create them. I tried to also create them using the standard NAT settings, but the would generally not get through. Only one of the 6 odd off the self containers I was trying to use The GUI was slow, annoying, kept logging me out, buttons needed clicked several times, or required a refresh to work. I lost my NFS settings and could no longer get a working configuration for my kubernetes pods on other devices, which worked before. I would try and change the few settings available and it wouldn't allow me to save as if I hadn't changed anything. Basically, it was a bit of a shit show but I persisted for a couple of weeks hoping it'd get better. After several upgrades, nothing much had changed so I reverted. I don't like to kick them while they're down, but it seems like a project that got caught up with modernising by rewriting a whole bunch of code, whilst I suspect many would have been happy with them just adding the VM and docker stuff into the old interface/middleware. But it sounds like they're persisting with yet another rewrite, so...

See my post above. 1. Upgrade did not come back up with disk mounted. 2. Changed import of encryption key so it would not mount volumes without user doing it. 3. LAG did not come up on reboot, has to be created again. 4. 1000 snapshot on 8 core FreeNAS mini took 20 minutes to mount all the file systems. 5. SMB shows started but no shares. Have to restart it. 6. GUI to slow in Firefox, asked to kill the script. 7. GUI completely locked up Chrome page. Had to kill.

colechristensen 10y ago

I did and had a series of issues. * Docker containers failing after running for ~24 hours due to networking problems with boot2docker vm. * Failing to automatically import my zfs pools on upgrade * UI "freezing" or generally stopping correct functioning (requiring reboot) * UI login failing requiring reboot I reverted back and forth a few times, I will probably stay with Corral until the next 9.10 release.

awinder 10y ago

I ran into an issue on upgrade that required me to connect to a monitor to figure out what was going on. Basically I just had out of date drivers on a storage controller so I needed to upgrade that, once I did, everything was smooth sailing.

unethical_ban 10y ago

After several days of it working fine, I couldn't access the storage menu. I just couldn't get any data to load when I clicked on it. And the 'cli' command error'ed out on every subcmd. So I don't know what happened or when, but it broke. I am going to fall back to 9.10.2 and let a bunch of other people test 9.10.3 before I upgrade.

leonroy 10y ago

Works fine, but little bugs and regressions like lack of form entry validation on some config fields for instance mean you could create a completely invalid config. I didn't try and find out what happened with an invalid config but did report the bug. Another big issue was that Chrome was the only supported browser which is something you expect from a beta. On top of that all the excellent docs from 9.10 were not updated for Corral so literally all Corral had were a few Wiki pages on a new site with a request for contributors to help fill in the blank pages. Very odd behaviour for a release but clear why now. It's a real shame, I upgraded my backup (personal) NAS which will have to be manually downgraded once iX release a FreeBSD 11 backed version of FreeNAS.

ownagefool 10y ago

Yeah, I tried to create several virtual machines and docker containers with bridged connections using DHCP and they error'd and dissapeared, then it just stopped letting me create them. I tried to also create them using the standard NAT settings, but the would generally not get through. Only one of the 6 odd off the self containers I was trying to use The GUI was slow, annoying, kept logging me out, buttons needed clicked several times, or required a refresh to work. I lost my NFS settings and could no longer get a working configuration for my kubernetes pods on other devices, which worked before. I would try and change the few settings available and it wouldn't allow me to save as if I hadn't changed anything. Basically, it was a bit of a shit show but I persisted for a couple of weeks hoping it'd get better. After several upgrades, nothing much had changed so I reverted. I don't like to kick them while they're down, but it seems like a project that got caught up with modernising by rewriting a whole bunch of code, whilst I suspect many would have been happy with them just adding the VM and docker stuff into the old interface/middleware. But it sounds like they're persisting with yet another rewrite, so...