[SEMI-SOLVED; STILL CURIOUS] no more /dev/disk/by-uuid

I installed another Arch in a spare partition, reformatting sda2 and sda5 (swap). Since I use UUIDs in fstab, when I rebooted the previous installation in sda1 it failed to activate swap, since the UUID of that partition changed. Not a big deal: just update fstab and activate swap manually.
While doing this anyway I noticed that there was no more /dev/disk/by-uuid directory.
Is this normal or should I be concerned? Also, can someone explain how this directory is populated at boot time?
Thanks in advance for your help.
SOLUTION: a broken installation of util-linux-ng: for unknown (at least to me) reasons, blkid was missing. I reinstalled the package and restarted udev: it worked.
I'm still curious to know how come that i did boot my system without a /dev/disk/by-uuid directory, given the fact that both fstab and menu.lst use UUIDs.
Last edited by daneel971 (2009-09-02 17:16:22)

Hello Daneel971!
What's the output of 'blkid' command ?

Similar Messages

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

[solved] cryptkey /dev/disk/by-uuid doesn't work - udev does?!

Hello,
I have a cryptkey="/dev/disk/by-uuid/...:start:offset" option in my grub.cfg
This one doesnt work (no keyfile found).
But when I create a udev-rule which makes the device appear as /dev/foo (and add it to mkinitcpio.conf), the following works:
cryptkey="/dev/foo:start:offset"
on the other side, cryptdevice="/dev/disk/by-uuid/..." works fine.
So why can't I use the first option but have to setup this rule instead?
Or did I forget something?
Last edited by weltio (2013-05-30 19:29:07)

Oh - no iam just retarded. The device /dev/sdb doenst have a uuid... of course not. So i guess the udev solution is the only possible one.

Flash [?] drive not appearing in /dev/disk/by-uuid

I'm not sure if "flash drive" is the correct term or not ... the filesystem I want to mount is on a Sansa c240 MP3 player (a refurbished unit I bought last week), which connects via USB. Now, I *can* mount the drive, and have been able to all along, but I would like to add a line in /etc/fstab, using the device name from /dev/disk/by-uuid, so I can mount the thing conveniently under my regular username. But the device is not listed in /dev/disk/by-uuid (I've checked many times over the last couple of days).
That's not how it started, though. When I first brought the thing home and plugged it in, it did appear in /dev/disk-by-uuid. But I ran into some difficulties, and in the course of trying to make the player play nice with Linux, I formatted the drive once or twice using the player's internal command--still no problem as long as I did that. But then, following somebody's recommendation, I ran mkfs.vfat on the partition under Linux ... and that seems to have coincided with the device's disappearing from /dev/disk/by-uuid.
Now, I gather that USB flash drives and such don't always have UUIDs, but this one apparently does:
# blkid /dev/sdc1
/dev/sdc1: LABEL="Sansa c240" UUID="CC07-5165" TYPE="vfat"
And, as you can see, the partition is definitely visible, and I can mount it as /dev/sd*1, and copy files to it. It also has an entry under /dev/disk/by-id, just not under /dev/disk/by-uuid. Any ideas why that might be, or what I can do about it?
TIA for any tips.

Sorry for the necrobumping..but I have the same problem on a headless server running the 2.6.31 kernel, and not just with flashdrives but any usb storage: I see the uuid with blkid, yet they don't show up in /dev/disk/by-uuid/ . I can mount them with /dev/sd[a-z][0-9] but I rather use uuids in my mount-scripts. Is there any solution other than making the symlinks in /dev/desk/by-uuid myself?
<edit>
solved it myself:
The cause was 'OPTIONS="last_rule"' that I added to some lines in a udev-rule file I made in /udev/rules.d/ for automounting usb drives based on the ones here: http://wiki.archlinux.org/index.php/Ude … SB_devices. After removing those parts both my udev rule gets executed and the links in /dev/disk/by-uuid are created when inserting a usb drive.
</edit?
Last edited by rwd (2010-01-20 21:37:23)

[Solved] Can't boot; udev not creating /dev/disk/

After doing a system upgrade I can no longer boot. I get the message that /dev/disk/by-uuid/{device id} cannot be found. (There is no /dev/disk/ path at all). I tried changing the grub boot path to dev/sdaX, but /dev/sda?? are also not created.
I have a Fedora rescue CD lying around, and if I boot from that I can see and mount the boot device (/dev/disk/by-uuid/ is created), so I don't think it's a hardware issue.
Last edited by rhodie (2012-03-20 18:26:53)

Booting from a NetInstaller CD worked.
A couple of notes in case others have the same issue.
I had to turn on networking before I could run pacman. I turned on networking by issuing these commands (not sure of the proper order for them or if they're all necessary, but it worked):
/etc/rc.d/networking start
ip link set eth0 up
dhcpd
I then ran through the steps listed at https://wiki.archlinux.org/index.php/Pa … nger_boot. , but I got errors on "mkinitcpio -p linux" so I added "pacman -S linux," which seemed to include mkinitcpio, but I ran mkinitcpio again afterwards just to be sure and got no errors.
Last edited by rhodie (2012-03-20 16:09:20)

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)

Disk by uuid

In Grub, the root device is specified by UUID, example:
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/8def79a8-3257-4412-a9d3-fe95a55fcb06 ro
After I built my custom kernel, which doesn't need an initrd, booting using UUIDs no longer worked (I got a kernel panic saying that it could not mount the root fs). Using the traditional /dev/sdX way works fine however.
Please can someone verify that the usage of UUIDs is only necessary when using an initrd (because the initrd might change the /dev/sdX naming)? If it's not, then in what way do I need to change my kernel config so it can handle UUIDs?
Thanks!
Last edited by roog (2008-08-13 05:42:53)

