Upgraded from 12a to 15a on a VM and lost access to the SF webgui so I went back to 12a all was good.

 

So on my N36L i tried the upgrade which didnt have SF webgui installed, all was good until I installed SF webgui and then I could not get to the GUI or the falsh drive through windows explorer, anyone else had this issue?

 

Lee

Get updated version of SF.  one or more of your plugins is probably out-dated.

It is my understanding rc16 will be out soon (a handful of us are running rc16 in a limited trial), so wait a bit any try again with it after updating your SF installation.

 

Joe L.

 

Why do we need an RC16?

 

I have the SF Webserver plugin 1.0.11 so think that is the latest unless anyone knows of one newer than that?

 

 

Upgraded from 12a to 15a on a VM and lost access to the SF webgui so I went back to 12a all was good.

 

So on my N36L i tried the upgrade which didnt have SF webgui installed, all was good until I installed SF webgui and then I could not get to the GUI or the falsh drive through windows explorer, anyone else had this issue?

 

Lee

Get updated version of SF.  one or more of your plugins is probably out-dated.

It is my understanding rc16 will be out soon (a handful of us are running rc16 in a limited trial), so wait a bit any try again with it after updating your SF installation.

 

Joe L.

 

Why do we need an RC16?

 

I have the SF Webserver plugin 1.0.11 so think that is the latest unless anyone knows of one newer than that?

Please move the remainder of this SF not-starting discussion to the user-customizations forum.  You'll get more guidance there.

 

SF or a plugin you are using may need updating for the upcoming 5.0 release, but it is not an issues of the rc15a release itself.   

 

Joe L.

I do have a few questions:

1) I use the 'enable_ahci' script in my 'go' file to ensure that one of my SATA interfaces is recognised.  I presume (but haven't tried) that safe mode will fail to enable the interface and, therefore, some of my drives will be missing in safe mde.  Is it possible to have this functionality added to the 'standard' release?

Right this will be a problem for you if you need the functionality of that script.  First perhaps disable the script and see if your controller is recognized, it's possible the it's PCI id has been added to this kernel.

 

I have tried this, and the script is definitely still needed.

 

Also if controller is not in "ahci" mode via bios, perhaps see if there's a way to do this via bios - probably you have already done this though.

 

To the best of my knowledge, the interface is already set to ahci mode.

 

I did add an enhancement entry for this, but this will not make it into 5.0 final:

http://lime-technology.com/forum/index.php?topic=28111.0

 

Excellent!

In RC15a I see the following messages in the syslog:

 

Jun 25 19:06:03 Tower1 kernel: mpt2sas0: log_info(0x31120434): originator(PL), code(0x12), sub_code(0x0434)

Jun 25 19:08:19 Tower1 kernel: mpt2sas0: log_info(0x31120434): originator(PL), code(0x12), sub_code(0x0434)

 

I never saw them before, what do they mean? Trouble?

 

In RC15a I see the following messages in the syslog:

 

Jun 25 19:06:03 Tower1 kernel: mpt2sas0: log_info(0x31120434): originator(PL), code(0x12), sub_code(0x0434)

Jun 25 19:08:19 Tower1 kernel: mpt2sas0: log_info(0x31120434): originator(PL), code(0x12), sub_code(0x0434)

 

I never saw them before, what do they mean? Trouble?

 

Probably not, they look more informational than alarming.  They look like a developer wants some info logged when a certain case occurs, in case something still needs tweaking,  a sign of a driver module that is not very mature yet.

 

To better understand them, some context (if available) would be useful.  Can you attach a current syslog, plus an older syslog from a previous UnRAID version for comparison?

In RC15a I see the following messages in the syslog:

 

Jun 25 19:06:03 Tower1 kernel: mpt2sas0: log_info(0x31120434): originator(PL), code(0x12), sub_code(0x0434)

Jun 25 19:08:19 Tower1 kernel: mpt2sas0: log_info(0x31120434): originator(PL), code(0x12), sub_code(0x0434)

 

I never saw them before, what do they mean? Trouble?

 

I'm not sure why but I spent quite a bit of time with Google trying to find something regarding these codes. Both of these links reference it but don't provide a clear answer (or even one consistent answer).

 

http://serverfault.com/questions/407703/deciphering-continuing-mpt2sas-syslog-messages

https://groups.google.com/a/zfsonlinux.org/forum/#!topic/zfs-discuss/i0mHfWZcA_8

 

...Donovan

I've upgraded to 15a, and it appears to be working fine.

Any date we can expect to see 5. I know we are getting closer but now it looks like rc16 will be released? I keep getting my hopes up.

 

I think I know a solution. If everyone stops testing then nobody will have/find any problems, and BAM! 5.0 final release!

Right, and then we can 'CrashnBrn' after 

I think we will see rc16 or rc17 today.

 

 

im suppose rc17 (rc16a is already in testers), maybe will be with latest stable kernel 3.9.8 from yesterday

@Tom if you something release on weekend please post somewhere on forum aditional patches wich you use for kernel, thx

im suppose rc17 (rc16a is already in testers), maybe will be with latest stable kernel 3.9.8 from yesterday

@Tom if you something release on weekend please post somewhere on forum aditional patches wich you use for kernel, thx

I doubt he'll change kernels at this point being so close to 5.0-final (but I've been wrong before)

 

