Mounting partition fails at boot time, but works after system is up

**EDIT: ok, I know now the daemon array comes too late. Looks like I have to fiddle with initial ramdisk or mount the partition daemon-style. Which is recommended?**
I have a fakeraid array which works well with device-mapper. I use dmraid as a daemon to create the nodes.
No problem when I mount the partition after boot. But now I want to move my /home there, so it has to mount during boot.
When I have it inside fstab, I get a corrupt superblock error during boot and arch throws me into an maintainance shell.
What's wrong? Is fstab processed before the daemon array? If that is the case, what would be a good clean way to launch dmraid if it cannot be a daemon?
Last edited by mindfall (2008-01-24 01:14:58)

All you should have to do is put dmraid in the HOOKS line in /etc/mkinitcpio.conf and rebuild your kernel (pacman -S kernel26). This will enable you to even have your root partition on the raid array. Edit /etc/fstab to include your home as usual using the device-mapper created raid-set and correct partition.
Wiki on dmraid

Similar Messages

SMF - start at boot time, but don't restart - possible?

I'm setting up a software package that has a number of background processes.
I've got SMF manifests created and imported for all of them, and they're working great for starting the processes at boot time, and doing the automatic restarts when one fails.
Here's my problem. It turns out that the users of this software want to be able to use the software's integrated process control methods to stop some of their processes. With the current configuration, they use the software's method to stop one of it's processes, and SMF promptly restarts it.
Is there a way to set up SMF managed software so that SMF starts it at boot time, but then doesn't care if stops later?
Richard

I'm not sure how it would be SMF "managed" in such a case. Obviously you want the management to be elsewhere.
You could use the "legacy" startup scripts in /etc/rcX.d. That will start a process and forget about it, just like pre-Solaris 10. You don't use manifests or have any other benefits of SMF.
If you do want SMF, I guess the question is how you want it to act..
When the users stop the processes, do you want SMF to say enabled or disabled? SMF does not track enabled processes by periodic polling, it does it by tracking contracts. This means that starting a process outside of SMF does not allow SMF to track it.
Darren

"F11 System Recovery" during boot does not work after Cloning hard drive.

Problem: “F11 System Recovery” during boot does not work after Cloning hard drive.
HP Envy m6-1125dx UEFI Notebook Computer with GPT hard drive.
Original Seagate Hard Disk GPT 700GB with Window 8.0_64 upgraded to Windows 8.1_64
Startup Menu (F11 System Menu works properly) only on original hard drive.
Following obtained from Disk Management & diskpart in Command Prompt.
GPT Disk <700GB>
Partition 1 WINRE NTFS Primary 235MB/400MB [Recovery]
Partition 2 EFI System FAT32 (LBA) Primary 108MB/260MB [System]
Partition 3 (NONE) Unformatted Primary 128MB/128MB [Reserve]
Partition 4 Main NTFS Primary 90GB/195GB [Primary “C”]
Partition 5 (NONE) NTFS Primary 372MB/450MB [Recovery]
Partition 6 Data NTFS Primary 7GB/475GB [Primary “E”]
Partition 7 NTFS Primary 26MB/350MB [Recovery]
Partition 8 Recovery NTFS Primary 24GB/26GB [Recovery “D”]
I have Cloned the original hard drive to a new HGST 1TB Hard Drive using four different methods (sector by sector):
Acronis True Image 2015
Acronis Backup for PC
AOMEI Backupper Professional
Macrium Reflect
Each time the cloning process completes successfully and has the same original partition arrangement. The computer works properly except when trying to use the “F11 System Menu” key during boot. It gives the following error message:
“Recovery
Your PC needs to be repaired
A required device isn’t connected or can’t be accessed.
Error code: 0xc0000225
You need to use the recovery tools on your installation media. If you don’t have any installation media (like a disc or USB device), contact your system administrator or PC manufacturer. “
Any suggestions why the F11 System Recovery does not work during boot and how to fix the problem would be appreciated. I have does various disk checking and file checking on both the original and new hard drive with no errors.
Thank you in advanced.

Hi,
How did you clone the HDD ? One-for-one or different method ?
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

Boot times vary extremely after SSD install on a Macbook 6,1

