Systemd boot up errors

Hi all,
I successfully moved to systemd after the gnome 3.6 update, however I have few issues reporting during boot up that I cannot figure out nor finding information on the forum/wiki/web hence the topic.
See below journalctl outpout:
Nov 26 10:58:55 linuxbox gnome-keyring-daemon[666]: Gkm: using old keyring directory: /home/sweetth/.gnome2/keyrings
Nov 26 10:58:55 linuxbox gnome-keyring-daemon[666]: Gkm: using old keyring directory: /home/sweetth/.gnome2/keyrings
Nov 26 10:58:57 linuxbox pulseaudio[731]: [pulseaudio] source.c: Default and alternate sample rates are the same.
Nov 26 10:58:57 linuxbox pulseaudio[731]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.ListAdapters() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
Nov 26 10:58:57 linuxbox pulseaudio[731]: [pulseaudio] module.c: module-combine is deprecated: Please use module-combine-sink instead of module-combine!
Nov 26 10:58:57 linuxbox pulseaudio[731]: [pulseaudio] module-combine.c: We will now load module-combine-sink. Please make sure to remove module-combine from your configuration.
Nov 26 10:58:58 linuxbox pulseaudio[761]: [pulseaudio] pid.c: Daemon already running.
Nov 26 10:59:01 linuxbox goa[796]: goa-daemon version 3.6.2 starting [main.c:112, main()]
Nov 26 10:59:02 linuxbox gnome-keyring-daemon[666]: keyring alias directory: /home/sweetth/.gnome2/keyrings
And the output of
sudo systemctl status dbus-org.bluez.service
dbus-org.bluez.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
Many thanks for your time,
Looking forward for your comments and advices,
Regards,

I have the same question related to the keyring issue as I get the following on boot:
Nov 30 07:25:03 thinkpad gnome-keyring-daemon[676]: Gkm: using old keyring directory: /home/orschiro/.gnome2/keyrings
Nov 30 07:25:03 thinkpad gnome-keyring-daemon[676]: Gkm: using old keyring directory: /home/orschiro/.gnome2/keyrings
Nov 30 07:26:27 thinkpad gnome-keyring-daemon[676]: keyring alias directory: /home/orschiro/.gnome2/keyrings
Nov 30 07:26:44 thinkpad gnome-keyring-daemon[676]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk
Does anybody know what this mean exactly?

Similar Messages

Systemd boot is extremely "loud" with the quiet kernel parameter

Systemd boot got really slow at some point.
It prints all the messages with all the green OK status. It is extremely slow, in fact, slower that any sequential boot 20 years ago. No errors though.
Kernel parameters are as per silent boot article with quiet and log level set appropriately.
Any help is appreciated. Maybe I can fiddle with some other systemd parameters? It does not look it parallelised at all.

headkase wrote:You're welcome. Do post your Blame when you can.
Here you go...
5.339s NetworkManager-wait-online.service
1.432s man-db.service
345ms dev-sda2.device
298ms NetworkManager.service
207ms systemd-journald.service
131ms systemd-modules-load.service
129ms proc-fs-nfsd.mount
114ms logrotate.service
113ms shadow.service
109ms polkit.service
103ms upower.service
85ms systemd-journal-flush.service
83ms [email protected]
82ms systemd-random-seed.service
76ms gssproxy.service
76ms wpa_supplicant.service
73ms rpc-statd-notify.service
70ms systemd-tmpfiles-clean.service
62ms home.mount
58ms nfs-config.service
52ms systemd-udevd.service
48ms accounts-daemon.service
41ms boot.mount
36ms var-lib-nfs-rpc_pipefs.mount
31ms systemd-udev-trigger.service
29ms colord.service
28ms udisks2.service
25ms systemd-sysctl.service
25ms gdm.service
20ms systemd-tmpfiles-setup.service
20ms systemd-logind.service
19ms systemd-update-utmp.service
17ms systemd-remount-fs.service
15ms sys-kernel-debug.mount
15ms [email protected]
12ms tmp.mount
10ms dev-hugepages.mount
9ms dev-mqueue.mount
8ms systemd-tmpfiles-setup-dev.service
8ms systemd-vconsole-setup.service
6ms kmod-static-nodes.service
5ms sys-fs-fuse-connections.mount
5ms rtkit-daemon.service
4ms systemd-user-sessions.service
4ms systemd-backlight@backlight:acpi_video0.service
2ms [email protected]
2ms [email protected]
1ms systemd-backlight@backlight:intel_backlight.service
1ms sys-kernel-config.mount
Please use code text when posting snippets -- Inxsible
Last edited by Inxsible (2015-05-01 14:26:02)

