[solved] Unable to find the root device after an upgrade - diff. case

Background: I recently upgraded my installation done in August 2011 to the most recent packages with 'pacman -Syu' - which, amongst some other minor issues that I fixed, apparently broke my installation's boot sequence. Not sure if this is relevant, but I forced the upgrade as it's been prescribed here.
Note to self: do backups before any major upgrades like this.
Problem: The problem is of the same origin as seen in this post - systems lets me know it cant access the root partition anymore. I'm halfway through the procedure that pineapple-biku suggested but since my partition layout is different - and - because I don't have much understanding of what *exactly* I'm supposed to do and accomplish, I'm stuck for now.
What is the best way to find out the exact labels of encrypted volumes and their corresponding kernel device IDs (i.e. /dev/sda6 for 'tmp' and so on)? I have several volumes of the same size, thus it's hard to guess which is which without knowing for sure.
Details: My setup has an unencrypted '/boot' partition and 7 other encrypted partitions, including /root, /usr and others. These are contained within a single extended partition.
Any help will be greatly appreciated. In case I've left out some important information, let me know, and I'll do my best to provide it.
Last edited by Raija (2012-02-28 03:06:25)

Thank you both for your assistance. Some more understanding was exactly what I was in need of.
falconindy wrote:The news item you posted says to force the installation of a single package, not the entire upgrade. These two things are not equivalent.
Thanks for pointing that out. I'm still a newbie when it comes to Pacman, thus prone to such mistakes.
Gcool wrote:
Raija wrote:What is the best way to find out the exact labels of encrypted volumes and their corresponding kernel device IDs (i.e. /dev/sda6 for 'tmp' and so on)? I have several volumes of the same size, thus it's hard to guess which is which without knowing for sure.
# ls -lah /dev/disk/by-label
# ls -lah /dev/disk/by-id
# ls -lah /dev/disk/by-uuid
This should get you on the way on discovering which disk is what exactly (you'll need to know the / and /boot partition in order to fix the issue).
Thank you. I'll try that.

Similar Messages

[SOLVED] Can't find LVM root device after pacman -Syu

Hey, can anyone give me a hand here? I haven't updated in about a month, but the last time I did was definitely after the changes-to-lvm post in the news (I know that because it's what got me on the last update )
I noted just before the update that cat /proc/1/comm displayed "init", which surprised me. Maybe I'd installed systemd but not configured it?
Anyway now I'm getting:
Waiting 10 seconds for device /dev/mapper/belle-root …
ERROR: Unable to find root device '/dev/mapper/belle-root'
You are being dropped to a recovery shell.
I've chrooted from a SUSE CD I had lying around and followed the "changes to LVM" instructions again in case I'd missed something, but nothing is changing.
Can anyone help me out? Thanks.
Last edited by DoctorWedgeworth (2013-03-27 00:32:41)

You have to use lvm first. As all those vg*, lv*, and pv* commands are actually links to the lvm command, you should have to do something like "lvm vgscan" instead of just "vgscan".
Edit: oh and at that point in the boot process, you are actually in the initramfs still (ash to be specific).
Edit2: I was having issues with a USB keyboard and a new machine (actually just a new bios), and found out that because of windows 8's requriement for a fast POST, the default is to turn off the scanning for usb devices. Though this was for UEFI, and I am not sure if the same would apply for a bios booting machine...
Last edited by WonderWoofy (2013-03-26 23:10:40)

Airport Utility was unable to find your Airport device after restarting.

- I just updated the firmware on my base station (it a white dome?? i think snow?) to 5.7
- I am running AirPort Utility 5.5.2 (also recently updated)
- I have (3) AirPort Expresses (just updated firmware yesterday) and now are not being seen in the airport utility. They had been running for about two years just fine.
I have done a hard reset and was then able to see the Airport Express and go through set up. Upon finalizing the set up I get this message:
"Airport Utility was unable to find your Airport device after restarting."
This is happening with all 3 AirPort Expresses

Hello !
I had the same kind of problems when I upgraded to the latest version of Airport (5,7).
The Airport express seemed to have been disconnected, and nothing I could do to reconfigure it, after hard resetting it, seemed to be working.
I did two or three hard resets before remembering having been in a situation like that a while ago.
I went back to the Mini, **deactivated the firewall (in the "preferences" panel), then deactivated also the firewall of the Modem/router provided for my internet connection. Then I went in the other room and did another hard reset of the Airport express, came back in the mini's room, opened the Airport utility, the icon of the Airport express was already visible (which wasn't the case before... ), did the re-configuring.
The reconfigured Airport express reappeared very quickly, then I reactivated the firewalls of the Mini and the router. Voilà !
It took less than two minutes !
And since then the Mini have been streaming music without a glitch to the Airport express.
I hope this will help you and others !

BIOS-GPT grub cannot find the root device in LVM setup

