FreeBSDD Upgrade Failing

[Shiv. Nath]

Hi FreeBSD Community,

i got warning that 9.1RC3 is approaching end of its life, i should upgrade
with in two week. when i started the upgrade, i get the following error.
any solution anyone knows?

[root@rock]# freebsd-update -r 9.1-RELEASE upgrade
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 9.1-RC3 from update5.FreeBSD.org... done.
Fetching metadata index... done.
Inspecting system... done.

The following components of FreeBSD seem to be installed:
kernel/generic src/src world/base world/doc world/games world/lib32

The following components of FreeBSD do not seem to be installed:

Does this look reasonable (y/n)? y

Fetching metadata signature for 9.1-RELEASE from update5.FreeBSD.org...
failed.
Fetching metadata signature for 9.1-RELEASE from update4.FreeBSD.org...
failed.
Fetching metadata signature for 9.1-RELEASE from update3.FreeBSD.org...
failed.
No mirrors remaining, giving up.


Thanks / Shiv. Nath

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSDD Upgrade Failing

[Chris Petrik]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

9.1-RELEASE is not officially released yet, so that is why you are
seeing that.

On 12/5/2012 1:50 AM, Shiv. Nath wrote:
> Hi FreeBSD Community,
> 
> i got warning that 9.1RC3 is approaching end of its life, i should
> upgrade with in two week. when i started the upgrade, i get the
> following error. any solution anyone knows?
> 
> [root@rock]# freebsd-update -r 9.1-RELEASE upgrade Looking up
> update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata
> signature for 9.1-RC3 from update5.FreeBSD.org... done. Fetching
> metadata index... done. Inspecting system... done.
> 
> The following components of FreeBSD seem to be installed: 
> kernel/generic src/src world/base world/doc world/games
> world/lib32
> 
> The following components of FreeBSD do not seem to be installed:
> 
> Does this look reasonable (y/n)? y
> 
> Fetching metadata signature for 9.1-RELEASE from
> update5.FreeBSD.org... failed. Fetching metadata signature for
> 9.1-RELEASE from update4.FreeBSD.org... failed. Fetching metadata
> signature for 9.1-RELEASE from update3.FreeBSD.org... failed. No
> mirrors remaining, giving up.
> 
> 
> Thanks / Shiv. Nath
> 
> ___ 
> freebsd-stable@freebsd.org mailing list 
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable To
> unsubscribe, send any mail to
> "freebsd-stable-unsubscr...@freebsd.org"
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQEcBAEBAgAGBQJQvwMzAAoJEAGnn5Nn8qWUBtAH/jpwSXbfxGKPvXSlif3G0hDD
gep7IouohqEC4mS/Ys2ZVzMSwdvibyD5QX1FAOfp9vYWRHa+XTnRSygZVZD8rZbW
9xY9A3M2sbyuQDPPSgzZUxwiXbCfEPcVuyDVdrh26IJbebFNi97P81BYIERAIxC+
G1yi9jFMNWpyI4EXzJBMeELDzoBs1HGNKL6SSzxOTGXkWh41JgaJl+ihOw7QencO
dnwGTYUkVxQUw68kdwD2Y0ZdFKwR/JRcS9QAjpsazSXMQkukVHOKPYGe71wxg1YI
514D4VzVhH/RoEDDqBmtLr3fITz0JA/UoQt61tcahYDdBE/xTOR36LRZNtSumtc=
=JXBB
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Update Failing FreeBSD 9.1-Release

[Shiv. Nath]

anyone knows what to do?

[root@rock]# freebsd-update -r 9.1-RELEASE upgrade
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 9.1-RC3 from update5.FreeBSD.org... done.
Fetching metadata index... done.
Fetching 1 metadata patches. done.
Applying metadata patches... done.
Inspecting system... done.

The following components of FreeBSD seem to be installed:
kernel/generic src/src world/base world/doc world/games world/lib32

The following components of FreeBSD do not seem to be installed:

Does this look reasonable (y/n)? y

Fetching metadata signature for 9.1-RELEASE from update5.FreeBSD.org...
failed.
Fetching metadata signature for 9.1-RELEASE from update4.FreeBSD.org...
failed.
Fetching metadata signature for 9.1-RELEASE from update3.FreeBSD.org...
failed.
No mirrors remaining, giving up.


Thanks / Shiv. Nath

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Update Failing FreeBSD 9.1-Release

[Ronald Klop]

On Wed, 05 Dec 2012 12:16:25 +0100, Shiv. Nath  
 wrote:



anyone knows what to do?


Maybe wait until 9.1-RELEASE is actually released.

Ronald.



[root@rock]# freebsd-update -r 9.1-RELEASE upgrade
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 9.1-RC3 from update5.FreeBSD.org... done.
Fetching metadata index... done.
Fetching 1 metadata patches. done.
Applying metadata patches... done.
Inspecting system... done.

