[solved] libusb couldn't open USB device /dev/bus/usb/003/010:

I have a working udev rule for my android phones that suddenly doesn' work, I think this happend after upgrading the udev package today... Is there something I need to do to make my rule work with the new version of udev, or is there something else I am missing?
My rules looks like this:
SUBSYSTEM=="usb|usb_device", SYSFS{idVendor}=="0bb4", MODE="0660", GROUP="plugdev"
SUBSYSTEM=="usb|usb_device", SYSFS{idVendor}=="04e8", MODE="0660", GROUP="plugdev"
SUBSYSTEM=="usb|usb_device", SYSFS{idVendor}=="18d1", MODE="0660", GROUP="plugdev"
SUBSYSTEM=="usb|usb_device", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0c02", SYMLINK+="android_adb"
SUBSYSTEM=="usb|usb_device", ATTR{idVendor}=="04e8", ATTR{idProduct}=="0c02", SYMLINK+="android_adb"
SUBSYSTEM=="usb|usb_device", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", SYMLINK+="android_adb"
And my user is a member of the plugdev group...
Regards,
BTJ
Last edited by bjorntj (2011-11-09 09:56:02)

Hmmm... So where can I find information about how my rule should look like now?
Edit: Dooh... never mind....
BTJ
Last edited by bjorntj (2011-11-09 09:50:09)

Similar Messages

Couldn't open mixer device /dev/audioctl

I have just installed Solaris10 x86 OS on my Toshiba Satellite Laptop, everything seesm to work fine but I have no audio. The volume control icon on the panel says > no audio device and when I click on it I get an error dialog saying> Couldn't open mixer device /dev/audioctl
I have downloaded the Solaris Audio Drivers 1.0, audio810 and audiovia823x from the Sun website and installed them but no use, I also installed the audio drivers from the http://www.tools.de/solaris/audio/ website > audio1371, audioemu, audioi810, audiovia8233 but nothing.
Could anyone please advise me how I can get the audio working.
Thanks,
Suraj

HI thankx,
I tried your solution but>
devfsadm: driver failed to attach: audio810
Warning: Driver (audio810) successfully added to system but failed to attach

Couldn't open audio: Couldn't open audio device or ESD

Got the Heroes of Might & Magic III for Linux, from Loki-games,
When I run the game, the terminal shows that 'Couldn't open audio: Couldn't open audio device or ESD connection'
and, of course, the game has no sound ; o
Does anyone play this under linux?
thanks

I was having sound issues with a game on a fresh Arch install, until i realised that pulseaudio had failed to start because dbus wasn't running.
So, i started dbus
# /etc/rc.d/dbus start
Then i started avahi-daemon
# /etc/rc.d/avahi-daemon start
then i started pulseaudio manually.
$ pulseaudio --start
also, make sure you're a member of the group 'audio'. If you're not, sound may not work properly, or at all.
If these steps work, be advised that, in all probability it will only work until reboot. But that's a story for another post.
HTH,
--Aaron
Last edited by usagi (2011-11-21 20:01:11)

[SOLVED] ERROR: Unable to find root device '/dev/sda3'

Earlier I updated the kernel to my arch system and found this error while trying to boot. I hate to post this because there are so many topics like it, but I've been looking for hours for a solution to this problem and can't find one.
Here is the output:
Booting 'Arch Linux'
root (hd0,1)
Filesystem type is ext2fs, partition type 0x83
kernet /vmlinuz-linux root=/dev/sda3 ro
[Linux-bzImage, setup=0x4200, size=0x2ff2d0]
initrd /initrd @ 0xfd17000, 0x2c878c bytes]
Probing EDD (edd=off to disable)... ok
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
:: Starting udevd...
done.
Waiting 10 seconds for device /dev/sda3 ...
ERROR: device '/dev/sda3' not found. skipping fsck.
ERROR: Unable to find root device '/dev/sda3'.
You are being dropped to a recovery shell
type 'exit' to try and continue booting
sh: can't access tty; job control turned off
My partition layout is like this:
swap: /dev/sda1
boot: /dev/sda2
root: /dev/sda3
extended: /dev/sda4
home: /dev/sda5
I have two hard drives, but i'm sure /dev/sda is the one with my OS.
Here are some things I've tried:
This was at the very bottom of the pacman wiki
# mkdir /mnt/arch
# mount /dev/sdaX /mnt/arch (your root partition)
# cd /mnt/arch
# mount -t proc proc proc/
# mount -t sysfs sys sys/
# mount -o bind /dev dev/
# mount /dev/sdaX boot/ (your /boot partition) #This step is not needed if you do not have a separate boot partition
# chroot .
# pacman -Syu udev mkinitcpio
# mkinitcpio -p linux
I've also tried performing the above, downgrading the kernel, updating my mirrorlist, reinstalling the kernel, and rebooting as mentioned here.
I've alsa tried a few other things that I've read, but can no longer remember.
Any help would be greatly appreciated! Thanks.
Last edited by colton7909 (2012-05-25 02:09:36)