Greetings Arch Linux Community,
Recently I started my journey of installing Arch Linux on my VMware Workstation.
I successfully installed the non-LVM instance not long before I noticed the advantages of LVM, then I just started a new Arch Linux setup with LVM.
However, after following the Beginners' Guide and LVM Guide carefully, I ran into a problem on boot that I cannot solve by myself due to my poor knowledge on boot/grub.
Here is the error message:
ERROR: device '4b28d500-8ed3-4fe5-ad26-97fbb01f979b' not found. Skipping fsck
ERROR: Unable to find root device '4b28d500-8ed3-4fe5-ad26-97fbb01f979b'
The error message itself is pretty clear; saying that the root device specified by my grub.cfg cannot be found and thus cannot be loaded.
However, I'm 100% sure that the device is actually there and just for some reason grub cannot see it.
Below please see the info from lsblk, pvdisplay, vgdisplay, lvdisplay, and some related info from fstab, grub.cfg and mkinitcpio.conf:
root@archiso / # lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
fd0
sda
├─sda1
├─sda2 swap a576bed1-929a-4ea5-b771-6b2e3b2e3808
├─sda3 ext4 659e5bcf-b34b-4083-b8e5-e336fdd20c3d /mnt/boot
└─sda4 LVM2_member GNznA5-fwUh-Gw6D-JvY4-rZKJ-d6fP-TIyoRZ
├─VolGroup00-lvroot ext4 4b28d500-8ed3-4fe5-ad26-97fbb01f979b /mnt
└─VolGroup00-lvhome ext4 dc1f1322-8d8e-4456-b61d-95966ae4e25d /mnt/home
sr0 iso9660 ARCH_201405 2014-05-01-05-20-54-00 /run/archiso/bootmnt
loop0 squashfs /run/archiso/sfs/root-image
loop1 ext4 f07bfb26-3377-487a-a022-efd840614a0d
└─arch_root-image ext4 f07bfb26-3377-487a-a022-efd840614a0d /
loop2 ext4 f07bfb26-3377-487a-a022-efd840614a0d
└─arch_root-image ext4 f07bfb26-3377-487a-a022-efd840614a0d /
root@archiso / # pvdisplay
--- Physical volume ---
PV Name /dev/sda4
VG Name VolGroup00
PV Size 8.50 GiB / not usable 2.98 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 2175
Free PE 0
Allocated PE 2175
PV UUID GNznA5-fwUh-Gw6D-JvY4-rZKJ-d6fP-TIyoRZ
root@archiso / # vgdisplay
--- Volume group ---
VG Name VolGroup00
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 8.50 GiB
PE Size 4.00 MiB
Total PE 2175
Alloc PE / Size 2175 / 8.50 GiB
Free PE / Size 0 / 0
VG UUID x8VegQ-OKr6-kNNk-HwHe-xxi1-Ecdt-W9Ydj2
root@archiso / # lvdisplay
--- Logical volume ---
LV Path /dev/VolGroup00/lvroot
LV Name lvroot
VG Name VolGroup00
LV UUID q8LxrZ-PXmf-K2Sl-7SNl-DlsF-IZ3s-2m2eHw
LV Write Access read/write
LV Creation host, time archiso, 2014-05-17 16:24:23 +0000
LV Status available
# open 1
LV Size 5.00 GiB
Current LE 1280
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
--- Logical volume ---
LV Path /dev/VolGroup00/lvhome
LV Name lvhome
VG Name VolGroup00
LV UUID 3q32Nf-CRZz-iYpB-5317-075y-ulj3-uurdwE
LV Write Access read/write
LV Creation host, time archiso, 2014-05-17 16:24:49 +0000
LV Status available
# open 1
LV Size 3.50 GiB
Current LE 895
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:2
root@archiso / # cat /mnt/etc/fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/VolGroup00-lvroot
UUID=4b28d500-8ed3-4fe5-ad26-97fbb01f979b / ext4 rw,relatime,data=ordered 0 1
# /dev/mapper/VolGroup00-lvhome
UUID=dc1f1322-8d8e-4456-b61d-95966ae4e25d /home ext4 rw,relatime,data=ordered 0 2
# /dev/sda3
UUID=659e5bcf-b34b-4083-b8e5-e336fdd20c3d /boot ext4 rw,relatime,data=ordered 0 2
# /dev/sda2
UUID=a576bed1-929a-4ea5-b771-6b2e3b2e3808 none swap defaults 0 0
root@archiso / # cat /mnt/boot/grub/grub.cfg | grep "root"
set root='lvmid/x8VegQ-OKr6-kNNk-HwHe-xxi1-Ecdt-W9Ydj2/q8LxrZ-PXmf-K2Sl-7SNl-DlsF-IZ3s-2m2eHw'
search --no-floppy --fs-uuid --set=root --hint='lvmid/x8VegQ-OKr6-kNNk-HwHe-xxi1-Ecdt-W9Ydj2/q8LxrZ-PXmf-K2Sl-7SNl-DlsF-IZ3s-2m2eHw' 4b28d500-8ed3-4fe5-ad26-97fbb01f979b
search --no-floppy --fs-uuid --set=root 4b28d500-8ed3-4fe5-ad26-97fbb01f979b
set root='hd0,gpt3'
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 659e5bcf-b34b-4083-b8e5-e336fdd20c3d
search --no-floppy --fs-uuid --set=root 659e5bcf-b34b-4083-b8e5-e336fdd20c3d
linux /vmlinuz-linux root=UUID=4b28d500-8ed3-4fe5-ad26-97fbb01f979b rw quiet
set root='hd0,gpt3'
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 659e5bcf-b34b-4083-b8e5-e336fdd20c3d
search --no-floppy --fs-uuid --set=root 659e5bcf-b34b-4083-b8e5-e336fdd20c3d
linux /vmlinuz-linux root=UUID=4b28d500-8ed3-4fe5-ad26-97fbb01f979b rw quiet
set root='hd0,gpt3'
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 659e5bcf-b34b-4083-b8e5-e336fdd20c3d
search --no-floppy --fs-uuid --set=root 659e5bcf-b34b-4083-b8e5-e336fdd20c3d
linux /vmlinuz-linux root=UUID=4b28d500-8ed3-4fe5-ad26-97fbb01f979b rw quiet
root@archiso / # cat /mnt/etc/mkinitcpio.conf| grep "HOOKS"
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# HOOKS="base"
# HOOKS="base udev autodetect block filesystems"
# HOOKS="base udev block filesystems"
# HOOKS="base udev block mdadm encrypt filesystems"
# HOOKS="base udev block lvm2 filesystems"
HOOKS="base udev autodetect modconf block lvm2 filesystems keyboard fsck"
Last edited by garrio (2014-05-18 00:42:36)