R61 R&R won't start after "unmountable boot volume" error

Hello all,
New user, first post - after problem, of course.
I have an R61 Thinkpad with Windows XP on it. (SP2 or SP3, not sure). Has worked flawlessly for years, then the other day I got the dreaded "unmountable boot volume" error and it would not start.
No problem - I re-start, hit the ThinkVantage button, then hit F11 to use the R&R hidden on a separate partition of the hard drive........I get the black screen with the big progress bar, ok, then a blue screen......then nothing. Hangs up and sits there. I have repeated this about 5 times now.
No problem! - I was smart enough to make an R&R CD set a while ago! Put the primary R&R disk in the CD drive, start the machine, ThinkPad button, F12 this time to choose boot from CD.....much CD activity ensues and I once again get the black screen with the big progress bar. It takes much longer, and I get teh blue screen - BUT - then it goes one extra step to display the "ThinkVantage Rescue & Recovery 4" screen with the life preserver image.
Excellent, I thing - except it then hangs there. Just sits there. No disk activity. No keys will do anything.
I can find no threads here or on any other forum with this particular issue.
Am I fubar? Or is there something else I can do?
Thanks a bunch.
Solved!
Go to Solution.

Hi jim, welcome to the forums,
Is the hard drive recognised in BIOS, was there an entry in the boot list against HDD0?
Regardless of it being shown in BIOS / boot list or not, the first thing I would do is to reseat the hard drive and see if that helps, maybe over time it's lost contact to the mainboard socket. If you don't know how to do this you can find out at the R61 movies site.
The next thing I would do is run a hard drive diagnosis check from a bootable cd, these can be downloaded from all HDD manufacturer's websites e.g. Hitachi's Drive Fitness Test. It may be that the drive has simply gone bad after all those years of work.
Let us know how you get on
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog

Unmountable Boot Volume error in Z61T

Hi Members,
I just encountered the the Error Unmountable Boot volume error(Blue Screen) in my Z61T Think pad laptop.
I'm not sure what caused this error. Is it possible to fix the error?
I tried to go in to Recovery Console using XP CD and then repair the OS, but unfortunately when i go to repair mode i get another error which says unable to recognize the hard drive. Im really confused as of what is the exact problem with my laptop and also im worried about that data.
appreciate if anyone can throw some light in to the issue and help me out in fixing the same.
Thanks
Rajesh

If you believe that your hard disk/file system may be corrupted, try using any bootable diagnostic cd.They are operating system independent and will let you know if your HDD is getting corrupted.
Try the data life guard diagnostics(bootable).
Cheers and regards,
• » νιנαｿѕαяα∂нι ѕαмανє∂αм ™ « •
●๋•کáŕádhí'ک díáŕý ツ
I am a volunteer here. I don't work for Lenovo

Hp mini 110 boot disk error after installing new hard drive and system recovery

Need help, HP mini 110 Windows 7 32 bit. using my recovery disks I created i was able to recover to the old 160 gb hard drive. After I installed new 320 Gig drive and used my recovery disks i now get boot disk error. Looks like system was installed on new drive. but will not boot to complete set up.

If you use the recovery disk, your machine will restore to its default factory state. Try to reinstall the 320 GB you have if you want it to get back.
Can't get enough of this Envy...

No Bootable Device - Insert Boot Disk Error...

Ok so today I installed Windows 7 Ultimate 64-Bit on my 750GB Toshiba HDD in my Optibay and was installed successfully, installed all the Drivers from Windows Support flash drive and when I try to reboot into Windows 7 I get the "No Bootable Device - Insert Boot Disk Error" everytime!! lol What the heck is going on here??
Specs:

lennarts wrote:
So, I encountered the same problem...
When I click the icon in bootcamp to install windows, after a bit of activity the Windows installation disc was spit put, the screen goes black and the error "No Bootable Device Insert Book Disk Press Any Key to Continue" appears on the screen. And nothing else but using the OSX installation disc helps.
I realised that the windows installation disc did not even spin up.
So what I did... I went back to OSX, reinserted windows installation disc, went to system preferences, selected the windows cd as a start up disc and locked it against the changes.
After that I went back to bootcamp and clicked gain to install windows. Everything worked fine now.
I just tried this and it didn't work for me. I keep getting a black screen with a cursor flashing in the upper left hand corner.

Boot camp error loading operating system

when i hit restart and held down option, i clicked on windows but it loaded a black screen saying error loading operating system. I am running Os X 10.9.4. Does anyone know why boot camps is not working?

Loner T, not sure if you saw this, but I created a new post with the information you were looking for. Any help you could provide would be great...thanks.
Re: Boot camp - error loading operating system

All Windows I Install return boot\bcd error