Thank colton
Same problem here, but on a mac book (not mine eyh )
So, for those how have the problem (or need a live usb for mac or uefi systems),
1) with a 32bits system
- download gparted live cd
- use it for the step 3
2) with a 64bits system:
- you need the gparted live cd too: mount it and copy the EFI directory somewhere; then umount it;
- download a 64bits system (system rescue cd, as colton said is enough, follow the instructions for installation on their website first);
- mount you live usb, install the 64bits system;
- copy EFI system on the key
- edit the grub.cfg in EFI/boot/ , add the following before the other entries:
menuentry "System Rescue" {
set gfxpayload=keep
linux /syslinux/altker64 nomodeset efi
initrd /syslinux/initram.igz
3) repairing...
- boot the broken computer with the live usb
- mount the partition on which your system is (e.g. /dev/sda1 on /mnt)
- chroot it, init the system as needed (mount /dev, /proc, etc. the easier way is using init scripts)
% chroot /mnt /bin/bash
% /etc/rc.sysinit
% mkinitcpio -p linux

[SOLVED] ERROR: Can't find root device /dev/disk/by-uuid/...

Yesterday I upgraded my Lenovo X100e
# pacman -Syu
and rebooted. Upon reboot, I received the error
ERROR: Cannot find root device '/dev/disk/by-uuid/[...]'
just after kernel decompression. I got dropped into the recovery shell
and could not boot.
The problem persisted despite using different root device names (e.g. /dev/sda3, the actual root device). After reading the instructions at https://wiki.archlinux.org/index.php/Chroot I used a core installation image (on a usb stick) to boot the machine, then chrooted into my installation. I ran mkinitcpio and found that the udev hook was missing, i.e. not in /lib/initcpio/hooks. Nor was there a file called 'udev' in /lib/initcpio/install.
I copied these files from a friend's installation and then re-ran mkinitcpio:
# mkinitcpio -p linux
I was able to reboot successfully after that.
The weird thing: I don't know how the udev hook script was deleted from /lib/initcpio/hooks.
If someone else runs into this problem: try to run mkinitcpio (e.g. by using the chroot), and check for this problem. I think the problem was that the root device could not be found because the udev hook had not run, and therefore /dev was unpopulated.

Betwen udev-181-2 and udev-181-5, the hooks have moved from /lib/initcpio to /usr/lib/initcpio. But mkinitcpio -L should still list them.
I have a similar problem since the last update. The kernel doesn't seem to load my raid driver anymore. Upon boot it throws some cryptic udev messages at me and then crashes. Haven't found out what that is about yet.

Cannot open/stat device

Good day to all.
I'm trying to install Solaris 10 (11/06) on my pentium D box. I have 1 SATA hdd (primary master) and 1 DVD-RW drive. The hdd have 2 primary partitions - 1st - win-xp, ntfs, 2nd - for Solaris OS and 1 logical partition. During installation process I have an error - installboot failed - failed to install boot block.
After that I boot in single user shell disagreed to mount found solaris partition on /a and entered command - /sbin/installgrub stage1 stage2 /dev/dsk/c1d0s0 and got an error - cannot open/stat device /dev/dsk/c1d0s2
I don't understand why installgrub trying to use c1d0s2 instead of c1d0s0?
By the way, mount /dev/dsk/c1d0s0 /a works fine.
Pls help!

Hi,
I have a disk with 2 partitions. 1st partition I installed solaris2 filesystem/slices. 2nd partition I created via fdisk from within solaris.
I assigned 2nd partition to a zpool. Creating the zpool trashed my MBR, and I could no longer boot Solaris off the hard drive.
booting into singleuser mode off the install cd, solaris detected the 1st partition, and mounted it at /a. Running installgrub gave me the same error message.
Trick I tried:
Copy stage1 and stage2 files off /a/boot/grub into /tmp.
unmount /a.
re-run installgrub
violla installgrub has no problem writing to device. The MBR was restored! Horray!

Can't format external HDD using terminal: Error: -69877: Couldn't open device

Disk Utility won't format / erase Seagate Barracuda 2TB (ST2000DM001) - it is an internal drive but I connected it using a docking station via USB. The disk is brand new and unformatted. System indicates that it is S.M.A.R.T incompatible
When trying to erase the disk, I get error message "disk / link could not be found / opened".
I tried using terminal "diskutil eraseDisk HFS+ newdisk /dev/disk3" but I get this message:
Started erase on disk3
Unmounting disk
Error: -69877: Couldn't open device
Any way I could force format the disk?