Efka wrote:when i was installing Arch, i installed grub on /dev/sda and my sda (gpt )was - sda1 (ext4)for / and sda2(ext4) for /home so when grub is installed it is installed into SDA ( or im wrong? ) but not into sda1 or sda2, but when i was doing my install i didnt made /boot ext4 partition (sda3 ext4 659e5bcf-b34b-4083-b8e5-e336fdd20c3d /mnt/boot) . i think u trying to mount grub into ext4 partition. is this right ? if yes... is it how it suposed to be ?
Sorry, im newbie ( dont take my advice seriously ), but im very curious about his, because once i couldnt install grub as well so i went for syslinux instead , and i know i will have one more fresh install of arch to do, so im curious
Hi Efka, I used grub-install and specified "/dev/sda" for argument. What I understand is that the sda is the identifier for the hard disk where all the sdaX reside. And if you look into the output of my lsblk, you will see that there is one partition sda1 that has no filetype, label and UUID on display; that is actually the bios boot partition where, as I understand, the grub code embeds itself.
We can have different partition scheme to deploy and having a separate partition for /boot is just my personal preference ans it should work as well.

Unable to find valid certification path after an upgrade from 11.1.1.6 to 11.1.1.7

Hi,
I had a small composite deployed in 11.1.1.6 and after an upgrade to 11.1.1.7 I am getting
javax.xml.soap.SOAPException: Message send failed: sun.security.validator.ValidatorException:
PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Does it mean that my soa composite now cannot validate the certificate of the server it is trying to connect to?
Can somebody share thoughts on how to fix it?
Thank you,
Anatoliy

Hi Robert,
Thank you much for the quick response. Not having big knowledge under my belt in this area I tried
1. Changed the keystore passphrase under my managed weblogic domain for the Demo Identity Keystore
2. ./keytool -importcert -alias avsclient -keystore /dnat8o/fmw/jrockit-jdk1.6.0_29-R28.2.2-4.1.0/jre/lib/security/cacerts -file client_cer.cer
Was prompted with the password but entering what I did enter in step 1 didn't help. Do I have to bounce the managed server once I change the passphrase, if what I a mdoing makes sense at all, not sure
Thank you,
Anatoliy

[Solved] Can't mount specific usb device after kernel upgrade

So, hi everyone
I've got a usb device which works on other systems (usb audio player, android tablet) but not on my archlinux htpc.
System is up to date, the usb stick worked a few days ago (here shown as /dev/sdc), relevant infos (shortened):
$ uname -a
Linux arch247 3.10.3-1-ARCH #1 SMP PREEMPT Fri Jul 26 11:26:59 CEST 2013 x86_64 GNU/Linux
$ lsusb
Bus 009 Device 006: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
$ dmesg
[ 1788.621747] usb 9-4: new full-speed USB device number 8 using ohci_hcd
[ 1788.771370] usb 9-4: not running at top speed; connect to a high speed hub
[ 1788.785511] usb-storage 9-4:1.0: USB Mass Storage device detected
[ 1788.793170] scsi13 : usb-storage 9-4:1.0
[ 1789.801391] scsi 13:0:0:0: Direct-Access General USB Flash Disk 1.00 PQ: 0 ANSI: 2
[ 1789.814964] sd 13:0:0:0: [sdc] 15669248 512-byte logical blocks: (8.02 GB/7.47 GiB)
[ 1789.819230] sd 13:0:0:0: [sdc] Write Protect is off
[ 1789.819243] sd 13:0:0:0: [sdc] Mode Sense: 03 00 00 00
[ 1789.825267] sd 13:0:0:0: [sdc] No Caching mode page present
[ 1789.825281] sd 13:0:0:0: [sdc] Assuming drive cache: write through
$ lsmod | grep ohci
ohci_hcd 26544 0
usbcore 176991 6 ath3k,btusb,usb_storage,ohci_hcd,usbhid,xhci_hcd
$ sudo fdisk -l
Disk /dev/sda: 120.0 GB, 120034123776 bytes, 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x89675d3a
Device Boot Start End Blocks Id System
/dev/sda1 2048 50333695 25165824 83 Linux
/dev/sda2 50333696 234441647 92053976 83 Linux
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x0004e72c
Device Boot Start End Blocks Id System
/dev/sdb1 2048 3907022847 1953510400 83 Linux
Disk /dev/sdc: 8022 MB, 8022654976 bytes, 15669248 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x0009ae2c
Device Boot Start End Blocks Id System
/dev/sdc1 2048 15669247 7833600 c W95 FAT32 (LBA)
I can't reformat the device at the moment (lack of computers here). The usb port on the pc is working (tested with another fat32 formatted usb stick).
Any ideas? Hints? Tips?
Last edited by D4ve (2013-08-18 18:48:35)

