Re: Invalid fdisk partition table found (fwd)
Hi, Please keep this on list. Forwarded from: Julian Stacey j...@berklix.com http://www.berklix.com/~jhs/ --- Forwarded Message From travelin...@cox.net Thu Nov 24 05:15:33 2011 From: Robert travelin...@cox.net To: Julian H. Stacey j...@berklix.com Subject: Re: Invalid fdisk partition table found Message-ID: 2023192154.5b0a64ab@dell64 In-Reply-To: 20232108.panl80g3041...@fire.js.berklix.net References: 2023123347.4f439c9c@dell64 20232108.panl80g3041...@fire.js.berklix.net X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Julian and Warren thanks for the responses. On Wed, 23 Nov 2011 22:08:00 +0100 Julian H. Stacey j...@berklix.com wrote: Robert wrote: Greetings [robert@dell64] ~ uname -a FreeBSD dell64.shasta204.local 8.2-STABLE FreeBSD 8.2-STABLE #34: Fri Nov 18 06:43:01 PST 2011 root@dell64.shasta204.local:/usr/obj/usr/src/sys/GENERIC amd64 I have two Lexar Professional 600X 16GB compact flash cards that are unusable. fdisk shows: clip Is there any way I can restore these CF cards to 16GB? Any help or suggestions will be greatly appreciated. @ suggestions: 1 Try bsdlabel -B -w -r /dev/da1 [robert@dell64] ~ sudo bsdlabel -B -w -r /dev/da1 Password: [robert@dell64] ~ echo unplug, reinsert Not sure if you actually wanted me to unplug and reinsert the CF card...so I did both [robert@dell64] ~ echo unplug, reinsert unplug, reinsert and physically unplugged and reinserted the CF card newfs /dev/da1a ^ ??? [robert@dell64] ~ sudo newfs /dev/da1a newfs: /dev/da1a: could not find special device [robert@dell64] ~ sudo newfs /dev/da1 /dev/da1: 29.5MB (60480 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 7.39MB, 473 blks, 960 inodes. super-block backups (for fsck -b #) at: 160, 15296, 30432, 45568 cg 0: bad magic number [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED No change from before. 2 Base of _my_ man fdisk When running multi user, you cannot write unless you first run this: sysctl kern.geom.debugflags=16 I had failed to mention in the original post that I had seen something in my searches about problems since 7.1. I had tried booting from an old 6.2 disk and attempted all of this under fixit with no luck. And also tried in single user mode. Warren, [robert@dell64] ~ sudo gpart destroy -F da1 gpart: geom 'da1': Invalid argument [robert@dell64] ~ sudo gpart create -s GPT da1 da1 created [robert@dell64] ~ sudo gpart bootcode -b /boot/pmbr da1 bootcode written to da1 [robert@dell64] ~ sudo gpart destroy -F da1 da1 destroyed [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED I see the flashing lights like it is writing to the CF card but nothing changes. More suggestions welcome. These are quite expensive CF cards. Thanks again Robert --- End of Forwarded Message ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Do you run OSSEC on 9.0?
Since /dev contains a special filesystem which cannot be used for simple files and directories, I would say that the IDS needs some knowledge about it and generic file-checking rules don't apply there. This sounds like a false alert, something must have changed from 8 to 9 and/or the ossec port (and/or ossec signatures). Disclaimer: I am not an ossec user! Nikos On 11/24/2011 11:04 AM, Odhiambo Washington wrote: Getting the same too, since I upgraded my 8.2 - 9.0-PRE. Would be interested in the answers too. On Thu, Nov 24, 2011 at 10:32, Rossbasarev...@gmail.com wrote: I am getting emails about hidden files in /dev. Before that (on 8.2) everything was OK. What should I do? OSSEC HIDS Notification. 2011 Nov 24 08:17:25 Received From: coffin-rootcheck Rule: 510 fired (level 7) - Host-based anomaly detection event (rootcheck). Portion of the log(s): Files hidden inside directory '/dev'. Link count does not match number of files (9,27). --END OF NOTIFICATION ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Diagnosing packet loss
On 24/11/2011 10:07, Kees Jan Koster wrote: This seems to be local to my machine. Here is another reason why I say that: I can reliably transmit data when I bind to the aliased IP address: If I use mtr to measure packet loss from saffron (the stricken machine) to cumin (another machine in a different data center) I see the following: saffron (ip address a) - cumin: packet loss saffron (ip address b) - cumin: no packet loss cumin - saffron (ip address a): packet loss cumin - saffron (ip address b): no packet loss This is consistent from running mtr for 5 minutes straight. This to me shows that the hardware is fine. Using the alias IP address I can run with no packet loss for as long as I like. Sooo Now what? I am completely at a loss. :-/ Hmm... I wouldn't dismiss hardware problems just yet. Earlier you showed the ifconfig output for your problem machine: [kjkoster@saffron ~]$ ifconfig bge0 bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8009bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE ether 00:e0:81:32:ed:b4 inet 91.196.169.165 netmask 0xfff8 broadcast 91.196.169.167 inet 91.196.169.166 netmask 0x broadcast 91.196.169.166 media: Ethernet autoselect (100baseTX full-duplex,flowcontrol,rxpause,txpause) status: active Where there is a one-bit difference between the addresses. Can you try temporarily using two even-numbered addresses and then two odd-numbered addresses and repeat your mtr tests? If the packet loss problem correlates with whether the address is even or odd, then I think that's pretty good evidence for a dud network interface: a one-bit problem in a memory register somewhere, occasionally flipping the least significant bit in the address to 0. Another test would be to swap the configuration order (ie. make .166 the primary address and .165 the alias) -- if it's always the first configured address that has problems, again that indicates memory trouble in the hardware. Are these NICs built-in to your motherboard? If so, they will almost certainly share a PHY, which is where the problem would be, and why swapping the cables between interfaces made no difference. Unfortunately in that case to fix the problem, you'll either have to swap out the motherboard or add a separate NIC card to your system. Hopefully the system is still under warranty. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: LAGG and Jails?
Sorry about my late reply, I was away for a while. I've fixed that. It was quite trivial but sometimes trivial issues make you get stuck for a while. :-/ ifconfig_bge0=up ifconfig_bge1=up cloned_interfaces=lagg0 ifconfig_lagg0=laggproto failover laggport bge0 laggport bge1 10.0.0.56/26 ifconfig_lagg0_alias_0=inet 10.0.0.40 netmask 255.255.255.255 ifconfig_lagg0_alias_1=inet 10.0.0.41 netmask 255.255.255.255 ifconfig_lagg0_alias_2=inet 10.0.0.42 netmask 255.255.255.255 ifconfig_lagg0_alias_3=inet 10.0.0.43 netmask 255.255.255.255 ifconfig_lagg0_alias_4=inet 10.0.0.44 netmask 255.255.255.255 ifconfig_lagg0_alias_5=inet 10.0.0.45 netmask 255.255.255.255 ifconfig_lagg0_alias_6=inet 10.0.0.46 netmask 255.255.255.255 ifconfig_lagg0_alias_7=inet 10.0.0.47 netmask 255.255.255.255 I thought that the first two lines wouldn't be necessary as the cloned_interface parameter would have done the job. I was wrong. Without specifying up the lagg0 interface comes up but not the physical interfaces. Now everything works well: bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8009bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE ether 00:14:5e:80:8a:c0 media: Ethernet autoselect (100baseTX full-duplex,flowcontrol,rxpause,txpause) status: active bge1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8009bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE ether 00:14:5e:80:8a:c0 media: Ethernet autoselect (100baseTX full-duplex,flowcontrol,rxpause,txpause) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 nd6 options=3PERFORMNUD,ACCEPT_RTADV lagg0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8009bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE ether 00:14:5e:80:8a:c0 inet 10.0.0.56 netmask 0xffc0 broadcast 10.0.0.63 inet 10.0.0.40 netmask 0x broadcast 10.0.0.40 inet 10.0.0.41 netmask 0x broadcast 10.0.0.41 inet 10.0.0.42 netmask 0x broadcast 10.0.0.42 inet 10.0.0.43 netmask 0x broadcast 10.0.0.43 inet 10.0.0.44 netmask 0x broadcast 10.0.0.44 inet 10.0.0.45 netmask 0x broadcast 10.0.0.45 inet 10.0.0.46 netmask 0x broadcast 10.0.0.46 inet 10.0.0.47 netmask 0x broadcast 10.0.0.47 media: Ethernet autoselect status: active laggproto failover laggport: bge1 flags=0 laggport: bge0 flags=5MASTER,ACTIVE Sorry for bothering you guys. Hope this would save some time to someone else. Cheers. On Fri, 2011-11-18 at 13:37 +0100, Damien Fleuriot wrote: On 11/18/11 8:09 AM, Snoop wrote: Does anyone know if it's possible to configure lagg for network redundancy on a FreeBSD server containing jails? I'm having problems with that. I couldn't found much around therefore I'm not even sure it's doable. Thanks in advance, any tip will be appreciated. Show your ifconfig output, I'm curious about how you configure your lagg Also please post your uname -a output and rc.conf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f Sponsor: Conto Arancio al 4,20%. Zero spese e massima liberta', aprilo in due minuti! Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=11919d=24-11 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
kvm_getenw
Hi! I had the same problem on FreeBSD 8.2 Release as I have now on 9.0-RC2 FreeBSD 9.0-RC2 #0: Sat Nov 12 18:09:11 UTC 2011 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386: console-kit-daemon[1800]: WARNING: kvm_getenvv failed: cannot open /proc /84597/mem In /etc/fstab I have a line: # Device Mountpoint FStype Options Dump Pass # - -- --- --- - linproc /compat/linux/proc linprocfsrw 00 and in /etc/rc.conf is linux_enable=YES mount shows: linprocfs on /compat/linux/proc (linprocfs, local) I use KDE4 not GNOME. How is possiblle to correct the problem, please? Thanks in advance. Mitja http://jpgmag.com/people/lumiwa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Rsync and Preservation of Ownership and Permissions
Michael Sierchio writes: Does the same user exist on the remote system, with the same uid, etc.? Yes. If you're using rsync with ssh as the transport, and connecting to the remote machine as the backups user, that's who will own the files on its local filesystem... I thought rsync had some encoding it might slip in to the tree that another rsync run as root on the recovering system could use to figure out all those thousands of ownerships and get them all straight, but this makes perfect sense. You've written a lot of narrative, but show us precisely what commands you're running. Why would you run the command as root, and ssh as backups, when you want them to be owned by normal ? Because root is the only user who can see files from all other users so root starts the process. Here is what I tried. Remember, folks, this will not work! This tries to backup a system named z. ##!/bin/sh #rsync --delete -alHvq --exclude /proc // back...@backup-server.okstate.edu:z You can run the command as root, and use restricted ssh keys (use authorized_keys to restrict it to executing a specific rsync command) you can run rsync as a regular user to that user's account on the remote system... per...@pluto.rain.com writes: Perhaps you could have rsync log in to a jail on the backup server, where it could safely be granted root permission. Hmm. It's all rather clear, now. A jailed environment that looks like root is about the only thing that could work. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Quick build of stripped-down kernel
Everyone: Happy Thanksgiving! This week, I've been building FreeBSD 9.0-RC2 kernels for various machines, and on some of the older and slower ones it's been taking quite a long time. One of the reasons for this is that even if you strip 98% of the drivers out of the kernel, they are all still built as loadable modules. The machines in question will NEVER use those modules, so it's a waste of time and disk space. How hard would it be to create a build target for make that would avoid building the loadable modules and just leave them out of the directory where the new kernel is placed after installation? I am not intimately familiar with the cascade of makefiles that does the build I could probably figure out what to tweak, but if someone who is expert in this can help it would be appreciated. It would save me countless hours. --Brett Glass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Quick build of stripped-down kernel
Brett Glass wrote: Everyone: Happy Thanksgiving! This week, I've been building FreeBSD 9.0-RC2 kernels for various machines, and on some of the older and slower ones it's been taking quite a long time. One of the reasons for this is that even if you strip 98% of the drivers out of the kernel, they are all still built as loadable modules. The machines in question will NEVER use those modules, so it's a waste of time and disk space. How hard would it be to create a build target for make that would avoid building the loadable modules and just leave them out of the directory where the new kernel is placed after installation? I am not intimately familiar with the cascade of makefiles that does the build I could probably figure out what to tweak, but if someone who is expert in this can help it would be appreciated. It would save me countless hours. Unless the man pages are out of date and inaccurate this used to be done with make.conf and NO_MODULES. I thought this had been moved into src.conf, but I don't see it in the man page for src.conf. man make.conf for details, as it is also possible to control which modules you want or do not want built as well. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Quick build of stripped-down kernel
Happy Thanksgiving! This week, I've been building FreeBSD 9.0-RC2 And to you, too. kernels for various machines, and on some of the older and slower ones it's been taking quite a long time. One of the reasons for this is that even if you strip 98% of the drivers out of the kernel, they are all still built as loadable modules. The machines in question will NEVER use those modules, so it's a waste of time and disk space. How hard would it be to create a build target for make that would avoid building the loadable modules and just leave them out of the directory where the new kernel is placed after installation? I am not intimately familiar with the cascade of makefiles that does the build I could probably figure out what to tweak, but if someone who is expert in this can help it would be appreciated. It would save me countless hours. If you are going to build most of the modules, but only want to exclude a few, then add the directories of the modules to be excluded (relative to /usr/src/sys/modules) to WITHOUT_MODULES, for example in /etc/make.conf. If you are only going to build a few modules, and want to exclude the majority of the modules, then add the directories of the modules that are to be built to MODULES_OVERRIDE. For no modules at all, set NO_MODULES. See /usr/src/sys/modules/Makefile and /usr/src/sys/conf/kern.post.mk for details. You may also save some time by using one of your faster machines to build the OS for the slower machines. b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
7.4 - 8.2
Hi all Almost classic question about updating from 7.4 to 8.2. Anyone known if I can temporally run a 7.4 userland+service with 8.2 kernel ? I've ask this because I've ~ 15 jail on one server. I can update the «host» pretty fast but with the 15 jail I need some time. And I would like to known if durring this time the jail going to work «normally». Regards. -- Albert SHIH DIO batiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 Heure local/Local time: jeu 24 nov 2011 16:06:49 CET ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
7.4 - 8.2
Albert Shih writes: Anyone known if I can temporally run a 7.4 userland+service with 8.2 kernel? My gut reaction was Are you familiar with the game of Russian Roulette?. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Setting up ZFS - Filesystem Properties and Installing on Root
On Tue, Nov 22, 2011 at 3:06 AM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 22/11/2011 02:09, APseudoUtopia wrote: Another quick question about swap: If I have 4 drives, with 512MB swap, the system uses all 4 swap partitions, correct? So it's not like it'd be going to waste? I'd have a total of 2 GB swap? Well, yes. If you just declare those raw partitions to be swap areas, that will be the case. However, doing this is asking for trouble: you subvert any resilience features obtained by using ZFS with raidz1. If any one of the drives fails, your swap area will break and your system will probably crash. Better to set up two pairs of gmirrors for swap -- the procedure is described here: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror in section3 Finish Install. This will effectively give you a raid10 for your swap, with a total size of 1GB. I'm not sure I understand this. How would that negatively affect the raidz1? The swap isn't in the zpool. I understand the system may crash if the OS was using the swap space and the drive failed. But would you not be able to reboot into a degraded zpool state and still have a usable system? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Setting up ZFS - Filesystem Properties and Installing on Root
On 24/11/2011 19:19, APseudoUtopia wrote: On Tue, Nov 22, 2011 at 3:06 AM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 22/11/2011 02:09, APseudoUtopia wrote: Another quick question about swap: If I have 4 drives, with 512MB swap, the system uses all 4 swap partitions, correct? So it's not like it'd be going to waste? I'd have a total of 2 GB swap? Well, yes. If you just declare those raw partitions to be swap areas, that will be the case. However, doing this is asking for trouble: you subvert any resilience features obtained by using ZFS with raidz1. If any one of the drives fails, your swap area will break and your system will probably crash. Better to set up two pairs of gmirrors for swap -- the procedure is described here: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror in section3 Finish Install. This will effectively give you a raid10 for your swap, with a total size of 1GB. I'm not sure I understand this. How would that negatively affect the raidz1? The swap isn't in the zpool. I understand the system may crash if the OS was using the swap space and the drive failed. But would you not be able to reboot into a degraded zpool state and still have a usable system? No -- it means a failed disk can cause your system to crash. That's not resilient behaviour. Yes, the data on the ZFS raidz1 should survive the crash and the reboot, but the point is ZFS raidz1 should be able to survive a disk failure like that /without/ a system crash. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Setting up ZFS - Filesystem Properties and Installing on Root
On Thu, Nov 24, 2011 at 2:26 PM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 24/11/2011 19:19, APseudoUtopia wrote: On Tue, Nov 22, 2011 at 3:06 AM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 22/11/2011 02:09, APseudoUtopia wrote: Another quick question about swap: If I have 4 drives, with 512MB swap, the system uses all 4 swap partitions, correct? So it's not like it'd be going to waste? I'd have a total of 2 GB swap? Well, yes. If you just declare those raw partitions to be swap areas, that will be the case. However, doing this is asking for trouble: you subvert any resilience features obtained by using ZFS with raidz1. If any one of the drives fails, your swap area will break and your system will probably crash. Better to set up two pairs of gmirrors for swap -- the procedure is described here: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror in section3 Finish Install. This will effectively give you a raid10 for your swap, with a total size of 1GB. I'm not sure I understand this. How would that negatively affect the raidz1? The swap isn't in the zpool. I understand the system may crash if the OS was using the swap space and the drive failed. But would you not be able to reboot into a degraded zpool state and still have a usable system? No -- it means a failed disk can cause your system to crash. That's not resilient behaviour. Yes, the data on the ZFS raidz1 should survive the crash and the reboot, but the point is ZFS raidz1 should be able to survive a disk failure like that /without/ a system crash. Ah! I understand. Thank you for the explanation. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Invalid fdisk partition table found (fwd)
On Thu, 24 Nov 2011 12:16:17 +0100 Julian H. Stacey j...@berklix.com wrote: Hi, Please keep this on list. Hi Julian, I noticed soon after my response that I must have hit reply instead of all so I resent my information to questions@. This morning I didn't see my email to questions@ so I checked the archives and my response is there. No idea why it did not get sent out to the masses. Anyway, I am still having this problem so I will paste my response below. Julian and Warren thanks for the responses. On Wed, 23 Nov 2011 22:08:00 +0100 Julian H. Stacey j...@berklix.com wrote: Robert wrote: Greetings [robert@dell64] ~ uname -a FreeBSD dell64.shasta204.local 8.2-STABLE FreeBSD 8.2-STABLE #34: Fri Nov 18 06:43:01 PST 2011 root@dell64.shasta204.local:/usr/obj/usr/src/sys/GENERIC amd64 I have two Lexar Professional 600X 16GB compact flash cards that are unusable. fdisk shows: clip Is there any way I can restore these CF cards to 16GB? Any help or suggestions will be greatly appreciated. @ suggestions: 1 Try bsdlabel -B -w -r /dev/da1 [robert@dell64] ~ sudo bsdlabel -B -w -r /dev/da1 Password: [robert@dell64] ~ echo unplug, reinsert Not sure if you actually wanted me to unplug and reinsert the CF card...so I did both [robert@dell64] ~ echo unplug, reinsert unplug, reinsert and physically unplugged and reinserted the CF card newfs /dev/da1a ^ ??? [robert@dell64] ~ sudo newfs /dev/da1a newfs: /dev/da1a: could not find special device [robert@dell64] ~ sudo newfs /dev/da1 /dev/da1: 29.5MB (60480 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 7.39MB, 473 blks, 960 inodes. super-block backups (for fsck -b #) at: 160, 15296, 30432, 45568 cg 0: bad magic number [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED No change from before. 2 Base of _my_ man fdisk When running multi user, you cannot write unless you first run this: sysctl kern.geom.debugflags=16 I had failed to mention in the original post that I had seen something in my searches about problems since 7.1. I had tried booting from an old 6.2 disk and attempted all of this under fixit with no luck. And also tried in single user mode. Warren, [robert@dell64] ~ sudo gpart destroy -F da1 gpart: geom 'da1': Invalid argument [robert@dell64] ~ sudo gpart create -s GPT da1 da1 created [robert@dell64] ~ sudo gpart bootcode -b /boot/pmbr da1 bootcode written to da1 [robert@dell64] ~ sudo gpart destroy -F da1 da1 destroyed [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED I see the flashing lights like it is writing to the CF card but nothing changes. More suggestions welcome. These are quite expensive CF cards. Thanks again Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.4 - 8.2
On Thu, 24 Nov 2011 10:44:00 -0500, Robert Huff wrote: My gut reaction was Are you familiar with the game of Russian Roulette?. Robert Huff I have played a variant of this game using six cans of Guinness. Shake one can vigorously, then shuffle them around. Take it in turns to hold a can next to your head and pull the ring. Best played outdoors. Tony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Invalid fdisk partition table found (fwd)
On Thu, 24 Nov 2011, Robert wrote: [robert@dell64] ~ sudo gpart destroy -F da1 da1 destroyed [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found The partition table was cleared. Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 And it starts with a default table equal to the size of the drive. I see the flashing lights like it is writing to the CF card but nothing changes. More suggestions welcome. These are quite expensive CF cards. The dd/fdisk and gpart results show the same problem, so it likely isn't in the partitioning. Do both cards report the same size? I found recently that there is some oddness with certain Sandisk flash memory that made it non-responsive to anything. FreeBSD couldn't do a thing with it. Before throwing it away, I tried it on a Windows Vista system... which recognized and formatted it without a complaint. Now it works on everything. Special vendor-specific code in Windows? Another option would be to attempt formatting the cards with a camera. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Quick build of stripped-down kernel
from b. f. bf1...@googlemail.com: If you are going to build most of the modules, but only want to exclude a few, then add the directories of the modules to be excluded (relative to /usr/src/sys/modules) to WITHOUT_MODULES, for example in /etc/make.conf. If you are only going to build a few modules, and want to exclude the majority of the modules, then add the directories of the modules that are to be built to MODULES_OVERRIDE. For no modules at all, set NO_MODULES. See /usr/src/sys/modules/Makefile and /usr/src/sys/conf/kern.post.mk for details. You may also save some time by using one of your faster machines to build the OS for the slower machines. Suppose you want to build more than one kernel so as to be able to choose at boot time. Then you might not want to build modules redundantly. So how would you make the modules from /boot/kernel accessible when booting /boot/kernel2? Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