I'm going to guess 5.0-final is very close.  I know of only a handful of items left in the "bug list" for 5.X that have not been taken care of, and I think they are being worked with the individuals that reported them.

 

Joe L.

im suppose rc17 (rc16a is already in testers), maybe will be with latest stable kernel 3.9.8 from yesterday

@Tom if you something release on weekend please post somewhere on forum aditional patches wich you use for kernel, thx

There's nothing in the change logs for either 3.9.7 or 3.9.8 that would affect unRaid users, so no kernel update for 5.0.

im suppose rc17 (rc16a is already in testers), maybe will be with latest stable kernel 3.9.8 from yesterday

@Tom if you something release on weekend please post somewhere on forum aditional patches wich you use for kernel, thx

There's nothing in the change logs for either 3.9.7 or 3.9.8 that would affect unRaid users, so no kernel update for 5.0.

 

Did you hear anything from reiserfs maintainer?

Did you hear anything from reiserfs maintainer?

 

No, I think he might be out of the office this week, but this will not prevent release of 5.0.  I will include the modified source in the 'bzroot' file system.

Upgraded from 4.7.  (booted in safemode)  Keep getting these errors in syslog:

Jun 26 23:54:13 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 26 23:54:13 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 26 23:54:13 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 26 23:54:13 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 26 23:54:33 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 26 23:54:33 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 26 23:54:33 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 26 23:54:33 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 26 23:56:18 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 26 23:56:18 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 26 23:56:18 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 26 23:56:18 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 26 23:57:14 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 26 23:57:14 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 26 23:57:14 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 26 23:57:14 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 26 23:57:32 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 26 23:57:32 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 26 23:57:32 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 26 23:57:32 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 27 00:03:08 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 27 00:03:08 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 27 00:03:08 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 27 00:03:08 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 27 00:06:56 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 27 00:06:56 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 27 00:06:56 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 27 00:06:56 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 27 00:07:51 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 27 00:07:51 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 27 00:07:51 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 27 00:07:51 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 27 16:10:48 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 27 16:10:48 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 27 16:10:48 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 27 16:10:48 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 27 16:11:42 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 27 16:11:42 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 27 16:11:42 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 27 16:11:42 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 27 16:12:04 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 27 16:12:04 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 27 16:12:04 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 27 16:12:04 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5

 

Did you hear anything from reiserfs maintainer?

... but this will not prevent release of 5.0.

 

Does that mean there will be a 5.0a or 5.1 to incorporate the "official" fix that your patch resolves?