It works on 3.9.11.
dmesg on 3.9.11:
[ 74.391651] usb 3-4: new high-speed USB device number 3 using xhci_hcd
[ 74.410514] usb 3-4: New USB device found, idVendor=0951, idProduct=1607
[ 74.410529] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 74.410532] usb 3-4: Product: DataTraveler 2.0
[ 74.410534] usb 3-4: Manufacturer: Kingston
[ 74.410536] usb 3-4: SerialNumber: 00137299803FA931262A00CD
[ 74.465400] Initializing USB Mass Storage driver...
[ 74.465654] scsi7 : usb-storage 3-4:1.0
[ 74.465726] usbcore: registered new interface driver usb-storage
[ 74.465728] USB Mass Storage support registered.
[ 75.465448] scsi 7:0:0:0: Direct-Access Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2
[ 75.465839] sd 7:0:0:0: Attached scsi generic sg4 type 0
[ 75.466277] sd 7:0:0:0: [sdd] 3973120 512-byte logical blocks: (2.03 GB/1.89 GiB)
[ 75.466620] sd 7:0:0:0: [sdd] Write Protect is off
[ 75.466625] sd 7:0:0:0: [sdd] Mode Sense: 23 00 00 00
[ 75.466955] sd 7:0:0:0: [sdd] No Caching mode page present
[ 75.466960] sd 7:0:0:0: [sdd] Assuming drive cache: write through
[ 75.469081] sd 7:0:0:0: [sdd] No Caching mode page present
[ 75.469087] sd 7:0:0:0: [sdd] Assuming drive cache: write through
[ 75.681901] sdd: sdd1 sdd2
[ 75.683219] sd 7:0:0:0: [sdd] No Caching mode page present
[ 75.683224] sd 7:0:0:0: [sdd] Assuming drive cache: write through
[ 75.683227] sd 7:0:0:0: [sdd] Attached SCSI removable disk
dmesg on 3.10.5:
[ 1370.659092] usb 3-4: new high-speed USB device number 8 using xhci_hcd
[ 1370.677899] usb 3-4: New USB device found, idVendor=0951, idProduct=1607
[ 1370.677906] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1370.677910] usb 3-4: Product: DataTraveler 2.0
[ 1370.677913] usb 3-4: Manufacturer: Kingston
[ 1370.677916] usb 3-4: SerialNumber: 00137299803FA931262A00CD
[ 1370.678442] usb-storage 3-4:1.0: USB Mass Storage device detected
[ 1370.678711] scsi12 : usb-storage 3-4:1.0
[ 1371.674797] scsi 12:0:0:0: Direct-Access Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2
[ 1371.675283] sd 12:0:0:0: Attached scsi generic sg4 type 0
[ 1371.675809] sd 12:0:0:0: [sdd] 3973120 512-byte logical blocks: (2.03 GB/1.89 GiB)
[ 1371.676184] sd 12:0:0:0: [sdd] Write Protect is off
[ 1371.676192] sd 12:0:0:0: [sdd] Mode Sense: 23 00 00 00
[ 1371.676560] sd 12:0:0:0: [sdd] No Caching mode page present
[ 1371.676567] sd 12:0:0:0: [sdd] Assuming drive cache: write through
[ 1402.372357] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1402.389648] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1402.389655] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1433.410334] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1433.427691] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1433.427698] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1464.352379] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1464.369587] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1464.369592] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1495.294439] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1495.311616] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1495.311623] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1495.314661] sd 12:0:0:0: [sdd] No Caching mode page present
[ 1495.314677] sd 12:0:0:0: [sdd] Assuming drive cache: write through
[ 1526.236340] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1526.253657] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1526.253665] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1557.306368] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1557.323619] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1557.323627] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1588.248358] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1588.265745] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1588.265752] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1619.190405] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1619.207780] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1619.207788] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1619.421206] sdd: sdd1 sdd2
[ 1619.422735] sd 12:0:0:0: [sdd] No Caching mode page present
[ 1619.422741] sd 12:0:0:0: [sdd] Assuming drive cache: write through
[ 1650.132306] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1650.149607] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1650.149614] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1681.202196] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1681.219363] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1681.219370] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1712.144197] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1712.161474] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1712.161482] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1743.086261] usb 3-4: reset high-speed USB device number 8 using xhci_hcd
[ 1743.103565] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ecdc0
[ 1743.103572] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88024d4ece00
[ 1743.104256] sd 12:0:0:0: [sdd] Attached SCSI removable disk
EDIT: Doesn't work on 3.11-rc4 either.
Last edited by gmesalazar (2013-08-06 01:30:00)

[Solved] kernel 2.6.27 - Root device not found (2.6.28 too)

