Authorisation Errors on 9.2
I have two strange errors but I am not sure whether they are related. ERROR-1: Slim allows login without checking for password. /var/log/auth.log shows: Oct 13 11:44:57: slim: gkr-pam: no password is available for user Oct 13 11:44:57: gnome-keyring-daemon[1225]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk ERROR-2: sshd disconnects (drops) client connections immediately after login. This happens when trying from host its self or some other client. Testing from host (162.168.1.10 is host's IP) $ ssh root@192.168.1.10 Password for root@server.freebsd: Last login: Sun Oct 13 13:02:09 2013 Welcome to myNetwork (the motd message) csh: No such file or directory Connection to 192.168.1.10 closed. /var/log/auth.log for ssh shows: Oct 13 19:41:37: Server listening on 0.0.0.0 port 22. Oct 13 19:42:37: Accepted keyboard-interactive/pam for root from 192.168.1.10 port 33248 ssh2 Oct 13 19:42:37: Received disconnect from 192.168.1.10: 11: disconnected by user Thanks for any advice on how to resolve these two issues. - FreeBSD-9.2-stable_amd64_root-on-zfs_clang-only-world -- View this message in context: http://freebsd.1045724.n5.nabble.com/Authorisation-Errors-on-9-2-tp5851543.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
Authorisation Errors on 9.2
Hi, I Inadvertently posted the gnome-keyring bit. That's almost standard error message on FreeBSD-Gnome. The relevant bit for the error is in fact: slim: gkr-pam: no password is available for user However, the user cannot login on a tty without providing a password. For ssh, the same error and dropped connection occurs for all users. sshd was modified to allow root login. All users have valid home directories defined. From /etc/passwd; I wonder if this has anything to do with it? sshd:*:22:22:Secure Shell Daemon:/var/empty:/usr/sbin/*nologin* Could it be a dud /root/.tcshrc? Or /etc/login.conf? The accounts which try to ssh login also login on host proper and do not have any login issues when logging-in directly on host - so I think we can eliminate these problems. Thanks and Regards - FreeBSD-9.2-stable_amd64_root-on-zfs_clang-only-world -- View this message in context: http://freebsd.1045724.n5.nabble.com/Authorisation-Errors-on-9-2-tp5851543p5851636.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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: Virtual Box on FreeBSD Server
Bill: 1. As I understand it you can install Virtual Box from the ports collection. That port or a good numbr of other VMWare apps exist in the ports tree - you are not restricted to V-Box. Starting the virtual machines is not xorg/login dependent. You can do this for any service through rc.conf So edit your /etc/rc.conf and insert whatevername_enable=YES to auto-start the service. The whatevername can be found by looking in /etc/rc.d for base-system included services or /usr/local/etc/rc.d for services installed through ports. 2. Once installed, I will be able to install something like Fedora or openSUSE? Yes, that's the whole idea behind VM's. Since SQL is needed, you will then have to install configure the mysql package for fedore/suse inside the VM. Installing mySQL from FreeBSD ports won't be of any good for the client's requirements. 3. 9-stable should do the job 4. Do whatever you are comfortable with. Finally: posted in an unrelated thread - you would have gotten better answers by starting your own. Good Luck. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/sata-ata-device-permission-for-user-tp5803691p5805091.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
dvd recorder audio cd problems
Bernt Hansson posted a message for using sysutils/cdrtools (not in the thread for some reason...) Interestingly I get a possibly informative error: % cdda2wav --device /dev/cd0 --bulk cdrom device (/dev/cd0) is not of type generic SCSI. Setting interface to cooked_ioctl. 307200 bytes buffer memory requested, transfer size 129024 bytes, 4 buffers, 27 sectors #Cdda2wav version 3.00_freebsd_10.0-current_amd64_amd64, real time sched., soundcard, libparanoia support Segmentation fault (core dumped) I am re-building the cdrtools to see if it will correct, but I was also interested in the dev/cd0 is not of type generic SCSI. Setting interface to cooked_ioctl. bit, and whether it was related to my other errors re permission etc. Regards. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/dvd-recorder-audio-cd-problems-tp5803899p5804717.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
sata/ata device permission for user
The user also needs access to the corresponding pass device which is shown by camcontrol devlist. He also needs access to /dev/xpt0 I think. HL-DT-ST DVDRAM GSA-4165B DL05 at scbus6 target 0 lun 0 (cd0,pass3) crw--- 1 root operator 0x48 Apr 18 07:08 pass0 crw--- 1 root operator 0x49 Apr 18 07:08 pass1 crw--- 1 root operator 0x4a Apr 18 07:08 pass2 crw--- 1 root operator 0x4b Apr 18 07:08 pass3 crw--- 1 root operator 0x42 Apr 18 07:08 xpt0 User is member of operator group. However, I agree with your idea because just now I was working with cdrtools and got this error, but when I ran as root no error: % cdda2wav summary --device /dev/cd0 cdda2wav: Permission denied. Open of /dev/xpt0 failed. Cannot open or use SCSI driver. cdda2wav: For possible targets try 'cdda2wav -scanbus'. Make sure you are root. Probably you did not define your SCSI device. Set the CDDA_DEVICE environment variable or use the -D option. Regards. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/sata-ata-device-permission-for-user-tp5803691p5804740.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
sata/ata device permission for user
But the group permissions are --- (none). D'oh! Well, that made a difference and I can query the cd0 device with cdda2wav as my user now. I still can't mount a data CD however. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/sata-ata-device-permission-for-user-tp5803691p5804757.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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: sata/ata device permission for user
What's the output of: sysctl vfs.usermount vfs.usermount: 1 I can mount USB devices... - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/sata-ata-device-permission-for-user-tp5803691p5804802.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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 as Samba Server and Windows as Client
There are just so many things that could go wrong on a samba setup that it is beyond funny in my opinion. You have authentication method (kerberos, pam, txt), ports, winbind and dns just to list a few. I suggest you start samba in debug mode and enable full logging. The documentation from samba its self is probably going to be much more comprehensive: http://www.samba.org/samba/docs/man/manpages-3/smbd.8.html I would also try to connect with various clients like a linux, XP, vista or win7. These connection attempts should generate comprehensive logs when samba is running in debug mode. You can then start to get some idea why the connection is being refused by reading through the generated logs. Also, several how-to's already exist on the FreeBSD forums - as an example: http://forums.freebsd.org/showthread.php?t=36137 - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/FreeBSD-as-Samba-Server-and-Windows-as-Client-tp5804306p5804418.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
zdb queries give error on healthy zpools
*SOLVED* I apparently already had an answer from a previous question of mine. http://freebsd.1045724.n5.nabble.com/ZFS-How-to-fix-corrupt-ZDB-td5758864.html # zpool reguid pool Corrects the problem. With thanks to Steve Hartland for that tip. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/zdb-queries-give-error-on-healthy-zpools-tp5804408p5804493.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
dvd recorder audio cd problems
Hi, Regarding audio playback via cdcontrol ... requires a seperate internal wiring (CD audio wire) to the sound card. Thanks: Using an older dvd drive, so that's probably the problem. On my linux I once had that cable to the mobo. on FreeBSD 8 you would have something like this in your kernel configuration:# ATA and ATAPI devices You seem to be using 8.* while I am on 10-current (info provided in my signature). Unfortunately there are a number of important hardware driver changes between 8-9-10. these are the only options allowed: # ATA controllers device ahci# AHCI-compatible SATA controllers device ata # Legacy ATA/SATA controllers # ATA/SCSI peripherals device scbus # SCSI bus (required for ATA/SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct ATA/SCSI access) device ses # Enclosure Services (SES and SAF-TE) #device ctl # CAM Target Layer In GENERIC, 'option ctl' is disabled because pulling in any one of the da/cd/pass etc also enables/calls ctl. For the same reason, '# atacontrol list ' = ATA_CAM option is enabled in kernel. Please use camcontrol instead. $ ll /dev/cam = crw--- 1 root operator 0x3f Apr 16 19:36 ctl So it seems, after playing around that 'acd_' is deprecated in 10. As to why /dev/cd0 does not show up in Brasero, it is probably related to my other thread on user-level permissions. Since my user cannot mount the cd0, brasero has not enabled access to it (problem valid for all GUI-based-apps unless root starts running a GUI) Regards. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/dvd-recorder-audio-cd-problems-tp5803899p5804272.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
zdb queries give error on healthy zpools
I have 3 pools and all zdb queries for these pools or child datasets return with an error message. All 3 pools are healthy and functioning correctly. # zpool list NAMESIZE ALLOC FREECAP DEDUP HEALTH ASHIFT bsds 48.8G 16.0G 32.8G32% 1.29x ONLINE 12 mylib 266G 740M 265G 0% 1.00x ONLINE 9 tank0 49.8G 19.1G 30.7G38% 1.00x ONLINE 12 '# zdb -C' works, but that command without any poolname reads data from zpool.cache. Pool or on child dataset-specific queries (while using any of -b -d -D -C -i -h ) give this: # zdb -vvv -h bsds zdb: can't open 'bsds': Device not configured zdb: can't open 'bsds/usr': Device not configured zdb: can't open 'mylib': Invalid argument zdb: can't open 'tank0': Invalid argument I also have a faulted zpool in the list: bsdr - - - - - FAULTED - But I do not think that this faulted status will cause such zdb problems. Regards. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/zdb-queries-give-error-on-healthy-zpools-tp5804408.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
ZFS mounting failed with error 2
one thing I'm not sure about is that some people create a dataset root but that actually mounts at / (and not /root) and some just create others mount points directly on the zpool You can do this either way. A ZFS dataset is created at the same time and with the same name as the zpool. You can use the zpool-named-dataset as root without any problem. As I recall, the separate root dataset was a work-around for some old problem, so it is not necessary any longer. That said, you can place and name the zfs root dataset anywhere you want, as long as you have the 'vfs.root.mountfrom=' path set correctly. In your example, it is set correctly. Now as to why you cannot boot - from my experience, the problem is your last command: '# zpool export tank' will leave the pool in an exported state, and when the system tries to boot, it will not be able to locate the zpool because the pool is in exportland. The solution is different. After you are finished with all your settings you should # zfs umount -a (unmount all tank child datasets in /mnt) # zfs set mountpoint=/ tank # reboot At step 2, dataset tank should not try to re-mount its self and remain un-mounted. The older versions of ZFS did not behave this way and would immediately mount the zpool on root. If this happens, you have to hard-reset and such because the system will freeze up. If all goes well, before reboot you can also check (zfs get all tank) and make sure that canmount=on is set for tank. The best zfs guide is FreeBSD's own docs: https://wiki.freebsd.org/RootOnZFS - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-mounting-failed-with-error-2-tp5802786p5804167.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
sata/ata device permission for user
My user is unable to mount cdrom and cannot use qemu for the HDD devices. Why is access to these devices being refused for my user? 1. % mount_cd9660 /dev/cd0 /cdrom mount_cd9660: /dev/cd0: Operation not permitted 2. % qemu-system-x86_64 -hda /dev/ada2 qemu-system-x86_64: -hda /dev/ada2: could not open disk image /dev/ada2: Operation not permitted *SETTINGS:* % id = uid=1001(xyz) gid=0(wheel) groups=0(wheel),5(operator),1001(xyz) /etc/devfs.rules has: [localrules=10] add path 'ada[0-9]*' mode 0660 group operator add path 'da[0-9]*' mode 0660 group operator add path 'cd[0-9]*' mode 0660 group operator /etc/rc.conf has: devfs_system_ruleset=localrules Regards. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/sata-ata-device-permission-for-user-tp5803691.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
sata/ata device permission for user
Hello, 1. Neglected to specify that vfs.usermount=1 is set in /etc/sysctl.conf. My user can mount USB drives. 2. Settings in /etc/devfs.rules is being passed to system correctly because ownership is correct: crw-rw 1 root operator 0x57 Apr 15 09:46 /dev/cd0 3. File permissions for /cdrom is root operator 2 Mar 3 2011 cdrom/ I had also tried mounting on a folder with 1777 permission before posting. Otherwise, * I had solved the qemu problem, it was a small oversight. It helps if the user is in the wheel group. Membership in operator should be sufficient... Looks correct, but doesn't seem to be sufficient. /etc/devfs.rules is used for dynamically allocated devices and /etc/devfs.conf for those present at boot time. As far as I understand, you can set rules for any device in devfs.rules, but not vice-versa. But I should also try with devfs.conf just to make sure... Regards. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/sata-ata-device-permission-for-user-tp5803691p5803879.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
dvd recorder audio cd problems
I have an audio CD I want to rip/copy but I have some problems: % cdcontrol -f /dev/cd0 info Starting track = 1, ending track = 17, TOC size = 146 bytes track start duration block length type - 1 0:02.00 4:02.31 0 18181 audio 2 4:04.31 5:08.45 18181 23145 audio etc... But when I do #-or-% cdcontrol -f /dev/cd0 play = starts playing (confirmed with 'status audio') But there is no sound. 'status volume' shows 255 for both channels. cam.ko is built-in to my custom kernel. From what I have read, shouldn't the DVD show up as /dev/acd0? In which case each song on the cd should be visible as /dev/acd0t__? Not happening though, since the dvd is registered as plain cd0 in /dev. # camcontrol devlist = HL-DT-ST DVDRAM GSA-4165B DL05 at scbus6 target 0 lun 0 (cd0,pass3) * A separate oddity is that /dev/cd0 does not show up in Brasero (shows no selectable recording device) Thanks and regards. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/dvd-recorder-audio-cd-problems-tp5803899.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
sata/ata device permission for user
EDIT: I had already placed in /etc/devfs.conf this entry some time ago: # Allow members of group operator to mount cdrom own /dev/cd0 root:operator perm/dev/cd0 0660 Not allowing mount despite all of these adjustments (being tested with data cd and NOT audio cd), which is what I am unable to figure out. - 10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/sata-ata-device-permission-for-user-tp5803691p5803900.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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: [ZFS] recover destroyed zpool - what are the available options?
Exported the existing zpool ran # zpool import -D -f -R /bsdr -N -F -X 12018916494219117471 rescue = Same result unfortunately. 'cannot import 'bsdr' as 'rescue': no such pool or dataset Destroy and re-create the pool from a backup source.' I tried the other bsdr zpool as well but result was same error msg. I feel like I'm overlooking something very simple... - 10-Current-amd64-portstree merged with marcuscom.gnome3 xorg.devel -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-recover-destroyed-zpool-what-are-the-available-options-tp5800299p5802512.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
[ZFS] recover destroyed zpool - what are the available options?
The '-n' flag should not be there: -n Used with the -F recovery option. Determines whether a non-importable pool can be made importable again, but does not actually perform the pool recovery # zpool import -D -f -R /bsdr -N -F -X 12018916494219117471 rescue = cannot import 'bsdr' as 'rescue': no such pool or dataset. Destroy and re-create the pool from a backup source. -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-recover-destroyed-zpool-what-are-the-available-options-tp5800299p5802063.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
[ZFS] recover destroyed zpool - what are the available options?
Actually if you see all 4 labels correctly you can try to proceed as ZFS would guess the correct disk size anyway. I should clarify: # zdb -l /dev/ada0p2 = all 4 LABELS visible and correct (zpool name: bsdr) # zdb -l /dev/ada0p1 = all 4 LABELS visible and correct (zpool name: asp) # zdb -l /dev/ada0 = only LABEL #2 visible (this is an OLDER zpool with GUID 5853256800575798014, also named bsdr, the pool was whole-disk-as-raw) This is the gpt table + partitions as I re-created them immediately after the gpt delete. It looks like I have re-created the gpt partitions correctly... I don't understand what you mean by you can try to proceed? # zpool import -D -f -R /bsdr -N -F -n -X bsdr cannot import 'bsdr': a pool with that name already exists. use the form 'zpool import pool | id newpool' to give it a new name -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-recover-destroyed-zpool-what-are-the-available-options-tp5800299p5801716.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
[ZFS] recover destroyed zpool - what are the available options?
Thank you for your help Volodymyr, 1. ZPOOL LIST shows that the pool is listed NAMESIZE ALLOC FREECAP DEDUP HEALTH ALTROOT bsdr - - - - - FAULTED - tank0 49.8G 13.3G 36.5G26% 1.00x ONLINE - 2. ZPOOL IMPORT = no pools available to import 3. zpool import -D -f -R /bsdr -N -F -n -X bsdr = Gives error because of condition (#1) 4. ZPOOL IMPORT -D shows 2 BSDR pools: A) config: bsdr UNAVAIL insufficient replicas 5853256800575798014 UNAVAIL cannot open (THIS IS NOT THE POOL I WANT - THIS ONE IS OLDER POOL, WHOLE-DISK-RAW) B) config: bsdrUNAVAIL insufficient replicas 17860002997423999070 UNAVAIL cannot open (THIS SHOULD BE THE POOL I NEED, BUT LOOK AT PROBLEM IN #5) 5. ZPOOL STATUS -V BSDR shows different guid!! config: bsdrUNAVAIL 0 0 0 12606749387939346898 UNAVAIL 0 0 0 was /dev/ada0p2 (THIS GUID DOES NOT MATCH THE GUID OF 4-B) It is normal in my opinion that the guid should not match, but that is why I cannot import pool 4-B. I must either delete the BSDR POOL that is shown as on-line, or import 4-B with another name I think. Thanks and Regards. -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-recover-destroyed-zpool-what-are-the-available-options-tp5800299p5801734.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
[ZFS] recover destroyed zpool - what are the available options?
Sadly, the command I ran did nothing - no error message, no output, no result: # zpool import -D -f -R /bsdr -N -F -n -X 12018916494219117471 newname -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-recover-destroyed-zpool-what-are-the-available-options-tp5800299p5801851.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
[ZFS] recover destroyed zpool - what are the available options?
Hi Mark. What does gpart show return? = 34 625142381 ada0 GPT (298G) 34 62914560 1 freebsd-zfs (30G) 62914594 562227821 2 freebsd-zfs (268G) Are all the pool members there and working? Yes - ada0p2 is the ONLY pool member. My guess is that one member is missing or a mbr is bad. After 'zpool destroy', I also deleted the partition before realising my mistake, I tried to recover the partition table with testdisk, but this was not successful. Next I created a new GPT table and the 2 partitions at the original size as I recalled them - so ada0p1 and ada0p2 have been re-created. I just realized a problem: gpart show -r = 62914594 562227821 2 516e7cba-6ecf-11d6-8ff8-00022d09712b (268G) The guid (?) that ZFS is looking for is most likely wrong. I need to find the ID that ZFS is looking for and change the ID of ada0p2 to that number - am I correct? Thanks. -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-recover-destroyed-zpool-what-are-the-available-options-tp5800299p5801568.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
[ZFS] recover destroyed zpool - what are the available options?
Thanks Volodymyr. The pools do not show up as deleted. # zpool list (the pool that had disappeared has returned) NAME SIZE ALLOC FREECAP DEDUP HEALTH ALTROOT asp - - - - - FAULTED - bsdr - - - - - FAULTED - bsds 48.8G 12.9G 35.8G26% 1.25x ONLINE - # zpool import no pools available to import # zpool import -D pool: bsdr id: 12018916494219117471 state: UNAVAIL (DESTROYED) status: One or more devices are missing from the system. action: The pool cannot be imported. Attach the missing devices and try again. config: bsdrUNAVAIL insufficient replicas *17860002997423999070* UNAVAIL cannot open pool: bsdr id: 16018525702691588432 state: UNAVAIL (DESTROYED) status: One or more devices are missing from the system. action: The pool cannot be imported. Attach the missing devices and try again. config: bsdr UNAVAIL insufficient replicas 5853256800575798014 UNAVAIL cannot open # zpool status -v bsdr pool: bsdr state: UNAVAIL status: One or more devices could not be opened. There are insufficient replicas for the pool to continue functioning. action: Attach the missing device and online it using 'zpool online'. config: NAMESTATE READ WRITE CKSUM bsdrUNAVAIL 0 0 0 *12606749387939346898* UNAVAIL 0 0 0 was /dev/ada0p2 Form my post #2 you can check that ZDB record has 2 GUIDs: guid: *17852168552651762162* and guid: *12606749387939346898* Thank You. -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-recover-destroyed-zpool-what-are-the-available-options-tp5800299p5801581.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
[ZFS] recover destroyed zpool - what are the available options?
test them with `zdb -l device`. When the output would be correct - you guessed your slice! LABEL 1 version: 28 name: 'bsdr' state: 2 txg: 10 pool_guid: 12018916494219117471 hostid: 2193536600 hostname: 'mfsbsd' top_guid: 17860002997423999070 guid: 17860002997423999070 vdev_children: 1 vdev_tree: type: 'disk' id: 0 guid: 17860002997423999070 path: '/dev/ad6p2' phys_path: '/dev/ad6p2' whole_disk: 1 metaslab_array: 30 metaslab_shift: 31 ashift: 9 asize: 287855869952 is_log: 0 create_txg: 4 Do you mean that in this case 'asize 287855869952' is what I should look at? But 287855869952 /1024 /1024 /2 = 137.260GB is far smaller than I recall the geom part to be... -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-recover-destroyed-zpool-what-are-the-available-options-tp5800299p5801588.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
[ZFS] recover destroyed zpool - what are the available options?
If anyone has ideas, zdb -C is now giving me detailed output. zpool status is: NAMESTATE READ WRITE CKSUM bsdrUNAVAIL 0 0 0 12606749387939346898 UNAVAIL 0 0 0 was /dev/ada0p2 zdb -C gives: bsdr: version: 5000 name: 'bsdr' state: 0 txg: 41845 pool_guid: 17852168552651762162 hostid: 2739729201 hostname: '' vdev_children: 1 vdev_tree: type: 'root' id: 0 guid: 17852168552651762162 create_txg: 4 vdev_stats[0]: 348476133 vdev_stats[1]: 4 vdev_stats[2]: 3 vdev_stats[3]: 0 vdev_stats[4]: 0 vdev_stats[5]: 0 vdev_stats[6]: 0 vdev_stats[7]: 0 vdev_stats[8]: 0 vdev_stats[9]: 0 vdev_stats[10]: 0 vdev_stats[11]: 0 vdev_stats[12]: 0 vdev_stats[13]: 0 vdev_stats[14]: 0 vdev_stats[15]: 0 vdev_stats[16]: 0 vdev_stats[17]: 0 vdev_stats[18]: 0 vdev_stats[19]: 0 vdev_stats[20]: 0 vdev_stats[21]: 0 vdev_stats[22]: 0 vdev_stats[23]: 0 vdev_stats[24]: 0 vdev_stats[25]: 0 children[0]: type: 'disk' id: 0 guid: 12606749387939346898 path: '/dev/ada0p2' phys_path: '/dev/ada0p2' whole_disk: 1 metaslab_array: 30 metaslab_shift: 31 ashift: 9 asize: 287855869952 is_log: 0 create_txg: 4 vdev_stats[0]: 348476133 vdev_stats[1]: 4 vdev_stats[2]: 1 vdev_stats[3]: 0 vdev_stats[4]: 0 vdev_stats[5]: 0 vdev_stats[6]: 287767527424 vdev_stats[7]: 18446743785853681664 vdev_stats[8]: 0 vdev_stats[9]: 0 vdev_stats[10]: 0 vdev_stats[11]: 0 vdev_stats[12]: 0 vdev_stats[13]: 0 vdev_stats[14]: 0 vdev_stats[15]: 0 vdev_stats[16]: 0 vdev_stats[17]: 0 vdev_stats[18]: 0 vdev_stats[19]: 0 vdev_stats[20]: 0 vdev_stats[21]: 0 vdev_stats[22]: 0 vdev_stats[23]: 0 vdev_stats[24]: 0 vdev_stats[25]: 0 features_for_read: -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-recover-destroyed-zpool-what-are-the-available-options-tp5800299p5801335.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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: [ZFS] recover destroyed zpool - what are the available options?
Volodymyr, thank you very much for answering. A strange problem is that ZFS thinks the pool is on-line: # zpool list NAMESIZE ALLOC FREECAP DEDUP HEALTH ALTROOT bsdr - - - - - FAULTED - So when I try to import, it objects. I can think of 2 things to do: a- export the pool first, then re-import b- Disconnect the original hdd / create pool bsdr on another hdd@s small gpt partition / re-connect the original hdd / somehow force the import or add the original pool to the newly created bsdr pool, and maybe the original data will come back on line?? What would you suggest? Thanks again. -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-recover-destroyed-zpool-what-are-the-available-options-tp5800299p5801356.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
[ZFS] recover destroyed zpool - what are the available options?
I had a second pool on another partition of the same HDD, which was in the same degraded state as the bsdr pool. The data on that pool had been backed-up previously. I decided to try the export re-import method on that pool (-Z gives message: invalid option 'Z'). Result: # zpool export oldpool # zpool import -D -f -R /mnt -N -F -n oldpool Now the pool just disappears. # zpool list - does not show oldpool # zpool import - no pools available to import So the export re-import method is NOT the way to do this. -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-recover-destroyed-zpool-what-are-the-available-options-tp5800299p5801470.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
[ZFS] recover destroyed zpool - what are the available options?
I destroyed my zpool but forgot to take the tar backup of /home folder. I was wondering if there's any way to restore the zpool? This was a single-HDD pool. zpool import -D shows the poolname but also shows that pool is unavailable and faulted. zdb commands give no records available for poolname The zpool command also shows the missing device by its ID number. I have left the HDD in the untouched state, and I am hopng that zpool may accept the HDD if I can figure out a way to pass the device number zpool is looking for to the GPT partition (or whatever ID mechanism zpool looks for) on the original HDD. Is there a way to do all that with ZFS? Thanks for any help. -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-recover-destroyed-zpool-what-are-the-available-options-tp5800299.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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