I have a white unibody Macbook (Macbook6,1), which is factory-built-to-order except for the following components that I installed yesterday:
- 8 GB (2x 4GB) DDR2 RAM from OWC
- OCZ Octane SATA 2.0 256 GB SSD Drive
I have a 100% clean install of OS X Snow Leopard, and all the updates have been performed.
The problem I have is the following: extremely long boot times, but only when booting after a full shutdown.
For example, during the update-restarts the computer re-booted extremely fast (as expected from an SSD).
Also, re-booting after OS X install was fast. When selecting restart from the OS, and watching the restart process, it boots very, very fast.
It's only when I'm starting up from a full shutdown that it seems like I have to wait forever, and by forever I really mean the "gear" is turning over 10 minutes (never bothered to time it, it's very, very long). It's even longer than a 'safe mode' boot (which, in my experiences, performs normally).
Does anyone have any idea what the problem could be here? I've read lots of other posts, but don't really see a similar pattern...
(I've also tried the "system preferences"-"select startup disk" item, but that doesn't help, also because the only disk in the system is the SSD...)
Thanks guys!!!

The drive worked fine booting from an external enclosure as well.
Below from a non-boot (hang) during startup:
Got boot device = IOService:/AppleACPIP...
BSD root: disk0s2, major 14, minor 2
Bug: launchctl.c:3557 (23930):6 ioctl(s6, SIOCAIFADDR_IN6, &ifra6) != -1
Running fsck on the boot volume...
Executing fsck_hfs (version diskdev_cmds-491.6~3).
launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
AppleAHCIDiskQueueManager::setPowerState(0xceb1b00, 2 -> 1) timed out after 100107 ms
When it boots slow, it hangs a bit on 'executing' and 'launchctl', but I didn't get a "timed out" before.
I just re-booted again and now I get this:
Got boot device = IOService:/Apple....
BSD root: disk0s2, major 14, minor 2
..and then it went very fast and I saw something like "fsck not needed because volume is journaled", and the desktop appeard instantly after.
Does anyone have any ideas why I'm getting such different booting patterns?

New Hard Drive, Mac partition cloned and boots fine, but I can't seem to get my BOOTCAMP (windows) partition to boot! Any ideas?

Hello all!
I got a new hard drive for my Mac Book Pro and an enclosure so I could clone the old partitions on to the new drive.
So I...
Put the new hard drive in the enclosure.
Booted up off an install disk and ran disk utility.
Copied the Mac and Bootcamp partitions over to the new drive that was connected VIA USB.
Turned off the computer, took the old hard drive out and put it in the enclosure.
Put the new hard drive in the Mac Book Pro.
Booted into Mac OSX with no problem.
When I rebooted held down the option key to boot into the windows side, it didn't show up as an option.
When I went back into the Mac side, I loaded Disk Utility and saw that I had the Mac partition, the BOOTCAMP partition, and a bunch of unallocated space. When I went into the System Preferences and set the target boot drive to the BOOTCAMP partition and restarted, I got some crazy error about there not being any bootable info on it.
That's where I am at. I have found other posts with people who are having the same problem, but I have yet to find a solution that doesn't involve me buying some 3rd party software. I know it has something to do with (what is called in Microsoft world) the Master Boot Record, but I don't know how to modify that to reflect that the BOOTCAMP partition is a bootable logical drive. I remember in MS DOS land there was some command line FDSK /something command that you would run (I think it was /MBR) to reset the MBR. To me though, all of these terms are shadowy figures in the Ether.
What do I do???
-Ricardo
p.s. I read somewhere to boot off the windows 7 disk and run the system repair tools. I tried that and no change.

I got it. It CAN be done. At least on 10.6
How I made it happen (for free) on Snow Leopard:
1) partition, dupe etc all that jazz that you know. Make the mac side work, which it seems we've all been able to do no issues. I used SuperDuper! It worked just fine. (Had it on a disk. I assume you could use any other free way of doing this.)
2) New hard drive running, I used bootcamp assistant to partition the new drive for a new Bootcamp. I don't know if it's necessary to make the new partition this way for some reason, but it's what the process ultimately included, so maybe try without, but it worked with.
3) Natively running original drive on the windows side. Used DirveImage XML to clone windows partition onto new drive connected externally.
4) Back on new hard drive running natively. (Sorry for all the switching.) You'll note that the new Bootcamp partition is NOT bootable at this point. It won't come up in the usual 'alt on startup' boot menu.
Download rEFInd and install on mac side. Technically this is freeware or w/e, but for the love of god, throw money at this man. He totally deserves it.
5) Restarting the computer, rEFInd's boot manager finally recognizes windows. But you'll find windows is a little messed up and still won't quite boot. Get out your Windows CD and pop it in. Do the 'alt boot' thing. Your boot menu options are now "EFI Manager," "Bootcamp," and "Windows Disk." Or some such. Holy Crap! It recognizes Windows!
6) Boot to the CD and tell it to repair the windows volume. It will. My computer also had to do a disk check next time I booted to Windows, which took for-stupid-ever, but eventually worked. (I went to bed in between.)
7) Everything is running smoothly. Plus, you get the rEFInd boot manager, which is also great.
Deets: I have a late 2010 MBP 13". Snow leopard/Windows 7 32-bit (long story) Moved from original 320GB seagate momentus to new 750GB Seagate Momentus XT.
Feel free to share/copy&paste this solution as you see useful. Cheers!