since the last kernel update, my ArchLinux won't boot anymore, as it seems to be unable to find the root partition "/dev/sda5". The exact output is:
:: Loading root filesystem module...
Attempting to create root device '/dev/sda5'
ERROR: Failed to parse block device name for '/dev/sda5'
unknown
ERROR: root fs cannot be detected. Try using the rootfstype= kernel parameter.
Waiting for devices to settle...done.
Root device '/dev/sda5' doesn't exist, attempting to create it
ERROR: Failed to parse block device name for '/dev/sda5'
ERROR: Unable to create/detect root device '/dev/sda5'
Dropping to a recovery shell... type 'exit' to reboot
NOTE: klibc contains no 'ls' binary, use 'echo *' instead
If the device '/dev/sda5' gets created while you are here,
try adding 'rootdelay=8' or higher to the kernel command-line
ramfs$
What I have tried:
1.- I have booted with an old Ubuntu LiveCD, and /dev/sda5 seems to be working and healthy, as it mounted flawlessly while in Ubuntu.
2.- I have also found that not even /dev/sda is created from the fallback recovery shell so, obviously, there is no root device to create.
3.- None of the suggested kernel command-line parameters worked: 'rootfstype=ext3' and/or 'rootdelay=8'(I mean, using them separately or both in the same kernel GRUB line) didn't give any positive result, or any behavior change.
And now, two questions:
1.- How can I fix this?
2.- If it's not possible, how can I downgrade the kernel from a LiveCD? I suppose this is possible by booting an ArchLinux LiveCD, chrooting my '/dev/sda5' finding a 2.26.X kernel pacman package and installing, but I'm almost iliterate in kernel issues, and some help would be nice.
Thank you all in advance!
EDIT: Oh, I have also waited for some time to see if the hard disk gets ready after the failed booting proccess but it seems it doesn't, so 'rootdelay=8' wouldn't help anyway, just to give some more details about the problem.
Last edited by 4s|m3tr|ko0 (2009-01-21 10:14:32)

4s|m3tr|ko0 wrote:
ballon wrote:It seems like my problems can be the same, however I haven't managed to solve it myself so if you can be more detailed that would be nice.
Of course I can, it's quite easy.
First of all, you have to boot from an Archlinux install CD, to have an usable environment. Once you have booted, I will assume a couple of things to make the examples, which are:
"/dev/sda2" is the root partition where the system is currently installed but not booting.
"/dev/sda1" is the boot partition (not needed if you don't have a separated boot partition, obviously).
"/mnt/myarch" is the directory where sda1 will be mounted on the live session.
The kernel version on sda2 is "2.6.27-ARCH", you can find which kernel versions are installed on sda2 by checking the directory names under "/lib/modules/"
Next you have to mount your root partition on any directory and mount the "boot" partition if you have one too:
mkdir /mnt/myarch #Creates the mount directory on the live session, you can use /mnt/ so this command is not neccesary
mount -t auto /dev/sda2 /mnt/myarch #Mount the root partition on the live session
mount -t auto /dev/sda1 /mnt/myarch/boot #Mount the boot partition, if you have to
Now, you'll have to bind three system directories to their true locations on the root partition:
mount -t proc proc /mnt/myarch/proc
mount -t sysfs sys /mnt/myarch/sys
mount -o bind /dev /mnt/myarch/dev
Next step is to use the command "chroot <target> <consolebin>" to "move" the system root to the <target> directory, using the <consolebin> command interpreter:
chroot /mnt/myarch/ /bin/bash
Now, you will be using your system just like if you had actually booted from your hard disk, but running the kernel from the liveCD, so the only remaining step is to generate the initcpio image.
In the example for this step, I will run the mkinitcpio twice, the first one to check that it's correctly generated, and the second to install it, using the parameter "-g". Another thing to keep in mind is that even before chrooting, the liveCD kernel is still running, so you will have tu use the "-k <kernelversion>" parameter to manually specify the kernel to use. Otherwise, mkinitcpio won't be able to find the correct modules to use:
mkinitcpio -k 2.6.27-ARCH #This will simulate the generation, if it runs fine, run the next command
mkinitcpio -g /boot/kernel26.img -k 2.6.27-ARCH #This will actually generate the image
And that's all, this should regenerate a default image. More info about mkinitcpio: http://wiki.archlinux.org/index.php/Mkinitcpio
Hope this heps
PS: Sweden, nice country .
I follow this guide and I saved my Arch installation. I don't know why the HOOKS array in my mkinitcpio.conf just contains "base" :-?
So, just before regenerate the ramdisk image I edit my /etc/mkinitcpio.conf and add all the neccessary hooks and generate. I can bring my Arch box back to life

How Do You Solve the Xcode 6.1.1, Playground's "unable to find suitable target device"?

Hi. I've reset Xcode 6.1.1 (I'm on Yosemite 10.10.2), have restarted the iMac (late 2009), have plugged in via USB the iPhone 5 (runs 8.1.3), resetted even the SMC and PRAM but I still get the Playground error: "unable to find suitable target device".
I checked the Xcode's Preferences - Downloads, on the Components pane or window it says iOS 7.1 Simulator which you could download but when I try to download it, it's just a blank progress bar, even if left for hours, it's not downloading at all. Yet when I press update and install in Preferences - Downloads, it checks it but says there's not update (if there's no update why is iOS 7.1 Simulator an option to be downloaded in the Components window?).
How do you solve this. Do I need to reset XCode at a more deeper level? Could this be a bug in 6.1.1 update?
Thank you in advance. God bless, Rev. 21:4

Hi. I've reset Xcode 6.1.1 (I'm on Yosemite 10.10.2), have restarted the iMac (late 2009), have plugged in via USB the iPhone 5 (runs 8.1.3), resetted even the SMC and PRAM but I still get the Playground error: "unable to find suitable target device".
I checked the Xcode's Preferences - Downloads, on the Components pane or window it says iOS 7.1 Simulator which you could download but when I try to download it, it's just a blank progress bar, even if left for hours, it's not downloading at all. Yet when I press update and install in Preferences - Downloads, it checks it but says there's not update (if there's no update why is iOS 7.1 Simulator an option to be downloaded in the Components window?).
How do you solve this. Do I need to reset XCode at a more deeper level? Could this be a bug in 6.1.1 update?
Thank you in advance. God bless, Rev. 21:4

After updating my IOS TO 8.1 (12B411) on 10/23/14, I went to update my blood sugar level in the IHealth app. And now after the new IOS update I'm unable to find the blood glucose option in the IHealth app. Did Apple remove it or just mess up AGAIN?

fter updating my IOS TO 8.1 (12B411) on 10/23/14, I went to update my blood sugar level in the IHealth app. And now after the new IOS update I'm unable to find the blood glucose option in the IHealth app. Did Apple remove it or just mess up AGAIN?

Apple removed blood glucose until further notice. The reason behind this is that it gave a distorted picture in countries where the medical world used other measuring units. I suspect it will be available again in a future update.

Unable to find the workbook on server after applied Package 13 NW2004S

Dear guys,
Yesterday we applied NW2004S Package13, and today we found that for user without SAPALL authorization, they got "Unable to find the workbook on server" when accessing workbook in roles. But for user with SAPALL, the workbooks still work fine.
I searched the forum and found similar problems for users migrated from 3.x to 7.0. However, ours is 7.0 and is not migrated.
The bex version:
BI AddOn 7.x(based on 6.40), SupportPackage 14, Patch3, Revision811
Pls help. sorry for having no points to assign since I am new here...:)