The following components of FreeBSD seem to be installed:
kernel/generic src/src world/base world/doc world/games world/lib32

The following components of FreeBSD do not seem to be installed:

Does this look reasonable (y/n)? y

Fetching metadata signature for 9.1-RELEASE from update5.FreeBSD.org...
failed.
Fetching metadata signature for 9.1-RELEASE from update4.FreeBSD.org...
failed.
Fetching metadata signature for 9.1-RELEASE from update3.FreeBSD.org...
failed.
No mirrors remaining, giving up.


Thanks / Shiv. Nath

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSDD Upgrade Failing

[Ronald Klop]

On Wed, 05 Dec 2012 08:50:04 +0100, Shiv. Nath  
 wrote:



Hi FreeBSD Community,

i got warning that 9.1RC3 is approaching end of its life, i should  
upgrade

with in two week.


Where did you get this warning? I have never seen it anywhere on the  
internet or on my machines.


Ronald.


when i started the upgrade, i get the following error.
any solution anyone knows?

[root@rock]# freebsd-update -r 9.1-RELEASE upgrade
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 9.1-RC3 from update5.FreeBSD.org... done.
Fetching metadata index... done.
Inspecting system... done.

The following components of FreeBSD seem to be installed:
kernel/generic src/src world/base world/doc world/games world/lib32

The following components of FreeBSD do not seem to be installed:

Does this look reasonable (y/n)? y

Fetching metadata signature for 9.1-RELEASE from update5.FreeBSD.org...
failed.
Fetching metadata signature for 9.1-RELEASE from update4.FreeBSD.org...
failed.
Fetching metadata signature for 9.1-RELEASE from update3.FreeBSD.org...
failed.
No mirrors remaining, giving up.


Thanks / Shiv. Nath

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Update Failing FreeBSD 9.1-Release

[Ronald Klop]

On Wed, 05 Dec 2012 14:58:52 +0100, Franci Nabalanci   
wrote:


And when update will be out? There are nothing about month on the  
official

site.


According to the commits it is planned for today (USA time, so for me it  
is tonight or tomorrow morning).

http://www.secnetix.de/olli/FreeBSD/svnews/index.py?r=243808
http://svnweb.freebsd.org/base/releng/9.1/UPDATING?r1=243709&r2=243708&pathrev=243709

As far as I know it can take a little while before freebsd-update handles  
the new version.


Ronald.

NB: please leave the freebsd-stable@ address in your replies.




 On Dec 5, 2012 5:30 AM, "Ronald Klop"   
wrote:



On Wed, 05 Dec 2012 12:16:25 +0100, Shiv. Nath <
shiv.nath@digital-infotech.**net >  
wrote:


 anyone knows what to do?




Maybe wait until 9.1-RELEASE is actually released.

Ronald.


 [root@rock]# freebsd-update -r 9.1-RELEASE upgrade

Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 9.1-RC3 from update5.FreeBSD.org...  
done.

Fetching metadata index... done.
Fetching 1 metadata patches. done.
Applying metadata patches... done.
Inspecting system... done.

The following components of FreeBSD seem to be installed:
kernel/generic src/src world/base world/doc world/games world/lib32

The following components of FreeBSD do not seem to be installed:

Does this look reasonable (y/n)? y

Fetching metadata signature for 9.1-RELEASE from update5.FreeBSD.org...
failed.
Fetching metadata signature for 9.1-RELEASE from update4.FreeBSD.org...
failed.
Fetching metadata signature for 9.1-RELEASE from update3.FreeBSD.org...
failed.
No mirrors remaining, giving up.


Thanks / Shiv. Nath

