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 dro
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
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.c
>> 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-tp580
>> 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
>> 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.
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
cr
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
*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
Corrects the problem. With thanks to Steve Hartland for that tip.
-
10-Current-amd64-using ccache-portstree merged wi
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 it
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
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
>> 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
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 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 aud
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
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 no
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 sam
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'
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-tp5800299p580185
I think I might have a better understanding of the situation.
'zpool status' and 'zdb -C' commands both show bsdr properties as:
pool_guid: 17852168552651762162
children[0]: \ type: 'disk' \ guid: 12606749387939346898
Whereas 'zpool import -D' and 'zdb -l' commands give the bsdr properties as
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. zpoo
>>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 /
>>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_gui
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.8
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
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
#
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
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: 'b
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
29 matches
Mail list logo
