Re: external USB drive on nas.naund.org
Hello, the external USB drive recently stopped being recognized at all by this server. FreeBSD files.local 11.4-RELEASE-p2 FreeBSD 11.4-RELEASE-p2 #0: Tue Aug 4 19:21:02 UTC 2020 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 This setup has worked for over 2 years, unfortunately I cannot tell to which date, or to which update it correlates to. This server is updated with freebsd-update and pkg (binary packages only), typically a few days after any security advisory comes out. Currently nothing happens when I attach or remove the drive from tany USB port of the Supermicor X8SIL motherboard. No BIOS changes were made in over a year. At this time, neither dmesg, usbconfig devlist nor camcontrol show the disk. I tried rollback from 11.3-RELEASE-p12 to 11.3-RELEASE-p11 and that did not work either, before upgrading all the way to 11.4-RELEASE-p2. What debugging should I try next? The disk is recognized OK on a CentOS 7 server with similar hardware and on my MacbookPro. I do have an older dmesg excerpt from when it had kernel 11.3-RELEASE-p11 and it still worked: ugen1.3: at usbus1 umass0 on uhub2 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x8100 umass0:4:0: Attached to scbus4 da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 da0: Fixed Direct Access SPC-4 SCSI device da0: Serial Number 24865351072710207E da0: 40.000MB/s transfers da0: 1144641MB (2344225968 512 byte sectors) da0: quirks=0x2 Thanks, andreas -- Andreas Ott andr...@naund.org ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 11.3-RELEASE-p7 is approaching its End-of-Life date ?
[I am not sure if this is the correct mailing list but trying to access other "releng" archives is giving me only 502 at the moment] I am trying to run freebsd-upgrade this morning to get fixes for the SAs. The system gives me this message: WARNING: FreeBSD 11.3-RELEASE-p7 is approaching its End-of-Life date. It is strongly recommended that you upgrade to a newer release within the next 2 months. Neither security page nor releng page show any end of support dates within two months, combining "11.4-RELEASE + 3 months" and "11.4-RELEASE June 2020" respectively. Would it be possible to update whatever file this trigger comes from to make the warning message be in line with upcoming release schedules? Thanks, andreas - Andreas Ott K6OTT +1.408.431.8727 andr...@naund.org ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: leapsecond file
Hi,
On Wed, Aug 24, 2016 at 06:55:37PM -0700, Cy Schubert wrote:
> The file was obtained from USNO. Except for a $FreeBSD$ and a minor
> spelling fix that was brought forward from r298087, the file was not
> altered in any way. One of the problems is that the minor spelling fix
> invalidated the secure hash at the end of the file, ntpd ignores the file.
> r298087 needs to be reverted. (cc'd pfg@) I'll revert r298087.
If I read the hash instructions towards the bottom of the file, you should
be good to fix typos or add $FreeBSD$ in a comment line, the only lines
that are hashed are the data and time stamps. Syslog shows that during the
last week the hash was considered OK on the file in 10.3-p7 with
$FreeBSD: releng/10.3/etc/ntp/leap-seconds 295461 2016-02-10 07:16:17Z cy $ .
2016 Aug 18 18:26:07 [ntp.notice] mon leapsecond file
('/var/db/ntpd.leap-seconds.list'): good hash signature
2016 Aug 18 18:26:07 [ntp.notice] mon leapsecond file
('/var/db/ntpd.leap-seconds.list'): loaded, expire=2016-06-01T00:00:00Z
last=2015-07-01T00:00:00Z ofs=36
2016 Aug 18 18:26:07 [ntp.err] mon leapsecond file
('/var/db/ntpd.leap-seconds.list'): expired less than 79 days ago
2016 Aug 18 18:26:07 [console.info] mon Aug 18 18:26:07 mon ntpd[584]:
leapsecond file ('/var/db/ntpd.leap-seconds.list'): expired less than 79 days
ago
> I'll revert pfg's spelling fixup which I had brought forward and I'll need
> to remove $FreeBSD$ as well, validating the hash again. Additional code
> will need to be added to rc.d/ntpd to replace the copy in /var/db if
> $FreeBSD$ exists.
Please check the hash instructions, I don't think it's needed to remove that.
-andreas
--
Andreas Ott K6OTT +1.408.431.8727 andr...@naund.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: leapsecond file
Hi, On Wed, Aug 24, 2016 at 02:21:14PM -0600, Ian Lepore wrote: > It looks like part of the problem here is that the Last Update value IS > changing when the leap data itself is not. Our commit logs say the > files have been obtained from USNO. Either USNO is violating the > standard in their files, or the value is getting modified before it's > commited to the freebsd repos. (I'm adding Cy to the CC list, since he > committed them.) The beauty of standards is, that there are too many to chose from. These seem to be the three top sources of the file (lmgtfy), and while they might agree in the actual leapsecond data, the meta information in it is very different. fetch -m --no-passive ftp://tycho.usno.navy.mil/pub/ntp/leap-seconds.list fetch https://www.ietf.org/timezones/data/leap-seconds.list fetch https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list [root@mon /tmp]# ls -la *list -rw-r--r-- 1 root wheel 10384 Mar 14 18:33 ietf-leap-seconds.list -rw-r--r-- 1 root wheel 8795 Jul 6 14:13 navy-leap-seconds.list -rw-r--r-- 1 root wheel 4920 Jul 6 14:37 obspm-leap-seconds.list [root@mon /tmp]# wc *list 2491960 10384 ietf-leap-seconds.list 22016578795 navy-leap-seconds.list 117 8814920 obspm-leap-seconds.list [root@mon /tmp]# egrep -e Update\|expires\|^'#\$'\|^'#@' *list ietf-leap-seconds.list:#Last Update of leap second values: 5 January 2015 ietf-leap-seconds.list:#$3629404800 ietf-leap-seconds.list:#Updated through IERS Bulletin C51 ietf-leap-seconds.list:#File expires on: 28 December 2016 ietf-leap-seconds.list:#@ 3691872000 navy-leap-seconds.list:#Last Update of leap second values: 6 Jul 2016 navy-leap-seconds.list:#$3676752000 navy-leap-seconds.list:#Updated through IERS Bulletin C 52 navy-leap-seconds.list:#File expires on: 1 Jun 2017 navy-leap-seconds.list:#@ 3705264000 obspm-leap-seconds.list:# Updated through IERS Bulletin C (ftp://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat) obspm-leap-seconds.list:#$ 3676752000 obspm-leap-seconds.list:# File expires on 28 June 2017 obspm-leap-seconds.list:#@ 3707596800 [root@mon /tmp]# For now, the following workaround did get me a current file that ended up in /var/db/ after being downloaded to /var/run/ . IMHO, I have bought myself some time that this either gets fixed upstream, or until I need to keep my own site copy of the file on a web server that I'm responsible to update every 5.95 months. [root@mon /tmp]# grep leap /etc/rc.conf ntp_leapfile_fetch_opts="-m --no-passive" ntp_leapfile_sources="ftp://tycho.usno.navy.mil/pub/ntp/leap-seconds.list; [root@mon /tmp]# -andreas -- Andreas Ott K6OTT +1.408.431.8727 andr...@naund.org ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: leapsecond file
On Sun, Aug 07, 2016 at 09:44:55PM -0700, Kevin Oberman wrote: > On 11.0-BETA4 I have: > > grep expires /var/db/ntpd.leap-seconds.list > #File expires on: 1 Jun 2017 > > But I see what you do on 10.3-RELEASE. Looks like the update has not made > it into 10 (an I would guess 9). The flaw is in the internal versioning of files, it does fetch the newer file from IETF and puts it into /var/run/ntpd.leap-seconds.list, but although the expiry is newer, the FreeBSD onboard source version claims to be newer in the 'last update date in NTP timestamp format' line ... FreeBSD 10.3-RELEASE-p7 onboard source is in /etc/ntp/leap-seconds, which gets copied to /var/db/ntpd.leap-seconds.list. The fetch IETF file downloads to /var/run/ntpd.leap-seconds.list . [root@mon ~]# egrep -e Update\|expires\|^'#\$' /etc/ntp/leap-seconds # Last Update of leap second values: 31 Dec 2015 #$ 3660508800 # Updated through IERS Bulletin C 50 # File expires on: 1 Jun 2016 [root@mon ~]# egrep -e Update\|expires\|^'#\$' /var/db/ntpd.leap-seconds.list # Last Update of leap second values: 31 Dec 2015 #$ 3660508800 # Updated through IERS Bulletin C 50 # File expires on: 1 Jun 2016 [root@mon ~]# egrep -e Update\|expires\|^'#\$' /var/run/ntpd.leap-seconds.list # Last Update of leap second values: 5 January 2015 #$ 3629404800 # Updated through IERS Bulletin C51 # File expires on: 28 December 2016 [root@mon ~]# with the end result that the file from /var/run/ never gets moved to /var/db/ . The 480.leapfile-ntpd used by periodic calls the same rc file fetch and comparison. -andreas -- Andreas Ott K6OTT +1.408.431.8727 andr...@naund.org ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: binary updates for 10.3 failing
On Thu, May 05, 2016 at 09:07:52AM -0700, Andreas Ott wrote: > I'm not sure if the stable list is the correct place to report this, Magically, overnight a PR appeared... https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209147 and it seems more widespread than 10.3-RELEASE. -andreas -- Andreas Ott K6OTT +1.408.431.8727 andr...@naund.org ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
binary updates for 10.3 failing
Hi, I'm not sure if the stable list is the correct place to report this, but currently binary updates are not working. I see posts on the forum but no solutions are being offered (other than updates from source, which are difficult on production systems missing the src component). Something broke recently, it worked to update from RELEASE to -p1. Symptoms are like this (note that the system is -p1 already but the binay updater identifies it as -p0): [root@www ~]# freebsd-version 10.3-RELEASE-p1 [root@www ~]# freebsd-update fetch src component not installed, skipped Looking up update.FreeBSD.org mirrors... none found. Fetching metadata signature for 10.3-RELEASE from update.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 10.3-RELEASE-p0. [root@www ~]# I deleted /var/db/freebsd-update/* and tried again, same result. -andreas - Andreas Ott K6OTT +1.408.431.8727 andr...@naund.org ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Error upgrading from 10.1-RELEASE to 10.2-RELEASE
Hi, On Mon, Aug 24, 2015 at 05:07:55PM +0200, Christian Kratzer wrote: The only way I have been able to upgrade systems is by repeatedly running freebsd-update. Same here, one system needed three attempts of running freebsd-upgrade and the other one four, on both I pointed to an update server with -s . -andreas - Andreas Ott K6OTT +1.408.431.8727 andr...@naund.org ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd-update to 10.2-RELEASE broken ?
320330340350.. done. Applying patches... done. Fetching 1810 files... e663aaaca813b1ffebc92189b0f209a413806d0faf5a700bab9c9326e6e5b556 has incorrect hash. [root@dev1 /var/db/freebsd-update]# Third run: [root@dev1 /var/db/freebsd-update]# freebsd-update -s update2.freebsd.org -r 10.2-RELEASE upgrade Looking up update2.freebsd.org mirrors... none found. Fetching metadata signature for 10.1-RELEASE from update2.freebsd.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/generic src/src world/base world/doc The following components of FreeBSD do not seem to be installed: world/games Does this look reasonable (y/n)? y Fetching metadata signature for 10.2-RELEASE from update2.freebsd.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. Fetching files from 10.1-RELEASE for merging... done. Preparing to download files... done. Fetching 1 patches. done. Applying patches... done. Fetching 521 files... done. Attempting to automatically merge changes in files... done. The following file could not be merged automatically: /etc/ntp.conf Press Enter to edit this file in /usr/bin/vi and resolve the conflicts manually... [manually fix diff and write file], then acknowledge the change log of all updated files, proceed with install (kernel), reboot and one more install (user land). Additional debug output available, just ask for it. I have a second server of the same specs awaiting upgrade as well, and then some more. Thanks, andreas -- Andreas Ott K6OTT +1.408.431.8727 andr...@naund.org ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