roog wrote:Please can someone verify that the usage of UUIDs is only necessary when using an initrd (because the initrd might change the /dev/sdX naming)? If it's not, then in what way do I need to change my kernel config so it can handle UUIDs?
The need for uuids is because they are a naming system that almost guarantees that that uuid belongs to that partition: if you reformat that partition, then you can't boot the new partition using a uuid, since that isn't the same partition. /dev/sdx naming would try to boot the new one.
That is more an issue if you have multiple disks and switch them, or if you have two hdd controllers whose modules cannot be loaded in a predefined order (people see this more often with which network device is eth0, which is eth1), or if the driver changes between releases to call a disk /dev/sda instead of /dev/hda, or some other scheme.
In any case it is a more robust system to use uuids, but the other way works too!
The code that goes into the ata_piix might have some info, though something might pop up when you run diff (vimdiff?) on your config and arch's config.

Persistend device in disk/by-path disk/by-uuid but no in disk/by-id

I have a cell phone with embedded memory and a memory slot with Memory Stick Micro (M2).
Embedded memory is 'connected' as sdb and MemoryStick as sdc.
Both of them appear in /dev/disk/by-path/ and in /dev/disk/by-uuid/.
But not in /dev/disk/by-id/ which would be most suitable for me.
$ ls -l /dev/disk/by-path/
razem 0
lrwxrwxrwx 1 root root 9 mar 15 11:48 pci-0000:00:1a.1-usb-0:1:2.0-scsi-0:0:0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 mar 15 11:48 pci-0000:00:1a.1-usb-0:1:2.0-scsi-0:0:0:0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 mar 15 11:48 pci-0000:00:1a.1-usb-0:1:2.1-scsi-0:0:0:0 -> ../../sdc
lrwxrwxrwx 1 root root 10 mar 15 11:48 pci-0000:00:1a.1-usb-0:1:2.1-scsi-0:0:0:0-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 9 mar 15 11:06 pci-0000:00:1f.1-scsi-0:0:0:0 -> ../../sr0
lrwxrwxrwx 1 root root 9 mar 15 11:06 pci-0000:00:1f.2-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 mar 15 11:06 pci-0000:00:1f.2-scsi-0:0:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 mar 15 11:06 pci-0000:00:1f.2-scsi-0:0:0:0-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 mar 15 11:06 pci-0000:00:1f.2-scsi-0:0:0:0-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 mar 15 11:06 pci-0000:00:1f.2-scsi-0:0:0:0-part5 -> ../../sda5
$ ls -l /dev/disk/by-uuid/
razem 0
lrwxrwxrwx 1 root root 10 mar 15 11:06 23d20d55-e010-4680-b053-a66dad672300 -> ../../sda5
lrwxrwxrwx 1 root root 10 mar 15 11:06 26e3884c-f201-48e7-9ea1-fd65850bb5f0 -> ../../sda2
lrwxrwxrwx 1 root root 10 mar 15 11:48 47DB-B750 -> ../../sdc1
lrwxrwxrwx 1 root root 10 mar 15 11:48 47DB-B75E -> ../../sdb1
lrwxrwxrwx 1 root root 10 mar 15 11:06 be4c9325-fbd8-4fc3-813f-e02e351e57c6 -> ../../sda1
$ ls -l /dev/disk/by-id/
razem 0
lrwxrwxrwx 1 root root 9 mar 15 11:06 ata-ST9120822AS_5MA6SN5A -> ../../sda
lrwxrwxrwx 1 root root 10 mar 15 11:06 ata-ST9120822AS_5MA6SN5A-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 mar 15 11:06 ata-ST9120822AS_5MA6SN5A-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 mar 15 11:06 ata-ST9120822AS_5MA6SN5A-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 mar 15 11:06 ata-ST9120822AS_5MA6SN5A-part5 -> ../../sda5
lrwxrwxrwx 1 root root 9 mar 15 11:06 scsi-SATA_ST9120822AS_5MA6SN5A -> ../../sda
lrwxrwxrwx 1 root root 10 mar 15 11:06 scsi-SATA_ST9120822AS_5MA6SN5A-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 mar 15 11:06 scsi-SATA_ST9120822AS_5MA6SN5A-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 mar 15 11:06 scsi-SATA_ST9120822AS_5MA6SN5A-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 mar 15 11:06 scsi-SATA_ST9120822AS_5MA6SN5A-part5 -> ../../sda5
lrwxrwxrwx 1 root root 9 mar 15 11:48 usb-Sony_Eri_Memory_Stick_3590870185708570-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 mar 15 11:48 usb-Sony_Eri_Memory_Stick_3590870185708570-0:0-part1 -> ../../sdb1
EDIT:
when I replug the device the disk/by-uuid directory looks like this:
$ ls -l /dev/disk/by-uuid/
razem 0
lrwxrwxrwx 1 root root 10 mar 15 11:06 23d20d55-e010-4680-b053-a66dad672300 -> ../../sda5
lrwxrwxrwx 1 root root 10 mar 15 11:06 26e3884c-f201-48e7-9ea1-fd65850bb5f0 -> ../../sda2
lrwxrwxrwx 1 root root 10 mar 15 12:22 47DB-BF3C -> ../../sdc1
lrwxrwxrwx 1 root root 10 mar 15 12:22 47DB-BF64 -> ../../sdb1
lrwxrwxrwx 1 root root 10 mar 15 11:06 be4c9325-fbd8-4fc3-813f-e02e351e57c6 -> ../../sda1
Both sdb1 and sdc1 changed it's name
Last edited by MAC!EK (2008-03-15 11:26:46)