Have a l645d-s4040.
Im Lost now.. I've read many threads similar to my problem, or exactly like my problem. Ive tried it all, and done at least 12 Different installs. heres the info:
Bought it brand new, was unaware of making the restoration disks until it was too late.
I had a virus, so I did "clean all" in diskpart, at the cmd prompt. So i can start fresh. I have a retail version of Windows 7 Home Premium 64 bit, which was the original OS. went through the installation process fine, until the reboot where its supposed to go through the second step of the installation. on reboot i get a "bcd\boot" error. Ive tried repairing the MBR, the Boot record, ive tried using align=1024, ive tried using paragon, and acronis to fix the boot record. Ive tried using boot managers. Ive tried installing windows vista, ive tried windows 7 ultimate 64 and 32 bit versions.. the only OS i can get to install is XP.. Im at a loss
of course of done : Startup Repair (http://www.sevenforums.com/tutorials/681-startup-repair.html)
So after the first step of of installation, which goes fine then reboots to continue the installation i get:
Windows Boot Manager
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. Insert your Windows installation disc and restart your computer.
2. Choose your language settings, and then click “Next.”
3. Click “Repair your computer.”
If you do not have this disc, contact your system administrator or computer manufacturer for assistance.
File: \Boot\BCD
Status: 0xc000000f
Info: An error occurred while attempting to read the boot configurations data.
Enter= Continue ESC=Exit
so i reboot with the install cd. which i downloaded from www.mydigitallife.info/windows-7-iso-x86-and-x64-official-direct- download-links-ultimate-professional-and-home-premium/.
And ran the startup repair, first time no OS found and failed to save startup options. rebooted and this time the repair worked and it booted fine running the 2nd step of the installation process.. on the reboot i got same boot\bcd error.. so i repeated the repair steps above.. it finally booted and finalized the installation.. i got to the desktop fine and installed all my drivers. when i rebooted i got the same error.
WHATS UP WITH THIS???

Satellite L645D-S4040
I would restore the hard disk to its original out-of-the-box contents using Toshiba recovery media, which you can obtain from Toshiba.
Order Toshiba Recovery Media
-Jerry

Logging all file opens immediately at systemd boot?

when I start my stage-2 systemd boot, I want to log every file that is being opened for reading or writing (to /var/log/accessed.log). am I reinventing the wheel if I write this or is there already a standard service that does this?
my plan is to use the fanotify_event framework to write a file logger, presumably with a service file like.
[Unit]
Description=fanotify-logger
DefaultDependencies=no
After=local-fs.target
[Service]
Type=oneshot
ExecStart=/usr/local/bin/fanotify-all / /var/log/accessed.log
is there a best-practices recommendation where local sysadmins should insert such services (e.g., which directory, steps, etc.) and, does my logger need to know how to shutdown, or will the standard systemd service shut this down by itself?
/iaw

You used to be able to do this with boot.kernel.org, but not anymore.
pxelinux.0 isn't the kernel, and you can only use it if you have an actual pxe installation available which I don't think is there at releng.archlinux.org.
You have to install your own pxe setup and yes it does use NFS.
If you are using qemu you don't even need the ipxe, it is already included with qemu.
Last edited by nomorewindows (2012-08-03 23:42:16)

Pavillion Boot Disk Error

My son's Pavilion g6 has two users, his and mine. When I log in as mine, the computer seems to work fine, in and out of Safe Mode. When I log in as his user, I get the blue screen data dump, then a boot disk error. Here is what I have tried:
Restore on my user
Windows security scan (which didn't finish before shutting down)
Booting with Safe Mode on his user (didn't work)
Took out the hard disk, sprayed with compressed air and reinserted the hard drive
What options do I have? Can I delete his user? Could it be a virus? I am stumped.
I can get to all of his files but I can't stay logged on with his user.
Thanks.

Yes you can delete his user account and create a new one. Just be sure to copy his files if he has stuff he doesn't want to lose. Restart the machine before trying o create a new user account for him.
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

MacBook Air will not boot. Error Message says "Your Computer restarted because of a problem."

MacBook Air will not boot. Error Message says "Your Computer restarted because of a problem."

If you can't start up and log in in the usual way, try in safe mode.
During startup, you’ll see a progress bar, and then the login screen, which appears even if you normally log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Log in as an administrator to carry out these instructions. If you have only one account, you are the administrator.
If you don't see any reports listed, but you know there was a panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
Safe mode is slower than normal, and some things won’t work at all.
Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t start in safe mode.
If you're able to log in, launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
In the Console window, select
DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar.
There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A panic report has a name that begins with "Kernel" and ends in ".panic". Select the most recent one. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report.

[SOLVED] Borked systemd setup -- dbus errors during boot; can't login

I have error messages very similar to this post. Unfortunately, as the author states, he never persisted in solving it but instead re-installed from scratch. I'd rather not do that.
For reference, I have a pure systemd setup -- no rc.conf file, no initscripts package, etc.
At boot I get the "Welcome to Arch!" messages followed by the various [OK] lines and then I get blindingly fast repeating lines about dbus not starting and attempting to restart it too quickly. If I walk away for about 1-2min, I finally see a login screen, but after entering my username/password, it just sits there and does nothing.
As for suspects... I had systemd working fine.
-- I updated some packages (not more than a few days worth and I'd have to check the list)
-- I also took care of manual updates to some .pacnew files I periodically check for. In this group were some biggies: group, shadow, and passwd. I did recall the odd bit about uuidd changing from uid 995 to 68, but in reading about that since then, it doesn't seem to be a big deal.
I've been booting in by appending
systemd.unit=emergency.target
to the kernel line, but my exploration hasn't been all that helpful. `journalctl since=date` reveals the errors, but I don't get much information about why dbus is having issues starting.
emergency.target also doesn't seem to be that helpful since I can't do anything with a read-only system. I'd love some suggestions about what, specifically, to check for before I reboot from Windows back into Arch and record more careful notes, probably by jotting notes onto a flash drive. Any places to start? For reference, I've done:
-- systemctl status dbus: lists as inactive (dead) and simply shows the errors I see at boot (failed to start)
-- systemctl list-units
-- systemctl list-unit-files
-- journalctl and looking around for instances of fail or failed or dbus
If I start systemd-logind.service or dbus.service, it displays a status message about running fsck and then takes me to a login prompt automatically. Then I can type in my username and password and then there's nothing after that. No prompt, just an apparent hang.
Thanks for any suggestions -- I'll take them and then collect more detailed results and report back.
Thanks!
Last edited by jwhendy (2012-11-08 16:07:33)

As I wondered, I think it's a problem with passwd. I don't have a dbus entry and must have missed it when I was copying things around between my version and the .pacnew. Downloading an install disc now since I can't seem to change it from the recovery console due to mounting root read-only.
I'd love to know of a way to boot that avoids starting dbus and other things that might break while still having read/write access to root. Will mark solved once I update /etc/passwd and reboot.

Boot\BCD error - SCCM 2012 R2

Hi,
This is a last ditch attempt before I throw in the towel and rebuild the server.
I am running an SCCM 2012 R2 Hierarchy with two primaries and multiple distribution points.
One of our main DPs has started coming up with an error when pxe booting a windows 7 machine. This happened after a corrupt driver was added to the boot image. The driver was removed and all the DP's rolled back but the issue still remains on this server
alone. We use an IPhelper to point the pxe requests at this server.
The error message is:
File: \Boot\BCD
Status: 0xc0000098
Info: The Windows Boot Configuration Data file does not contain a valid OS entry.
I have tried the following:
1. Removing the PXE role and reapplying it.
2. Removing the Boot images and reapplying them.
3. Removing the DP altogether from the console and reapplying.
4. Removing all data from the DP and starting again.
5. Redistributing the boot images. both x86 and x64
6. creating a new boot image for both x86 and x64 and applying those.
smspxe log is as follows
D4:3D:7E:BF:11:A4, 00000000-0000-0000-0000-D43D7EBF11A4: device is not in the database.
SMSPXE 20/10/2014 09:30:44
5064 (0x13C8)
Warning: Matching Processor Architecture Boot Image (0) not found
SMSPXE 20/10/2014 09:30:44
5064 (0x13C8)
D4:3D:7E:BF:11:A4, 00000000-0000-0000-0000-D43D7EBF11A4: Not serviced.
SMSPXE 20/10/2014 09:30:44
5064 (0x13C8)
Warning: Matching Processor Architecture Boot Image (0) not found
SMSPXE 20/10/2014 09:31:04
5064 (0x13C8)
D4:3D:7E:BF:11:A4, 00000000-0000-0000-0000-D43D7EBF11A4: Not serviced.
SMSPXE 20/10/2014 09:31:04
5064 (0x13C8)
Begin validation of Certificate [Thumbprint C435C200EAF495312097132FFE12CF330A54DA8A] issued to '3ed87d92-4f15-4d7d-ba52-35dc6b972484'
SMSPXE 20/10/2014 09:33:20
2208 (0x08A0)
Completed validation of Certificate [Thumbprint C435C200EAF495312097132FFE12CF330A54DA8A] issued to '3ed87d92-4f15-4d7d-ba52-35dc6b972484'
SMSPXE 20/10/2014 09:33:20
2208 (0x08A0)
Begin validation of Certificate [Thumbprint C435C200EAF495312097132FFE12CF330A54DA8A] issued to '3ed87d92-4f15-4d7d-ba52-35dc6b972484'
SMSPXE 20/10/2014 10:33:20
5012 (0x1394)
Completed validation of Certificate [Thumbprint C435C200EAF495312097132FFE12CF330A54DA8A] issued to '3ed87d92-4f15-4d7d-ba52-35dc6b972484'
SMSPXE 20/10/2014 10:33:20
5012 (0x1394)
Found new image CAS00004 SMSPXE
20/10/2014 10:53:11 6076 (0x17BC)
ADK installation root registry value not found.
SMSPXE 20/10/2014 10:53:11
6076 (0x17BC)
Loaded C:\Windows\system32\wimgapi.dll SMSPXE
20/10/2014 10:53:11 6076 (0x17BC)
Opening image file D:\RemoteInstall\SMSImages\CAS00004\boot.CAS00004.wim
SMSPXE 20/10/2014 10:53:11
6076 (0x17BC)
Found Image file: D:\RemoteInstall\SMSImages\CAS00004\boot.CAS00004.wim
PackageID: CAS00004
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
SMSPXE
20/10/2014 10:53:11 6076 (0x17BC)
Closing image file D:\RemoteInstall\SMSImages\CAS00004\boot.CAS00004.wim
SMSPXE 20/10/2014 10:53:11
6076 (0x17BC)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 10:53:40
6076 (0x17BC)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 10:53:40
6076 (0x17BC)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 10:58:12
4928 (0x1340)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 10:58:12
4928 (0x1340)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 10:59:07
4928 (0x1340)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 10:59:07
4928 (0x1340)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:00:05
4928 (0x1340)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:00:05
4928 (0x1340)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:05:24
4928 (0x1340)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:05:24
4928 (0x1340)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:06:05
4928 (0x1340)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:06:05
4928 (0x1340)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:07:15
4928 (0x1340)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:07:15
4928 (0x1340)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:07:58
4928 (0x1340)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:07:58
4928 (0x1340)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:09:31
4664 (0x1238)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:09:31
4664 (0x1238)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:11:58
4664 (0x1238)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:11:58
4664 (0x1238)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:13:52
4664 (0x1238)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:13:52
4664 (0x1238)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE
20/10/2014 11:15:27 5064 (0x13C8)
E8:03:9A:B3:F3:8A, 163A84E0-1DD8-11B2-8000-DF82815C2DDB: device is not in the database.
SMSPXE 20/10/2014 11:15:27
5064 (0x13C8)
Getting boot action for unknown machine: item key: 2046820364
SMSPXE 20/10/2014 11:15:27
5064 (0x13C8)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820364" ServerName=""><Machine><ClientID>47938388-164c-4bfb-8621-28b57859ad3c</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="PNL20009" OfferIDTime="26/02/2014 15:13:00" PkgID="PNL0000C" PackageVersion="" PackagePath="http://INTCMNCLDP001.intraining.co.uk/SMS_DP_SMSPKG$/CAS00004"
BootImageID="CAS00004" Mandatory="0"/></ClientIDReply>
SMSPXE
20/10/2014 11:15:27 5064 (0x13C8)
E8:03:9A:B3:F3:8A, 163A84E0-1DD8-11B2-8000-DF82815C2DDB: found optional advertisement PNL20009
SMSPXE 20/10/2014 11:15:27
5064 (0x13C8)
Getting boot action for unknown machine: item key: 2046820364
SMSPXE 20/10/2014 11:16:14
5064 (0x13C8)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820364" ServerName=""><Machine><ClientID>47938388-164c-4bfb-8621-28b57859ad3c</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="PNL20009" OfferIDTime="26/02/2014 15:13:00" PkgID="PNL0000C" PackageVersion="" PackagePath="http://INTCMNCLDP001.intraining.co.uk/SMS_DP_SMSPKG$/CAS00004"
BootImageID="CAS00004" Mandatory="0"/></ClientIDReply>
SMSPXE
20/10/2014 11:16:14 5064 (0x13C8)
E8:03:9A:B3:F3:8A, 163A84E0-1DD8-11B2-8000-DF82815C2DDB: found optional advertisement PNL20009
SMSPXE 20/10/2014 11:16:14
5064 (0x13C8)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:26:15
4664 (0x1238)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:26:15
4664 (0x1238)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:27:12
4664 (0x1238)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:27:12
4664 (0x1238)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:27:25
4664 (0x1238)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:27:25
4664 (0x1238)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:28:36
4664 (0x1238)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:28:36
4664 (0x1238)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:29:41
4664 (0x1238)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:29:41
4664 (0x1238)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:30:43
4664 (0x1238)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:30:43
4664 (0x1238)
Begin validation of Certificate [Thumbprint C435C200EAF495312097132FFE12CF330A54DA8A] issued to '3ed87d92-4f15-4d7d-ba52-35dc6b972484'
SMSPXE 20/10/2014 11:33:20
4664 (0x1238)
Completed validation of Certificate [Thumbprint C435C200EAF495312097132FFE12CF330A54DA8A] issued to '3ed87d92-4f15-4d7d-ba52-35dc6b972484'
SMSPXE 20/10/2014 11:33:20
4664 (0x1238)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:33:51
4664 (0x1238)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:33:51
4664 (0x1238)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:35:31
4664 (0x1238)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:35:31
4664 (0x1238)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:37:29
6076 (0x17BC)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:37:29
6076 (0x17BC)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:39:25
6076 (0x17BC)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:39:25
6076 (0x17BC)
================= PXE Provider shutdown. =====================
SMSPXE 20/10/2014 11:42:25
4700 (0x125C)
================= PXE Provider loaded. =====================
SMSPXE 20/10/2014 11:43:19
4372 (0x1114)
Machine is running Windows Longhorn. (NTVersion=0X603, ServicePack=0)
SMSPXE 20/10/2014 11:43:19
4372 (0x1114)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:43:19
4372 (0x1114)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:43:19
4372 (0x1114)
Begin validation of Certificate [Thumbprint C435C200EAF495312097132FFE12CF330A54DA8A] issued to '3ed87d92-4f15-4d7d-ba52-35dc6b972484'
SMSPXE 20/10/2014 11:43:19
4372 (0x1114)
Completed validation of Certificate [Thumbprint C435C200EAF495312097132FFE12CF330A54DA8A] issued to '3ed87d92-4f15-4d7d-ba52-35dc6b972484'
SMSPXE 20/10/2014 11:43:19
4372 (0x1114)
Initializing PXEPerfObject. SMSPXE
20/10/2014 11:43:19 4372 (0x1114)
Could not load logging configuration for component ccmperf. Using default values.
SMSPXE 20/10/2014 11:43:19
4372 (0x1114)
HTTP is selected for Client. The current state is 0.
SMSPXE 20/10/2014 11:43:19
4372 (0x1114)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE
20/10/2014 11:43:20 4372 (0x1114)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE
20/10/2014 11:43:20 4372 (0x1114)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE
20/10/2014 11:43:20 4372 (0x1114)
Adding CAS00004.40 SMSPXE
20/10/2014 11:43:20 4372 (0x1114)
Adding CAS00005.45 SMSPXE
20/10/2014 11:43:30 4372 (0x1114)
Found new image CAS00004 SMSPXE
20/10/2014 11:43:44 4372 (0x1114)
ADK installation root registry value not found.
SMSPXE 20/10/2014 11:43:44
4372 (0x1114)
Loaded C:\Windows\system32\wimgapi.dll SMSPXE
20/10/2014 11:43:44 4372 (0x1114)
Opening image file D:\RemoteInstall\SMSImages\CAS00004\boot.CAS00004.wim
SMSPXE 20/10/2014 11:43:44
4372 (0x1114)
Found Image file: D:\RemoteInstall\SMSImages\CAS00004\boot.CAS00004.wim
PackageID: CAS00004
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
SMSPXE
20/10/2014 11:43:44 4372 (0x1114)
Closing image file D:\RemoteInstall\SMSImages\CAS00004\boot.CAS00004.wim
SMSPXE 20/10/2014 11:43:44
4372 (0x1114)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:44:34
2028 (0x07EC)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:44:34
2028 (0x07EC)
Found new image CAS00005 SMSPXE
20/10/2014 11:44:56 4372 (0x1114)
ADK installation root registry value not found.
SMSPXE 20/10/2014 11:44:56
4372 (0x1114)
Loaded C:\Windows\system32\wimgapi.dll SMSPXE
20/10/2014 11:44:56 4372 (0x1114)
Opening image file D:\RemoteInstall\SMSImages\CAS00005\boot.CAS00005.wim
SMSPXE 20/10/2014 11:44:56
4372 (0x1114)
Found Image file: D:\RemoteInstall\SMSImages\CAS00005\boot.CAS00005.wim
PackageID: CAS00005
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
SMSPXE
20/10/2014 11:44:56 4372 (0x1114)
Closing image file D:\RemoteInstall\SMSImages\CAS00005\boot.CAS00005.wim
SMSPXE 20/10/2014 11:44:57
4372 (0x1114)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:45:45
2028 (0x07EC)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:45:45
2028 (0x07EC)
Begin validation of Certificate [Thumbprint C435C200EAF495312097132FFE12CF330A54DA8A] issued to '3ed87d92-4f15-4d7d-ba52-35dc6b972484'
SMSPXE 20/10/2014 11:45:54
4372 (0x1114)
Completed validation of Certificate [Thumbprint C435C200EAF495312097132FFE12CF330A54DA8A] issued to '3ed87d92-4f15-4d7d-ba52-35dc6b972484'
SMSPXE 20/10/2014 11:45:54
4372 (0x1114)
PXE Provider finished loading. SMSPXE
20/10/2014 11:45:54 4372 (0x1114)
Error opening file: D:\RemoteInstall\SMSImages\CAS00005\boot.CAS00005.wim. Win32=32
SMSPXE 20/10/2014 11:46:33
4744 (0x1288)
Retrying D:\RemoteInstall\SMSImages\CAS00005\boot.CAS00005.wim
SMSPXE 20/10/2014 11:46:33
4744 (0x1288)
Boot image CAS00005 has changed since added
SMSPXE 20/10/2014 11:46:36
4744 (0x1288)
ADK installation root registry value not found.
SMSPXE 20/10/2014 11:46:36
4744 (0x1288)
Loaded C:\Windows\system32\wimgapi.dll SMSPXE
20/10/2014 11:46:36 4744 (0x1288)
Opening image file D:\RemoteInstall\SMSImages\CAS00005\boot.CAS00005.wim
SMSPXE 20/10/2014 11:46:36
4744 (0x1288)
Found Image file: D:\RemoteInstall\SMSImages\CAS00005\boot.CAS00005.wim
PackageID: CAS00005
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
SMSPXE
20/10/2014 11:46:36 4744 (0x1288)
Closing image file D:\RemoteInstall\SMSImages\CAS00005\boot.CAS00005.wim
SMSPXE 20/10/2014 11:46:36
4744 (0x1288)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:46:53
2028 (0x07EC)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:46:53
2028 (0x07EC)
Boot image CAS00005 has changed since added
SMSPXE 20/10/2014 11:47:50
4744 (0x1288)
ADK installation root registry value not found.
SMSPXE 20/10/2014 11:47:50
4744 (0x1288)
Loaded C:\Windows\system32\wimgapi.dll SMSPXE
20/10/2014 11:47:50 4744 (0x1288)
Opening image file D:\RemoteInstall\SMSImages\CAS00005\boot.CAS00005.wim
SMSPXE 20/10/2014 11:47:50
4744 (0x1288)
Found Image file: D:\RemoteInstall\SMSImages\CAS00005\boot.CAS00005.wim
PackageID: CAS00005
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
SMSPXE
20/10/2014 11:47:50 4744 (0x1288)
Closing image file D:\RemoteInstall\SMSImages\CAS00005\boot.CAS00005.wim
SMSPXE 20/10/2014 11:47:50
4744 (0x1288)
================= PXE Provider shutdown. =====================
SMSPXE 20/10/2014 11:47:58
4372 (0x1114)
================= PXE Provider loaded. =====================
SMSPXE 20/10/2014 11:48:26
5008 (0x1390)
Machine is running Windows Longhorn. (NTVersion=0X603, ServicePack=0)
SMSPXE 20/10/2014 11:48:26
5008 (0x1390)
Cannot read the registry value of MACIgnoreListFile (00000000)
SMSPXE 20/10/2014 11:48:26
5008 (0x1390)
MAC Ignore List Filename in registry is empty
SMSPXE 20/10/2014 11:48:26
5008 (0x1390)
Begin validation of Certificate [Thumbprint C435C200EAF495312097132FFE12CF330A54DA8A] issued to '3ed87d92-4f15-4d7d-ba52-35dc6b972484'
SMSPXE 20/10/2014 11:48:26
5008 (0x1390)
Completed validation of Certificate [Thumbprint C435C200EAF495312097132FFE12CF330A54DA8A] issued to '3ed87d92-4f15-4d7d-ba52-35dc6b972484'
SMSPXE 20/10/2014 11:48:26
5008 (0x1390)
Initializing PXEPerfObject. SMSPXE
20/10/2014 11:48:26 5008 (0x1390)
Could not load logging configuration for component ccmperf. Using default values.
SMSPXE 20/10/2014 11:48:26
5008 (0x1390)
HTTP is selected for Client. The current state is 0.
SMSPXE 20/10/2014 11:48:26
5008 (0x1390)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE
20/10/2014 11:48:26 5008 (0x1390)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE
20/10/2014 11:48:26 5008 (0x1390)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE
20/10/2014 11:48:26 5008 (0x1390)
Adding CAS00004.40 SMSPXE
20/10/2014 11:48:26 5008 (0x1390)
Adding CAS00005.45 SMSPXE
20/10/2014 11:48:50 5008 (0x1390)
Found new image CAS00004 SMSPXE
20/10/2014 11:49:15 5008 (0x1390)
ADK installation root registry value not found.
SMSPXE 20/10/2014 11:49:15
5008 (0x1390)
Loaded C:\Windows\system32\wimgapi.dll SMSPXE
20/10/2014 11:49:15 5008 (0x1390)
Opening image file D:\RemoteInstall\SMSImages\CAS00004\boot.CAS00004.wim
SMSPXE 20/10/2014 11:49:15
5008 (0x1390)
If anyone has any further info on this please can you let me know?
Thanks so much.
Katie

Hello,
Is your WDS running properly? If WDS is stopped, can you start it manually?
Or you get an error like 'The service did not respond in a timely fashion'?
The symptom is so similar to that I have encountered. You referred that you have tried to remove WDS, DP, but I wonder how. Before removing WDS and DP role, try to delete corrupt package in SCCMContentLib folder.
I just recreated SCCMContentLib, and WDS did start working. I guess there are corrupt packages in the my folder as well. But another problem occur, I installed all the roles on the same server in my lab, so it is a primary site server as well. As a result,
it seems that I have to re-deploy all the packages. Not sure if there is any further problem yet. Since it is just a lab environment, it doesn't matter for me.
I hope what I have done will give you some clue.

LVM /dev/mapper is empty, + systemd boot hangs

Hi!
1st problem:
I have 2 vgs with 1 lv each -- called Sys/Linux and Sys2/Var. Booting the kernel with root=/dev/mapper/Sys-Linux works, but after mounting the root fs, /dev/mapper is empty:
$ ls /dev/mapper
control
2nd problem:
I changed UUID= to /dev/dm-1 for /var for testing purposes, but systemd will timeout on mounting /var. Note: after entering the emergency console, I can just type mount /var and it will mount.
The system is was quite old and I changed to systemd-only right now, because I upgraded the filesystem package (that removes /bin, /sbin, /usr/sbin and required me to remove outdated packages). ((Yes, I'm late )).
I hope anyone has some pointers; please tell me, which config files you need to see if any, to help out.
Thanks,
Andy
Last edited by Black Sliver (2013-08-12 20:14:40)

[2013-08-12 19:33] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-08-12 19:33] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Starting build: 3.10.5-1-ARCH
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [lvm2]
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> ERROR: file not found: `/usr/sbin/dmsetup'
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [resume]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [shutdown]
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Creating lzma initcpio image: /boot/initramfs-linux.img
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Starting build: 3.10.5-1-ARCH
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [lvm2]
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> ERROR: file not found: `/usr/sbin/dmsetup'
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [resume]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [shutdown]
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Creating lzma initcpio image: /boot/initramfs-linux-fallback.img
[2013-08-12 19:34] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
Note that initial mounting of root=/dev/mapper/Sys-Linux works. Can this be the problem anyway? I rebuilt the initrd, I'll try to boot it tomorrow.
[2013-08-12 19:42] [PACMAN] Running 'pacman -R initscripts sysvinit' # NOTE: this was required for the filesystem upgrade to work (/sbin)
[2013-08-12 19:42] [ALPM] warning: /etc/rc.conf saved as /etc/rc.conf.pacsave
[2013-08-12 19:42] [ALPM] warning: /etc/inittab saved as /etc/inittab.pacsave
Theese are not required with systemd ?
Everything else is just upgrade/install/remove or uninteresting. Or do you want to see everything?
Last edited by Black Sliver (2013-08-12 22:48:32)

Annoying systemd boot mounting behaviour?

Id like to change behaviour..
Currently....
When you have some unmountable entry at fstab, it wont let you boot in the system, even if it were an usb? I experienced that with a secondary harddrive. (or maybe it did not boot because there is a swap on the second hdd)
If systemd really does not boot in to the login prompt,because ofunmountable entry in fstab,can it be changed ?

thisoldman wrote:
Add 'nofail' to the mount options for the USB drive in your fstab.
From 'man mount':
nofail Do not report errors for this device if it does not exist.
Owe thanks This bugged the crap out of me too.
Awebb wrote:Curious. I remember the same effect a year ago. Maybe you had some other configurations done preventing this behavior in the past.
No, initscripts do not have this problem.
Last edited by hunterthomson (2012-12-25 01:54:50)

Systemd boot up errors

Similar Messages

Maybe you are looking for