No loopback devices (/dev/loop#)[solved]

Hi,
I seem to be missing the /dev/loop0, /dev/loop1, etc. devices. This means that when I try to mount a filesystem image to a folder (with -o loop) mount complains about the missing loopback devices and the mount fails. Does anyone else have the same problem? Does this need to be reported? Thanks in advance.
edit: I found the problem myself. Sorry!
Last edited by Bralkein (2008-06-01 22:07:25)

@sirocco:
That solution is great and works... but only temporarily.
In order for the system to boot with the loopback devices permanently, just add a file called loopback-dev.conf under /etc/modules-load.d/ with the following contents:
loop
(Source https://wiki.archlinux.org/index.php/kernel_modules)

Similar Messages

/dev/loop# missing

Hi folks.
I'm trying to mount an iso image with the loop device but it's gone!
I just typed this (as root): mount /bla/bla/xxx.iso /mnt/iso -o loop
And it gives me:
mount: could not find any device /dev/loop#
Where is my loop device?!?!
Thanks.
Last edited by tsenart (2008-10-22 23:01:49)

Thanks for searching

[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] - 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: 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.

Flood ping of loopback device gives 20% packet loss!

While trying to diagnose a problem with my Airport Express (high packet loss even with a strong signal), I noticed that my Macbook cannot reliably flood ping its own loopback device!
bash-3.2$ $ sudo ping -f 127.0.0.1
PING 127.0.0.1 (127.0.0.1): 56 data bytes
....^C
--- 127.0.0.1 ping statistics ---
994 packets transmitted, 750 packets received, 24% packet loss
round-trip min/avg/max/stddev = 0.012/0.017/0.103/0.007 ms
As the loopback interface is internal, I get precisely the same result whether Airport is turned on or off.
This seems completely crazy to me! Anyone have any idea what might be going on?
Message was edited by: zzz Matt Taylor (replaced ping output with one with linebreaks to avoid excessively wide post)

Can't help you specifically with that, but just last night my Atheros AR5008 adapter starting dropping 40%-80% of the packets to my router. It's unusably slow now. I had this problem with the 2.6.38 kernel and was able to solve it by passing the nohwcrypt option to the ath9k module, but that doesn't work anymore.
I'm now on the 3.0.4 kernel, Arch x64. Last updates that MAY be relevant were dbus-sharp, dbus-sharp-glib, and gnutls. I started having problems the day after upgrading these packages. I'm connecting in 802.11n mode.
I've been looking for evidence of related bugs but so far nothing. I wonder if this is a broader issue affecting more than just the Atheros or Ralink drivers?
EDIT: downgrading gnutls from 3.0.3-1 to 3.0.2-1 reduced my packet loss to about 15%, so the internet is now basically usable. I also tried downgrading glib-networking (which I updated to version 2.28.7-5 a few days back), but that didn't seem to help.
Last edited by rsking84 (2011-09-22 01:32:59)

Trouble with mkinitrd (All of your loopback devices are ...)

Hi all,
I'm trying to rebuild the kernel, and have been somewhat succesful. The only step missing is building the "initrd-image". This I can however not do, as mkinitrd is failing (ERROR: All of your loopback devices are in use!). A bit of googling turned up these postings
http://lists.us.dell.com/pipermail/linu … 07473.html
that I believe is an accurate description of my troubles (lsmod | grep loop returns nothing, and I can not find loop.[o|ko] in /lib/modules/`uname -r`).
The abovementioned postings recommend booting from a live-cd with a stock kernel, mounting whatever neccesary and then doing mkinitrd. I however do not have a live-cd (or arch install cd) available, so I was wondering whether it would be possible to just compile loop.o for the running kernel and the modprob'ing it? Any suggestions would be welcomed.
Thanks,
Mads
PS. I'm also a bit curious as to why loopback support is not compiled as a module in the stock kernel (I believe it was recently updated with pacman). Has something gone wrong in this update, or is this an error of some sort?

Try resetting your router. Unplug it for about 30 seconds, then plug it in again. Turn WiFi off on your iPad, reboot the iPad, turn WiFi on again.
Reboot the iPad by holding down on the sleep and home buttons at the same time for about 10-15 seconds until the Apple Logo appears - ignore the red slider if it appears on the screen - let go of the buttons. Let the iPad start up.
If that doesn't work, reset network settings. Settings>General>Reset>Reset Network Settings.

Strange "loopback device" actions on Mac OS X Leopard

Hi all,
I want to explain my little problem to you, hoping someone can give me an answer:
from about a week I'm trying to develop an application that use pylibpcap (a python extension of pcap library) to sniff packets on a pc on ethernet and examine udp packets sniffed.
This python program works very well on LAN, on two different computers (1Gnu/Linux and 1Mac), but if I try to make it work on loopback device (both server program and client program), some strange things happen.
The client simply do this:
*bunnybox:~ alex$ python*
*Python 2.5.1 (r251:54863, Oct 5 2007, 21:08:09)*
*GCC 4.0.1 (Apple Inc. build 5465)] on darwin*
*Type "help", "copyright", "credits" or "license" for more information.*
*>>> import socket*
*>>> s=socket.socket(socket.AF_INET, socket.SOCK_DGRAM)*
*>>> s.connect(("127.0.0.1",23))*
*>>> s.send("try to send this")*
16
Listening on loopback device (lo0) with Wireshark (a Sniffer Program), it returns (this is the exported log):
*No. Time Source Destination Protocol Info*
*11 2.840622 127.0.0.1 127.0.0.1 UDP Source port: 49256 Destination port: telnet [UDP CHECKSUM INCORRECT]*
*Frame 11 (48 bytes on wire, 48 bytes captured)*
Null/Loopback
*Internet Protocol, Src: 127.0.0.1 (127.0.0.1), Dst: 127.0.0.1 (127.0.0.1)*
*User Datagram Protocol, Src Port: 49256 (49256), Dst Port: telnet (23)*
*Data (16 bytes)*
*0000 74 72 79 20 74 6f 20 73 65 6e 64 20 74 68 69 73 try to send this*
*As you can see, there is a problem on UDP checksum.*
But if I try the same command on a different computer on my LAN,
for example: a Gnu/Linux Box of Address: 192.168.1.20 (Mac OS X has address: 192.168.1.100),
this is the python code:
*alex@boxxolo ~ $ python*
*Python 2.4.4 (#1, Oct 28 2007, 15:48:55)*
*GCC 4.1.2 (Gentoo 4.1.2)] on linux2*
*Type "help", "copyright", "credits" or "license" for more information.*
*>>> import socket*
*>>> s=socket.socket(socket.AF_INET, socket.SOCK_DGRAM)*
*>>> s.connect(("192.168.1.100",23))*
*>>> s.send("try to send this")*
16
and this is the result sniffed by Wireshark on Mac Os X Leopard Computer (this is the exported log):
*No. Time Source Destination Protocol Info*
*4953 57.558319 192.168.1.20 192.168.1.100 UDP Source port: filenet-tms Destination port: telnet*
*Frame 4953 (60 bytes on wire, 60 bytes captured)*
*Ethernet II, Src: 00:e0:18:29:74:28 (00:e0:18:29:74:28), Dst: 00:19:e3:43:85:e8 (00:19:e3:43:85:e8)*
*Internet Protocol, Src: 192.168.1.20 (192.168.1.20), Dst: 192.168.1.100 (192.168.1.100)*
*User Datagram Protocol, Src Port: filenet-tms (32768), Dst Port: telnet (23)*
*Data (16 bytes)*
*0000 74 72 79 20 74 6f 20 73 65 6e 64 20 74 68 69 73 try to send this*
As you can see, no errors on UDP Checksum, datagram correctly received and no problems.
*NOTE: don't care about port 23, because no telnet or other services are listening on it, it's only a closed port.*
I don't know if it's a bug of loopback device (lo0),
or a bug of Python's Socket, or pcap problem..
Hope someone can give me an answer,
PS: If this is not an appropriate place to publish this type of question, please tell me where I can.
Have a nice day,
Alessandro.

Hi,
Have you receive some answers about your problem because I have the same ...
Thanks,
Leyoda

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

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.

ERROR: Device '/dev/sda3' not found.

This is my first time compiling a custom kernel. I am trying to compile zen kernel 3.12.3. Whenever I try to boot it up, it says this:
ERROR: device '/dev/sda3' not found. Skipping fsck
ERROR: Unable to find root device '/dev/sda3'
Then it drops me to a recovery shell. When I look at the contents of '/dev' none of my partitions are found on sda. '/dev/sda' is listed but nothing else. Has anybody else had this problem? /i have read various fixes but none of them have helped.
Sorry this is my first post.
Thanks in advance.

Well, the whole point of the initramfs is to have it load the necessary modules to mount the rootfs. So if mkinitpcio complains that there are no modules to put in there, that is pretty problematic.
I think you should take a look at the PKGBUILD for the official Arch kernel. It includes a few lines that allow you to use menuconfig or nconfig or whatever, prior to that actual 'make'. I think that any time you install things to your system, you should probably be leveraging the package manager in order to properly track the files. This is particularly true when you are an Arch user and the creation of packages is so damn easy.

Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff path

$ dmesg -l err
[ 6.330201] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache2
[ 6.332384] systemd[1]: Device dev-disk-by\x2dlabel-raid0.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache2 and /sys/devices/virtual/block/bcache1
[ 6.334041] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache1
[ 6.730564] systemd[1]: Device dev-disk-by\x2dlabel-raid0.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache2 and /sys/devices/virtual/block/bcache3
[ 6.732213] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache3
[ 6.997304] systemd[1]: Device dev-disk-by\x2dlabel-jabod.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf3
[ 6.999960] systemd[1]: Device dev-disk-by\x2duuid-0d19cfc3\x2d7588\x2d4c19\x2db85e\x2dbf3a3db2d4a0.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf3
[ 7.003235] systemd[1]: Device dev-disk-by\x2dlabel-raid1.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf1
[ 7.005881] systemd[1]: Device dev-disk-by\x2duuid-99fd7889\x2dde7a\x2d4b30\x2d9745\x2d8ccb2b1ee75d.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf1
[ 7.194594] systemd[1]: Device dev-disk-by\x2dlabel-aroot.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde1
[ 7.197369] systemd[1]: Device dev-disk-by\x2duuid-3873d8ba\x2d9472\x2d4d92\x2dab0d\x2de94574bd0eae.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde1
[ 7.207859] systemd[1]: Device dev-disk-by\x2dlabel-raid1.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde3
[ 7.210477] systemd[1]: Device dev-disk-by\x2duuid-99fd7889\x2dde7a\x2d4b30\x2d9745\x2d8ccb2b1ee75d.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde3
[ 7.240459] systemd[1]: Device dev-disk-by\x2dlabel-aroot.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2
[ 7.243114] systemd[1]: Device dev-disk-by\x2duuid-3873d8ba\x2d9472\x2d4d92\x2dab0d\x2de94574bd0eae.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2
[ 8.062829] systemd[1]: Device dev-disk-by\x2dlabel-jabod.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb4
[ 8.065328] systemd[1]: Device dev-disk-by\x2duuid-0d19cfc3\x2d7588\x2d4c19\x2db85e\x2dbf3a3db2d4a0.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb4
I've been getting this since I upgraded systemd last week. I tried fixing some of these by removing partitions with the same label that I wasn't using, which worked. The reason I have so many partitions with the same label is due to btrfs. Each partition that makes up a volume in btrfs has the same label. Apparently systemd doesn't like this.
Everything on my system seems to be working fine, however I would like to stop these errors since they are annoying/scary, but without having to reduce all my volumes to single.
Last edited by nstgc (2015-04-26 15:53:20)

I'm running with a wired-only set up. I'll have to wait for the weekend to look into the wireless angle, however I doubt that is the cause for me.
Following dront78's example below is the output of "# hwinfo --partitions"
75: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: bdUI.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda1
Device Files: /dev/sda1, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part1, /dev/disk/by-id/wwn-0x6829766019904589826x-part1, /dev/disk/by-partuuid/77f1354c-3b20-454d-ba60-9dbab9bc8640, /dev/disk/by-uuid/ff387510-d0ad-498f-8d1b-576b26ed103e
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
76: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 2pkM.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda2
Device Files: /dev/sda2, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part2, /dev/disk/by-id/wwn-0x6829766019904589826x-part2, /dev/disk/by-partuuid/44596381-4cfe-4a2d-8e7b-f6427cc089d0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
77: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: W__Q.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda3
Device Files: /dev/sda3, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part3, /dev/disk/by-id/wwn-0x6829766019904589826x-part3, /dev/disk/by-partuuid/c9b404ec-f407-4081-a69c-9b10360d4cf7
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
78: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: z9FV.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda4
Device Files: /dev/sda4, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part4, /dev/disk/by-id/wwn-0x6829766019904589826x-part4, /dev/disk/by-partuuid/69c0972d-51ed-429c-acea-6e1afd7ebb1f
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
80: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: h4pj.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb1
Device Files: /dev/sdb1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part1, /dev/disk/by-id/wwn-0x17950130428369588225x-part1, /dev/disk/by-uuid/2c0f1039-2d4b-4f75-8fa4-529d19cd18fc
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
81: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 8G3o.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb2
Device Files: /dev/sdb2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part2, /dev/disk/by-id/wwn-0x17950130428369588225x-part2, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
82: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: bRJs.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb3
Device Files: /dev/sdb3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part3, /dev/disk/by-id/wwn-0x17950130428369588225x-part3, /dev/disk/by-label/old-raid1, /dev/disk/by-uuid/dfa989d8-edac-4c7e-b6fc-45237e6a0ebc
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
83: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 2dZw.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb4
Device Files: /dev/sdb4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part4, /dev/disk/by-id/wwn-0x17950130428369588225x-part4, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
85: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: mX79.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc1
Device Files: /dev/sdc1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part1, /dev/disk/by-id/wwn-0x4611505914592251905x-part1, /dev/disk/by-uuid/80780835-de4b-462c-b7f0-2b389d3e2c2f
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
86: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: DjND.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc2
Device Files: /dev/sdc2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part2, /dev/disk/by-id/wwn-0x4611505914592251905x-part2, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
87: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: gudH.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc3
Device Files: /dev/sdc3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part3, /dev/disk/by-id/wwn-0x4611505914592251905x-part3, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
88: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 74uL.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc4
Device Files: /dev/sdc4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part4, /dev/disk/by-id/wwn-0x4611505914592251905x-part4, /dev/disk/by-label/old-aroot, /dev/disk/by-uuid/b396dd50-e3f1-4b74-8cac-7d8d79a75386
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
90: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: r_Ra.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd1
Device Files: /dev/sdd1, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part1, /dev/disk/by-id/wwn-0x14865109125905272832x-part1, /dev/disk/by-partlabel/Microsoft\x20reserved\x20partition, /dev/disk/by-partuuid/f3e9ce24-988d-40ef-bd5c-6313c808bef2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
91: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: IAie.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd2
Device Files: /dev/sdd2, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part2, /dev/disk/by-id/wwn-0x14865109125905272832x-part2, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/f3344931-99c3-11e4-8601-806e6f6e6963, /dev/disk/by-uuid/30F403F0F403B75E
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
92: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: lLyi.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd3
Device Files: /dev/sdd3, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part3, /dev/disk/by-id/wwn-0x14865109125905272832x-part3, /dev/disk/by-partlabel/EFI\x20system\x20partition, /dev/disk/by-partuuid/ffbaa0cc-99c7-11e4-8625-806e6f6e6963, /dev/disk/by-uuid/0DE5-0CB0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
93: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: CXCn.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd4
Device Files: /dev/sdd4, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part4, /dev/disk/by-id/wwn-0x14865109125905272832x-part4, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/ffbaa0b6-99c7-11e4-8625-806e6f6e6963, /dev/disk/by-uuid/FE2648382647EFE7
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
94: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: fiSr.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd5
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd5
Device Files: /dev/sdd5, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part5, /dev/disk/by-id/wwn-0x14865109125905272832x-part5, /dev/disk/by-label/flbck, /dev/disk/by-partuuid/bd84f197-066e-4b9e-bf9b-b0b3a4090cde, /dev/disk/by-uuid/832bcc8d-836e-4b4e-8d9c-0a19f5bcf7dd
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
95: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 6uiv.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd6
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd6
Device Files: /dev/sdd6, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part6, /dev/disk/by-id/wwn-0x14865109125905272832x-part6, /dev/disk/by-partuuid/8f77bc79-ba57-462e-8beb-d09db5c77490
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
96: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: oKuO.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd7
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd7
Device Files: /dev/sdd7, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part7, /dev/disk/by-id/wwn-0x14865109125905272832x-part7, /dev/disk/by-partuuid/7ca3eb27-d198-4915-9c71-e96fa7a34d8b, /dev/disk/by-uuid/fd43f1bd-9f52-41b7-badc-4ab7881473ee
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
97: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: GW8T.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd8
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd8
Device Files: /dev/sdd8, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part8, /dev/disk/by-id/wwn-0x14865109125905272832x-part8, /dev/disk/by-partuuid/550f9e19-c0ec-4474-9e98-84c727854158
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
98: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: cPdt.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd10
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd10
Device Files: /dev/sdd10, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part10, /dev/disk/by-id/wwn-0x14865109125905272832x-part10, /dev/disk/by-label/bckup, /dev/disk/by-partuuid/de7eaa1e-66b0-4058-ad71-d0f8ea470b2f, /dev/disk/by-uuid/723d7788-8514-4777-8e07-e0faa48c9a83
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
100: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: wRm+.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde1
Device Files: /dev/sde1, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part1, /dev/disk/by-id/wwn-0x9832618751734861824x-part1, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
101: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: Nd04.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde2
Device Files: /dev/sde2, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part2, /dev/disk/by-id/wwn-0x9832618751734861824x-part2, /dev/disk/by-uuid/aa19d2cf-e59d-4277-a5e6-d0078ede6d3b
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
102: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: qoG8.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde3
Device Files: /dev/sde3, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part3, /dev/disk/by-id/wwn-0x9832618751734861824x-part3, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
103: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: H_WC.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde4
Device Files: /dev/sde4, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part4, /dev/disk/by-id/wwn-0x9832618751734861824x-part4
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
105: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: +u4R.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf1
Device Files: /dev/sdf1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part1, /dev/disk/by-id/wwn-0x8355873293896667137x-part1, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
106: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: S4LV.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf2
Device Files: /dev/sdf2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part2, /dev/disk/by-id/wwn-0x8355873293896667137x-part2, /dev/disk/by-uuid/96fa47c5-061d-4849-8582-7186cc1695d2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
107: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: vFbZ.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf3
Device Files: /dev/sdf3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part3, /dev/disk/by-id/wwn-0x8355873293896667137x-part3, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
108: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: NRrd.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf4
Device Files: /dev/sdf4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part4, /dev/disk/by-id/wwn-0x8355873293896667137x-part4, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
i don't have time to look at this in detail this morning, but I will this afternoon.
Thank you for all the replies. Have any of you found this to actually be damaging?
[edit] In an effort to not be completely lazy, and because I was curious, I did check a bit into netctl. Running "$ netctl list" returned exactly nothing. I have no profiles.
[edit2]
I just ran "$ dmesg -l err" on my laptop and I'm not getting any errors.
Last edited by nstgc (2015-04-27 15:09:46)

"Unable to find root device /dev/sda2"

Hi!
After an update - seemingly unsuccessfull - I get dropped into a recovery shell. The messages are:
/usr/lib/suspend/resume: /usr/lib/libpng14: version `PNG14_0`not found (required by /usr/lib/libsplshrender.so.1)
ERROR: unable to find root device '/dev/sda2'
I read that now I'm supposed to run a LiveCD and chroot something... can someone please be a little more specific here? I don't want to lose that system and I have no idea why it doesn't find my disk anymore. I just performed a pacman4 uprade, but it seems pacman4 is rather immature, leaving a system unuseable like that.
There is no sdaX in /dev any more. And I have very little experience with recovering Arch Linux. Until now
Best,
wishi

I have some wild problems here
1.) I used an Arch Live CD, did the chroot trick from the wiki (https://wiki.archlinux.org/index.php/Ch … nging_Root) and rebuild my initcpio (https://wiki.archlinux.org/index.php/Mkinitcpio). That ends successfull, and says it adds hooks for sata etc.
-> But I had to remove the udev hook: http://bbs.archbang.org/viewtopic.php?pid=11304 - I guess that's the reason why it still doesn't find my /dev/sda2 - I'm not sure this is related though.
2.) I ran pacman -Qk to ensure everything is sane. No errors. I reinstalled linux and udev two minutes ago. No change.
But I don't see how I can fix this. What's that voodoo with some udev hooks wandering around? The new kernel is 3.2.5-1 ARCH.