... Not necessarily a "bad" thing => but if a day or two's delay to hear from the maintainer would eliminate that, it may be worth waiting for 

... or perhaps an RC17 that's effectively v5.0 except for the official ReiserFS patch (with a release note that says as much).

 

Upgraded from 4.7.  (booted in safemode)  Keep getting these errors in syslog:

Jun 26 23:54:13 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 26 23:54:13 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 26 23:54:13 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 26 23:54:13 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 26 23:54:33 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 26 23:54:33 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 26 23:54:33 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 26 23:54:33 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 26 23:56:18 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 26 23:56:18 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 26 23:56:18 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 26 23:56:18 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 26 23:57:14 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 26 23:57:14 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 26 23:57:14 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 26 23:57:14 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 26 23:57:32 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 26 23:57:32 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 26 23:57:32 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 26 23:57:32 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 27 00:03:08 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 27 00:03:08 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 27 00:03:08 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 27 00:03:08 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 27 00:06:56 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 27 00:06:56 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 27 00:06:56 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 27 00:06:56 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 27 00:07:51 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 27 00:07:51 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 27 00:07:51 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 27 00:07:51 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 27 16:10:48 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 27 16:10:48 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 27 16:10:48 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 27 16:10:48 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 27 16:11:42 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 27 16:11:42 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 27 16:11:42 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 27 16:11:42 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5
Jun 27 16:12:04 VBox-v5-RC kernel: md: disk0: ATA_OP e3 ioctl error: -5
Jun 27 16:12:04 VBox-v5-RC kernel: md: disk1: ATA_OP e3 ioctl error: -5
Jun 27 16:12:04 VBox-v5-RC kernel: md: disk2: ATA_OP e3 ioctl error: -5
Jun 27 16:12:04 VBox-v5-RC kernel: md: disk3: ATA_OP e3 ioctl error: -5

Please post entire system log.

Hi,

 

Is there a mirror somewhere to get the rc15a ? I can't download it from the main page, the download is to slow and then stop. Perhaps it's a server overload ?

 

Thanks.

Hi,

 

Is there a mirror somewhere to get the rc15a ? I can't download it from the main page, the download is to slow and then stop. Perhaps it's a server overload ?

 

Thanks.

 

Hmmm, I just went on the site and the dl maxes out my connection...

 

try again

Hi guys,

got a bit of an issue. Im not great with Linux and been a while since upgrading beta versions but need to put some bigger drives in.

Anyway, I was previously on RC4, everything working smoothly.

 

As directed by release notes, i copied over bzroot and bzimage, as well as : "Delete the file config/super.dat. You will need to re-assign all your hard drives."

 

theres isnt a mention of syslinux.cfg to copy over, but in a previous thread, it was mentioned to do so, i havent yet, wanted to confirm.

Anyway, on boot up, all my drives are unassigned, which is fine, thats what the step above says it would do, but the next line in the release notes says:

"you should see "Stopped. Configuration valid." array status with all disks assigned correctly"

 

so im a bit confused. I did take a screenshot of where each disk is assigned in which slot, but should i do so? i tried assigning parity drive, and was a blue ball. That good?

What should i expect after all drives assigned correctly and array started?

 

thanks in advance

 

 

 

Noticed this thread might not be so active, so will repost in general support.

Thanks

Noticed this thread might not be so active, so will repost in general support.

Thanks

 

This is in the wiki for the upgrade

 

5.0-rc9 through 5.0-rc15

1. Prepare the flash: either shutdown your server and plug the flash into your PC or Stop the array and perform the following actions referencing the flash share on your network:  Copy the files bzimage, bzroot, and syslinux.cfg from the zip file to the root of your flash device, overwriting the same-named files already there.

 

So yes you should have the 3 files

 

Thanks mejutty. I was only looking in rc4 section.

 

As for the other issue, I contacted a friend who recently upgraded and was told to assign drives as they were so i did that. All is good. parity rebuilding.

 

hope this helps someone else