when you insert a device, it gets a device name,. i.e sd[a,b,...][1,2,...];
this is an automatic name dependent on the order of insertion/detection.
a fs / disk label, is embeded into the partiton's filesystem, so when you insert the device, it can be detected and the device is avaialble
by that name under /dev/disk/by-label
e.g
e2label /dev/sda13 ZeroSpace
would result in /dev/disk/by-label/ZeroSpace when the device is inserted.
so you can mount it by that name every time, instead of having to figure out where the device
-node(sda13) actually is

[Solved] Can't Import ZFS Pool as /dev/disk/by-id

I have a 4 disk raidz1 pool "data" made up of 3TB disks. Each disk is so that that partition 1 is a 2GB swap partition, and partition 2 is the rest of the drive. The zpool was built out of /dev/disk/by-id(s) pointing to the second partition.
# lsblk -i
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 2.7T 0 disk
|-sda1 8:1 0 2G 0 part
`-sda2 8:2 0 2.7T 0 part
sdb 8:16 0 2.7T 0 disk
|-sdb1 8:17 0 2G 0 part
`-sdb2 8:18 0 2.7T 0 part
sdc 8:32 0 2.7T 0 disk
|-sdc1 8:33 0 2G 0 part
`-sdc2 8:34 0 2.7T 0 part
sdd 8:48 0 2.7T 0 disk
|-sdd1 8:49 0 2G 0 part
`-sdd2 8:50 0 2.7T 0 part
sde 8:64 1 14.9G 0 disk
|-sde1 8:65 1 100M 0 part /boot
`-sde2 8:66 1 3G 0 part /
I had a strange disk failure where the controller one one of the drives flaked out and caused my zpool not to come online after a reboot, and I had to zpool export data/zpool import data to get the zpool put back together. However, now it is fixed, but my drives are now identified by their device name:
[root@osiris disk]# zpool status
pool: data
state: ONLINE
scan: resilvered 36K in 0h0m with 0 errors on Wed Aug 13 22:37:19 2014
config:
NAME STATE READ WRITE CKSUM
data ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
sda2 ONLINE 0 0 0
sdb2 ONLINE 0 0 0
sdc2 ONLINE 0 0 0
sdd2 ONLINE 0 0 0
errors: No known data errors
If I try to import by-id without a zpool name, I get this (its trying to import the disks, not the partitions):
cannot import 'data': one or more devices is currently unavailable
[root@osiris disk]# zpool import -d /dev/disk/by-id/
pool: data
id: 16401462993758165592
state: FAULTED
status: One or more devices contains corrupted data.
action: The pool cannot be imported due to damaged devices or data.
see: http://zfsonlinux.org/msg/ZFS-8000-5E
config:
data FAULTED corrupted data
raidz1-0 ONLINE
ata-ST3000DM001-1CH166_Z1F28ZJX UNAVAIL corrupted data
ata-ST3000DM001-1CH166_Z1F0XAXV UNAVAIL corrupted data
ata-ST3000DM001-1CH166_Z1F108YC UNAVAIL corrupted data
ata-ST3000DM001-1CH166_Z1F12FJZ UNAVAIL corrupted data
[root@osiris disk]# zpool status
no pools available
... and the import doesn't succeed.
If I put the pool name at the end, I get:
[root@osiris disk]# zpool import -d /dev/disk/by-id/ data
cannot import 'data': one or more devices is currently unavailable
Yet, if I do the same thing with the /dev/disk/by-partuuid paths, it seems to work fine (other than the fact that I don't want partuuids). Presumably because there are no entries here for entire disks.
[root@osiris disk]# zpool import -d /dev/disk/by-partuuid/ data
[root@osiris disk]# zpool status
pool: data
state: ONLINE
scan: resilvered 36K in 0h0m with 0 errors on Wed Aug 13 22:37:19 2014
config:
NAME STATE READ WRITE CKSUM
data ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
d8bd1ef5-fab9-4d47-8d30-a031de9cd368 ONLINE 0 0 0
fbe63a02-0976-42ed-8ecb-10f1506625f6 ONLINE 0 0 0
3d1c9279-0708-475d-aa0c-545c98408117 ONLINE 0 0 0
a2d9067c-85b9-45ea-8a23-350123211140 ONLINE 0 0 0
errors: No known data errors
As another approach, I tried to offline and replace sda2 with /dev/disk/by-id/ata-ST3000DM001-1CH166_Z1F28ZJX-part2, but that doesn't work either:
[root@osiris disk]# zpool offline data sda2
[root@osiris disk]# zpool status
pool: data
state: DEGRADED
status: One or more devices has been taken offline by the administrator.
Sufficient replicas exist for the pool to continue functioning in a
degraded state.
action: Online the device using 'zpool online' or replace the device with
'zpool replace'.
scan: resilvered 36K in 0h0m with 0 errors on Wed Aug 13 22:37:19 2014
config:
NAME STATE READ WRITE CKSUM
data DEGRADED 0 0 0
raidz1-0 DEGRADED 0 0 0
sda2 OFFLINE 0 0 0
sdb2 ONLINE 0 0 0
sdc2 ONLINE 0 0 0
sdd2 ONLINE 0 0 0
errors: No known data errors
[root@osiris disk]# zpool replace data sda2 /dev/disk/by-id/ata-ST3000DM001-1CH166_Z1F28ZJX-part2
invalid vdev specification
use '-f' to override the following errors:
/dev/disk/by-id/ata-ST3000DM001-1CH166_Z1F28ZJX-part2 is part of active pool 'data'
[root@osiris disk]# zpool replace -f data sda2 /dev/disk/by-id/ata-ST3000DM001-1CH166_Z1F28ZJX-part2
invalid vdev specification
the following errors must be manually repaired:
/dev/disk/by-id/ata-ST3000DM001-1CH166_Z1F28ZJX-part2 is part of active pool 'data'
I would appreciate if anyone else had any suggestions/workarounds on how to fix this
As I was typing this up, I stumbled upon a solution by deleting the symlinks that pointed to entire devices in /dev/disk/by-id (ata-* and wwn*). I then was able to do a zpool import -d /dev/disk/by-id data and it pulled in the partition 2's. It persisted after a reboot and my symlinks were automatically regenerated when the system came back up:
[root@osiris server]# zpool status
pool: data
state: ONLINE
scan: resilvered 36K in 0h0m with 0 errors on Wed Aug 13 23:06:46 2014
config:
NAME STATE READ WRITE CKSUM
data ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
ata-ST3000DM001-1CH166_Z1F28ZJX-part2 ONLINE 0 0 0
ata-ST3000DM001-1CH166_Z1F0XAXV-part2 ONLINE 0 0 0
ata-ST3000DM001-1CH166_Z1F108YC-part2 ONLINE 0 0 0
ata-ST3000DM001-1CH166_Z1F12FJZ-part2 ONLINE 0 0 0
It would appear to be an issue with specifically importing non-whole devices by-id. Although this was mainly rambling and no longer a question, hopefully this might help someone having issues re-importing a zpool by /dev/disk/by-id.
Matt

This just saved my morning Thank you!
I was using Ubuntu 14.04 and after an upgrade to 3.13.0-43-generic it somehow broke... Anyhow now the zpool survives restarts again and I don't have to import it every time using partuuids.

[semi-solved] dell xps 12 touchscreen not working (2013, 12-9Q33)

does anyone know how to get the touch screen working the dell xps 12?
ran windows on it for a few days and there did not appear to be any hardware issues with touchscreen (or anything else).
deleted all windows partitions and installed arch + kde with no issues, boots and runs great. but no response from the touch screen.
have tried to cat every /dev/input/event* but get nothing when tapping touch screen.
beleve it uses an atmel maxtouch digitizer... which i think should be picked up by udev... but dont think udev even sees the device, it just detetcs boring old mouse.
this looks like a simmilar issue with ubuntu https://bugs.launchpad.net/ubuntu/+sour … ug/1218973 but on my system there is no indication that it is an i2c device.
tried atmel kernel but still no action https://git.kernel.org/cgit/linux/kerne … mel-mxt-ts
lsusb
Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:09fa Intel Corp.
Bus 001 Device 003: ID 0bda:5716 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 8087:07dc Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
input
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ Integrated Webcam id=9 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
↳ Dell WMI hotkeys id=12 [slave keyboard (3)]
sudo cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input0
U: Uniq=
H: Handlers=sysrq kbd event0
B: PROP=0
B: EV=120013
B: KEY=1100f02902000 8380307cf910f001 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2
U: Uniq=
H: Handlers=event2
B: PROP=0
B: EV=21
B: SW=1
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
U: Uniq=
H: Handlers=kbd event3
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0001 Vendor=10ec Product=0668 Version=0001
N: Name="HDA Digital PCBeep"
P: Phys=card1/codec#0/beep0
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/input/input4
U: Uniq=
H: Handlers=kbd event4
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card1/input5
U: Uniq=
H: Handlers=event5
B: PROP=0
B: EV=21
B: SW=4
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input6
U: Uniq=
H: Handlers=kbd event6
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Dell WMI hotkeys"
P: Phys=wmi/input0
S: Sysfs=/devices/virtual/input/input7
U: Uniq=
H: Handlers=kbd rfkill event7
B: PROP=0
B: EV=13
B: KEY=1500b00000000 200300000 0 0
B: MSC=10
I: Bus=0003 Vendor=0bda Product=5716 Version=3204
N: Name="Integrated Webcam"
P: Phys=usb-0000:00:14.0-5/button
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input8
U: Uniq=
H: Handlers=kbd event8
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input9
U: Uniq=
H: Handlers=mouse0 event9
B: PROP=5
B: EV=b
B: KEY=e520 610000 0 0 0 0
B: ABS=660800011000003
I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input10
U: Uniq=
H: Handlers=kbd event10
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel MID HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input11
U: Uniq=
H: Handlers=event11
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel MID HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input12
U: Uniq=
H: Handlers=event12
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel MID HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input13
U: Uniq=
H: Handlers=event13
B: PROP=0
B: EV=21
B: SW=140
sudo dmidecode
[sudo] password for gamera:
# dmidecode 2.12
# SMBIOS entry point at 0x000f04c0
SMBIOS 2.7 present.
56 structures occupying 2720 bytes.
Table at 0x000EBA70.
Handle 0xDA00, DMI type 218, 251 bytes
OEM-specific Type
Header and Data:
DA FB 00 DA B2 00 0D 5F 0F 37 40 7D 00 00 00 00
00 7E 00 01 00 00 00 75 01 01 80 01 00 76 01 02
80 01 00 4F 02 05 80 01 00 50 02 06 80 00 00 A5
02 02 00 00 00 A6 02 02 00 01 00 9C 00 03 00 01
00 9B 00 03 00 00 00 8A 01 04 00 01 00 89 01 04
00 00 00 7F 01 05 00 00 00 80 01 05 00 01 00 53
01 06 00 00 00 52 01 06 00 01 00 7B 01 07 00 00
00 7C 01 07 00 01 00 94 01 08 00 00 00 93 01 08
00 01 00 7D 00 09 00 00 00 2D 00 0A 00 01 00 2E
00 0A 00 00 00 6E 00 0B 00 00 00 95 00 0C 00 01
00 96 00 0C 00 00 00 2F 02 0D 00 01 00 30 02 0D
00 00 00 50 02 0E 00 00 00 51 02 0E 00 01 00 52
02 0E 00 02 00 53 02 0E 00 03 00 54 02 0E 00 04
00 56 02 0E 00 05 00 F0 00 5D 80 01 00 ED 00 5E
80 01 00 4B 01 5F 80 01 00 4A 01 60 80 01 00 EA
00 0F 00 01 00 FF FF 00 00 00 00
Handle 0xDA01, DMI type 218, 251 bytes
OEM-specific Type
Header and Data:
DA FB 01 DA B2 00 0D 5F 0F 37 40 EB 00 0F 00 00
00 37 01 61 80 01 00 38 01 62 80 01 00 39 01 63
80 01 00 3D 03 66 80 01 00 3E 03 67 80 01 00 2E
02 07 80 01 00 2D 02 08 80 01 00 4F 03 09 80 01
00 50 03 0A 80 01 00 0E 01 64 80 01 00 0F 01 65
80 01 00 47 01 68 80 01 00 46 01 69 80 01 00 36
02 17 80 01 00 35 02 18 80 01 00 36 03 19 80 01
00 37 03 1A 80 01 00 3A 03 1B 80 01 00 3B 03 1C
80 01 00 41 03 1D 80 01 00 42 03 1E 80 01 00 43
03 1F 80 01 00 44 03 20 80 01 00 45 03 21 80 01
00 46 03 22 80 01 00 47 03 23 80 01 00 4B 03 24
80 01 00 4C 03 25 80 01 00 4A 02 0B 80 01 00 26
03 0C 80 01 00 5B 03 0D 80 01 00 5C 03 0E 80 01
00 5D 03 0F 80 01 00 5E 03 10 80 01 00 5F 03 11
80 01 00 60 03 12 80 01 00 0C 80 13 80 01 00 04
A0 14 80 01 00 FF FF 00 00 00 00
Handle 0xDA02, DMI type 218, 29 bytes
OEM-specific Type
Header and Data:
DA 1D 02 DA B2 00 0D 5F 0F 37 40 44 01 15 80 01
00 45 01 16 80 01 00 FF FF 00 00 00 00
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: A02
Release Date: 07/26/2013
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 2048 kB
Characteristics:
MCA is supported
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 0.2
Firmware Revision: 0.2
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Dell Inc.
Product Name: XPS 12-9Q33
Version: A02
Serial Number: FZS4SY1
UUID: 4C4C4544-005A-5310-8034-C6C04F535931
Wake-up Type: Power Switch
SKU Number: XPS 12-9Q33
Family:
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: Dell Inc.
Product Name: XPS 12-9Q33
Version: A02
Serial Number: .FZS4SY1.CN1296139P0049.
Asset Tag: Not Specified
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: To Be Filled By O.E.M.
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
Manufacturer: Dell Inc.
Type: Portable
Lock: Not Present
Version: Not Specified
Serial Number: FZS4SY1
Asset Tag: Not Specified
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000000
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 0
SKU Number: To be filled by O.E.M.
Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: PS2Mouse
External Connector Type: PS/2
Port Type: Mouse Port
Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1A1
Internal Connector Type: None
External Reference Designator: Keyboard
External Connector Type: PS/2
Port Type: Keyboard Port
Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A1
Internal Connector Type: None
External Reference Designator: TV Out
External Connector Type: Mini Centronics Type-14
Port Type: Other
Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A2A
Internal Connector Type: None
External Reference Designator: COM A
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2A2B
Internal Connector Type: None
External Reference Designator: Video
External Connector Type: DB-15 female
Port Type: Video Port
Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External Reference Designator: USB1
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External Reference Designator: USB2
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3A1
Internal Connector Type: None
External Reference Designator: USB3
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9A1 - TPM HDR
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9C1 - PCIE DOCKING CONN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J2B3 - CPU FAN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J6C2 - EXT HDMI
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J3C1 - GMCH FAN
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0015, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J1D1 - ITP
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0016, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9E2 - MDC INTPSR
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0017, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: J9E4 - MDC INTPSR
Internal Connector Type: Other
External Reference Designator: Not Specified
External Connector Type: None
Port Type: Other
Handle 0x0018, DMI type 9, 17 bytes
System Slot Information
Designation: J6B2
Type: x16 PCI Express
Current Usage: In Use
Length: Long
ID: 0
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:00:01.0
Handle 0x0019, DMI type 9, 17 bytes
System Slot Information
Designation: J6B1
Type: x1 PCI Express
Current Usage: In Use
Length: Short
ID: 1
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:00:1c.3
Handle 0x001A, DMI type 10, 6 bytes
On Board Device Information
Type: Video
Status: Enabled
Description: Mobile Intel HD Graphics
Handle 0x001B, DMI type 11, 5 bytes
OEM Strings
String 1: Dell System
String 2: 1[05E3h]
String 3: 3[1.0]
String 4: 4[0001]
String 5: 5[0000]
String 6: 6[D0, D4, D8, DA, DE]
String 7: 7[]
String 8: 8[]
String 9: 9[]
String 10: 10[A02]
String 11: 11[]
String 12: 12[]
String 13: 13[P20S]
String 14: 14[0]
String 15: 15[0]
Handle 0x001C, DMI type 12, 5 bytes
System Configuration Options
Option 1: To Be Filled By O.E.M.
Handle 0x001D, DMI type 21, 7 bytes
Built-in Pointing Device
Type: Touch Pad
Interface: Bus Mouse
Buttons: 2
Handle 0x001E, DMI type 22, 26 bytes
Portable Battery
Location: System Battery
Manufacturer: SDI
Manufacture Date: Not Specified
Serial Number: Not Specified
Name: DELL 7YM0739
Chemistry: Lithium Ion
Design Capacity: 51060 mWh
Design Voltage: 7400 mV
SBDS Version: 1.0
Maximum Error: 100%
OEM-specific Information: 0x00000001
Handle 0x001F, DMI type 32, 20 bytes
System Boot Information
Status: No errors detected
Handle 0x0021, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x00000000
Handle 0x0022, DMI type 28, 20 bytes
Temperature Probe
Description: CPU Internal Temperature
Location: Processor
Status: OK
Maximum Value: 127.0 deg C
Minimum Value: 0.0 deg C
Resolution: 1.000 deg C
Tolerance: 0.5 deg C
Accuracy: Unknown
OEM-specific Information: 0x00000000
Handle 0xB000, DMI type 176, 10 bytes
OEM-specific Type
Header and Data:
B0 0A 00 B0 00 00 00 00 E3 05
Handle 0xB100, DMI type 177, 12 bytes
OEM-specific Type
Header and Data:
B1 0C 00 B1 1A 06 00 00 00 00 00 00
Handle 0x0025, DMI type 208, 12 bytes
OEM-specific Type
Header and Data:
D0 0C 25 00 02 05 FE 00 E3 05 01 02
Strings:
20130614
20130924
Handle 0x0026, DMI type 212, 57 bytes
OEM-specific Type
Header and Data:
D4 39 26 00 70 00 71 00 01 49 50 48 9C 00 49 FC
01 9B 00 49 FC 00 7F 01 4A FB 04 80 01 4A FB 00
53 01 4A F7 08 52 01 4A F7 08 7B 01 4A EF 10 7C
01 4A EF 10 FF FF 00 00 00
Handle 0x0027, DMI type 216, 9 bytes
OEM-specific Type
Header and Data:
D8 09 27 00 01 02 01 00 00
Strings:
INTEL
0000
Handle 0x0028, DMI type 217, 8 bytes
OEM-specific Type
Header and Data:
D9 08 28 00 01 02 00 00
Strings:
Handle 0x0029, DMI type 219, 11 bytes
OEM-specific Type
Header and Data:
DB 0B 29 00 00 01 02 03 00 04 05
Strings:
Handle 0x002A, DMI type 220, 22 bytes
OEM-specific Type
Header and Data:
DC 16 2A 00 01 F0 00 00 02 F0 00 00 00 00 03 F0
04 F0 00 00 00 00
Handle 0x002B, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 2B 00 00 00 00 00 00 03 00 00 00 00 00 00
00 00 00
Handle 0x002C, DMI type 222, 16 bytes
OEM-specific Type
Header and Data:
DE 10 2C 00 01 08 FF FF 00 00 00 00 00 00 00 00
Handle 0x002D, DMI type 4, 42 bytes
Processor Information
Socket Designation: SOCKET 0
Type: Central Processor
Family: Core i5
Manufacturer: Intel
ID: 51 06 04 00 FF FB EB BF
Signature: Type 0, Family 6, Model 69, Stepping 1
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz
Voltage: 1.2 V
External Clock: 100 MHz
Max Speed: 3800 MHz
Current Speed: 1600 MHz
Status: Populated, Enabled
Upgrade: Socket rPGA988B
L1 Cache Handle: 0x0004
L2 Cache Handle: 0x0005
L3 Cache Handle: 0x0006
Serial Number: Not Specified
Asset Tag: Fill By OEM
Part Number: Fill By OEM
Core Count: 2
Core Enabled: 2
Thread Count: 4
Characteristics:
64-bit capable
Handle 0x0004, DMI type 7, 19 bytes
Cache Information
Socket Designation: CPU Internal L1
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 128 kB
Maximum Size: 128 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Other
Associativity: 8-way Set-associative
Handle 0x0005, DMI type 7, 19 bytes
Cache Information
Socket Designation: CPU Internal L2
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Back
Location: Internal
Installed Size: 512 kB
Maximum Size: 512 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 8-way Set-associative
Handle 0x0006, DMI type 7, 19 bytes
Cache Information
Socket Designation: CPU Internal L3
Configuration: Enabled, Not Socketed, Level 3
Operational Mode: Write Back
Location: Internal
Installed Size: 3072 kB
Maximum Size: 3072 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: 12-way Set-associative
Handle 0x0007, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 16 GB
Error Information Handle: Not Provided
Number Of Devices: 2
Handle 0x0020, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x0007
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 2048 MB
Form Factor: SODIMM
Set: None
Locator: ChannelA-DIMM0
Bank Locator: BANK 0
Type: DDR3
Type Detail: Synchronous
Speed: 1600 MHz
Manufacturer: Hynix/Hyundai
Serial Number: 00000001
Asset Tag: 0987654321
Part Number:
Rank: 1
Configured Clock Speed: 1600 MHz
Handle 0x0023, DMI type 20, 35 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x0020
Memory Array Mapped Address Handle: 0x002F
Partition Row Position: 2
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x0024, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x0007
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 2048 MB
Form Factor: SODIMM
Set: None
Locator: ChannelB-DIMM0
Bank Locator: BANK 2
Type: DDR3
Type Detail: Synchronous
Speed: 1600 MHz
Manufacturer: Hynix/Hyundai
Serial Number: 00000002
Asset Tag: 0987654321
Part Number:
Rank: 1
Configured Clock Speed: 1600 MHz
Handle 0x002E, DMI type 20, 35 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FFFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x0024
Memory Array Mapped Address Handle: 0x002F
Partition Row Position: 2
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x002F, DMI type 19, 31 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FFFFFFFF
Range Size: 4 GB
Physical Array Handle: 0x0007
Partition Width: 2
Handle 0x0037, DMI type 131, 64 bytes
OEM-specific Type
Header and Data:
83 40 37 00 31 00 00 00 00 00 00 00 00 00 00 00
F8 00 43 9C 00 00 00 00 01 20 00 00 05 00 09 00
D1 05 02 00 00 00 00 00 C8 00 FF FF 00 00 00 00
00 00 00 00 26 00 00 00 76 50 72 6F 00 00 00 00
Handle 0x0038, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1
Handle 0x0039, DMI type 127, 4 bytes
End Of Table
Last edited by fungi (2013-10-13 10:31:45)

Semi solved the problem by building a kernel with an ubuntu .config from http://kernel.ubuntu.com/~kernel-ppa/ma … y/current/
I think i have multi touch working on the touchscreen, but this has resulted in breakage of the synapic touchpad which is now operating in a very simple mode (no scrolling or multitouch).
Probably best to follow https://bugs.launchpad.net/ubuntu/+sour … ug/1218973 and http://thread.gmane.org/gmane.linux.kernel.input/32207 for a real solution

[Solved] Persistent Device Naming for Full Disk Encryption & USB Boot

Using the following boot option does not work while using FDE (dm-crypt plain) due to the filesystem being unreachable until decryption.
cryptdevuce=UUID=xxxx-xxxx:root
sda
└ root /
sdb
└ sdb1 /boot
This forces the use of /dev/sda for booting, but occasionally a USB device is mapped to sda instead.
Is there a way to use Persistent Block Device Naming for this type of FDE?
Last edited by easton741 (2015-02-05 01:42:57)

MSC wrote:What exactly is not working? It shouldn't matter if the USB device maps to /dev/sda because the partition with that UUID still resides on the same disk.
I guess I should be more clear. The entire sda device is encrypted. This meas that during the initialization there is no UUID is read from the disk because the filesystem cannot be read until it is unencrypted.
This leaves me in a catch 22 where I cannot use UUID until the device is unencrypted, but I need UUID to boot & decrypt the device properly. Here is an example of what the computer sees in the Arch Install.
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
sdb iso9660 ARCH_201501 2015-01-01-09-54-22-00
├─sdb1 iso9660 ARCH_201501 2015-01-01-09-54-22-00 /run/archiso/bootmnt
└─sdb2 vfat ARCHISO_EFI 9051-9287
sdc
└─sdc1 vfat 4EC5-5B7D (normally /boot)
As you can see, sda has no uuid.
So I guess what I'm asking is if there is any alternative method because it does not look like I can use anything in the wiki.

[SEMI-SOLVED] MonoDevelop fonts are invisible in XMonad

A MonoDevelop project open in the XMonad tiling window manager:
The same MonoDevelop project is shown, but this time I opened it in the MATE Desktop Environment:
Any idea what might be causing the fonts to “disappear” in XMonad?
Note that the text is actually there in XMonad: in MonoDevelop’s editor, I can do CTRL+A CTRL+C and then paste in e.g. LeafPad and see that the text does exist, it is just misteriously invisible.
I would really like to solve this since I want to use XMonad as my everyday environment.
Last edited by Montague (2014-02-14 18:19:33)

Well this issue is semi-solved, but honestly I do not know what fixed it.
I wish I had a specific fix to share in case someone else encouters the same issue, but for the record here is what I tried, in no particular order.
(The two last points probably have nothing to do with the problem I was having, as they relate to how Java programs behave in tiling WM, but as I said, I have no clue what fixed my invisible fonts in MonoDevelop (in XMonad), so I’ll just dump everything I did in that list…) :
installed ttf-ms-fonts from the AUR
installed a few themes from the AUR, i.e. adwaita-x-dark-and-light-theme and a few others
removed `wmname LG3D' from my `~/.xinitrc'
uncommented export _JAVA_AWT_WM_NONREPARENTING=1 in `/etc/profile.d/jre.sh'
I think that’s it.
P.S. : however, fonts are still invisible on some tabs in MonoDevelop, but that problem happens in both XMonad and MATE, so I marked this as [SEMI-SOLVED]. Any input appreciated !
XMonad :
MATE :
Last edited by Montague (2014-02-14 18:07:02)

In PSE will I use more hard-disk space by using iPhoto plus Organizer for photos?

I have PSE 10 on my MAC. I normally download my photos onto iPhoto (and a while ago, onto Bridge CS3 which came with an earlier version of PSE) but more recently have become interested in using the PSE Organizer for my photo library. I have started to transfer/copy the photos from iPhoto but, having read various topics on organizing photos, am a little worried that by having the photos in 2/3 places on the MAC I will use much more hard-disk space. I know that the original files for iPhoto are in the 'Library' so that I just see thumbnails on iPhoto ( I may be wrong here?), but will the photos I now have on Organizer be working off those same 'Library' originals or am I doubling up on the space required to store these photos?

For information my iPhoto is v 9.5.1 and would seem not to like .dng files so won't load them (I am using the Adobe RAW to DNG 8.3 Converter at the moment mainly because I would have to upgrade to PSE12 to get the RAW plug-in to process my Lumix G-6 RAW files, which is fairly expensive and, even then, my iPhoto would still be the same version unless I upgraded that as well!).
I can load the RAW files onto iPhoto but when I then send them to PSE or iPhoto itself for editing they seem to be automatically converted to .jpg and do not have the usual RAW editing selection palette. However, the PSE Organizer seems happy to accept the .dng files (but not the RAW files) and when sent to PSE for editing I do get the RAW type palette, so it looks like storing my .dng files in Organizer is a good idea and, therfore, I might as well store other photos there as well rather than run two different organizers - I will leave the photos in Bridge as they are.
If you are talking about photos not in iphoto, this is correct. If you use "from iPhoto" you will get automatic duplicates of the originals in a new location. If you export them manually and use from files and folders, yes, the organizer just makes a thumbnail.
This paragraph made me think! I'm pretty sure that when I decided to transfer my photos from iPhoto into PSE Organizer I used "from iPhoto" as this seemed the easiest way. Does this mean that I have duplicated the file size of my iPhoto library and am therefore using much more hard-disc space than if I had used "from files and folders" (getting just thumbnails)? The transfer seems to have pulled in a lot of folders! If this is the case, is there any way to go back and do it again but "from files and folders" next time?!
This is all rather complicated it would seem (or I'm making it that way!) and I really appreciate your help.

Still curious about the ideacentre Stick?

Last week, we announced the ideacentre Stick, which is a stick computer that you can plug into any TV display and turn it into a Windows PC with 2GB RAM and enough power to browse the web, create documents, etc.
So, what are some best practices when it comes to stick computing? Well, we have some below, check 'em out:
If you're still curious about what our device is, check out our datasheet here: http://news.lenovo.com/images/20034/LenovoideacentreStick300Datasheet_Final.pdf

We had an absolute blast. I don't think I'll ever see a bigger fireworks display. I took a few pictures through our weekend (but not nearly enough to truly show what all we did!)
This was the view from our hotel in Backbay. That water line is where the fireworks were set off.
this is one street over from Newbury st. We were on our way to an improv show and ended up walking all the way to the center of the metro! (not a good idea when the wife was in heels, but we learned our lesson and took the subway whenever the walk was more then 20 minutes)
This was actually shot from the science museum through a window. For reasons.
Waiting for the fireworks. Everyone who had boats were piled up about a quarter mile from the barge. also city lights.
and more city lights (we have a competition at work, this and one other will be my entries!)

Did a clean install 10.9.4. on a stock Fusion HD. When I run "diskutil list" via Terminal, everything is wrong. I have "EFI" and "apple Boot Boot OSX in every dev/disk** How do I fix? Any help would be much appreciated, thank you

Did a clean install 10.9.4. on a Apple Stock 1TB Fusion Hard Drive. When I run "diskutil list" via Terminal, everything is wrong. I have "EFI" and "apple Boot Boot OSX" in every dev/disk** Everything is out of place, How can I repair? Im willing too reformat if need be, however thats what I did in the first place. Any help would be much appreciated, thank you.
I know this cannot be correct
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage                         121.0 GB   disk0s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:          Apple_CoreStorage                         999.3 GB   disk1s2
   3:                 Apple_Boot Boot OS X               650.0 MB   disk1s3
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Fusion                 *1.1 TB     disk2
/dev/disk7
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                                                   *121.9 GB   disk7

It appears as if my startup disk has been reversed and not using the fusion ssd portion as it should. At least its now reversed as to what it used to be originally before. the 128gb ssd used to be on top. Is my mac booting fusion correctly? Thank you for responding as I was about to reformat.
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group C2619AFE-0EB5-4721-8C50-3F3DBA520D1B
    =========================================================
    Name:         fusion
    Status:       Online
    Size:         1120333979648 B (1.1 TB)
    Free Space:   114688 B (114.7 KB)
    |
    +-< Physical Volume 583AAEA9-E333-4A83-9BE3-E937396E9248
    |   ----------------------------------------------------
    |   Index:    0
    |   Disk:     disk0s2
    |   Status:   Online
    |   Size:     120988852224 B (121.0 GB)
    |
    +-< Physical Volume B0C1CB16-D46F-4387-A679-B55392BB7934
    |   ----------------------------------------------------
    |   Index:    1
    |   Disk:     disk1s2
    |   Status:   Online
    |   Size:     999345127424 B (999.3 GB)
    |
    +-> Logical Volume Family FB42B9F4-CB77-4162-831B-7DCB7816E760
        Encryption Status:       Unlocked
        Encryption Type:         None
        Conversion Status:       NoConversion
        Conversion Direction:    -none-
        Has Encrypted Extents:   No
        Fully Secure:            No
        Passphrase Required:     No
        |
        +-> Logical Volume C0B8479B-C51C-45BF-B59B-1AA5DF3A3B83
            Disk:                  disk2
            Status:                Online
            Size (Total):          1111826497536 B (1.1 TB)
            Conversion Progress:   -none-
            Revertible:            No
            LV Name:               Fusion
            Volume Name:           Fusion
            Content Hint:          Apple_HFS
FoHeazys-Mac-mini:~ FoHeazy$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage                         121.0 GB   disk0s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:          Apple_CoreStorage                         999.3 GB   disk1s2
   3:                 Apple_Boot Boot OS X               650.0 MB   disk1s3
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Fusion                 *1.1 TB     disk2

[SEMI-SOLVED; STILL CURIOUS] no more /dev/disk/by-uuid

Similar Messages

Maybe you are looking for