Arch Linux won't boot, "working on device dev/sda..."

Everytime I try to boot Arch there is a repeating message that pops up about every 3 seconds after the 'udev' events loads. My boot gets hung on the "working on device dev/sda6 (my linux partition on my laptop) and this message just keeps popping up every few seconds, repeatedly, non-stop:
ata1.00: exeption Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000008
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: emd 60/08/600:f1:69:51/00:00:16:00:00/40
ata1.00: tag 0 ncq 4096 in
ata1.00: status: {DRDY ERR}
ata1.00: error:{UNC}
and after 3 messages like the one above this message appears:
Ext4-fs error(device sda 6) __ext4_get_inod0 ...
I'm not sure if anyone could help me but I figured I would give it a shot. I might also mention that my HDD has been having tons of issues and has loads of bad sectors, I'm just saving up for a new one but for now I'm dealing with the one I have. My HDD also clicks when these messages start coming up.
Is there any way to fix this?

I might also mention that my HDD has been having tons of issues and has loads of bad sectors, I'm just saving up for a new one but for now I'm dealing with the one I have. My HDD also clicks when these messages start coming up.
LOL. That's like getting to the altar and saying to your soon-to-be-spouse "I might also mention that I'm sterile."
The ata1.00... are hardware errors. Probably drive problems, based on your belated exposition. If you haven't already run a bad sector reallocation tool, do so. The only other thing I would suggest is try the drive on another controller make sure it is only drive problems. I've seen issues on laptops that seemed to be fixed by a new drive, but the problems returned shortly after replacement.

No loopback devices (/dev/loop#)[solved]

Similar Messages

Maybe you are looking for