ZFS Woes... Guru needed
Hi Guys, I have a FreeBSD9.3-stable system with 3x 68GB IBM Disks (Cheeta) configured wirh gpt and zfs as pool zroot. In the last days one of the disks was dying and I've disconnected the bad going drive to connect an other one. The new disk is physically identical but replacing the bad disk with the new one failed, since the new disk reported only 65 insted of 68GByte free space (other firmware, IBMAS400 in the inquiry string). So I looked at the bad disks and found one with defective electronics and one with defective platters and exchanged the controllers (all Disks are in real life ST373453LC disks, original with 534 Byte sector size or so). I've rebooted the system, set up a camcontrol cmd for changing the sector size to 512Byte and begun to format the disk with camcontrol format. While formating for a while the system apniced with an adaptec register dump and would'nt boot anymore with the infamous ZFS: i/o error - all block copies unavailabe, kernel booted but mountroot failed. I've found out that I could boot the system when I manually load the zfs.ko module at the loader prompt. The filesystem is somewhat broken now, /boot/loader.conf isn't readable and so are other files, /etc/rc.conf for example, /usr/home is empty. I've tried to reformat the disk a 2nd time, but it never finished. Tried the next disk and this worked, tried a replace in the with zpool but I have an unclear state here: # zpool status -v pool: zroot state: DEGRADED status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://illumos.org/msg/ZFS-8000-8A scan: resilvered 42.4G in 1h25m with 2 errors on Sat Jul 11 12:28:53 2015 config: NAME STATE READ WRITE CKSUM zroot DEGRADED 0 086 raidz1-0 DEGRADED 0 0 344 gpt/disk0 ONLINE 0 0 0 gpt/disk1 ONLINE 0 0 0 replacing-2DEGRADED 0 0 0 6329731321389372496 OFFLINE 0 0 0 was /dev/gpt/disk 2/old gpt/disk2ONLINE 0 0 0 errors: Permanent errors have been detected in the following files: zroot:0x0 zroot/var/db:0x0 # I'm unable to remove thedisk with that id 6329731321389372496 and don't know what replacing-2 could mean at all. I do have an tar backup from my /home from almost a week ago, but in the meantime I've done some serious work with Kicad (PCB's) tat I really don't want to loose. The Backups from the system itselves are really old... How can I repair this trouble? Can I get my data back at all? zpool scrub ran several times, resilvering too. I can't remove that loader.conf file or others. (cat /etc/rc.conf .. unknown error 122) I think I need ZFS Guru here...please help.. Regards, Holm -- Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583 www.tsht.de, i...@tsht.de, Fax +49 3731 74200, Mobil: 0172 8790 741 ___ 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: ZFS Woes... Guru needed
Hi, On 11 Jul 2015, at 14:19, Holm Tiffe h...@freibergnet.de wrote: So I looked at the bad disks and found one with defective electronics and one with defective platters and exchanged the controllers (all Disks are in real life ST373453LC disks, original with 534 Byte sector size or so). Can’t comment on the ZFS aspects, but I’m not sure you can rely on swapping drive electronics these days. I believe that in at least some cases boards are parameterised for the particular platters and heads during production. -- Bob Bishop r...@gid.co.uk ___ 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 10.2-BETA1 Now Available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The first BETA build of the 10.2-RELEASE release cycle is now available. Installation images are available for: o amd64 GENERIC o i386 GENERIC o ia64 GENERIC o powerpc GENERIC o powerpc64 GENERIC64 o sparc64 GENERIC o armv6 BEAGLEBONE o armv6 CUBOX-HUMMINGBOARD o armv6 RPI-B o armv6 WANDBOARD Installer images and memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.2/ The image checksums follow at the end of this email. If you notice problems you can report them through the Bugzilla PR system or on the -stable mailing list. If you would like to use SVN to do a source based update of an existing system, use the stable/10 branch. A list of changes since 10.1-RELEASE are available on the stable/10 release notes: https://www.freebsd.org/relnotes/10-STABLE/relnotes/article.html Please note, the release notes page is not yet complete, and will be updated on an ongoing basis as the 10.2-RELEASE cycle progresses. === Virtual Machine Disk Images === VM disk images are available for the amd64 and i386 architectures. Disk images may be downloaded from the following URL (or any of the FreeBSD FTP mirrors): ftp://ftp.freebsd.org/pub/FreeBSD/releases/VM-IMAGES/10.2-BETA1/ The partition layout is: ~ 512k - freebsd-boot GPT partition type (bootfs GPT label) ~ 1GB - freebsd-swap GPT partition type (swapfs GPT label) ~ ~17GB - freebsd-ufs GPT partition type (rootfs GPT label) The disk images are available in QCOW2, VMDK, and raw disk image formats The image download size is approximately 135 MB, which decompress to a 20GB sparse image. Note: A last-minute issue was discovered with the VHD-formatted images, and they have been pulled from the mirrors as a result. === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMIs are available in the following regions: us-east-1 region: ami-df1dd5b4 us-west-1 region: ami-8f8b78cb us-west-2 region: ami-61a6a651 sa-east-1 region: ami-d7a62aca eu-west-1 region: ami-18f1bc6f eu-central-1 region: ami-e8211bf5 ap-northeast-1 region: ami-a0d67fa0 ap-southeast-1 region: ami-02f3f350 ap-southeast-2 region: ami-712c6b4b === Azure / VM Depot Images === FreeBSD/amd64 images are available for use within the Microsoft Azure hosting platform through VM Depot. For deployment instructions, see: https://vmdepot.msopentech.com/Vhd/Show?vhdId=56718version=59022 === Vagrant Images === FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can be installed by running: % vagrant init freebsd/FreeBSD-10.2-BETA1 % vagrant up --provider vmware_desktop Note: At this time, support exists only for the vmware_desktop provider. === Upgrading === The freebsd-update(8) utility supports binary upgrades of amd64 and i386 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as follows: # freebsd-update upgrade -r 10.2-BETA1 During this process, freebsd-update(8) may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install It is recommended to rebuild and install all applications if possible, especially if upgrading from an earlier FreeBSD release, for example, FreeBSD 9.x. Alternatively, the user can install misc/compat9x and other compatibility libraries, afterwards the system must be rebooted into the new userland: # shutdown -r now Finally, after rebooting, freebsd-update needs to be run again to remove stale files: # freebsd-update install == ISO CHECKSUMS == o 10.2-BETA1 amd64 GENERIC: SHA256 (FreeBSD-10.2-BETA1-amd64-bootonly.iso) = 36e01ce780a777f4cfd091f10572dfa0d2af2d0e076d1dec13dacc1db7465f67 SHA256 (FreeBSD-10.2-BETA1-amd64-bootonly.iso.xz) = 12bcee785d24d04ee919e5848b491ad56064c5f18f4bda102ab1436e8f13902d SHA256 (FreeBSD-10.2-BETA1-amd64-disc1.iso) = be2db9c92da93b4b0d810b081e29efbc8f119a8cb1032393fe8215d6288d2071 SHA256 (FreeBSD-10.2-BETA1-amd64-disc1.iso.xz) = 299a6f79f4f83819cb68016bc85365d6c8e306945eca558a3845ab5148575053 SHA256 (FreeBSD-10.2-BETA1-amd64-dvd1.iso) = 55f74425f78e7fd4ece91ce0af22e7dfab74a7e7fa6063d0329256fe06b213bf SHA256 (FreeBSD-10.2-BETA1-amd64-dvd1.iso.xz) = 1edbbc8e59a2ad717141e24a59e50866c0990a2aa1f41b59f6ad340924f97894 SHA256 (FreeBSD-10.2-BETA1-amd64-memstick.img) = d47e5d59dc8b212b11483992bc46534b474627e10e89bbce69460df45da3cd5e SHA256 (FreeBSD-10.2-BETA1-amd64-memstick.img.xz) = 97beb17192a2f99bd9efd5d60128adc13f757ba7fefc990cc79a3246ce4fdd71 SHA256 (FreeBSD-10.2-BETA1-amd64-mini-memstick.img) =
Re: OFED on stable/9 is not buildable at least on stable/10
Hans Petter, On Sat, 4 Jul 2015, Dmitry Morozovsky wrote: on stable/10 trying to buildkernel with ALL_MODULES chokes at OFED (actually, for quite a few months already): Could you please take a look at this? Does this patch fix the problem for you: https://svnweb.freebsd.org/changeset/base/285088 yes it does, thank you! could you please MFC this small change to reduce burden of local patches a bit? :) Thans! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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
r284665 causes MSI problems - ahcich2: Timeout in slot 11 port 0
Hello, r284665 causes ahci(4) to fail with timeouts when using MSI (the default). 'hint.ahci.0.msi=0' is one way to make ahci(4) working with r284665, but obviously not the desired solution, it just disables usage of an MSI. I can't find suspicious code in r282213 which could cause this strange regression, but I verified carefully that problem arises with r284665. Actually, r282901 (https://svnweb.freebsd.org/base?view=revisionsortby=daterevision=282901) is the real trigger, verified by putting nooptions RACCT nooptions RACCT_DEFAULT_TO_DISABLED nooptions RCTL into my kernel config - problem vanishes! Setting kern.racct.enable=1 doesn't make any difference, as soon as 'kern.features.racct' exists, there's the ahci(4)/ahcich2 timeout and machine doesn't finish booting. Unfortunately, I don't have any idea how to track this down to the actual culprit, but I hope the RACCT hackers do have ;-) Shall I open a bugzilla ticket? Thanks, -Harry signature.asc Description: OpenPGP digital signature
Re: Will 10.2 also ship with a very stale NTP?
On Sat, Jul 11, 2015 at 09:58:11 +1000, John Marshall wrote: It's me again with my annual NTP whinge. The answer to the perennial will release $foo ship with old / insecure / otherwise deficient $bar? is still install $bar from ports. -- Chris Nehren ___ 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
Slow frame rate running stable running r285364M with Radeon 3850
Hi, I am running stable on a HTPC and I was running 10.1 with no problems the frame rate was around 28-30 fps. I updated to 10.2 and now the frame rate went down to 10-12 fps. uname -a FreeBSD mediamaster 10.2-BETA1 FreeBSD 10.2-BETA1 #1 r285364M: Fri Jul 10 20:01:48 PDT 2015 root@FileKeeper:/usr/obj/usr/src/sys/MEDIAMASTER amd64 Has anyone else seen this? ___ 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: OFED on stable/9 is not buildable at least on stable/10
On 07/11/15 19:14, Dmitry Morozovsky wrote: Hans Petter, On Sat, 4 Jul 2015, Dmitry Morozovsky wrote: on stable/10 trying to buildkernel with ALL_MODULES chokes at OFED (actually, for quite a few months already): Could you please take a look at this? Does this patch fix the problem for you: https://svnweb.freebsd.org/changeset/base/285088 yes it does, thank you! could you please MFC this small change to reduce burden of local patches a bit? :) Here you go: https://svnweb.freebsd.org/changeset/base/285410 --HPS ___ 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
Jenkins build is back to normal : Build-UFS-image #1949
See https://jenkins.FreeBSD.org/job/Build-UFS-image/1949/changes ___ 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: Will 10.2 also ship with a very stale NTP?
On 2015-Jul-11 23:22:56 -0400, Chris Nehren cnehren+freebsd-sta...@pobox.com wrote: On Sat, Jul 11, 2015 at 09:58:11 +1000, John Marshall wrote: It's me again with my annual NTP whinge. The answer to the perennial will release $foo ship with old / insecure / otherwise deficient $bar? is still install $bar from ports. That's a non-answer. It just changes the question to why bother to include $bar in base when I need to install the port anyway. -- Peter Jeremy pgpKqgl4dmmHG.pgp Description: PGP signature