Thank you @MrHofman. I had a setup with 2 dock stations and 2 HDDs (my TimeCapsule had crashed and I needed to recover its content disassembling the "box"). I disconnected everything. I restarted the computer., I swithched the USB ports in which I had connected the dock stations; I swithched the HDDs from dock stations, and voilà, the system allowed me to format the "recovery" HDD. Sometimes the "simplest" solutions work...
@Linc Davis: prior to the fix described above, when trying to partition, same thing would occur : "can't open link / disk" error message. But now it seems to be working fine. Thank you anyway!

Could not open the device file /dev/nvidia0

and yet:
[root@mythfe01 dev]# ls -alh nvid*
crw-rw-rw- 1 root root 195, 0 Mar 26 16:06 nvidia0
crw-rw-rw- 1 root root 195, 255 Mar 26 16:06 nvidiactl
and:
[root@mythfe01 dev]# lsmod | grep nv
nvidia 4083280 0
agpgart 28872 1 nvidia
but:
NVIDIA: could not open the device file /dev/nvidia0 (Input/output error).
(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
(EE) NVIDIA(0): *** Aborting ***
I am using a homemade kernel, but i can't think of a reason why that would prevent things from working properly considering the module loaded ok.
Any thoughts?

Moo-Crumpus wrote:Do you use udev? Have a look if there is a ruleset for nvidia, I remember there was one. Afaik, nvidia should be owned by the video group - well, once it was, I am not up to date and have no arch machine with nvidia right now.
Could anyone specify how to do that? I have the exact same problem, although I use the default kernel that came with Arch.
NVIDIA: could not open the device file /dev/nvidia0 (Permission denied).
NVIDIA: Direct rendering failed; attempting indirect rendering.
[kristjans@myhost ~]$ cat /proc/driver/nvidia/cards/0
Model: GeForce 6200 TurboCache(TM)
IRQ: 22
Video BIOS: 05.44.02.52.00
Card Type: PCI-E
DMA Size: 39 bits
DMA Mask: 0x7fffffffff
[kristjans@myhost dev]$ ls -alh nvid*
crw-rw---- 1 root 27 195, 0 2007-10-06 19:10 nvidia0
crw-rw-rw- 1 root 27 195, 255 2007-10-06 19:10 nvidiactl
[kristjans@myhost dev]$ lsmod | grep nv
nvidia 6829684 40
i2c_core 20352 2 nvidia,i2c_piix4
agpgart 27224 2 nvidia,ati_agp
Last edited by KSiimson (2007-10-11 04:23:18)

HT204053 i couldn't open new terms and conditions of icloud, and so i can't use the icloud on my device iphone 5, this problem appears, when I get new ios 7

i couldn't open new terms and conditions of icloud, and so i can't use the icloud on my device iphone 5, this problem appears, when I get new ios 7

Try download the Find My Friends app and signing in to accept the terms and conditions there.

[SOLVED] - Arch Boot Error: Unable to find Root Device /dev/sdb1

I had Arch running perfectly using /dev/sdb1 (versus Disk Label or UUID) and decided to do a update. After the Update I can't boot
to a running system, and I get this error message:
ERROR: Unable to find root device /dev/sdb1
You are being dropped into a recovery shell.
Is there an easy way to convert to UUID or Disk Label since the latest Upgrade doesn't allow me to continue to use /dev/sdb1 ??
I'd prefer not to have to rebuild both USB Flash Drives to get functional systems.
Any Help is greatly appreciated.
Suggestions?
Larry
Last edited by lkraemer (2012-02-21 15:14:02)

Check your grub and read https://wiki.archlinux.org/index.php/UUID#By-uuid
Edit:
https://bbs.archlinux.org/viewtopic.php … 0#p1059160
https://bbs.archlinux.org/viewtopic.php?pid=1059338
https://bbs.archlinux.org/viewtopic.php?id=135288
Last edited by karol (2012-02-21 01:07:21)

[SOLVED]Error opening PCM device hw:0,0

I am trying to use Jesusonic, but I get the following error:
mmanu > Desktop/jesusonic-0.991-linux-x86/jesusonic -mode ALSA -nbufs 2
Jesusonic v0.991 - Copyright (C) 2004-2005 Cockos Incorporated
Using output mode: 'ALSA'
Opening ALSA 'hw:0,0' for read
Opening ALSA 'hw:0,0' for write
Error opening PCM device hw:0,0
My audio card is an integrated Intel one:
Audio device: Intel Corporation module: snd-hda-intel
82801G (ICH7 Family) High Definition Audio Controller
I am not very expert with audio devices and functionality, so is there anything I can look up or do to solve this problem?
Thank you for your time

My lack of understanding is really showing here...
The default format for alsa is implicitly defined like this:
jesusonic -mode ALSA -in hw:0,0 -out hw:0,0
I'm posting this in the hope that someone that knows hardware will be able to tell you how to identify the proper address. Of course another (very hackish) solution is to just try some other value like hw:0,1 on both. 0,0 and 0,1 work on my machine, but it fails with the same error you have on 0,2.
Last edited by skottish (2008-09-21 16:17:33)

Unable to open USB port device file: Permission denied

I have an up-to-date system (full "pacman -Syu" yesterday), I am in a "lp" group and the printer (Canon Pixma MP270) started to give "Unable to open USB port device file: Permission denied" error, although in the past it worked and still works in Windows. Doesn't anybody have a similar problem?

Thanks for reply.
CUPS worked, I could use CUPS-PDF and localhost:631 was accessible and working.
Today I managed to print again. I did "pacman -Rcsn cups" and reinstalled it again.
My printer is Canon Pixma MP270 and so far it wasn't the best choice for Arch Linux—scanning works fine but it's like throwing a coin when it comes to printing. I've written a simple PKGBUILD for installing its printing driver as a regular package, but I don't know what to set as a license.
pkgname=mp270-printer
pkgver=3.20
pkgrel=1
pkgdesc="Canon Pixma MP270 printer driver"
arch=('i686')
url="http://software.canon-europe.com/products/0010753.asp"
license=('unknown')
depends=('libpng12' 'gtk2' 'popt')
makedepends=('deb2targz')
source=(http://files.canon-europe.com/files/soft37268/software/MP270_debian_driver_pack.tar)
md5sums=('d26c36e2d1799ddc09e644dc7765f0a3')
build() {
cd $srcdir
tar xzf cnijfilter-mp270series-$pkgver-1-i386-deb.tar.gz
cd cnijfilter-mp270series-$pkgver-1-i386-deb/packages
deb2targz *
tar xzf cnijfilter-common_$pkgver-1_i386.tar.gz
tar xzf cnijfilter-mp270series_$pkgver-1_i386.tar.gz
ln -s /usr/lib/libtiff.so usr/lib/libtiff.so.4
package () {
cd $srcdir/cnijfilter-mp270series-$pkgver-1-i386-deb/packages
cp -r usr $pkgdir/

Opening device /dev/sg3 failed - access denied to /dev/sg* device file

Opening device /dev/sg3 failed - access denied to /dev/sg* device file (OB scsi device driver)
Got this message when running an automated RMAN job.
To my knowledge the only thing that has changed since being able to run RMAN jobs with OSB and not being able to run them is that the permissions on /usr/tmp were changed from drwxr-xr-x, not drwxrwxrwx.
Transcript below:
2010/01/27.04:03:20 ______________________________________________________________________
2010/01/27.04:03:20
2010/01/27.04:03:20 Transcript for job oracle/6142.1 running on backup01
2010/01/27.04:03:20
2010/01/27.04:03:20 (amh) qdv__automount_in_mh tape1 at 2010/01/27.04:03:20, flags 0x100
2010/01/27.04:03:20 (amh) mount volume options list contains:
2010/01/27.04:03:20 (amh) vtype 3, vid (null), vs_create 0, family PAS-RMAN, retain (null), size 0, scratch 0
2010/01/27.04:03:21 (amh) don't preserve previous mh automount state
2010/01/27.04:03:21 (amh) loaded volume has no barcode
2010/01/27.04:03:22 (amh) beginning pass 1
2010/01/27.04:03:22 (mmr) volset containing oid 20859 (vid PASWLY-000215, tag 000086L3) is closed
2010/01/27.04:03:22 (amh) 1 oid 20859 doesn't meet mount requirements - volume set is closed to further update (OB device mgr)
2010/01/27.04:03:22 (mmr) need next volume after oid 20543 (vid PAS-RMAN-018887, tag 000048L3) for append; its oid 20604
2010/01/27.04:03:22 (amh) 2 oid 20543 doesn't meet mount requirements - the next volume of this set is needed (OB device mgr)
2010/01/27.04:03:22 (mmr) oid 20949 (vid PAS-RMAN-018935, tag 000021L3) passes criteria
2010/01/27.04:03:22 (amh) 3 loading
2010/01/27.04:04:04 (mt) qdv__read_label() succeeded; read 65536 bytes
2010/01/27.04:04:05 (atv) automount worked
2010/01/27.04:04:05 (amh) 3 automount worked - returning
2010/01/27.04:04:05 (amh) end of automount at 2010/01/27.04:04:05 (0x0)
2010/01/27.04:04:05 Info: volume in tape1 is usable for this operation.
2010/01/27.04:04:05 (pvfw) at BOT
2010/01/27.04:04:05 (pvfw) previous state is invalid
2010/01/27.04:04:05 (alv) backup image label is valid, file 1, section 1
2010/01/27.04:04:05 (pvfw) invalidating tape position in mount db
2010/01/27.04:04:05 (ial) invalidate backup image label (was valid)
2010/01/27.04:05:17 (pvfw) space to EOD
2010/01/27.04:05:26 (pvfw) inspect_recs BSR: rtypes [0] = filemark
2010/01/27.04:05:26 (pvfw) inspect_recs BSR: rtypes [1] = filemark
2010/01/27.04:05:26 (pvfw) inspect_recs BSR: rtypes [2] = data
2010/01/27.04:05:26 (pvfw) inspect_recs BSR: rtypes [3] = filemark
2010/01/27.04:05:26 (pvfw) inspect_recs FSF
2010/01/27.04:05:26 (pvfw) inspect_recs ready to mount
2010/01/27.04:05:26 (pvfw) mounting at inspect_rec's request in rw_mode 2
2010/01/27.04:05:28 (pvfw) mounted ok
2010/01/27.04:05:28 (pvfw) at OB EOD, returning (2)
2010/01/27.04:05:28 (pvfw) pos_vol_cleanup not returning pstate
2010/01/27.04:05:28 (dmap) tape1 success
04:05:28 OBTR: obtar version 10.2.0.3.0 (linuxamd64) -- Wed Sep 24 11:12:44 PDT 2008
Copyright (c) 1992, 2007, Oracle. All rights reserved.
04:05:28 OBTR: obtar -c -Xjob:oracle/6142.1 -Xob:10.2 -Xstat -X shm:/usr/tmp/obsbt_10985_0_126458300010985a -Xbga:oracle/6142.1 -y /usr/tmp/[email protected] -J -F5 -f tape1 -Xrescookie:0x99ECC895 -H backup01 -zR
04:05:28 OBTR: running as root/root
04:05:28 OBTR: record storage set to internal memory
04:05:28 ATAL: reserved drive tape1, cookie 0x99ECC895
04:05:28 OBTR: obsd=1, is_job=1, is_priv=0, os=15
04:05:28 OBTR: rights established for user oracle, class admin
04:05:28 SUUI: user info oracle/oinstall, ??/??
04:05:28 STTY: background terminal I/O or is a tty
04:05:28 MAIN: interactive
04:05:28 SET: volume has no expiration time
04:05:28 CNPC: data host reports this butype_info:
04:05:28 CNPC: tar (attr 0x2C78: B_DIRECT, R_DIRECT, B_INCR, R_INCR, B_FH_DIR)
04:05:28 CNPC: DIRECT = y
04:05:28 CNPC: HISTORY = y
04:05:28 CNPC: LEVEL = 0
04:05:29 DOLM: nop (for tape1 (raw device "/dev/sg3"))
04:05:29 DOLM: ok
04:05:30 RLE: connecting to volume/archive database host
04:05:30 RLE: device tape1 (raw device "/dev/sg3")
04:05:30 RLE: mount_info is valid
04:05:30 A_O: tape device is local
04:05:30 A_O: Devname: HP,Ultrium 3-SCSI,G63Z
04:05:30 Info version: 11
04:05:30 WS version: 10.2
04:05:30 Driver version: 10.2
04:05:30 Max DMA: 2097152
04:05:30 Blocksize in use: 65536
04:05:30 Query frequency: 134217728
04:05:30 Rewind on close: false
04:05:30 Can compress: true
04:05:30 Compression enabled: true
04:05:30 8200 media: false
04:05:30 Error threshold: 8%
04:05:30 Remaining tape: 403359744
04:05:30 A_GB: ar_block at 0x2B544951A000, size=2097152
04:05:30 A_GB: ar_block_enc at 0x2B544971E000, size=2097152
04:05:30 ADMS: reset library tape selection state
04:05:30 ADMS: reset complete
04:05:30 VLBR: not at bot: 0x9
04:05:30 VLBR: tag on label just read: "000021L3"
04:05:30 VLBR: master tag now "000021L3"
04:05:30 RLE: set kb remaining to 403359744
04:05:30 RLE: noticed nil label
04:05:30 ARVI: resetting volume id from nil to PAS-RMAN-018935
04:05:30 PF: here's the label at the current position:
Volume label:
Volume tag: 000021L3
Intro time: Tue Jun 02 17:00:51 2009
Volume UUID: d0e25812-ed54-102c-a34d-001143fd735c
Volume ID: PAS-RMAN-018935
Volume sequence: 1
Volume set owner: root
Volume set created: Tue Jan 26 23:32:25 2010
Media family: PAS-RMAN
Volume set expires: never; content manages reuse
Original UUID: d0e25812-ed54-102c-a34d-001143fd735c
Archive label:
File number: 5
File section: 1
Owner: root
Client host: merge01
Backup level: 0
S/w compression: no
Archive created: Wed Jan 27 00:08:56 2010
Marker: End of data
04:05:30 PF: at desired location
04:05:30 RCVW: volume "PAS-RMAN-018935" / vuuid d0e25812-ed54-102c-a34d-001143fd735c reserved for writing
04:05:30 CREA: tape position after open_archive() is 0001A1800000
04:05:30 GLMT: returning "000021L3", code = 0x0
04:05:30 IMF: inherited media family PAS-RMAN is content-managed
04:05:30 CREA: setting history tag to "000021L3" from volume label
04:05:30 RLE: overwrite invalid/blank/marker section
04:05:30 VLBW: on entry, l->tag = "", master tag = "000021L3", bot = 0
04:05:30 VLBW: setting voltag from "" to "000021L3"
04:05:30 VLBW: volume is content-managed
04:05:30 RLE: write volume PAS-RMAN-018935, file 5, section 1, vltime 1264566745, vowner root, voltag 000021L3
04:05:30 VSLW: set last write time for volume oid 20949
04:05:31 ULVI: set mh db volume id "PAS-RMAN-018935" (retid "000021L3"), volume oid 20949, code 0
04:05:31 ULTG: set mh db tag "000021L3" (retid "PAS-RMAN-018935"), volume oid 20949, code 0
04:05:31 RLE: set kb remaining to "invalid or unknown"
Volume label:
Volume tag: 000021L3
Intro time: Tue Jun 02 17:00:51 2009
Volume UUID: d0e25812-ed54-102c-a34d-001143fd735c
Volume ID: PAS-RMAN-018935
Volume sequence: 1
Volume set owner: root
Volume set created: Tue Jan 26 23:32:25 2010
Media family: PAS-RMAN
Volume set expires: never; content manages reuse
Original UUID: d0e25812-ed54-102c-a34d-001143fd735c
Archive label:
File number: 5
File section: 1
Owner: root
Client host: backup01
Backup level: 0
S/w compression: no
Archive created: Wed Jan 27 04:05:28 2010
Archive owner UUID: 9d92d00e-0368-102b-89f6-001143fd735c
Owner class UUID: edde6dc8-f857-102a-a357-001143fd735c
Backup piece name: 8sl4ft06_1_1
Backup db name: emrep
Backup db id: 3844670930
Backup copy number: not applicable
Backup content: archivelog
04:05:31 RCVW: volume "PAS-RMAN-018935" / vuuid d0e25812-ed54-102c-a34d-001143fd735c reserved for writing
04:05:31 ADMS: reset library tape selection state
04:05:31 ADMS: reset complete
04:05:31 SNP: using NDMP protocol version 4
04:05:36 FLDB: drive buffer flush to medium took 0:05 (min:sec)
04:05:36 BNPC: volume position "0001A181" added to s_vol_start_pos
04:05:36 BNPC: initial volume label "PAS-RMAN-018935" added to s_vids, s_last_section 1
04:05:36 BNPC: initial volume tag "000021L3" added to s_vtags, s_last_section 1
04:05:36 BNPC: environment variable DATA_BLOCK_SIZE = 64
04:05:36 BNPC: environment variable DATA_ARCH_UUID = f3ccd49e-ed7a-102c-be2b-001143fd735c
04:05:36 MGS: ms.record_size 65536, ms.record_num 0x0, ms.bytes_moved 0x0
04:05:36 SMWB: setting mover window for possible checkpoint during backup
04:05:36 MLIS: mover listen ok for local connection
04:05:36 APNI: a preferred network interface does not apply to this connection
04:05:36 DPNI: a local NDMP data connection is in use
04:05:36 BNPC: directing data service to connect to mover
04:05:42 BNPC: issuing NDMP_DATA_START_BACKUP
04:05:47 BNPC: started OSB NDMP backup of backup01 to tape1
04:16:51 MNPO: data service halted with reason=successful
04:16:51 SNPD: Data Service reported bytes processed 0x6DF20000
Opening device /dev/sg3 failed - access denied to /dev/sg* device file (OB scsi device driver)

Permissions problem on the drive for the user running the job.

[SOLVED] Initramfs trim: "device '/dev/sda3' not fount" still boots.

SOLUTION I should have never removed UUIDs from my fstab, instead I should have ADDED them to my bootloader config. Putting UUIDs back in fstab and adding the UUID for my root partition to syslinux.cnf solved this.
I've been pruning my initramfs following falconindy's blog post which I learned about from success stories in the systemd startup times thread.
I ended up with this mkinitcpio.conf
MODULES="ahci sd_mod ext4"
BINARIES="fsck fsck.ext4"
HOOKS="base consolefont"
COMPRESSION="lzop"
I've also tried without the compression method specified. I've added in a couple modules which I admittedly don't know much about, but I found them in the lsmod list after appending the "break=postmount" to a working initramfs. These included uhci_hcd and ehci_hcd.
In every case I get the same error message on boot:
device '/dev/sda3' not found. Skipping fsck
Unable to find root device '/dev/sda3'
and I am dropped to a recovery shell. There is a message that says (paraphrasing) "type exit to attempt to continue". I type exit and hit enter and I get a message:
Trying to continue (This will likely fail)
But it does not fail - it works perfectly and the system boots successfully.
So in short - everything works, but there is some early boot test that "thinks" it won't work and leads to me having to exit from a recovery shell.
I realized my fstab still had UUIDs, so I changed those to /dev/sdaX and rebuilt the initramfs, but this had no effect.
The best I can guess (and it is a wild guess) is that the only remaining difference between the working initramfs and this problematic stripped down version is the absence of udev. I did look at a diff of the lsinitcpio of a working version and the failing trimmed down version. I've removed any items that went both ways in the diff output (eg ">some/file ... <some/file") and this is what remains:
7c6
< ./hooks/udev
16,18d14
< ./usr/bin/fsck.ext3
20,21c16,17
< ./usr/bin/udevadm
< ./usr/bin/udevd
130a127,128
> ./usr/lib/libpthread-2.16.so
> ./usr/lib/libpthread.so.0
137,151d134
< ./usr/lib/udev
< ./usr/lib/udev/scsi_id
< ./usr/lib/udev/ata_id
< ./usr/lib/udev/rules.d
< ./usr/lib/udev/rules.d/80-drivers.rules
< ./usr/lib/udev/rules.d/60-persistent-storage.rules
< ./usr/lib/udev/rules.d/50-udev-default.rules
< ./usr/lib/libpthread-2.16.so
< ./usr/lib/libpthread.so.0
< ./usr/lib/libattr.so.1.1.0
< ./usr/lib/libattr.so.1
< ./usr/lib/librt-2.16.so
< ./usr/lib/librt.so.1
< ./usr/lib/libacl.so.1.1.0
< ./usr/lib/libacl.so.1
254a238,246
> ./usr/lib/modules/3.5.3-2-ck/kernel/hwa-hc.ko
> ./usr/lib/modules/3.5.3-2-ck/kernel/isp116x-hcd.ko
> ./usr/lib/modules/3.5.3-2-ck/kernel/isp1362-hcd.ko
> ./usr/lib/modules/3.5.3-2-ck/kernel/isp1760.ko
> ./usr/lib/modules/3.5.3-2-ck/kernel/ohci-hcd.ko
> ./usr/lib/modules/3.5.3-2-ck/kernel/oxu210hp-hcd.ko
> ./usr/lib/modules/3.5.3-2-ck/kernel/r8a66597-hcd.ko
> ./usr/lib/modules/3.5.3-2-ck/kernel/sl811-hcd.ko
> ./usr/lib/modules/3.5.3-2-ck/kernel/u132-hcd.ko
255a248,250
> ./usr/lib/modules/3.5.3-2-ck/kernel/whci-hcd.ko
> ./usr/lib/modules/3.5.3-2-ck/kernel/xhci-hcd.ko
> ./usr/lib/modules/3.5.3-2-ck/kernel/ftdi-elan.ko
256a252,256
> ./usr/lib/modules/3.5.3-2-ck/kernel/wusb-wa.ko
> ./usr/lib/modules/3.5.3-2-ck/kernel/wusbcore.ko
> ./usr/lib/modules/3.5.3-2-ck/kernel/umc.ko
> ./usr/lib/modules/3.5.3-2-ck/kernel/uwb.ko
> ./usr/lib/modules/3.5.3-2-ck/kernel/whci.ko
274,275d273
< ./etc/udev
< ./etc/udev/udev.conf
The ck-modules lead me to try this with a "vanilla" arch kernel which I also have installed. With the default arch kernel I am left in a recovery shell but exiting does not lead to a successful boot. I don't know what this really means, but perhaps something unique to the ck-kernel setup allows a recovery from this problem.
Any suggestions for further troubleshooting or exploration?
edit I put udev back in the hooks array, rebuilt the image, and now it works fine. So udev is the relevant peice of the puzzle. I thought the idea of using the modules, though, was so that udev wouldn't be needed. I must have missed a needed module, though I cant figure what it would be.
edit2 I've used "break=postmount" on both the working image with udev, and with the failing image without udev and I do an "lsmod" in the shell. I get the exact same list of modules. So all the correct modules are all loaded properly. But the absence of udev seems to cause a problem.
Last edited by Trilby (2012-09-01 15:10:14)

Thanks. I solved the issue. I found this thread: https://bbs.archlinux.org/viewtopic.php?pid=901651
Basically I just copied all of the modules listed in lsmod to the MODULES section of the mkinitcpio.conf on the HD, removed autodetect from the hooks, and ran mkinitcpio -p linux-mac. I'm not sure what all of that was actually mandatory, I didn't check, but I know it worked. I think the main thing was the pata_macio module.
Turns out persistent block device naming wasn't my issue at all. I reverted back to using /dev/sdaX names.

[SOLVED]Couldn't open file for 'Log debug file /var/log/tor/debug.log'

Hello,
I'm trying to run a tor relay on my arch linux box. Trying to launch the tor daemon, here's the log via
$ systemctl status tor.service
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.877 [notice] Tor v0.2.4.21 (git-505962724c05445f) running on Linux with Libevent 2.0.21-stable and OpenSSL 1.0.1g.
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.877 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.877 [notice] Read configuration file "/etc/tor/torrc".
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.909 [notice] Opening Socks listener on 127.0.0.1:9050
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.909 [notice] Opening OR listener on 0.0.0.0:9798
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [warn] Couldn't open file for 'Log debug file /var/log/tor/debug.log': Permission denied
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [notice] Closing partially-constructed Socks listener on 127.0.0.1:9050
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [notice] Closing partially-constructed OR listener on 0.0.0.0:9798
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [warn] Failed to parse/validate config: Failed to init Log options. See logs for details.
May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [err] Reading config failed--see warnings above.
May 20 11:53:10 arch systemd[1]: tor.service: main process exited, code=exited, status=255/n/a
May 20 11:53:10 arch systemd[1]: Unit tor.service entered failed state.
Why the tor daemon cannot write into /var/log/tor/debug.log ?
Here's my /etc/group
root:x:0:root
bin:x:1:root,bin,daemon
daemon:x:2:root,bin,daemon
sys:x:3:root,bin
adm:x:4:root,daemon,nue
tty:x:5:
disk:x:6:root
lp:x:7:daemon
mem:x:8:
kmem:x:9:
wheel:x:10:root,nue
ftp:x:11:
mail:x:12:
uucp:x:14:
log:x:19:root
utmp:x:20:
locate:x:21:
rfkill:x:24:
smmsp:x:25:
http:x:33:
games:x:50:
lock:x:54:
uuidd:x:68:
dbus:x:81:
network:x:90:
video:x:91:
audio:x:92:
optical:x:93:
floppy:x:94:
storage:x:95:
scanner:x:96:
power:x:98:
nobody:x:99:
users:x:100:
systemd-journal:x:190:
nue:x:1000:
avahi:x:84:
lxdm:x:121:
polkitd:x:102:
git:x:999:
transmission:x:169:
vboxusers:x:108:
tor:x:43:
mysql:x:89:
Last edited by giuscri (2014-05-20 12:18:56)

SidK wrote:You must have modified your torrc to print to that log file. systemd starts the service as the tor user (see /usr/lib/systemd/system/tor.service). So if if you want to log to a file the tor user must have write access to it. By default however tor it set to log to the journal, which doesn't require any special permissions.
Yes. I did edit the torrc file since I wanted the log to be store in that file. Indeed
## Logs go to stdout at level "notice" unless redirected by something
## else, like one of the below lines. You can have as many Log lines as
## you want.
## We advise using "notice" in most cases, since anything more verbose
## may provide sensitive information to an attacker who obtains the logs.
## Send all messages of level 'notice' or higher to /var/log/tor/notices.log
#Log notice file /var/log/tor/notices.log
## Send every possible message to /var/log/tor/debug.log
Log debug file /var/log/tor/debug.log
## Use the system log instead of Tor's logfiles
Log notice syslog
## To send all messages to stderr:
#Log debug stderr
I missed the file systemd uses to choose who's the process owner.
Course, I could edit /usr/lib/systemd/system/tor.service such that root will become the process owner; or, I could add the user I use everyday in the root group, then change the permission of /var/log/tor/debug.log such that it will be writable also for the folks in the root group.
Yet they both seems to be a bit unsafe ...
What is the best choice, to you guys?
Thanks,

[solved] libusb couldn't open USB device /dev/bus/usb/003/010:

Similar Messages

Maybe you are looking for