Hi,
on thing I noticed... SP 13 is not that stable...
Hint: ask your technical guys to implement support pack 14... I think your problem will be solved then... because you say you only have this problem since you upgraded...
Ciao
Joke

HT3728 Base station error, air port utility was unable to find my airport device. Why does it say this when it recognizes my airport on the computer? Yellow light has been on

Base station error, air port utility was unable to find my airport device. Why does it say this when it recognizes my airport on the computer? Yellow light has been on

On the older version of the AE you can still use older airport utility.
But once you load the new one you cannot easily go back.. you can load an older 5.6 version though.. instructions below.
For 6.3 you need to run ipv6 local link.
see http://support.apple.com/kb/TS4597
How to load 5.6 into ML.
1. Download 5.6 for Lion.
http://support.apple.com/kb/DL1482
Click to open the dmg but do not attempt to install the pkg.. it won't work anyway.
Leave the package open on the desktop so you can see the file. AirportUtility56.pkg
2. Download and install unpkg.
http://www.timdoug.com/unpkg/
Run unpkg on the desktop.. If your Mac refuses to run the software, because it wasn’t downloaded from the Apple store, go to security in preferences and allow other software to work.. this is limitation of trade methinks. You can set back later if you like.
Now drag the AirPortUtility56.pkg file over to unpkg.. and it will create a new directory of the same name on the desktop.. in finder, open the new directory, drill down.. applications, utilities .. there lo and behold is Airport utility 5.6 .. drag it to your main utilities directory or just run it from current location.
You cannot uninstall version 6 (now 6.3 if you updated) so don't try.. and you cannot or should not run them both at the same time.. although I have had no problems when doing so.

Grub can't find root device after system update today (12/30)

I did a system update (kernel was updated to 2.6.32) today and turned off my computer. When I tried to boot up, Grub said it couldn't find my root device (/dev/sdb3) which is on my external hard drive. Grub and my kernel is on my external hard drive too (/dev/sdb1) so the hard drive itself seems to be working. If it'll help, here are my hooks:
HOOKS="base udev autodetect pata scsi sata usb filesystems"