Boot keys stopped working after Leopard install

I have seen others having this problem in another thread but no answers, so thought I'd give it a go.
After reading these threads finally got Leopard to install and run okay. Many thanks all. But, along the way, my boot keys stopped working. It doesn't matter what I hold down, whether 'c' or 'cmd-opt-p-r' or 'shift' or any other key combination the machine just boots straight into Leopard.
I have tried resetting the PMU (or whatever it is these days) via the internal button in desperation but still no luck.
Anyone with any ideas?

Same problem here, so I'll pull this post up. No key works.
I always have to go to the Start Drive (or whatever it's called in english) in Preferences Panes and choose the partition I wish to start directly in OSX or Windows for booting back to OSX. This is very annoying. Alt key won't show up any possible boot disk although their both internal drives.
If someone would kindly post any ideas how to change that, would be great. I've done a fresh install, with a Time Machine recovery, but this didn't seem to help.
EDIT:
I found another subjet here from november '07:
http://discussions.apple.com/thread.jspa?threadID=1224639
it seems the new Apple Keyboard is the origin of the Problem on iMac Core Duo. Apple techs said that a new firmeware should be coming before the end of 2007 (but it's february 2008 now ?!?). Any other ideas how to get this work ? I'll write on Aplpe feedback page for sure. Maybe the other boot keys aren't working because of this keyboard too.
Message was edited by: Nordlaser

Apple TV, cannot activate on network, but works after

Our environment is a school. We have a Sonicwall firewall and Lightspeed for content filtering. We just purchased 50 Apple TVs.
When we first turn on the Apple TV, we join it to our wireless network. Then it gets stuck on setting date and time. It gets stuck on setting date and time no matter of we are wireless or wired.
So, I broke out my Verizon MiFi and joined the TV to the Mifi. Once on my Mifi, the TV works perfectly, sets up and rocks and rolls.
Then we take it off of the Mifi and join it bac to our network and it works perfectly.
So, we only have to use the Mifi for the first boot up and initial time sync. After that, it works on our network just fine.
Of course, I'm thinking the firewall is blocking something, but I don't know what to look for. What ports does the initial activation use that it doesn't use after that? Nothing is blocked outbound, but I'm guessing there is some return traffic that never makes it to the TV in that initial activation so I need to know what it is.
Ideas? Thoughts? Suggestions?
Thanks
Cliff

This might help:
Apple TV (2nd gen.) saw my wireless network but did not accept my password (gave a network error message). It fixed instantly doing this:
Made a note of the Apple TV's MAC address. Get it by pressing Menu on the remote, then Settings > General > About. It's called "WiFi address."
Use your browser on a network connected computer to go to your router settings (usually 192.168.1.1).
Under "Wireless > Wireless MAC Filter" (or something similar) do these steps:
Enable Wireless MAC filter
Enable "Permit PCs listed below to access the wireless network"
Enter the Apple TV's MAC address
Click "Save Setting"
When I did this the network connection immediately started working.
Note: These instructions are based on a Cisco Wireless-N Broadband, model WRT160Nv2, firmware v2.0.02.

Face Time stopped working after 10.9.5 update

Have been on with Tech support in a chat, but was unable to resolve the issue.
Now I can not get back on in a chat, the option is no longer on the screen. I am not in a location where phone calls are possible so chat is the only way to get assistance. Does anyone have any suggestions?

My challenge is that when 10.9.5 was installed, it stopped Face time from working. I can no longer log in. Get a continuous loop from log in to verify back to log in.
I have read that others have had this issue at various times over the past year, but no solution have been posted

Start and Start apps don't work after System Restore

Hey guys, I tried to install Andy (Android emulator) on my PC today and I had to reboot after the setup was complete. This time when booting up, my computer froze before login screen. I've restarted the computer several times, but no login screen.
So I used System Restore to restore my system (refresh point is 2 days old) and voila, everything works like it should...
Except for Start menu, Cortana & search bar and notifications. Restarting explorer.exe didn't fix the problem. Even Start menu apps like Music or Store don't work... Only way to open the Settings app is to click on my network connection icon. Help please!
I'm using build 9926

..............So I used System Restore to restore my system (refresh point is 2 days old)...............
It is possible that you are missing the updates that were installed in that 2 days. You rolled back 2 days, now you need to reinstall those updates.
If you cannot use Start Menu, please follow this instruction given by Insider Hub......
Checking for updates may fix this problem. To check for updates without the Start menu, do the following:
Select the Internet Explorer icon.
Type http://update.microsoft.com into the address bar and select
Enter.
If you are prompted to run a control, click
Yes or Confirm
This should bring up the Check for updates window. Install updates.
If no update is available, or the available updates don’t fix the issue, restart the device–this should make the Start menu appear. To reboot without using the Start menu:
Hold down the Windows key and select L to lock the device. Swipe up or select
Enter to open the sign in screen. Select the
Power icon on the log in screen to restart the computer.
OR
Hold down the Windows key and select R to bring up a command prompt. In the prompt, type
shutdown –r to restart
Good luck.

Touch screen not working after system update

A few months ago, my laptop (Satelitte P55t-A5202) went through an automatic system update. Ever since then, my touch screen won't work. I followed the directions to reinstall the HDI programs several times. The first time it worked but only for a few hours. The next time I tried to reinstall, it worked for a second. Now reinstalls do nothing.
Before the system update, my touchscreen worked fine. And in reading the forums, this seems to be a common problem with the updates. I called TOSHIBA customer service for help. The FIRST thing they want to do is charge me for tech support because my laptop is out of warranty. I told the customer service rep repeatedly that my touch screen worked fine until the update. He refused to give me any help because I did not want to pay for him to tell me how to resolve...
In my opinion, this is a toshiba issue not mine so regardless if my laptop is out of warranty, Toshiba should take ownership and be accountable for the problems they cause.
Does anyone have any suggestions as to how to take care of this?
By the way, Toshiba customer service representative was rude, you could barely understand him because of his accent, I had to repeat SEVERAL times what my issue was because he couldn't get past the warranty issue and I had to ask several times to speak with a supervisor ( to which he told me a supervisor would call me instead)

See my reply in the laptop forum.
-Jerry

RFC connections do not work after system restart

Hi PI experts!
We're facing a problem with our PI 7.0 system. After each restart of the system, all RFC sender communication channels do not work. When testing the connection in the sending SAP system, the connection test fails. Currently we workaround the issue by manually restarting the RFC adapter after system restart.
Does anybody has any idea how th fix that problem? <<text removed>>
Cheers,
Matthias
Edited by: Matt on Apr 29, 2009 3:26 PM - don't offer points

Mathias,
Your problem is due to the fact that SAP is not up and running when XI restarts.
there is a parameter in RFC adapter that you can modify in order to fix that
Please, see the following link and let me know: /people/community.user/blog/2006/09/21/xi-rfcadapter-reconnect-issue
best regards,
David

Suspends fails the first time, but succeeds the second time

Hi all,
I am running Arch Linux on my Dell XPS 15 9530 laptop, and overall I am very happy with the combination. I have however had some issues with suspending.
The problem is that the first time I try to suspend the machine it seems to go to sleep, but then two seconds later it automatically wakes up again. If I then immediately try again to suspend, it works (it does not wake up automatically). Does anyone know what could be going on, and how this can be fixed?
Usually I suspend from my gnome 3 desktop, but I have also tried to suspend directly using 'systemctl suspend' without having an X server running, and the result is exactly the same. I have tried a few versions of the vanilla kernel, but also the linux-lts and the linux-ck images, but to no avail.
Here is the output from dmesg, where suspend fails:
PM: Syncing filesystems ... done.
PM: Preparing system for mem sleep
bbswitch: enabling discrete graphics
Freezing user space processes ... (elapsed 0.543 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
sd 1:0:0:0: [sda] Synchronizing SCSI cache
smsc75xx 3-1:1.0 enp0s20u1: entering SUSPEND2 mode
sd 1:0:0:0: [sda] Stopping disk
Removing pn544
PM: suspend of devices complete after 334.544 msecs
PM: late suspend of devices complete after 0.201 msecs
ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
PM: noirq suspend of devices complete after 26.944 msecs
ACPI: Preparing to enter system sleep state S3
PM: Saving platform NVS memory
Disabling non-boot CPUs ...
kvm: disabling virtualization on CPU1
smpboot: CPU 1 is now offline
kvm: disabling virtualization on CPU2
smpboot: CPU 2 is now offline
kvm: disabling virtualization on CPU3
smpboot: CPU 3 is now offline
kvm: disabling virtualization on CPU4
smpboot: CPU 4 is now offline
kvm: disabling virtualization on CPU5
smpboot: CPU 5 is now offline
kvm: disabling virtualization on CPU6
smpboot: CPU 6 is now offline
kvm: disabling virtualization on CPU7
smpboot: CPU 7 is now offline
ACPI: Low-level resume complete
PM: Restoring platform NVS memory
Enabling non-boot CPUs ...
x86: Booting SMP configuration:
smpboot: Booting Node 0 Processor 1 APIC 0x2
kvm: enabling virtualization on CPU1
Intel pstate controlling: cpu 1
CPU1 is up
smpboot: Booting Node 0 Processor 2 APIC 0x4
kvm: enabling virtualization on CPU2
Intel pstate controlling: cpu 2
CPU2 is up
smpboot: Booting Node 0 Processor 3 APIC 0x6
kvm: enabling virtualization on CPU3
Intel pstate controlling: cpu 3
CPU3 is up
smpboot: Booting Node 0 Processor 4 APIC 0x1
kvm: enabling virtualization on CPU4
Intel pstate controlling: cpu 4
CPU4 is up
smpboot: Booting Node 0 Processor 5 APIC 0x3
kvm: enabling virtualization on CPU5
Intel pstate controlling: cpu 5
CPU5 is up
smpboot: Booting Node 0 Processor 6 APIC 0x5
kvm: enabling virtualization on CPU6
Intel pstate controlling: cpu 6
CPU6 is up
smpboot: Booting Node 0 Processor 7 APIC 0x7
kvm: enabling virtualization on CPU7
Intel pstate controlling: cpu 7
CPU7 is up
ACPI: Waking up from system sleep state S3
acpi LNXPOWER:01: Turning OFF
xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
PM: noirq resume of devices complete after 73.424 msecs
PM: early resume of devices complete after 0.091 msecs
mei_me 0000:00:16.0: irq 49 for MSI/MSI-X
snd_hda_intel 0000:00:03.0: irq 50 for MSI/MSI-X
snd_hda_intel 0000:00:1b.0: irq 53 for MSI/MSI-X
mei_me 0000:00:16.0: NFC MEI VERSION: IVN 0x1 Vendor ID 0x1 Type 0x1
Probing NFC pn544
ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata2.00: failed to get NCQ Send/Recv Log Emask 0x1
usb 3-1: reset high-speed USB device number 2 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
ata2.00: failed to get NCQ Send/Recv Log Emask 0x1
ata2.00: configured for UDMA/133
sd 1:0:0:0: [sda] Starting disk
usb 3-1: reset high-speed USB device number 2 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
usb 3-1: reset high-speed USB device number 2 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd75180
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd751c0
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd75200
smsc75xx 3-1:1.0 enp0s20u1: resuming from SUSPEND2
usb 3-4: reset full-speed USB device number 3 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
usb 3-4: reset full-speed USB device number 3 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
usb 3-4: reset full-speed USB device number 3 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9ac0
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9a80
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9a40
usb 3-6: reset full-speed USB device number 4 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
usb 3-6: reset full-speed USB device number 4 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
[drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
usb 3-6: reset full-speed USB device number 4 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804174ddc80
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804174ddcc0
usb 3-11: reset high-speed USB device number 6 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
usb 3-11: reset high-speed USB device number 6 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
usb 3-11: reset high-speed USB device number 6 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9480
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9440
usb 3-9: reset full-speed USB device number 5 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
usb 3-9: reset full-speed USB device number 5 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
pciehp 0000:00:1c.0:pcie04: Link Training Error occurs
pciehp 0000:00:1c.0:pcie04: Failed to check link status
dpm_run_callback(): pnp_bus_resume+0x0/0xa0 returns -19
PM: Device 00:08 failed to resume: error -19
usb 3-9: reset full-speed USB device number 5 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db000
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db040
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db080
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880417451e80
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880417451ec0
PM: resume of devices complete after 2769.054 msecs
PM: Finishing wakeup.
Restarting tasks ...
iwlwifi 0000:06:00.0: no hotplug settings from platform
rtsx_pci 0000:07:00.0: no hotplug settings from platform
done.
Bluetooth: hci0: read Intel version: 370710018002030d00
Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
video LNXVIDEO:00: Restoring backlight state
video LNXVIDEO:01: Restoring backlight state
bbswitch: disabling discrete graphics
ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
smsc75xx 3-1:1.0 enp0s20u1: link down
smsc75xx 3-1:1.0 enp0s20u1: link down
smsc75xx 3-1:1.0 enp0s20u1: kevent 4 may have been dropped
smsc75xx 3-1:1.0 enp0s20u1: link down
smsc75xx 3-1:1.0 enp0s20u1: link down
and here where suspend succeeds:
smsc75xx 3-1:1.0 enp0s20u1: kevent 4 may have been dropped
smsc75xx 3-1:1.0 enp0s20u1: link up, 100Mbps, full-duplex, lpa 0xC5E1
smsc75xx 3-1:1.0 enp0s20u1: link up, 100Mbps, full-duplex, lpa 0xC5E1
PM: Syncing filesystems ... done.
PM: Preparing system for mem sleep
bbswitch: enabling discrete graphics
Freezing user space processes ... (elapsed 0.412 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
sd 1:0:0:0: [sda] Synchronizing SCSI cache
smsc75xx 3-1:1.0 enp0s20u1: entering SUSPEND2 mode
sd 1:0:0:0: [sda] Stopping disk
Removing pn544
PM: suspend of devices complete after 780.265 msecs
PM: late suspend of devices complete after 0.387 msecs
ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
PM: noirq suspend of devices complete after 26.988 msecs
ACPI: Preparing to enter system sleep state S3
PM: Saving platform NVS memory
Disabling non-boot CPUs ...
kvm: disabling virtualization on CPU1
smpboot: CPU 1 is now offline
kvm: disabling virtualization on CPU2
smpboot: CPU 2 is now offline
kvm: disabling virtualization on CPU3
smpboot: CPU 3 is now offline
kvm: disabling virtualization on CPU4
smpboot: CPU 4 is now offline
kvm: disabling virtualization on CPU5
smpboot: CPU 5 is now offline
kvm: disabling virtualization on CPU6
smpboot: CPU 6 is now offline
kvm: disabling virtualization on CPU7
smpboot: CPU 7 is now offline
ACPI: Low-level resume complete
PM: Restoring platform NVS memory
Enabling non-boot CPUs ...
x86: Booting SMP configuration:
smpboot: Booting Node 0 Processor 1 APIC 0x2
kvm: enabling virtualization on CPU1
Intel pstate controlling: cpu 1
CPU1 is up
smpboot: Booting Node 0 Processor 2 APIC 0x4
kvm: enabling virtualization on CPU2
Intel pstate controlling: cpu 2
CPU2 is up
smpboot: Booting Node 0 Processor 3 APIC 0x6
kvm: enabling virtualization on CPU3
Intel pstate controlling: cpu 3
CPU3 is up
smpboot: Booting Node 0 Processor 4 APIC 0x1
kvm: enabling virtualization on CPU4
Intel pstate controlling: cpu 4
CPU4 is up
smpboot: Booting Node 0 Processor 5 APIC 0x3
kvm: enabling virtualization on CPU5
Intel pstate controlling: cpu 5
CPU5 is up
smpboot: Booting Node 0 Processor 6 APIC 0x5
kvm: enabling virtualization on CPU6
Intel pstate controlling: cpu 6
CPU6 is up
smpboot: Booting Node 0 Processor 7 APIC 0x7
kvm: enabling virtualization on CPU7
Intel pstate controlling: cpu 7
CPU7 is up
ACPI: Waking up from system sleep state S3
acpi LNXPOWER:01: Turning OFF
xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
PM: noirq resume of devices complete after 73.411 msecs
PM: early resume of devices complete after 0.097 msecs
mei_me 0000:00:16.0: irq 49 for MSI/MSI-X
snd_hda_intel 0000:00:03.0: irq 50 for MSI/MSI-X
snd_hda_intel 0000:00:1b.0: irq 53 for MSI/MSI-X
mei_me 0000:00:16.0: NFC MEI VERSION: IVN 0x1 Vendor ID 0x1 Type 0x1
Probing NFC pn544
ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata2.00: failed to get NCQ Send/Recv Log Emask 0x1
usb 3-4: reset full-speed USB device number 3 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
ata2.00: failed to get NCQ Send/Recv Log Emask 0x1
ata2.00: configured for UDMA/133
sd 1:0:0:0: [sda] Starting disk
usb 3-4: reset full-speed USB device number 3 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
usb 3-4: reset full-speed USB device number 3 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9ac0
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9a80
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9a40
usb 3-1: reset high-speed USB device number 2 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
usb 3-1: reset high-speed USB device number 2 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
usb 3-1: reset high-speed USB device number 2 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd75180
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd751c0
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007fd75200
smsc75xx 3-1:1.0 enp0s20u1: resuming from SUSPEND2
usb 3-9: reset full-speed USB device number 5 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
usb 3-9: reset full-speed USB device number 5 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 4.
[drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
usb 3-9: reset full-speed USB device number 5 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db000
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db040
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804181db080
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880417451e80
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880417451ec0
usb 3-6: reset full-speed USB device number 4 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
usb 3-6: reset full-speed USB device number 4 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
usb 3-6: reset full-speed USB device number 4 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804174ddc80
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804174ddcc0
usb 3-11: reset high-speed USB device number 6 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
usb 3-11: reset high-speed USB device number 6 using xhci_hcd
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 5.
pciehp 0000:00:1c.0:pcie04: Link Training Error occurs
pciehp 0000:00:1c.0:pcie04: Failed to check link status
dpm_run_callback(): pnp_bus_resume+0x0/0xa0 returns -19
PM: Device 00:08 failed to resume: error -19
usb 3-11: reset high-speed USB device number 6 using xhci_hcd
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9480
xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804148f9440
PM: resume of devices complete after 2801.389 msecs
PM: Finishing wakeup.
Restarting tasks ...
iwlwifi 0000:06:00.0: no hotplug settings from platform
rtsx_pci 0000:07:00.0: no hotplug settings from platform
done.
Bluetooth: hci0: read Intel version: 370710018002030d00
Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
video LNXVIDEO:00: Restoring backlight state
video LNXVIDEO:01: Restoring backlight state
bbswitch: disabling discrete graphics
ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
systemd[1]: Requested transaction contradicts existing jobs: File exists
systemd[1]: Service sleep.target is not needed anymore. Stopping.
smsc75xx 3-1:1.0 enp0s20u1: kevent 4 may have been dropped
smsc75xx 3-1:1.0 enp0s20u1: link down
smsc75xx 3-1:1.0 enp0s20u1: link down
It seems to me like the only real difference has to do with the xhci_hcd errors, perhaps the following:
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
Any input or help would be highly appreciated.

Rexilion wrote:Maybe you could confirm your suspicion by rmmoding xhci before suspend and modprobing it after resume?
Thanks for the response. I should have said so, but I had already tried that, but without any luck. It seems like it doesn't change anything.

[solved] Unlocking luks partitions fails at boot, no prompt.

Hello,
I have just installed Arch and I really like it so far - I'm a convert from Ubuntu. I did face a couple of problems that I have not been able to solve and have not been able to find any solutions for anywhere. The most important one at the moment is that with my two encrypted partitions.
Here's my fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
/dev/scd0 /media/dvd udf,iso9660 user,noauto,exec,utf8 0 0
/dev/sda3 / ext3 defaults 0 1
/dev/sdb1 swap swap defaults 0 0
/dev/sdb2 /home reiserfs user,owner,auto 0 0
/dev/sda6 /home/nerd/E reiserfs defaults 0 0
/dev/mapper/croot /home/nerd/F ext3 defaults 0 0
/dev/mapper/crypt /home/nerd/D ext3 defaults 0 0
and here's my crypttab:
crypt /dev/sda5 none
croot /dev/sda7 none
I have cryptsetup installed, enabled the dm-crypt and aes-i586 kernel modules, and even edited mkinitcpio and added the encrypt hook. At boot, my computer does see both of the drives, but it just doesn't prompt for passwords, what it prints out is:
Password:!unlocking encrypted volume crypt
command failed: No key available with this passphrase.
I am able to mount the drives manually using cryptsetup, and the data is there. Is there any way for me to fix that? Thanks!
Last edited by DavidR (2009-09-19 10:32:57)

afaik, you should have 'ASK' instead of 'none' in crypttab
edit: argh. too late again
Last edited by bender02 (2009-09-18 19:35:37)

[solved] lvm fails at boot time / lvm pv scan hangs (often)

Hi,
I switched from ubuntu to Archlinux two weeks ago and about half of my boot attempts fail because of some problems with my lvm-volumes
My setup
I have my root partition on /dev/sda2 and an lvm partition /dev/sda3 containing logical volumes for /var /home and /boot
If booting succeeds these volumes appear as
/dev/mapper/VolGroup01-varVol
/dev/mapper/VolGroup01-homeVol
/dev/mapper/VolGroup01-bootVol
If my booting fails, My screen shows
startin version 218
/dev/sda2: clean, blabla files, blabla blocks
A start job is running for LVM PV scan on devices 8:3
This last message (together with 3 start jobs for dev-disk-by-x2duuid-SOMENUMBERS) appears for 90 seconds and then emergency mode is started
After logging in for maintenance /dev/mapper only contains "control" but not my logical volumes
module dm_mod is loaded
dmesg does not seem to show anything related to lvm or sda3
and /var/log contains only empty files (btmp, lastlog, wtmp)
Where can I find informations about this problem?
Any suggestions how to solve this problem?
Last edited by DaAlx (2015-04-06 12:45:17)

DaAlx wrote:
Hi,
I switched from ubuntu to Archlinux two weeks ago and about half of my boot attempts fail because of some problems with my lvm-volumes
My setup
I have my root partition on /dev/sda2 and an lvm partition /dev/sda3 containing logical volumes for /var /home and /boot
If booting succeeds these volumes appear as
/dev/mapper/VolGroup01-varVol
/dev/mapper/VolGroup01-homeVol
/dev/mapper/VolGroup01-bootVol
If my booting fails, My screen shows
startin version 218
/dev/sda2: clean, blabla files, blabla blocks
A start job is running for LVM PV scan on devices 8:3
This last message (together with 3 start jobs for dev-disk-by-x2duuid-SOMENUMBERS) appears for 90 seconds and then emergency mode is started
After logging in for maintenance /dev/mapper only contains "control" but not my logical volumes
module dm_mod is loaded
dmesg does not seem to show anything related to lvm or sda3
and /var/log contains only empty files (btmp, lastlog, wtmp)
Where can I find informations about this problem?
Any suggestions how to solve this problem?
Hello,
Disclaimer: Without any logs to see what is happening, this is just an educated guess because it sounds like what happened to me. Try getting the logs during the emergency shell process.
I've run into an issue myself with LVM. From what I understand, the pvscan processes get stuck waiting for a udev sync that no longer exists because udev is restarted while pvscan processes are running in the background. There hasn't been an official solution but I modified udev hook with this (can be found in /usr/lib/initcpio/hooks/udev):
while [ "$(pgrep -f pvscan)" ]; do
sleep 0.1
done
which forces udev to wait until the LVM processes finish before telling it to die. It is hacky and poor for a long term solution because we have lvm code in the udev hook is bad design but I haven't had that issue any more.
You can also try
In /etc/mkinitcpio.conf, you must change your HOOKS list:
HOOKS="base udev autodetect modconf block lvm2 filesystems keyboard fsck" is a hook list for script
HOOKS="base systemd autodetect modconf block sd-lvm2 filesystems keyboard fsck" is a hook list for systemd
but that stopped working for a few people on 3.19.
Here is the bug report to keep you up to date:
https://bugs.archlinux.org/task/41833#comment133971
Last edited by SirMyztiq (2015-04-06 00:36:46)

Printer GPOs fail on some computers but work on others - error code 0x80070034

Hello, I have a couple of GPOs that roll our printers. They have been running smoothly for quite some time, then suddenly started giving our errors on our newer machines. Meaning, the GPOs will work fine on some clients but will not work on others. Also
all other GPOs work fine on all clients. The clients are similar Lenovo Windows 7 64-bit machines.
This is the error: Event ID: 4098, Group Policy Printers. The computer '123.123.123.123' preference item in the 'Deploy printers - {3F6DE6D0-86DC-4D1F-AB99-81BC07F23F3C}' Group Policy object did not apply because it failed with error code '0x80070034 You
were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name.' This error was suppressed.
I turned every stone I could think of on the problematic machines but cannot find out a reason. I disabled anti-virus/firewall, I logged in as domain admin and I tried both user & computer GPOs. No luck. Notice that I can successfully connect manually
to the Printer shares (the ones used to distribute the drivers).
Domain is Win2008 R2. The printers "live" on a Win2012 machine and the drivers come from there. I am using Group Policy Preferences. Ideas are welcome.
Thanks
Christos

Hello and thanks for the suggestion. Yes the drivers are okay, all clients (working and not) run the same Win 7 x64. Let me summarize the situation:
- The GPO runs because the printer IP ports are created
- The Printer Shares (that distribute the drivers) are accessible because the printer is installed without any problems/warnings if I manually double click on them (the shares)
- Security prompts for driver installs are disabled
I also noticed the following. The error says "The computer '123.123.123.123' preference item in the Group Policy object ... etc" The IP mentioned in that error is NOT the computer/client running the GPO but the IP address of the target printer.
So the client thinks the Printer already exists or the IP is already taken (or something of that sort).
Here is the GPresult XML for this
<GPO>
<Name>Printers - deploy - user</Name>
<Path>
<Identifier xmlns="http://www.microsoft.com/GroupPolicy/Types">{5C21
1010-F5E0-445C-99F3-0B8A9D9CB680}</Identifier>
<Domain xmlns="http://www.microsoft.com/GroupPolicy/Types">mydomain.com</Domain>
</Path>
<VersionDirectory>34</VersionDirectory>
<VersionSysvol>34</VersionSysvol>
<Enabled>true</Enabled>
<FilterId>MSFT_SomFilter.ID="{6272C5C1-9C4E-40B7-BD5A-277ED70B337D}",Domain="mydomain.com"</FilterId>
<FilterName>Any Win Desktop OS</FilterName>
<IsValid>true</IsValid>
<FilterAllowed>true</FilterAllowed>
<AccessDenied>false</AccessDenied>
<Link>
<SOMPath>mydomain.com/Configuration/Sites/MainOffice</SOMPath>
<SOMOrder>3</SOMOrder>
<AppliedOrder>1</AppliedOrder>
<LinkOrder>4</LinkOrder>
<Enabled>true</Enabled>
<NoOverride>false</NoOverride>
</Link>
</GPO>

Mounting partition fails at boot time, but works after system is up

Similar Messages

Maybe you are looking for