FN7.2-N4F9.1.0.1.573 Failure? Or just need some fixing?

[Gink]

Hello, upgraded my old FreeNAS 0.7.2 8191 Embedded install to NAS4Free 9.1.0.1.573 earlier today. It went pretty smoothly but I've got a handful of problems with the system now. I'm wondering if they are a sign that the upgrade didn't go as smoothly as it seemed and I need to start over/try again, or if I just need to keep working at fixing the individual issues to get things running smoothly.

First thing I noticed was my sickbeard/sabnzbd setup I had on FN no longer works, no access to the webguis for either service. Also on boot I see several messages such as "Shared Object libutil.so.7 not found needed by python... might be a reason why sb/sab are no longer working.

I decided to ssh into N4F to dig into the issue, only to get "connection refused". On the webgui I see SSH enabled, but not operating. SSH log shows "listening to port 22 on 0.0.0.0" I would assume that should be the systems IP address instead of 0.0.0.0? A glance at the LAN Interface section of the webgui shows nothing... no interfaces in the dropdown, even though the system has 2 NICs. But the connected NIC does seem to be working obviously, as I can access webgui and smb shares seem fine.

Also, some portions of the webgui don't seem to work. Status|Process is a blank page, File Manager throws a 404, in the Bittorrent service page the link to the webgui is http://:9091, leaving out the IP completely. I can still manually enter the correct URL and get to it, but found that odd.

Last but not least, my logs have "init: getty repeating too quickly on port /dev/ttyv0, sleeping 30 secs" repeating endlessly every 30 seconds for each of ttyv0, ttyv1, and ttyv2.

So all in all, does this amount to a failed upgrade? Should I just try again, maybe redownload, reburn the N4F image, etc doing CRC checks at each step? Or does each of these issues seem minor enough, or solvable enough to just keep tinkering until things start working again?

[raulfg3]

Hello, upgraded my old FreeNAS 0.7.2 8191 Embedded install to NAS4Free 9.1.0.1.573 earlier today

please describe how you upgrade or what guide do you use.

Also, some portions of the webgui don't seem to work. Status|Process is a blank page, File Manager throws a 404, in the Bittorrent service page the link to the webgui is http://:9091, leaving out the IP completely. I can still manually enter the correct URL and get to it, but found that odd

this can be cache problems in your explorer.

Clear cache or use a different explorer to be sure if status|process is show or not.

save your config in a safe place.

At the end if problems persist, the more secure way is to start from scratch, do a new embeded install, and configure services by hand ( load disk and pools or raid is trivial in this version due a new button " clear config and load new disk" or something simmilar in Disk page.

you ned to installl sickbeard/sabnzbd unless are installed on a jail.

[Gink]

please describe how you upgrade or what guide do you use.

1. Used dd to clone CF, booted to new CF to make sure it worked.
2. Download LiveCD iso and burned to disk
3. Boot to LiveCD and selected to Upgrade Embedded
4. After Upgrade Complete rebooted to CF which now had N4F
5. Backup Config File

Pretty simple process, so would be easy to give it another shot and see if the results are the same or different. Since I have my original CF card and config file I can get back to a working FreeNAS setup in minutes.

At the end if problems persist, the more secure way is to start from scratch, do a new embeded install, and configure services by hand ( load disk and pools or raid is trivial in this version due a new button " clear config and load new disk" or something simmilar in Disk page.

you need to installl sickbeard/sabnzbd unless are installed on a jail.

sab/sb are installed in a jail, so hopefully I can avoid a complete reinstall. I'd rather reconfigure all my disks, shares and services than reconfig sb/sab. I think their main issues are the files listed as "not found" and needed by python, xml, stunnel, etc.

As long as SSH is broken I can't really accomplish much, so I guess I'll reclone my CF and try the upgrade over again.