I can not from 2.1.5 to 2.2.1

kejianshi

Can you go to Diagnostics > smart status > in the info section, select all - Then press view. Can you past the output here?

Assuming this rig is SMART capable.

yon

@kejianshi:

Can you go to Diagnostics > smart status > in the info section, select all - Then press view. Can you past the output here?

Assuming this rig is SMART capable.

this is working PF2.1.5 with IDE DISK 80GB

![PF2.1.5 - Diagnostics S.M.A.R.T. Monitor Tools.png](/public/imported_attachments/1/PF2.1.5 - Diagnostics S.M.A.R.T. Monitor Tools.png)
![PF2.1.5 - Diagnostics S.M.A.R.T. Monitor Tools.png_thumb](/public/imported_attachments/1/PF2.1.5 - Diagnostics S.M.A.R.T. Monitor Tools.png_thumb)

kejianshi

Can you check your bios and enable SMART if its an option. Currently its either missing or turned off.

After that, try to view the smart info and paste here again. Thanks.

yon

my bois have no this option. where find it ?

IMG_20150302_161903.jpg_thumb

IMG_20150302_161703_mh1425284487689.jpg_thumb

stephenw10

The fact that it's dropped you at the assign interfaces screen means that one of your interfaces detected in 2.1.5 is no longer detected for some reason. What interfaces do you have defined in 2.1.5?

I see you have a run(4) interface. Remove that before upgrading to 2.2. At this time at least some run devices seem to cause a kernel panic in 2.2. The one I have here does.

Steve

kejianshi

To turn on smart, you will have to look inside each one of those menus there and find smart. Turn it on and save. As for the run(4) issue, if thats a freebsd issue, you may be just screwed.

yon

@kejianshi:

To turn on smart, you will have to look inside each one of those menus there and find smart. Turn it on and save. As for the run(4) issue, if thats a freebsd issue, you may be just screwed.

i have no find the smart option.

yon

@stephenw10:

The fact that it's dropped you at the assign interfaces screen means that one of your interfaces detected in 2.1.5 is no longer detected for some reason. What interfaces do you have defined in 2.1.5?

I see you have a run(4) interface. Remove that before upgrading to 2.2. At this time at least some run devices seem to cause a kernel panic in 2.2. The one I have here does.

Steve

I will try remove interface in pf2.1.5

yon

@stephenw10:

The fact that it's dropped you at the assign interfaces screen means that one of your interfaces detected in 2.1.5 is no longer detected for some reason. What interfaces do you have defined in 2.1.5?

I see you have a run(4) interface. Remove that before upgrading to 2.2. At this time at least some run devices seem to cause a kernel panic in 2.2. The one I have here does.

Steve

your are right. it is becasue not using interface has no remove. just upgrad to PF2.2.1

but the pf2.2.x ipv6 not normal work. just ipv6 gateway show online, but LAN ipv6 can not go to internet. The DHCPV6 not normal work.

![pf2.2.1 ipv6 - Status Dashboard.png](/public/imported_attachments/1/pf2.2.1 ipv6 - Status Dashboard.png)
![pf2.2.1 ipv6 - Status Dashboard.png_thumb](/public/imported_attachments/1/pf2.2.1 ipv6 - Status Dashboard.png_thumb)

stephenw10

You will need to be more specific. IPv6 is not broken as far as I know in 2.2.1 snaps.

Steve

charliem

@stephenw10:

I see you have a run(4) interface. Remove that before upgrading to 2.2. At this time at least some run devices seem to cause a kernel panic in 2.2. The one I have here does.

Just FYI, run(4) should be fixed in the next snapshot:
https://redmine.pfsense.org/issues/4117#change-17648

stephenw10

Yep, I tested it this morning and it worked fine.

Steve

kejianshi

run(away)