__**_
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/**mailman/listinfo/freebsd-**stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@**
freebsd.org "


__**_
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/**mailman/listinfo/freebsd-**stable
To unsubscribe, send any mail to  
"freebsd-stable-unsubscribe@**freebsd.org

"

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSDD Upgrade Failing

[Ronald Klop]

On Wed, 05 Dec 2012 14:56:35 +0100, Franci Nabalanci   
wrote:



Did you try FreeBSD-update fetch?


No, I have never used that.

Ronald.

 On Dec 5, 2012 5:31 AM, "Ronald Klop"   
wrote:



On Wed, 05 Dec 2012 08:50:04 +0100, Shiv. Nath <
shiv.nath@digital-infotech.**net >  
wrote:


 Hi FreeBSD Community,


i got warning that 9.1RC3 is approaching end of its life, i should  
upgrade

with in two week.



Where did you get this warning? I have never seen it anywhere on the
internet or on my machines.

Ronald.

 when i started the upgrade, i get the following error.

any solution anyone knows?

[root@rock]# freebsd-update -r 9.1-RELEASE upgrade
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 9.1-RC3 from update5.FreeBSD.org...  
done.

Fetching metadata index... done.
Inspecting system... done.

The following components of FreeBSD seem to be installed:
kernel/generic src/src world/base world/doc world/games world/lib32

The following components of FreeBSD do not seem to be installed:

Does this look reasonable (y/n)? y

Fetching metadata signature for 9.1-RELEASE from update5.FreeBSD.org...
failed.
Fetching metadata signature for 9.1-RELEASE from update4.FreeBSD.org...
failed.
Fetching metadata signature for 9.1-RELEASE from update3.FreeBSD.org...
failed.
No mirrors remaining, giving up.


Thanks / Shiv. Nath

__**_
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/**mailman/listinfo/freebsd-**stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@**
freebsd.org "


__**_
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/**mailman/listinfo/freebsd-**stable
To unsubscribe, send any mail to  
"freebsd-stable-unsubscribe@**freebsd.org

"

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: cam SCSI negotiation issues (mpt in that case), only 3.300MB/s transfers

[Harald Schmalzbauer]

 schrieb Harald Schmalzbauer am 23.11.2012 14:39 (localtime):
> ...
> found out thathint.mpt.0.msi_enable="1"
> solves the interrupt storm problem, although dmesg output still is
> exactly the same:
> mpt0:  port 0x4000-0x40ff mem
> 0xd644-0xd645,0xd642-0xd643 irq 18 at device 0.0 on pci3
> mpt0: MPI Version=1.2.15.0
> Btw, I'm still curious what the sysctl "hw.mpt.0.role" means? With my
> LSI1030 it's "3", an onther 1068, it's "1"

Any hint for me what "hw.mpt.0.role" means?


> ...I had no luck using "camcontrol negotiate sa0 -R 40" to
> alter the negotiation parameters.
> It always shows 3,300MB/s and seems to reflect reality

I'd still need help here if possible.
Is there any point to start for non-developers? Any SCSI command
"secrets" I can try?
If anybody is interested in solving, but lacks hardware, I'd donate one
LSI20320IE.

Thanks,

-Harry (not subscribed to freebsd-scsi@)



signature.asc
Description: OpenPGP digital signature

12/5/2012

[LOTTO IT]

Hello freebsd-stable@freebsd.org , Please confirm if you are the owner of this 
email. Reply

 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: cam SCSI negotiation issues (mpt in that case), only 3.300MB/s transfers

[Harald Schmalzbauer]

 schrieb Harald Schmalzbauer am 05.12.2012 21:04 (localtime):
>  schrieb Harald Schmalzbauer am 23.11.2012 14:39 (localtime):
>> ...
>> found out thathint.mpt.0.msi_enable="1"
>> solves the interrupt storm problem, although dmesg output still is
>> exactly the same:
>> mpt0:  port 0x4000-0x40ff mem
>> 0xd644-0xd645,0xd642-0xd643 irq 18 at device 0.0 on pci3
>> mpt0: MPI Version=1.2.15.0
>> Btw, I'm still curious what the sysctl "hw.mpt.0.role" means? With my
>> LSI1030 it's "3", an onther 1068, it's "1"
> Any hint for me what "hw.mpt.0.role" means?
>
>
>> ...I had no luck using "camcontrol negotiate sa0 -R 40" to
>> alter the negotiation parameters.
>> It always shows 3,300MB/s and seems to reflect reality
> I'd still need help here if possible.
> Is there any point to start for non-developers? Any SCSI command
> "secrets" I can try?
> If anybody is interested in solving, but lacks hardware, I'd donate one
> LSI20320IE.
>

Found dev.mpt.0.debug, set to 8:

Dec  5 21:05:36 wega kernel: mpt0: exit mpt_intr
Dec  5 21:05:36 wega kernel: mpt0: enter mpt_intr
. (some hundred times repeated)

kernel: mpt0: exit mpt_intr
kernel: mpt0: enter mpt_intr
kernel: mpt0: TMF complete: req 0xff8030ace480:304 status 0x0
kernel: mpt0: exit mpt_intr
kernel: SCSI IO Request @ 0xff823ffa7b00
kernel: Chain Offset  0x00
kernel: MsgFlags  0x00
kernel: MsgContext0x0001012a
kernel: Bus:0
kernel: TargetID0
kernel: SenseBufferLength   32
kernel: LUN:  0x0
kernel: Control   0x0500  NODATATRANSFER  UNTAGGED
kernel: DataLength 0x
kernel: SenseBufAddr   0x911255e0
kernel: CDB[0:6]   00 00 00 00 00 00
kernel: mpt0: enter mpt_intr
kernel: mpt0: exit mpt_intr
kernel: mpt0: enter mpt_intr
kernel: mpt0: Address Reply:
kernel: SCSI IO Request Reply @ 0xff823fff9a00
kernel: IOC StatusSuccess
kernel: IOCLogInfo0x
kernel: MsgLength 0x08
kernel: MsgFlags  0x00
kernel: MsgContext0x0001012a
kernel: Bus:  0
kernel: mpt0: enter mpt_intr
kernel: mpt0: exit mpt_intr
kernel: mpt0: enter mpt_intr
kernel: mpt0: exit mpt_intr
kernel: mpt0: enter mpt_intr
kernel: mpt0: exit mpt_intr
kernel: mpt0: enter mpt_intr
kernel: mpt0: exit mpt_intr
kernel: mpt0: enter mpt_intr
kernel: mpt0: exit mpt_intr
kernel: mpt0: enter mpt_intr
kernel: mpt0: exit mpt_intr
kernel: mpt0: enter mpt_intr
kernel: mpt0: TMF complete: req 0xff8030ace480:304 status 0x0
kernel: mpt0: exit mpt_intr
kernel: SCSI IO Request @ 0xff823ffa7b00
kernel: Chain Offset  0x00
kernel: MsgFlags  0x00
kernel: MsgContext0x0001012a
kernel: Bus:0
kernel: TargetID0
kernel: SenseBufferLength   32
kernel: LUN:  0x0
kernel: Control   0x0500  NODATATRANSFER  UNTAGGED
kernel: DataLength 0x
kernel: SenseBufAddr   0x911255e0
kernel: CDB[0:6]   00 00 00 00 00 00
kernel: mpt0: enter mpt_intr
kernel: mpt0: exit mpt_intr
kernel: mpt0: enter mpt_intr
kernel: SCSI IO Request Reply @ 0xff823fff9a00
kernel: IOC StatusSuccess
kernel: IOCLogInfo0x
kernel: MsgLength 0x08
kernel: MsgFlags  0x00
kernel: MsgContext0x0001012a
kernel: Bus:  0
kernel: TargetID  0
kernel: CDBLength 6
kernel: SCSI Status:  Check Condition
kernel: SCSI State:   (0x0001)AutoSense_Valid
kernel: TransferCnt   0x
kernel: SenseCnt  0x0012
kernel: ResponseInfo  0x
kernel: mpt0: exit mpt_intr
kernel: SCSI IO Request @ 0xff80002ae3d0
kernel: Chain Offset  0x00
kernel: MsgFlags  0x00
kernel: MsgContext0x0001012b
kernel: Bus:0
kernel: TargetID0
kernel: SenseBufferLength   18
kernel: LUN:  0x0
kernel: Control   0x02000500  READ  UNTAGGED
kernel: DataLength 0x0024
kernel: SenseBufAddr   0x911257e0
kernel: CDB[0:6]   12 00 00 00 24 00
kernel: 64_BIT_ADDRESSING LAST_ELEMENT END_OF_BUFFER END_OF_LIST
kernel: mpt0: enter mpt_intr
kernel: mpt0: Context Reply: 0x0001012b
kernel: mpt0: exit mpt_intr
kernel: SCSI IO Request @ 0xff80002ae3d0
kernel: Chain Offset  0x00
kernel: MsgFlags  0x00
kernel: MsgContext0x0001012c
kernel: Bus:0
kernel: TargetID0
kernel: SenseBufferLength   18
kernel: LUN:  0x0
kernel: Control   0x02000500  READ  UNTAGGED
kernel: DataLength 0x0038
kernel: SenseBufAddr   0x911259e0
kernel: CDB[0:6]   12 00 00 00 38 00
kernel: SE64 0xff8240020830: Addr=0x57ce18f8
FlagsLength=0xd338
kernel: 64_BIT_ADDRESSING LAST_ELEMENT END_OF_BUFFER END_OF_LIST
kernel: mpt0: enter mpt_intr
kernel: mpt0: Context Reply: 0x0001012c
kernel: mpt0: exit mpt_intr
kernel: mpt0: enter mpt_intr
kernel: mpt0: exit mpt_intr
kernel: mpt0: mpt_get_spi_settings[0]: current NP 0 Info 9
kernel: mpt0: mpt_get_spi_settings[0]: ACTIVE flags 0x29 per 0x0 off=0
kernel: SCSI IO Request @ 0xff80002ae3d0
kernel: Chain Offset  0x00
kernel: MsgContext 

Re: cam SCSI negotiation issues (mpt in that case), only 3.300MB/s transfers

[Harald Schmalzbauer]

 schrieb Harald Schmalzbauer am 05.12.2012 22:23 (localtime):
> kernel: IOC StatusSCSI: Data Underrun

Searching for this topic showd an 53c1030 errata fix:

https://patchwork.kernel.org/patch/94223/

Like you guessed, I can't make use of it, but probably someone else?

Thanks,

-Harry



signature.asc
Description: OpenPGP digital signature