Fix - Journaled partition fails to mount (journal magic error)

Before trying to repair or recover a 'Mac OS Extended (Journaled)' disk or partition that fails to mount in the Finder, check whether it is just the journal file that is corrupted. If the partition appears in Disk Utility, the fix is to turn off Journaling. If the partition can now be mounted and your files are present, the problem is solved and journaling can be reenabled.
To confirm a problem with the journal search for console error messages with "journal magic" that occur when tring to mount the partition.
In Disk Utility select the partition that will not mount, hold the Option key and select 'Disable Journaling' in the File menu drop down. It will take a few seconds to complete. Now mount the partition using the Mount button or the File menu. To turn journaling back on (recreating a clean journal file), select Enable Journaling from the File menu or the green toolbar button. (This can also be done through Terminal with the diskutil command. See https://discussions.apple.com/message/12838806#12838806 and search on "journal magic" for details.)
I spent two days trying to recover my data from an external drive. Neither Disk Utility or Disk Warrior 4.4 was able to repair this problem. DU said the partition could not be repaired and DW failed with an "insufficient memory error (2154)". Of course your problem could be a more sever corruption, or the disk does not appear at all in DU, but this is easy to try first.
Hope this is helpful.

Let me be more specific
W2000 SP4 server, MacBook client, trying to mount shared volume thru SMB
-on the same subnet (i.e. lappy next to the server on the same switch) both mount_smbfs and smbclient work OK
-from home smbclient is working, mount_smbfs does not (Err -36)
-from home my wife can mount the shared volume thru Network Neighbours on her XP notebook
-it does not seem to be TCP/IP related - all comp can make FTP or VNC to the server verywhere
-err log of mount_smbfs is "negotiate phase failed: syserr Operation timed out in the console", no idea is there a way to verbose mount_smbfs
-smb.conf looks basic...secure passwords=enable, no nsmb.conf
-W2000 SP4 sever is all default secure policies, running FTP server w/o any issues.
So is there a key on server...or the client which I have to tweak?
Thank you.
MB 2.0 Mac OS X (10.4.9)
MB 2.0 Mac OS X (10.4.9)

Similar Messages

I'm trying to update to Firefox 4.0 on an IMac 10.2.8 but get error: Firefox 4.0 Beta11.dmg failed to mount due to error 95. (no mountable file system). Can someone help?

No details. This is the only message I get every time I try to upgrade.

To use Firefox 4 you need at least OS X 10.5 and an Intel Mac.
The last version of Firefox that works on OS X 10.2.8 is Firefox 2.0.0.20 available from ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/2.0.0.20/mac/en-US/

After fixing drive partition numbers, got error

Hi,
After fixing drive partition numbers, I got the following error from cfdisk:
FATAL ERROR: Bad logical partition 6: enlarged logical partitions overlap
Press any key to exit cfdisk
However, I can see all my partitions with fdisk and gparted, I can mount and use all of them.
I used the following guide to fix the drive numbers order:
http://www.linkedbits.com/2011/05/26/re … -in-linux/
Does somebody know whet is cfdisks problem and how can I fix it?
Thank you!

Do you see any problems after 'fdisk -l'?
I don't know if the cfdisk error message is showing something catastrophic or something that can be safely ignored. I have found that the only sure-fire method to avoid cfdisk errors is to edit partitions by using cfdisk.
cfdisk is very particular about what it considers correct and often shows errors on disks originally partitioned by fdisk or gparted. Oddly, cfdisk is recommended over fdisk in the fdisk man page – see the 'BUGS' section. The man page for sfdisk recommends using parted in some situations.
You might be able to see the problem cfdisk finds by using cfdisk:
# cfdisk -P t /dev/sda
Partition Table for /dev/sda
---Starting---- ----Ending----- Start Number of
# Flags Head Sect Cyl ID Head Sect Cyl Sector Sectors
1 0x80 32 33 0 0x83 223 19 12 2048 204800
2 0x00 223 20 12 0x82 244 35 273 206848 4194304
3 0x00 244 36 273 0x05 70 5 38913 4401152 620740608
4 0x00 0 0 0 0x00 0 0 0 0 0
5 0x00 22 5 274 0x83 53 61 2232 2048 31457280
6 0x00 86 31 2232 0x83 128 62 2754 2048 8388608
7 0x00 161 32 2754 0x83 236 21 33431 2048 492830720
8 0x00 13 54 33432 0x07 70 5 38913 872 88055808
# cfdisk -P s /dev/sda
Partition Table for /dev/sda
First Last
# Type Sector Sector Offset Length Filesystem Type (ID) Flag
Primary 0 2047* 0# 2048*Free Space None
1 Primary 2048* 206847* 0 204800*Linux (83) Boot
2 Primary 206848* 4401151* 0 4194304*Linux swap / So (82) None
3 Primary 4401152* 625141759* 0 620740608*Extended (05) None
5 Logical 4401152* 35860479* 2048# 31459328*Linux (83) None
6 Logical 35860480* 44251135* 2048# 8390656*Linux (83) None
7 Logical 44251136* 537083903* 2048# 492832768*Linux (83) None
Logical 537083904* 537085079 0 1176*Free Space None
8 Logical 537085080 625141759* 872# 88056680*HPFS/NTFS/exFAT (07) None
Pri/Log 625141760* 625142447* 0 688*Free Space None
Other options to print a partition table to the terminal screen, besides fdisk and cfdisk, are 'parted /dev/sdX unit s print' and 'sfdisk -l -V /dev/sdX'.

CDs and dmg files failing to mount on an eMac; any suggestions?

Dear all,
I have not posted here before and hope someone can assist please; I'm a long-time Apple user, having started with the Apple II and currently owning an iMac G5 and PowerBook G4.
Having obtained a G4 eMac, I discovered a serious software/hardware for which I can't find a solution. It is running OS X.2.8 which has an issue mounting .dmg and CDs. When I attempt to mount .dmg files, it reports the error message:
"FILE NAME failed to mount due to error 95. (no mountable file systems)"
All CDs will not appear on the desktop with the exception of the Apple Hardware Test CD. They do appear through Disk Utility but can't be mounted. I have tried apps such as "Mount" without success.
Apple has recognised this problem:
http://docs.info.apple.com/article.html?artnum=106345
http://docs.info.apple.com/article.html?artnum=107288
but none of the suggested remedies have worked for me. Various forums suggest solutions, a summary of which may be found here:
http://www.macattorney.com/tutorial.html#anchor-diskimage
but none worked.
I have also tried holding the "c" key with the Install CD but it won't mount.
Any suggestions please? I can boot with System 9 - as a last resort would it be possible to then delete key files from the OS X's "System" folder, following which I might be able to boot from the "Install" CD?
Many thanks,
Peter

They sometimes say you're better helping yourself!
I seem to have solved this after many hours of experimentation. I decided to hook up my iMac G5 (running 10.4.11) via a firewire cable. Having started the iMac, I followed the instructions for a target disk, connected the cable and fired up the eMac (hold "T" etc). Within minutes the eMac with its inserted CD could be seen on my iMac's desktop. However, I now needed to see if it worked the other way around - if I could somehow boot up with the eMac and use the iMac as the target disk, putting the CD into the iMac.
The eMac read the iMac's drive but unfortunately I could not see the inserted CD. Having then turned off the iMac, I left the firewire cable plugged in and then inserted the eMac's Install disk - to my great surprise the Install disk suddenly appeared on the eMac's desktop for the first time! I clicked the Installer which then announced it would start up from the CD. It duly did - and I managed to revert back to System 10.2, rather than the problematic Apple upgrade 10.2.8 which had been installed (and apparently caused the problems).
I'm trying to obtain a copy of 10.3 Panther, simply to run the excellent Elgato EyeTV.
Fingers crossed!
PJD.

Bootcamp partitioning error: "enable journaling", but my drive is journaled already.

Hi,
I'm trying to partition my Mac OS X (10.6.8) to install Windows 7, but during the partitioning process an error comes up that tells me my drive needs to be in Extended (Journaled) format, and directs me to Disk Utilities. However, my drive is already in that format, it always has been, and the option to do so is grayed out as a result. I've combed the message boards for similar problems but the only solution I've seen involved already existing partitions that weren't all journaled, but that doesn't apply to my case. Any thoughts?
Thanks!

Are there any other partitions on the drive besides your startup volume?
You might try:
Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

Tip regarding the "systemd[1]: Failed to start Journal Service" error

Just a tip regarding the well-known
systemd[1]: Failed to start Journal Service
error (which I ran into last weekend) to maybe save one or two among you a couple of hours of your time:
The error is described here https://bbs.archlinux.org/viewtopic.php?id=151012 as well as in several other threads in other language boards / in other forums etc. It is usually (as in the linked thread) 'solved' by reinstalling the system - good old Windows magic, also useful when dealing with systemd.
The Problem with this error is that you do not get into your system. Instead, systemd will print you the mentioned "Failed to start Journal Service" error message a couple of million times. There are also no logs that you could retrieve (when booting from a livesystem) and that would give you any helpful hints, since journal is systemd's logging service, old-style system logs are not kept, and the dmesg log doesn't survive the reboot with default settings.
As pointed out in the above mentioned thread, you will see a few more instructive error messages when adding 'emergency' to the kernel line in the bootloader config.
Now there may be plenty of reasons why the systemd journal service might not work. The most common and most annoying, however, appears to be this one:
In this case you will see that the problem actually lies in
systemd[1]: Cannot open /etc/machine-id: No such file or directory
Now, 'man machine-id' reveals that "the /etc/machine-id file contains the unique machine id of the local system that is set during installation. (...) The machine ID is usually generated from a random source (...)". It is obviously perfectly justified to refuse to boot the system because an absolutely insignificant random number is missing. As far as systemd is concerned anyway.
Usually, it seems, the /etc/machine-id is set by /usr/bin/systemd-machine-id-setup during installation or system upgrade. It is not documented anywhere that this is a rather important step and that you should better check if this was or was not actually done before rebooting. Obviously (but for no apparent reasons) systemd fails to run this (or to run this successfully) sometimes.
Also to be recommended: Always retain (back up) your old kernel and initramfs and edit your bootloader config appropriately to be able to boot with your old kernel again ... just to have one or two options left to get back into the system in case of running into an unpleasant surprise from the side of systemd or other packages.
The solution is, obviously, to create this file /etc/machine-id ... You probably want to do that from a livesystem (if you want to try it from the emergency shell, you would need to remount / (i.e. root) as rw and hope that systemd will not punish you for that) by just running the program that was designed for creating this file manually: /usr/bin/systemd-machine-id-setup
http://permalink.gmane.org/gmane.comp.s … devel/7528 states that it might also work with merely creating the file 'touch /etc/machine-id'. Though I didn't try that since I had enough fun with systemd for one week and didn't want to break my system again just to see if that works.

Jristz wrote:
ackalker wrote:Sorry for necrobumping this.
Generating the machine-id in a consistent way is very important when working with KVM and containers, where the machine-id can be set for the VM or container. See `man systemd-machine-id-setup`.
Again, _don't_ just put some random UUID in there, especially not in the systemd package install script, this makes provisioning Arch Linux containers a PITA.
If you thing that the way that arch is handlynbg the machine-id is wrong or can be improved, then file a bug.
He already did.
Jristz wrote:Anyway, I thing if reinstalling systemd package or if systemd have a command to reinitialize the machine-id file.
Like so many of your posts, I had to read this a half dozen times before it made any sense. I think you're hinting at the utility that ackalker already pointed out in the post you're replying to. And, if you read the install scriptlet, you wouldn't need to think about whether or not reinstalling would be an option. You would know that it isn't.

I have a 750GB HDD. Speaking visually (looking at Disk Utility) I had a 250GB Mac Journaled partition on the top, and a 500GB Mac Journaled partition on the bottom. The 250GB partition is now free space, now how do I expand the 500GB partition upwards?

I have a 750GB HDD. Speaking visually (looking at Disk Utility) I had a 250GB Mac Journaled partition on the top, and a 500GB Mac Journaled partition on the bottom.
The 250GB partition has been deleted and is now free space.
Now how do I expand the 500GB partition "upwards" when the GUI only gives me a resizing handle on the bottom right corner in Disk Utility?
I am comfortable with Terminal if there is a non-destructive CLI way to do this, since the Disk Utility GUI seems to have failed here...

OK.
You will need to check out a third-party utility. The diskutil CLI utility cannot non-destructively change the start of a partition map, only the end (which is why you only get the draggable handle in the GUI at the bottom of each partition...same idea).
To be honest, I'm not even sure how well third-party tools will do at this either. Changing the start of a partition is non-trivial, be cause of the partition map files, b-trees and so on which have to be moved. iPartition is well regarded, but also not free.
And regardless of what tool you use, you will want a backup of your data (assuming that it's data you want to keep, or you wouldn't care about non-destructive repartitioning). Which might mean that just getting a new HDD , copying the data and then repartitioning the current one and having an extra HDD because of it may be the simplest and safest solution anyway...

FDM Journal Import Fails

Hello,
We are FDM 11.1.2.1 and are having an issue when importing a journal template (Excel 97-2003 format). After checking in the journal and hitting "Post" we get an error message "Error: File Import Failed. Detail: File not found". I checked and double checked the location, category and period but to no avail. This file was used for another location and worked fine and was only updated with different data for a different location. Below is the error log out of the outbox if that helps at all. I also checked that the upsJournal range was appropriately set. Any thoughts would be appreciated.
Thanks,
Jason
** Begin FDM Runtime Error Log Entry [2011-10-06 15:30:10] **
ERROR:
Code............................................. 13
Description...................................... Type mismatch File=
Procedure........................................ clsMPLoader.fMultiImportExcel
Component........................................ upsWMPLoaderDM
Version.......................................... 1112
Thread........................................... 9940
IDENTIFICATION:
User............................................. hqqujdn
Computer Name.................................... NAHQWEB41
App Name......................................... FDM_GCCons
Client App....................................... WebClient
CONNECTION:
Provider......................................... SQLOLEDB
Data Server...................................... vnahqclu2app\sql2k8app
Database Name.................................... Upstream_GCCons
Trusted Connect.................................. False
Connect Status.. Connection Open
GLOBALS:
Location......................................... Algeria
Location ID...................................... 774
Location Seg..................................... 22
Category......................................... Actual
Category ID...................................... 13
Period........................................... Sep - 2011
Period ID........................................ 9/30/2011
POV Local........................................ True
Language......................................... 1033
User Level....................................... 1
All Partitions................................... True
Is Auditor....................................... False

Hi it seems like error description is abreviated: it is saying "Type mismatch File=". Can you try to get the full error description.
"Type Mismatch" errors also occur for Excel uploads in case the UPS range contains Excel errors like #VALUE or #NAME errors.
And did you check Regional Settings were the same as before when you saved the updated Journal template?

Error code -50 on boot partition (Mac OS Extended (Journaled) )

I`m often experiencing error code -50 when trying to change or move files on boot partition (Mac OS Extended (Journaled) ) on my MacBook PRO 5,5.
I already know that this error is related to MS-DOS formatted disks. But this one is all the time Mac OS Extended (Journaled).
All the files are created on Mac OS X 10.6.7 - so there can`t be a problem with a filename.
Is there another solution than corrupted harddisk?

while the next error code -50, I looked into Console and kernel says: "BootCache: too many history clusters (151, limit 151)". So that`s the cause of error, but how can I manage with it?
I tried this one in Terminal
code:
/usr/sbin/BootCacheControl stop
but no success. "-BootCacheControl: could not stop cache: Operation not permitted"
any ideas?

Journal Entrie - Failed to get next member of range member UJJ_JRNID

Hi experts,
I am using the BPC NW 7.5 SP04 version and have created a journal template. When I try to save the journal entry, I get the following error "new journal ID: Failed to get next member of range member (UJJ_JRNID - ). "
I have this error only in production environment. I save and post journal entry in develop environment without error.
Best regards,
Marilia Costa

Hi Friend,
Application parameters yes marked as YES, and I have change the number range as following
No.__ from number ____to number___current number
1____0000000001_____9999999999__1
But still i am getting error as" UJJ_JRNID - 000002"
My subobject no. is 000002
Please Advice
Thanks in advance
Aryan

Journal Import fails with EC12 issue

Journal Import fails with EC12 issue, we knew the AR credit memo transactions causing this issue have distribution lines with accounted_dr value as zero and entered_dr as non zero, same is the case with accounted_cr and entered_cr.
Issue is with the Credit memos generated out of iReceivables that are creating distributions with null amounts when applied on invoices with rules. Null amounts are on REV/UNEARN distribution lines. Applied patch# 12957348 as suggested in metalink and we noticed more number of such transactions after patch application.
Any pointers are really appreciated. We have over 5000 such lines and is not possible to clear them manually and since these CM's are phased, we are sure to see them again with this issue till it is resolved. Note# 285995.1 didn't help either.
We are on 11.5.10.2 and 10g database.
K

FOR l_rec IN (SELECT ledger_id,group_id from apps.gl_interface
WHERE status='NEW'
AND user_je_source_name='GIS_DATA_CONVERSION'
GROUP BY ledger_id,group_id
ORDER BY group_id
LOOP
apps.gl_journal_import_pkg.populate_interface_control (user_je_source_name => 'GIS_DATA_CONVERSION',
GROUP_ID => l_rec.group_id,
set_of_books_id => l_rec.ledger_id,
interface_run_id =>vl_interface_id,
table_name => 'GL_INTERFACE',
processed_data_action=>'D'
COMMIT;
vl_request_id := apps.fnd_request.submit_request (application => 'SQLGL', -- application short name
program => 'GLLEZLSRS', -- program short name
description => NULL, -- program name
start_time => NULL, -- start date
sub_request => FALSE, -- sub-request
argument1 => 2065, --Data access set id
argument2 => 'GIS_DATA_CONVERSION', --Source
argument3 => l_rec.ledger_id, -- set of books id
argument4 => l_rec.group_id,
argument5 => 'N', -- error to suspense flag
argument6 => NULL, -- create summary flag
argument7 => 'N' -- import desc flex flag
COMMIT;
IF ( vl_request_id = 0 ) THEN
xxgis.gis_conv_util_pkg.debug_print_p(1,'FND_LOG','E001: Journal Import Submission Failed. ' || SQLERRM);
retcode := 2;
EXIT;
ELSE
xxgis.gis_conv_util_pkg.debug_print_p(1,'FND_LOG','P001: Submitted Journal Import Program for group id: ' || l_rec.group_id ||
'and ledger :'||l_rec.ledger_id|| ', Request ID: ' || vl_request_id);
END IF;
END LOOP;

WebADI Journal Fails to Upload due to Error ''Enter A Valid Ledger''

We are in 12.1.3 version.
I tried to create a document from "AAA" GL module, but the DATA ACCESS SET name populated as "BBB" ledger name.
So, I managed to change it by manually with "AAA" ledger name and then tried, journal upload fails and showing error as "enter a valid ledger".
Can any expert advice me, how to get the "AAA" ledger name should automatically populate, while trying to create a (webadi) document ?
Thanks in advance.

Hi,
Please check the Data Access Set, profile option set for the responsibility you are using to create the document.
Also, If you want only 'AAA' to appear always, you can update the Web ADI template that you are using and make the Ledger field as constant to 'AAA'.

Posting a journal Entry failed

Hello All
I created a Journal Entry and edited the Journal Entry. When I tried to post it, I got an error saying
Could not start child program C:\PT8.49\cblbinA\GLPPPOST REMOTEA ....
When I looked at my folder structure I donot have that directory at all. .When I read the documentation it seems Posting process GLPPPOST is a Cobol Process. Does that I mean I need to setup cobol environment too?
Any thoughts?
Thanks
Sri

Posting process GLPPPOST is a Cobol Process. Does that I mean I need to setup cobol environment too?If you want to run a cobol, you obviously need to configure the cobol env. Starting by the Microfocus install, and compilation. Take a look in the PeopleTools installation guide for more information (OS/database vendor dependant) :
http://download.oracle.com/docs/cd/E05406_01/psft/html/docset.html
Nicolas.

Starting Form on Journal Entry fail with FRM-92101

Hi guys,
When we try to create Journal on GL we get FRM-92101: There was a failure in the Forms Server during startup. this could happen due to invalid configuration. Please look into the web-server for the details.
Details...
Java Exception:
Oracle.forms.net.ConnectionException:Forms Session<1,142> aborted: unable to communicate with runtime process.
at oracle.forms.net.ConnectionException.createConnectionException(Unknow Source)
at oracle.forms.net.HTTPNStream.getResponse(unknown source)
at oracle.forms.net.HTTPNStream.doFlust(unknown source)
at oracle.forms.net.HTTPNStream.flush(unknown source)
at java.io.DataOutputStream.flush(unknown source)
at oracle.forms.net.StreamMessageWriter.run(unknown source)
And checkin' the corresponding log I found:
File does not exist: /oracle/PROD01/apps/apps_st/comn/java/classes/oracle/forms/engine/RunformBundle_es_US.properties
File does not exist: /oracle/PROD01/apps/apps_st/comn/java/classes/oracle/ewt/alert/resource/AlertBundle_es_US.class
Looking for that path, we only reach to /oracle/PROD01/apps/apps_st/comn/java/classes/oracle/
We operate on eBusiness 12.0.4 with 10G Database 10.2.0.4 all this in RAC
Edited by: IvanBalVe on Aug 3, 2012 12:11 PM

Was this working before? If yes, any changes been done recently?
Do you have any invalid objects in the database?
Any errors in the database log file?
Please see these docs.
Show Full Journal Button In Arabic Instance Leads To Error FRM-92101 [ID 841590.1]
Users Receive FRM-92101 oracle.forms.net.ConnectionException Errors When Launching E-Business Suite Forms Responsibility and Function [ID 1258305.1]
R12 GLXIQACC Show Full Journal Button Errors With FRM-92101for Arabic [ID 802261.1]
If you still have the same issue, please generate the form via adadmin and check then -- How to Generate a Specific Form Through AD utility adadmin [ID 178722.1]
Thanks,
Hussein

[SOLVED] Arch failed to mount /boot

Hey there,
after my btrfs filesystem somehow got corrupted, so it would only mount my "/"-filesystem as read-only, I backed it up with rsync, recreated the partition and then transfered the data back. After that, I was unable to boot anymore with this error:
[1.593560] systemd-fsck[306]: fsck.fat 3.0.27 (2014-11-12)
[1.594292] systemd-fsck[306] /dev/sda1: 98 files, 43105/98304 clusters
Mounting boot...
[FAILED]Failed to mount /boot.
See "systemctl status boot.mount" for details
SystemD the prompted me with it's emergency mode, but this didn't react to any keyboard presses, so I couldn't check the exact error with sth. like journalctl -xb. I then booted a, today downloaded, Arch Live-CD and tried to access the logs via journalctl -b -D /var/log/journal/ didn't work out: It only had the logs from before the boot problem.
With a bit of googling I figured a way of fixing this could be chrooting in and reinstalling initramfs, typing chroot errored out with:
chroot: failed to run command /usr/bin/zsh: No such file or directory
I tried commenting out /boot in fstab, but at booting something [FAILED] with Load Kernel Modules and I instantly got prompted with a blank, black screen with a "_" blinking in the top left corner, like a normal console, expect any prompt of any kind was missing and it didn't react to my keystrokes, similiar to SystemD's emergency mode
So essentially two smaller problems with few google results are hindering me from solving my big problem.
Thanks for any help in advance,
Quanttek
Last edited by Quanttek (2015-05-26 09:48:21)

Head_on_a_Stick wrote:
Quanttek wrote:I use plain "chroot". "chroot --help" works, but not chroot itself. I also tried to rebuild the symbolic link from the normal lib -> /usr/lib to /lib/* -> /usr/lib/* and it didnt work
https://wiki.archlinux.org/index.php/Ch … ing_chroot
Probably easier to use `arch-chroot` though:
https://wiki.archlinux.org/index.php/Ch … rch-chroot
Thanks. Using arch-chroot worked out. It is/was certainly no environment issue, I even tested it with both i386 and x86_64.
I used it to reinstall mkinitcpio and to update my system, so now on boot I dont get a failure on mounting /boot anymore, but I still have problems with Load Kernel Modules.
My screen now looks something like this: http://m.imgur.com/ATWHJoq
Again it's not reacting to any keystrokes. I'll get some sleep now and will look tomorrow into getting some information from the journal logs.

Fix - Journaled partition fails to mount (journal magic error)

Similar Messages

Maybe you are looking for