This is from pacman.log, from when I updated on 12/30.
[2009-12-30 10:19] synchronizing package lists
[2009-12-30 10:20] starting full system upgrade
[2009-12-30 10:29] upgraded consolekit (0.4.1-1 -> 0.4.1-2)
[2009-12-30 10:29] upgraded hdparm (9.27-1 -> 9.27-2)
[2009-12-30 10:29] upgraded libdrm (2.4.16-1 -> 2.4.17-2)
[2009-12-30 10:29] upgraded libgl (7.6-2 -> 7.7-1)
[2009-12-30 10:29] upgraded intel-dri (7.6-2 -> 7.7-1)
[2009-12-30 10:29] upgraded kernel26-firmware (2.6.31-1 -> 2.6.32.2-2)
[2009-12-30 10:29] >>> Updating module dependencies. Please wait ...
[2009-12-30 10:29] >>> MKINITCPIO SETUP
[2009-12-30 10:29] >>> ----------------
[2009-12-30 10:29] >>> If you use LVM2, Encrypted root or software RAID,
[2009-12-30 10:29] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2009-12-30 10:29] >>> More information about mkinitcpio setup can be found here:
[2009-12-30 10:29] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2009-12-30 10:29]
[2009-12-30 10:29] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2009-12-30 10:29] ==> Building image "default"
[2009-12-30 10:29] ==> Running command: /sbin/mkinitcpio -k 2.6.32-ARCH -c /etc/mkinitcpio.conf -g /boot/arch/kernel26.img
[2009-12-30 10:29] :: Begin build
[2009-12-30 10:29] :: Parsing hook [base]
[2009-12-30 10:29] :: Parsing hook [udev]
[2009-12-30 10:29] :: Parsing hook [autodetect]
[2009-12-30 10:29] :: Parsing hook [pata]
[2009-12-30 10:29] :: Parsing hook [scsi]
[2009-12-30 10:29] :: Parsing hook [sata]
[2009-12-30 10:29] :: Parsing hook [usb]
[2009-12-30 10:29] :: Parsing hook [filesystems]
[2009-12-30 10:29] :: Generating module dependencies
[2009-12-30 10:29] :: Generating image '/boot/arch/kernel26.img'...SUCCESS
[2009-12-30 10:29] ==> SUCCESS
[2009-12-30 10:29] ==> Building image "fallback"
[2009-12-30 10:29] ==> Running command: /sbin/mkinitcpio -k 2.6.32-ARCH -c /etc/mkinitcpio.conf -g /boot/arch/kernel26-fallback.img -S autodetect
[2009-12-30 10:29] :: Begin build
[2009-12-30 10:29] :: Parsing hook [base]
[2009-12-30 10:29] :: Parsing hook [udev]
[2009-12-30 10:29] :: Parsing hook [pata]
[2009-12-30 10:29] :: Parsing hook [scsi]
[2009-12-30 10:30] :: Parsing hook [sata]
[2009-12-30 10:30] :: Parsing hook [usb]
[2009-12-30 10:30] :: Parsing hook [filesystems]
[2009-12-30 10:30] :: Generating module dependencies
[2009-12-30 10:30] :: Generating image '/boot/arch/kernel26-fallback.img'...SUCCESS
[2009-12-30 10:30] ==> SUCCESS
[2009-12-30 10:30] upgraded kernel26 (2.6.31.6-1 -> 2.6.32.2-2)
[2009-12-30 10:30] upgraded libgcrypt (1.4.4-2 -> 1.4.5-1)
[2009-12-30 10:30] installed parted (1.9.0-3)
[2009-12-30 10:30] installed libatasmart (0.17-1)
[2009-12-30 10:30] installed devicekit-disks (009-3)
[2009-12-30 10:30] installed gnome-disk-utility (2.28.1-1)
[2009-12-30 10:30] installed gvfs (1.4.3-1)
[2009-12-30 10:30] upgraded libgnome (2.28.0-1 -> 2.28.0-2)
[2009-12-30 10:30] upgraded libsndfile (1.0.20-3 -> 1.0.21-1)
[2009-12-30 10:30] upgraded mesa (7.6-2 -> 7.7-1)
[2009-12-30 10:30] upgraded mono (2.6-1 -> 2.6.1-1)
[2009-12-30 10:30] upgraded mtasc (20080105-1 -> 20091229-1)
[2009-12-30 10:30] upgraded nano (2.2.0-1 -> 2.2.1-1)
[2009-12-30 10:31] upgraded netbeans (6.8-1 -> 6.8-2)
[2009-12-30 10:31] upgraded pycups (1.9.46-2 -> 1.9.47-1)
[2009-12-30 10:31] upgraded system-config-printer-common (1.1.13-1 -> 1.1.15-1)
[2009-12-30 10:31] upgraded system-config-printer-gnome (1.1.13-1 -> 1.1.15-1)
[2009-12-30 10:31] upgraded totem (2.28.4-1 -> 2.28.5-1)
[2009-12-30 10:31] upgraded tzdata (2009s-1 -> 2009t-1)
[2009-12-30 10:31] upgraded xorg-server (1.7.3.901-1 -> 1.7.3.902-1)
I'll try running mkinitcpio though.
Edit: from the chroot'd shell:
[ root@ubuntu ] [ / ]
[ # ] > mkinitcpio -p kernel26
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.32-ARCH -c /etc/mkinitcpio.conf -g /boot/arch/kernel26.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [usb]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/arch/kernel26.img'...SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.32-ARCH -c /etc/mkinitcpio.conf -g /boot/arch/kernel26-fallback.img -S autodetect
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [usb]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/arch/kernel26-fallback.img'...SUCCESS
==> SUCCESS
[ root@ubuntu ] [ / ]
[ # ] > ls /boot/arch
kernel26-fallback.img kernel26.img
I'll try booting with both the disk by UUID and the disk named as /dev/sdb3 in the Grub commands.
Last edited by megajosh2 (2010-01-02 00:17:45)

Preflight keeps saying "Unable to save the PDF File after post processing"

I'm at a loss how to overcome this. Spent almost a whole day, together with another person, trying to fix it with no success!
I use Adobe pro CC on a PC
I usually receive pdf files from this one client who edits and formats a book in Mac Pages. Up until a few days ago I had no problems converting the client's pdfs into pdf/x3, but the last three versions of the latest file have stumped me.
Just to test, I first just tried to convert the file (33MB), unchanged, to pdf/x3 using the save as other option - message reads "the document has been saved, however, it could not be converted according to the selected standard profile: convert to PDF/X. Please use preflight with the profile "Convert to PDF/X" in order to identify those properties of the document which prevent it from being compliant to this profile"
if I then choose under Profiles - convert to PDF/X3 - it says no problems found, and appears to have saved the file. If I try to save again as a pdf/x3, just to make sure, it then tells me it's not pdf/x3 compliant
OK - so then I go back to preflight - and choose the standards function - then pdf/x3, then continue with the default colour profile. About halfway through the conversion, at the point of saving the file, I get the message "unable to save the pdf file after post processing"
So far I've had no luck figuring out what this is.
I then choose the option of "verify compliance of ppdf/x3" - message reads "pdf/x3 version key (GTS_PDFXVersion) missing", and "Trapped key not true or false"
Help!! How can I be sure the file converted / or not?
kim

Yes I was/am aware of Preflight's inability to play nicely over cloud technologies in certain cases, especially wrt Standards technologies, this will be partially addressed in an upcoming version of Preflight without saying too much. But the same thing could theoretically have happened if the file was also located on another local network client or server. Leaving aside the argument that this may violate the Acrobat User Agreement - since purchasing the software, the user agrees to employ its functionality on a single host system and precludes host-client-based scenarios - this simply is not a supported use, meaning the user may not have expectations that it will work at all, if the applications requirements are not observed. There do exist server-solutions for Preflight files within networks, but Acrobat and by extension Acrobat Preflight is not one of those solutions, and (still) belongs in the single host-based desktop environment.
However most (99.9%) functions within Acrobat <-> acrobat.com file exchange are supported, file syncing across multiple devices will soon be supported, but Standards compliance is still admittedly a problem at this point. Some testing has been done using 3rd party cloud technologies starting with enterprise-based solutions, such as Office 365, and this will continue to ramp up to include other 3rd party products.
As for the second point, Preflight will usually change the PDF version to be complaint, are you saying that it was unable to do so in this case? It seems that this error should have popped up during the normal Preflight conversion attempt. Personally I think solving a workflow problem using the print path is a little bit of a heavy-handed approach, but if helped and the results are acceptable, then that is good. Since that path is non-existent on a Mac, as one needs to Save as Adobe PDF from the Print dialog's PDF drop-down menu, I am assuming your workflow involved file creation on a Mac, then further processing on Windows using the PDF printer. I am wondering if a simple resave/Save As... to PDF with overwrite on a Mac, or Preflighting the file using a PDF version compatibility profile before the PDF/X conversion would have helped. Since there are such a multitude of methods that a PDF can be created, there are also many ways within Acrobat that a user can shape the file to be compatible with the expected workflow, ie, 'many ways to skin a cat', without being morbid.

CRVS2010 Beta - Unable to find the report in the manifest resources

I upgraded to VS2010 Beta where we soon encountered this error.
Unable to find the report in the manifest resources. Please build the project, and try again.
at CrystalDecisions.CrystalReports.Engine.EngineExceptionUtils.DoThrowException(String message, EngineExceptionErrorID id)
   at CrystalDecisions.CrystalReports.Engine.ExceptionThrower.ThrowEngineException(String messageID, EngineExceptionErrorID id)
   at CrystalDecisions.CrystalReports.Engine.ReportClass.Load(String reportName, OpenReportMethod openMethod, Int16 parentJob)
   at CrystalDecisions.CrystalReports.Engine.ReportDocument.EnsureLoadReport()
   at CrystalDecisions.CrystalReports.Engine.ReportDocument.SetDataSourceInternal(Object val, Type type)
   at CrystalDecisions.CrystalReports.Engine.ReportDocument.SetDataSource(IEnumerable enumerable)
Searching the forums I saw some similar issues. Here is how the issue was solved on my end.
Looking at the properties of the crystal report file in VS2010 the Build Action was "None". After setting it compile things worked as normal. The exception made sense after finding the cause.
I'm not sure if this was caused by VS2010 as my organization was in the middle of migrating to TFS 2010 that may have caused an issue.
Hope this helps someone.

Cliff, thank you very much for sharing this soution with the community. Once CRVS2010 RTMs, I'll create a KBase on it.
Happy coding,
Ludek

PS CC unable to find the JavaScript plug-in?

I am on a Windows 7 pro platform - Hi, when trying to launch PS I get the following message: "Could not complete the command because PS was unable to find the JavaScript plug-in" after clicking ok another message pops up: " There is a problem with Generator. .... "
This problem occurred first after my one year discount run out and I paid the full amount. I thought the problem would be corrected by the next major upgrade - but no luck there.
Any idea how to solve this problem?
Thanks, Bee

In reply to JJMacks,
1 min ago
Why are you posting
to both DPreview forum and Adobe forum now? You didn't answer me on the Adobe
forum with this post. This is where you and I had been communicating. It was
only by chance that I saw this posting on the DPreview forum.
To ensure that we connect with each other I intend to post
on both of the forums until we resolve this issue.
I don't find this posting helpful - I am not an IT
professional at all except as a user ( English by the way is not my native
language).
In this post you say I should have the 15.2.2... versions of PS
CC. On your earlier post in the Adobe forum you told me I should have the 14...
versions - which is it?
As you know I do have only the 15.2.2... versions. Is there a
compatibility problem between the 15... versions of these Adobe Plug-ins and
the main PS CC program?
If you can't help me please put me into a telephone chat
(they can call me) or an on-line chat with someone who is able to walk me
through to a solution.
Thanks, Bee

[solved] Unable to find the root device after an upgrade - diff. case

Similar Messages

Maybe you are looking for