Mail Reset After Kernel Panic- Accounts/Rules/preferences missing
My MbP had a kernel panic this evening and after the restart, I opened mail and got the "Welcome to Mail" message.
Tried restarting again, resetting pram (not sure why, but did), deleting preferences, etc. But all my mail preferences and accounts are missing.
They do still exist in the ~/library/Mail folder
But all my rules, smart folders, custom settings, etc are gone.
Any idea why this would happen?
Just wanted to make a quick reply because I had the same problem happen today, my MacBook Pro running 10.6.6, crashed with a kernel panic while using mail, although after checking the logs, it appears coreaudio caused the crash (had iTunes open in the background, perhaps a problem there?), had to do a force shutdown and restart (this is a very rare occurance that my MBP crashes).
When I started up again, mail would not start directly, instead was asking for details to set up a new account with the 'Welcome to Mail' message.
The fix was to move the mail preferences file (~/library/preferences/com.apple.mail.plist) to the desktop (or trash) and recover the most recent preferences file (com.apple.mail.plist) from time machine or other backup to the original location (~/library/preferences/com.apple.mail.plist).
Once I did that, restarted mail and all settings, messages, mailboxes, etc.. were exactly in place with no change (even the message I was typing when it crashed was still in the Drafts folder).
So this fix works as long as you have a back up.
(note I added extra info/explanation into this post for search engine's sake to make it easier to find)
Similar Messages
-
Having trouble accessing my email account thru the mail app, after entering the account information in the settings page, hotmail returns with the error message " The user name or password for Hotmail is incorrect". Help
Hotmail is having problems:
http://bostinno.streetwise.co/2013/08/15/hotmail-outage-hotmail-is-down-for-user s-still-photos/
http://www.engadget.com/2013/08/14/outlook-outage/
http://www.infoworld.com/d/applications/microsofts-skydrive-outlookcom-are-down- some-users-224940
http://mashable.com/2013/08/14/outlook-down/
http://techcrunch.com/2013/08/14/microsoft-acknowledges-outlook-com-messenger-sk ydrive-outages/ -
Macbook Pro won't load past white loading screen when turned on after kernel panics
Hello,
I have a Macbook Pro and recently its been having repeated kernel panics. In the past few days its been turning off every few minutes or so. yesterday it had one and now when I try to turn it on it doesn't load. I get the white loading screen with the apple logo and a loading bar underneath. But after the bar fills about 5% of the way (if that) the bar just disappears and the spinning loading icon just keeps going without anything happening (however long I leave it).
Please can someone give me some suggestions to fix this. Just a few things to note:
a) I'm not great with computers so any fixes please explain in the most simple terms
b) I have VERY important work files on there that are NOT backed up (big mistake I know), so please only suggest fixes that will not remove these Microsoft Word files. Guaranteeing the safety of my work is paramount with any suggestions.
c) I may not have any of the disks which came with the Macbook Pro originally (though I may somewhere)
d) I've read some other forum posts and it seems that I need to know the details of my operating system. I don't know these and have no way of accessing them on the computer (for obvious reasons). Its a late 2011 Macbook Pro if that is of any help.
A massive thank you to anyone who can suggest a fix to these, I shall be eternally grateful.Take each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a boot failure is to secure your data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since your last backup, you can skip this step.
There are several ways to back up a Mac that is unable to boot. You need an external hard drive to hold the backup data.
a. Boot into the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.”
b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
c. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. The easiest way to deal with the problem is to boot from an external drive, or else to use either of the techniques in Steps 1b and 1c to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a boot failure can be resolved by resetting the NVRAM.
Step 4
If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've booted from an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.
Boot in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually 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.
When you boot in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, your boot volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 6.
If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then reboot as usual (i.e., not in safe mode.)
If the boot process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select your startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then reboot as usual.
Step 9
Reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 10
Repeat Step 9, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a Time Machine or other backup.
Step 11
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a boot failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 12
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider. -
Compressor hung up after kernel panic
My 2.5ghz G5 (OS 10.4.11) experienced a kernel panic (it's fans rev'ving up big time) during a (Apple) Compressor v3 run. After a restart it seems to get stuck at the beginning of a new compression task (Unknown time remaining) with no progress in the progress bar. I've tried several source files, compression presets and target destinations, nada.
Recently I noticed that progress bar would go from little to lots in a big leap but I don't think that's related. Do I have any other choice but a reinstall? (like trashing some kind of preference?)
Saw this in a related post "Try going to Compressor > Reset Background Processing." it seemed to clear things up for a minute but then back to hang-up land
Thanks in advance for any suggestions.
PaulWhat specific version of Compressor are you using? Version 3 is included in both Final Cut Studio 2 and 3.
The main difference between the two is that Final Cut Studio 3 is Intel Only, which would be incompatible with your G5 and OS.
Incompatible Quicktime versions with your OS could also be causing problems as well. -
SSD fails to verify after kernel panic?
I have been using a 256GB Samsung 840 Pro SSD as my main boot drive in my MBP for about 6 months now with no issues. Last week, I randomly got a kernel panic and had to reboot my mac, however, it failed to boot. After opening the recovery tools, the disk utility failed to mount the SSD. After trying to reboot several times, the drive finally mounted and I tried a verify/repair, both of which failed. I also tried the Apple hardware diagnostic tool which ran without issue.
I then took the drive out and placed it in my Windows desktop. Using Samsung's disk "magician" I ran a diagnostics of the disk which said nothing was wrong. I updated the firmware and tried it in my MBP again where it still failed to mount/verify. I then put the disk in an external SATA->thunderbolt enclosure I had and the disk was not only recognized but booted, verified, etc completely fine as an external drive.
I then took my old internal HDD and put that in my MBP, wondering if perhaps it was my macbook that had the issue. However, this also booted and verified fine, suggesting it was in fact the SSD with the issue.
I called Samsung, and (painlessly) returned the drive and they shipped another one out to me. I continued to use my old HDD in my MBP with no issues while waiting on the shipment. Today it arrived, first I restored my OS to the SSD using my external enclosure and the drive booted and verified fine with no issues. I reinstalled it inside my Macbook and suddenly the drive no longer boots or verifies properly and will not repair - disk utility tells me to format the drive, which I tried, which then produces the same result.
I then tried resetting the SMC and PRAM, both of which had no effect.
I am completely at a loss at this point....
tl;dr Kernel panic, SSD no longer works internally, but is fine in external SATA->thunderbolt enclosure, original HDD boots fine internally. Replacement SSD also fails with same weird issue (works externally but not internally). Regular HDD still works in internal bay.
After using an SSD for so long I can't go back to just using a regular HDD, the speed difference is painful...but SSD no longer seems to work. What is going on here? Has anyone experienced anything like this before and what are my options?The new SSD seems to only have issues verifying partitions. If I select the physical volume in disk utility, it verifies fine with no errors. Any and all Mac partitions (MSDOS seems to work....) fail to verify or repair.
From what I've found, the only people with similar issues either A) had a "faulty" SATA cable or B) didn't enable TRIM on their SSD. Since a regular HDD still works fine in the internal bay where the SSD was installed, it can't be the former and I had enabled TRIM when I installed the SSD so it shouldn't be the latter. -
Please Help, I deleted an account that was the same name as the administrator but was not the administrator. Also a samsung galaxy s phone was charging through the usb port.
I closed out a program and got a message that the temp file could not be stored/saved.
Then a Kernel panic message occurred and restart was necessary.
The restart resulted in the screen with the apple logo and a continous swirl for 6+hrs,
Attempted Safe Mode start up, unsuccessful,
Single User Mode-sucess.
Ran $ fsck_hfs -rfd /dev/disk0s2 Ran several times repairs made with one which remained. something about a node.
No change in start up attempts
Started with install CD matching current OS 10.6
Ran Disk Utility Repair Permissions resulting in multiple errors:
One line/error
Warning: SUID file /////Ardagent has been modified and will not be repaired
144 lines/errors of this type of series of lines
Group permissions differ on...should be drwxr-xr-x, they are -rw-r--r-- .
permissions differ on...should be drwxr-xr-x, they are -rw-r--r-- .
unable to set owner and group...error 22: Invalid Argument
unable to set permissions on...error 22: Invalid Argument
Ran Repair Disk, result:
Error: Could not unmount disk (in red)
Ran Verify Disk, result:
The volume HD appears to be ok (in green)
Next I attempted to erase the dist to start from scratch since I have data backed up on time machine.
Error message box
Volume Erase failed
Volume Erase failed with error:
Could not unmount disk
I am looking to solve without buying DiskWarrior unless only resort.So it looks like solved it for now I will update later. What I did was after starting from the install cd for the 10.6 system I ran from terminal ran:
diskutil disablejournaling /dev/disk0s2
diskutil disableownership /dev/disk0s2
diskutil repairPermissions /dev/disk0s2
then i closed terminal and then when to disk utility and chose to repair disk with results all was fine. Then ran repair permissions and got similar results from terminal function next I erased disk and then chose to restore from time machine and it is now restoring! yea! -
Gray Screen of death after kernel panic
Hi guys,
Today I got a kernel panic and after restarting my macbook pro (early 2011) it stucks at a gray screen (without the Apple logo).
I tried a SMC-reset and also a NVRAM-reset but this doesn't help. Furthermore I tried to do a hardware test and booting from my Snow Lepoard DVD but this doesn't work too. When I start while holding c key the gray screen appears but nothing happens.
I removed the harddisc and connected to my server for getting all my files. This worked so the harddisc seems to be ok. In Addition to that I replaced my 8 Gb RAM to the original 4 Gb but this doesn't heller einher.
Has anyone suggestions what I can do?
Regards robertIf you can get it to start, go into System Prefs and check your startup volume...
-
Issue after kernel panic from update! Please help
Is anyone having issues with their computer after doing the reinstall? I too had the same problem yesterday as thousands of other people had. Took me 9 hours to reinstall lion. I was very happy when I realized I didn't lose all my data. (Guess I learned my lesson on backups) My problem is: Today after my computer is working again is is so stinking slow..... Im talking it has been 15 minutes to load the new mac commercial (30 second ad, on apple.com) In that 15 minutes it has only loaded 20 seconds of it. It is still trying to load the rest so I can stream it? I have never had an issue with speed. It is taking me nearly 4-5 minutes for every email I click just to pull up and read it. Something is wrong? I know it isn't my internet, we have 3 other computers in the house that work the way they always have. My laptop has always been the fastest of them all. I need help! Anyone have any suggestions? Is is possible if the update damaged the flash drive or something? All I know after 9 hours computer loss yesterday and my computer taking all day today to answer a few lousy emails is killing me, I need a solution. I have tried cleared the cache and reset safari with no luck.
Please advise...HI Chris,
Kernel panics are sometimes causes by hardware issues. Probably a good idea at this point to check the boot disk for errors.
Open Disk Utility, in the Utilities folder in the Applications folder.
Select your disk, and click First Aid.
Click Verify Disk.
If the disk needs repairs, do one of the following:
Insert your Mac OS X Install disc in your computer’s optical drive or an optical drive connected to your computer, and then restart your computer. When you hear the startup tone, hold down the C key until you see the progress indicator, which looks like a spinning gear.
Follow the onscreen instructions until the menu bar appears with the Utilities menu in it, choose Utilities > Disk Utility, click First Aid, and then click Repair Disk.
Checking a hard disk to see if it’s going to fail
You can check the health of your hard disk by checking its Self-Monitoring, Analysis, and Reporting Technology (S.M.A.R.T.) status in Disk Utility. Most disk drives include S.M.A.R.T. hardware. Developed by IBM, S.M.A.R.T. hardware allows hard disks to test themselves for potential problems.
Starting up in “safe mode” may help you to diagnose problems you’re having with your computer.
To start up in safe mode:
Shut down your computer and wait 10 seconds.
Press the power button.
Immediately after you hear the startup tone, hold down the Shift key.
You should press the Shift key as soon as possible after your hear the startup tone, but not before.
Release the Shift key when you see the gray Apple logo and progress indicator (spinning gear).
To leave safe mode, restart the computer normally without holding down any keys during startup.
More help here resolving kernel panics; http://www.thexlab.com/faqs/kernelpanics.html
If the boot disk appears to be ok, you could try installing the 10.5.6 combo update available here;
http://support.apple.com/downloads/MacOS_X_10-5-6_ComboUpdate
About the Mac OS 10.5.6 update
Carolyn -
Recovery session canceled due to errors. Can't start DB after kernel panic.
Hi all,
I have a cluster Oracle 10 DB that was incorrectly shutdown (node 1 got a kernel panic when I disconnected the cluster interconnect and after a while node 2 also had a panic).
Now the DB doesn't start and I already tried an endless loop of solutions that don't work and lead me right to the start. I was hoping someone could help me fix this bloody thing please. This DB was running in archive log mode.
/export/home/oracle
oracle@dbsce066/1 - TSP/(CLIENT_10.2.0)/SERVER_10.2.0/(CRS_10.2.0)
sqlplus '/ as sysdba'SQL*Plus: Release 10.2.0.3.0 - Production on Mon Jul 18 23:18:24 2011
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 9680453632 bytes
Fixed Size 2162704 bytes
Variable Size 1570701296 bytes
Database Buffers 7969177600 bytes
Redo Buffers 138412032 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> shutdown
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 9680453632 bytes
Fixed Size 2162704 bytes
Variable Size 1553924080 bytes
Database Buffers 7985954816 bytes
Redo Buffers 138412032 bytes
Database mounted.
SQL> recover database using backup controlfile until cancel;
ORA-00283: recovery session canceled due to errors
ORA-01110: data file 87: '/export/home/oracle/dev/DX/dx_index10_logging3'
ORA-01110: data file 86: '/export/home/oracle/dev/DX/dx_index10_logging2'
ORA-00372: file 86 cannot be modified at this time
ORA-01110: data file 86: '/export/home/oracle/dev/DX/dx_index10_logging2'
SQL> select name,status,file# from v$datafile where name like '%index10_logging%';
NAME
STATUS FILE#
/export/home/oracle/dev/DX/dx_index10_logging1
ONLINE 85
/export/home/oracle/dev/DX/dx_index10_logging2
RECOVER 86
/export/home/oracle/dev/DX/dx_index10_logging3
ONLINE 87
SQL> ALTER DATABASE OPEN resetlogs ;
ALTER DATABASE OPEN resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/export/home/oracle/dev/DX/dx_system'
SQL>
I also saw the "_allow_resetlogs_corruption". But I would like to leave this as last resort.
Thanks in advanceThank you everyone for the advices. I used this tutorial to implement the allow reset logs corruption, but still it didn't allow me to startup the DB normally without errors or recover the datafile 86.
@@ How to use "_allow_resetlogs_corruption"
@@ http://dba-oracle.fr/dba/content/view/14/9/
vi /export/home/oracle/products/10.2.0/dbs/initDX1.ora
"/export/home/oracle/products/10.2.0/dbs/initDX1.ora" 94 lines, 4520 characters
DX1.undo_tablespace=dx_undo1
DX1.log_archive_dest_1= 'LOCATION=/export/home/oracle/dev/DX/archivelog1 REOPEN=10'
DX1.local_listener="(address=(protocol=tcp)(HOST=localhost)(PORT=1531))"
### cluster specific parameters
*.cluster_database = true
*.cluster_database_instances = 2
allowresetlogs_corruption=TRUE
"/export/home/oracle/products/10.2.0/dbs/initDX1.ora" 95 lines, 4553 characters
SQL> STARTUP MOUNT
ORACLE instance started.
Total System Global Area 9680453632 bytes
Fixed Size 2162704 bytes
Variable Size 1570701296 bytes
Database Buffers 7969177600 bytes
Redo Buffers 138412032 bytes
Database mounted.
SQL> ALTER DATABASE OPEN RESETLOGS;
ALTER DATABASE OPEN RESETLOGS
ERROR at line 1:
ORA-01110: data file 86: '/export/home/oracle/dev/DX/dx_index10_logging2'
ORA-00372: file 86 cannot be modified at this time
ORA-01110: data file 86: '/export/home/oracle/dev/DX/dx_index10_logging2'
SQL> SELECT 'alter database datafile /export/home/oracle/dev/DX/dx_index10_logging2 END BACKUP;' from v$datafile;
'ALTERDATABASEDATAFILE/EXPO
alter database datafile /export/home/oracle/dev/DX/dx_index10_logging2 END BACKUP;
alter database datafile /export/home/oracle/dev/DX/dx_index10_logging2 END BACKUP;
alter database datafile /export/home/oracle/dev/DX/dx_index10_logging2 END BACKUP;
SQL> recover database until cancel using backup controlfile;
ORA-00283: recovery session canceled due to errors
ORA-01110: data file 87: '/export/home/oracle/dev/DX/dx_index10_logging3'
ORA-01110: data file 86: '/export/home/oracle/dev/DX/dx_index10_logging2'
ORA-00372: file 86 cannot be modified at this time
ORA-01110: data file 86: '/export/home/oracle/dev/DX/dx_index10_logging2'
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> shut
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
root@dbsce066> ls -l /export/home/oracle/dev/DX/
total 450
lrwxrwxrwx 1 root other 29 Apr 13 2010 dx_index10_logging1 -> /dev/md/oraindex1dg/rdsk/d651
lrwxrwxrwx 1 root other 29 Apr 13 2010 dx_index10_logging10 -> /dev/md/oraindex1dg/rdsk/d660
lrwxrwxrwx 1 root other 29 Apr 13 2010 dx_index10_logging2 -> /dev/md/oraindex1dg/rdsk/d652
I can access the file and it is readable:
root@dbsce066> ls -ltr /export/home/oracle/dev/DX/dx_index10_logging2
lrwxrwxrwx 1 root other 29 Apr 13 2010 /export/home/oracle/dev/DX/dx_index10_logging2 -> /dev/md/oraindex1dg/rdsk/d652
root@dbsce066> ls -ltr /dev/md/oraindex1dg/rdsk/d652
lrwxrwxrwx 1 root root 44 Aug 2 17:59 /dev/md/oraindex1dg/rdsk/d652 -> ../../../../../devices/pseudo/md@0:3,652,raw
root@dbsce066> dd if=/dev/md/oraindex1dg/rdsk/d652 of=/dev/null
^C18564+0 records in
18564+0 records out
root@dbsce066>
SQL> select * from v$datafile where FILE#=86;
FILE# CREATION_CHANGE# CREATION_TIME TS# RFILE# STATUS
ENABLED CHECKPOINT_CHANGE# CHECKPOINT_TIME UNRECOVERABLE_CHANGE#
UNRECOVERABLE_TIME LAST_CHANGE# LAST_TIME OFFLINE_CHANGE#
ONLINE_CHANGE# ONLINE_TIME BYTES BLOCKS CREATE_BYTES BLOCK_SIZE
NAME
PLUGGED_IN BLOCK1_OFFSET
AUX_NAME
FIRST_NONLOGGED_SCN FIRST_NONLOGGED_TIM
86 184062 2010-04-13:17:18:24 62 86 RECOVER
READ ONLY 498989920 2011-07-18:15:28:29 0
485512497
496226794 2011-07-16:00:01:53 660602880 80640 660602880 8192
/export/home/oracle/dev/DX/dx_index10_logging2
0 8192
NONE
0
select STATUS,ENABLED,NAME from v$datafile where FILE#=86
STATUS ENABLED NAME
RECOVER READ ONLY /export/home/oracle/dev/DX/dx_index10_logging2
SQL> select name from v$tablespace where TS#=62;
NAME
DX_INDEX10_LOGGING2
SQL> alter tablespace DX_INDEX10_LOGGING2 read write;
alter tablespace DX_INDEX10_LOGGING2 read write
ERROR at line 1:
ORA-01109: database not open
SQL> ALTER DATABASE DATAFILE 86 ONLINE;
Database altered.
SQL> select STATUS,ENABLED,NAME from v$datafile where FILE#=86;
STATUS ENABLED
NAME
RECOVER READ ONLY
/export/home/oracle/dev/DX/dx_index10_logging2
SQL>
SQL> alter tablespace DX_INDEX10_LOGGING2 end backup;
alter tablespace DX_INDEX10_LOGGING2 end backup
ERROR at line 1:
ORA-01235: END BACKUP failed for 1 file(s) and succeeded for 0
ORA-01199: file 86 is not in online backup mode
ORA-01110: data file 86: '/export/home/oracle/dev/DX/dx_index10_logging2'
SQL> select log_mode from v$database;
LOG_MODE
ARCHIVELOG
SQL> SELECT FILE#, ERROR, ONLINE_STATUS, CHANGE#, TIME FROM V$RECOVER_FILE;
FILE# ERROR ONLINE_ CHANGE# TIME
86 ONLINE 498989920 2011-07-18:15:28:29
SQL> recover database until cancel using backup controlfile;
ORA-00279: change 497920329 generated at 07/18/2011 12:53:10 needed for thread 2
ORA-00289: suggestion : /export/home/oracle/dev/DX/archivelog1/LOG_DX_8574_2_716223168.ARC
ORA-00280: change 497920329 for thread 2 is in sequence #8574
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log '/export/home/oracle/dev/DX/archivelog1/LOG_DX_8574_2_716223168.ARC'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/export/home/oracle/dev/DX/dx_system'
@@ Attempt to start DB without that datafile:
SQL> ALTER DATABASE DATAFILE '/export/home/oracle/dev/DX/dx_index10_logging2' OFFLINE DROP;
Database altered.
SQL> SHUTDOWN IMMEDIATE;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> SQL> startup
ORACLE instance started.
Total System Global Area 9680453632 bytes
Fixed Size 2162704 bytes
Variable Size 1570701296 bytes
Database Buffers 7969177600 bytes
Redo Buffers 138412032 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> ALTER DATABASE OPEN NORESETLOGS;
ALTER DATABASE OPEN NORESETLOGS
ERROR at line 1:
ORA-01588: must use RESETLOGS option for database open
SQL> ALTER DATABASE OPEN RESETLOGS;
ALTER DATABASE OPEN RESETLOGS
ERROR at line 1:
ORA-01245: offline file 76 will be lost if RESETLOGS is done
ORA-01110: data file 76: '/export/home/oracle/dev/DX/dx_data10_logging2'
SQL>
@@ Nothing works. I can't even start the DB without that datafile. So I give up of this recovery scenario. Re-install from scratch. -
MDD Dual 1.0GHz Power-up chime, NO BOOT or video after Kernel Panic
My MDD DP 1.0 (FW400) suffered a recent kernel panic on startup, and since then it has failed to boot...
It chimes and the power light stays on, fans run, but seems not to access the hard drive, and or power the DVD drives, USB/keyboard, or Video.
I Can't reach her via ARD either.
I have tried:
Reset PMU Power cord in.
Reset PMU Power cord out
Replaced the Battery,
Left battery out for 48hrs
Started up holding X key
Started up holding Space bar
etc. etc.
Any ideas? I really don't to loose this trusty old server.
Other details.
Hard Drives Are 2 month old Hitachi 7k250 have been tested as working in a D2 enclosure
Video Stock Radeon 9000 as new
PSU was replaced as part of the PSU replacement programme
Extra 1GB (2x512) Crucial installed when new.
Thanks In advance
HenrikWith care, you can manually open the optical drive tray. Pull open the outer door and use a good light to look at the front face of the drive beneath the hinged door. Somewhere there is a small hole, often under the tray, just slightly larger than a large paper clip's wire diameter.
Partially straighten a large paper clip and GENTLY insert the wire STRAIGHT into the hole. You should feel resistance after about 1/4 inch. Apply a little more pressure and the tray will start to move out. Grab it with your fingers and gently extend it all the way. I had to do this when I had the boot problems I mentioned.
Once you insert the System CD/DVD, push the tray closed and try to start, this time holding down the "C" key on your keyboard to force the computer to start from the optical drive.
BTW, be sure to check all internal cables for secure connections. As you're not even getting a gray screen, I'm getting a little concerned that your power supply has taken the long trail. When my MDD did the boot craziness, I at least got a gray screen. -
MacPro 1,1 10.6.8 won't boot after kernel panic
I apologize for the long post, but figured I'd lay out the whole scenario.
I had a kernel panic in Safari yesterday. Powered down. Powered on. Message appeared saying to power down, and restart again. Did that. Then the fun started. The restart was slower than normal, with each screen (gray, blue, Snow Leopard background screen) slow to come up and move to next. Finally, it stopped on the Snow Leopard screen but the login screen never appeared.
I have my fair share of kernel panics, sometimes triggered by something Virus Barrier is guarding against, sometimes for other reasons. I regularly save the reports but can't say off the top of my head that I know of something that could be implicated in this present issue.
Since this issue surfaced, I've tried multiple interventions to no avail. I used Disk Warrior to rebuild the directory and optimize the disk, both reported by the software as successful. The SMART status of the disk was normal. Verified and repaired permissions. As is typical, some were reported but nothing noticeably out of the ordinary. Still not able to reboot.
Used Apple's Disk Utility to check the status of the drive, and ran through the other available diagnostic tests. Still not able to reboot.
Among different attempts to restart, sometimes it stopped at blue screen, sometimes at Snow Leopard default background screen image.
Reset PRAM. Still no reboot. Booted into Single user mode/verbose mode. Then fsck -fy. The second time I ran the latter, it reported "FILE SYSTEM WAS MODIFIED" and I ran fsck -fy once more.
The report on screen in Single User mode showed some things I don't know how to interpret. Lines of the report beginning with "AppleACPICPU: Processor Id= " were as follows:
AppleACPICPU: Processor Id=0 LocalApicId=0
AppleACPICPU: Processor Id=0 LocalApicId=1
AppleACPICPU: Processor Id=0 LocalApicId=7
AppleACPICPU: Processor Id=0 LocalApicId=6
AppleACPICPU: Processor Id=0 LocalApicId=0
AppleACPICPU: Processor Id=0 LocalApicId=0
AppleACPICPU: Processor Id=0 LocalApicId=0
AppleACPICPU: Processor Id=0 LocalApicId=0
Other things from the report:
• Mac Framework successfully initialized using 16384 buffer headers and 4096 cluster IO buffer headers
• BSD root: disk1s2, major 14, minor 5
• jnl: unknown-dev
• com.apple.launched 1 com.apple.launched1 *** launched[1] has started up. ***
Do things in this list look normal? Any red flags?
As it stands now, none of the measures have enabled the computer to reboot. When I power on it goes straight to the default Snow Leopard screen. Oddly, if I power it off but then later go back and hit the space bar, such as one would do when the computer has been idle and the computer or screen has gone to sleep, the computer instantly powers itself on. Likewise, trying to power on and hold down the "c" key to attempt to boot from the system CD to Disk Utility does the same thing. That's really odd. Powering on via any key on keyboard is not expected behavior!
So ... what I most want to determine is:
• Were Disk Warrior and Disk Utility mistaken in reporting that the hard drive is functioning normally? Was it actually failing?
• Did the fsck -fy routine, with the reported action "FILE SYSTEM WAS MODIFIED," hasten it to its death?
• Is it more likely that the processor or some other major hardware issue is involved?
The computer is old, and has been more fitful over the past 6 months or so, but I've also had more issues with Virus Barrier forcing kernel panics during that same time, so it's been hard to say whether it was the computer that was acting wonky or Virus Barrier causing the wonkiness.
I just need to know whether I should wipe and reformat the existing WD disk, go buy a new disk to format, or give up on the computer and order a new MacPro model to replace it. If the latter was undertaken, I would really prefer to get the old MacPro functioning long enough to have use of it while I can complete an order and get something new set up. I have some tasks that I need to be getting done and data that I need to access to take of other tasks. I have a current Time Machine back up. But now that I can't even boot from Disk Utility, it seems I will have to buy another drive to do the interim solution.
I would very, very appreciative of any expert advice.
DebbieHi hatter,
Good to talk with you again about my Mac Pro 1,1. Can't believe I still have this stalwart machine, but it just keeps on keepin' on.
I have a Mac Box Set with Snow Leopard. That's the disk I was using Disk Utility from. I did the hardware tests that I saw among the tools available when one boots from the disk. Could be I'm missing something.
While I was waiting for a reply from someone at Discussions, I went looking at Walmart for an SATA disk. They were completely out of them due to local storms that fried a lot of people's computers and hardware. It's a small town. Not a lot of options. So I came back home and thought I'd try again to boot from the Apple DVD. That time it worked. I was going to do a restore from the Time Machine backup, but then decided to just reinstall the OS from the DVD and see what happened. Clean seemed better than dirty, you know?
At any rate, I installed the OS - to the same WD Caviar Black hard disk. When it restarted, everything came up looking back to normal, except that I need to update to 10.6.8 and reinstall iWork apps and other Apple add-ons as needed. Oh what a relief it is!
I would like to do some hardware testing though. If you can advise, I would appreciate it. -
MBP can't find SSD after kernel panic
I installed a Crucial M500 240GB SATA 2.5-Inch 7mm drive using an Other World Computing adapter into my MacBook Pro back in October. It has been working very well until yesterday. I typically leave my laptop on and just close the case. When I opened it yesterday, a kernel panic message came up and after a few seconds the machine rebooted to my internal hard drive and I was able to continue working. The SSD just had my applications and system so my work materials (docs, etc.) are OK. However, the machine can "see" the SSD drive. I have tried Disk Utility and Drive Genius with the same result. Before I start opening the MBP, can anyone suggest other steps to take? I have the system backed up to Time Machine.
Mandy:
Welcome to Apple Discussions.
Are you able to boot from the install disk or the Apple Hardware Test disk?
If so, boot from the install disk and Repair Disk
Insert Installer disk and Restart, holding down the "C" key until grey Apple appears.
Go to Installer menu (Panther and earlier) or Utilities menu (Tiger) and launch Disk Utility.
Select your HDD (manufacturer ID) in the left panel.
Select First Aid in the Main panel.
(Check S.M.A.R.T Status of HDD at the bottom of right panel, and report if it says anything but Verified)
Click Repair Disk on the bottom right.
If DU reports disk does not need repairs quit DU and restart.
If DU reports errors Repair again and again until DU reports disk is repaired.
If DU reports errors it cannot repair you will need to use a utility like Tech Tool Pro or Disk Warrior
Then boot from the AHT disk and run all tests in a loop by holding down Command + L during the tests.
Good luck.
cornelius -
Intel Mac Mini constantly resetting then kernel panic
I've got a Mac Mini that on start up just constantly resets, I've tried to boot from the OS X install discs but as soon as the installer starts to load I get a Kernel Panic.
Can't think of anything else really, the machine's not been fiddled with or opened up. I've done the usual disconnect the cables and hold the power button reset but that doesn't help
Picture of the panic is here:
http://lenore.newmeja.com/stuff/panic.jpgIt's definitely not been opened, its kept in a locked room with a kensington lock on it. It's definitely the original Apple RAM.
I've tried booting from some other Mac Mini install media and I get the same kernel panic.
Need to get the machine back up quickly so I've been in touch with Apple who are just going to repair it under warranty. -
How to resolve booting issues after kernel panic?
After a kernal panic occurred, whenever I restart my computer the light flashes and it emits one loud harsh beep. I have to force it off and turn it on again to get it to boot, everything else works normally. Any help would be greatly appreciated!
This screen appeared, which apparently indicates a kernel panic.
The issues are similar to these two threads:
https://discussions.apple.com/thread/1935615?threadID=1935615
https://discussions.apple.com/message/4776709#4776709Interval Since Last Panic Report: 1779896 sec
Panics Since Last Report: 1
Anonymous UUID: 9AFA25D5-E2C1-4E87-89DF-1D76F6CD8A20
Sun Jun 19 13:22:02 2011
panic(cpu 1 caller 0x42259a): "hfs_swap_HFSPlusBTInternalNode: attr key #4095 offset too big (0x0000)\n"@/SourceCache/xnu/xnu-1504.9.37/bsd/hfs/hfs_endian.c:735
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x46503b38 : 0x21b510 (0x5d9514 0x46503b6c 0x223978 0x0)
0x46503b88 : 0x42259a (0x5c380c 0xfff 0x0 0x6e)
0x46503c28 : 0x417561 (0x46503c48 0x5884ce8 0x1 0x1)
0x46503c68 : 0x2cc70d (0x2d99e520 0x587d004 0x58004bc 0x12445ad)
0x46503cb8 : 0x1247c40 (0x2d99e520 0x0 0x0 0x2000)
0x46503ce8 : 0x123eb6b (0x5d5c0d4 0x0 0x2000 0x0)
0x46503d58 : 0x1247c40 (0x584ea00 0x5d5c0c0 0x0 0x2000)
0x46503d88 : 0x159704f (0x46503dc4 0x0 0x2000 0x0)
0x46503de8 : 0x159926a (0x582b200 0x561d290 0x82a000 0x0)
0x46503e08 : 0x11a467e (0x5836200 0x5792780 0x0 0x2be9604c)
0x46503e38 : 0x11a5270 (0x5826b00 0x5792780 0xc0ae720c 0x578aa00)
0x46503e58 : 0x11ad05c (0x5792780 0x5792780 0x0 0x2a358d)
0x46503e98 : 0x11ad1b6 (0x578aa00 0x5792780 0x0 0x0)
0x46503ed8 : 0x11aecc0 (0x578aa00 0x80000 0x106ea8 0x573c7a8)
0x46503f38 : 0x11ab130 (0x578aa00 0x82a000 0x1 0x3)
0x46503f58 : 0x55028c (0x578b940 0x7478000 0x46503fa8 0x21915d)
0x46503f88 : 0x5506e6 (0x578bac0 0x7478000 0xffe007c5 0xffffffff)
0x46503fc8 : 0x2a06dc (0x578bac0 0x0 0x10 0x7473a84)
Kernel Extensions in backtrace (with dependencies):
com.apple.iokit.IOAHCIBlockStorage(1.6.3)@0x1594000->0x15a6fff
dependency: com.apple.iokit.IOAHCIFamily(2.0.4)@0x11a2000
dependency: com.apple.iokit.IOStorageFamily(1.6.2)@0x1236000
com.apple.driver.AppleAHCIPort(2.1.5)@0x11a8000->0x11bbfff
dependency: com.apple.iokit.IOAHCIFamily(2.0.4)@0x11a2000
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x908000
com.apple.iokit.IOAHCIFamily(2.0.4)@0x11a2000->0x11a7fff
com.apple.iokit.IOStorageFamily(1.6.2)@0x1236000->0x124dfff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
10J869
Kernel version:
Darwin Kernel Version 10.7.0: Sat Jan 29 15:17:16 PST 2011; root:xnu-1504.9.37~1/RELEASE_I386
System model name: MacBook5,2 (Mac-F22788AA)
System uptime in nanoseconds: 475669227090
unloaded kexts:
com.apple.driver.AirPortBrcm43xx 423.91.27 (addr 0xf83000, size 0x1900544) - last unloaded 96256802454
loaded kexts:
com.apple.driver.AppleHWSensor 1.9.3d0 - last loaded 34597603457
com.apple.driver.AGPM 100.12.19
com.apple.driver.AppleHDA 1.9.9f12
com.apple.driver.AppleUpstreamUserClient 3.5.4
com.apple.driver.AppleMCCSControl 1.0.17
com.apple.driver.AppleBacklight 170.0.34
com.apple.driver.SMCMotionSensor 3.0.0d4
com.apple.filesystems.autofs 2.1.0
com.apple.driver.AudioAUUC 1.54
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AudioIPCDriver 1.1.6
com.apple.driver.ACPI_SMC_PlatformPlugin 4.5.0d5
com.apple.GeForce 6.2.6
com.apple.driver.AppleLPC 1.4.12
com.apple.driver.AppleIntelPenrynProfile 27
com.apple.driver.AppleUSBTrackpad 200.3.2
com.apple.driver.AppleUSBTCKeyEventDriver 200.3.2
com.apple.driver.AppleUSBTCKeyboard 200.3.2
com.apple.driver.AppleIRController 303.8
com.apple.iokit.SCSITaskUserClient 2.6.5
com.apple.BootCache 31
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.iokit.IOAHCIBlockStorage 1.6.3
com.apple.nvenet 2.0.15
com.apple.driver.AppleFWOHCI 4.7.1
com.apple.driver.AirPortBrcm43224 427.36.9
com.apple.driver.AppleAHCIPort 2.1.5
com.apple.driver.AppleUSBHub 4.1.7
com.apple.driver.AppleUSBEHCI 4.1.8
com.apple.driver.AppleUSBOHCI 4.1.5
com.apple.driver.AppleSmartBatteryManager 160.0.0
com.apple.driver.AppleEFINVRAM 1.4.0
com.apple.driver.AppleRTC 1.3.1
com.apple.driver.AppleHPET 1.5
com.apple.driver.AppleACPIButtons 1.3.5
com.apple.driver.AppleSMBIOS 1.6
com.apple.driver.AppleACPIEC 1.3.5
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 105.13.0
com.apple.security.sandbox 1
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.1.11
com.apple.driver.AppleIntelCPUPowerManagement 105.13.0
com.apple.driver.DspFuncLib 1.9.9f12
com.apple.driver.AppleProfileReadCounterAction 67
com.apple.iokit.IOFireWireIP 2.0.3
com.apple.nvidia.nv50hal 6.2.6
com.apple.driver.AppleProfileTimestampAction 67
com.apple.driver.AppleProfileThreadInfoAction 67
com.apple.driver.AppleProfileRegisterStateAction 67
com.apple.driver.AppleProfileKEventAction 67
com.apple.driver.AppleProfileCallstackAction 69
com.apple.iokit.IOSurface 74.2
com.apple.iokit.IOBluetoothSerialManager 2.4.0f1
com.apple.iokit.IOSerialFamily 10.0.3
com.apple.iokit.IOAudioFamily 1.8.0fc1
com.apple.kext.OSvKernDSPLib 1.3
com.apple.driver.AppleHDAController 1.9.9f12
com.apple.iokit.IOHDAFamily 1.9.9f12
com.apple.driver.AppleSMC 3.1.0d3
com.apple.driver.IOPlatformPluginFamily 4.5.0d5
com.apple.NVDAResman 6.2.6
com.apple.iokit.IONDRVSupport 2.2
com.apple.iokit.IOGraphicsFamily 2.2
com.apple.iokit.AppleProfileFamily 61
com.apple.driver.BroadcomUSBBluetoothHCIController 2.4.0f1
com.apple.driver.AppleUSBBluetoothHCIController 2.4.0f1
com.apple.iokit.IOBluetoothFamily 2.4.0f1
com.apple.iokit.IOUSBHIDDriver 4.1.5
com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.5
com.apple.iokit.IOUSBMassStorageClass 2.6.5
com.apple.driver.AppleUSBMergeNub 4.1.8
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.5
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6
com.apple.driver.AppleUSBComposite 3.9.0
com.apple.driver.XsanFilter 402.1
com.apple.iokit.IOAHCISerialATAPI 1.2.5
com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.5
com.apple.driver.NVSMU 2.2.7
com.apple.iokit.IOFireWireFamily 4.2.6
com.apple.iokit.IO80211Family 314.1.1
com.apple.iokit.IONetworkingFamily 1.10
com.apple.iokit.IOAHCIFamily 2.0.4
com.apple.iokit.IOUSBUserClient 4.1.5
com.apple.iokit.IOUSBFamily 4.1.8
com.apple.driver.AppleEFIRuntime 1.4.0
com.apple.iokit.IOHIDFamily 1.6.5
com.apple.iokit.IOSMBusFamily 1.1
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 6
com.apple.driver.DiskImages 289
com.apple.iokit.IOStorageFamily 1.6.2
com.apple.driver.AppleACPIPlatform 1.3.5
com.apple.iokit.IOPCIFamily 2.6
com.apple.iokit.IOACPIFamily 1.3.0
System Profile:
Model: MacBook5,2, BootROM MB52.0088.B06, 2 processors, Intel Core 2 Duo, 2.13 GHz, 2 GB, SMC 1.38f5
Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.10.131.36.9)
Bluetooth: Version 2.4.0f1, 2 service, 12 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: Hitachi HTS543216L9SA02, 149.05 GB
Serial ATA Device: MATSHITADVD-R UJ867A
USB Device: eGo USB, 0x059b (Iomega Corporation), 0x047a, 0x26200000
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06100000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8215, 0x06110000
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0229, 0x04600000
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x04500000 -
Mdadm raid1 stops to work after kernel panic
Accidentally I've booted with wrong grub parameters and my systems hanged with a kernel panic. After reboot my /dev/md2 device (raid1) stopped to work.
These are some logs:
wax@persifae:~$cat /proc/mdstat
Personalities : [raid1]
md2 : inactive sda1[0](S)
293049600 blocks
md1 : active raid1 sdc6[0] sdb2[1]
152264000 blocks [2/2] [UU]
md0 : active raid1 sdb1[1] sdc5[0]
7815488 blocks [2/2] [UU]
unused devices: <none>
wax@persifae:~$sudo mdadm -Q /dev/md2
/dev/md2: is an md device which is not active
wax@persifae:~$sudo mdadm --assemble --scan /dev/md2
mdadm: failed to add /dev/sdc1 to /dev/md2: Invalid argument
mdadm: /dev/md2 assembled from 0 drives - not enough to start the array.
wax@persifae:~$cat /etc/mdadm.conf
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=2a37b0a1:4b6b28fc:0209446b:c3b28f2a
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=19c49c5d:e3193aa1:657f267b:b23c2dee
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=62a5cb51:36ca61a3:1298e6c2:30fde3ba
Thanks in advance for your help
Last edited by Foschini (2008-05-04 20:22:42)_Marco_ wrote:hi, welcome here
you say "I booted with wrong grub parameters" so the system is ok except grub modifications.. have you tried to use a live cd,
mount the arch partition and edit grub to revert the changes?
Long story short I tried to use bootchart and i create a new grub menu called Arch linux bootchart, but I made a mistake and I wrote wrong raid1 partition. This is the code:
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/md0 ro md=0,/dev/sdc5,/dev/sdb1 vga=795
initrd /boot/kernel26.img
# (1) Arch Linux
title Arch Linux bootchart
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/md0 ro md=0,/dev/sdb5,/dev/sdc1 vga=795 init=/sbin/bootchartd WRONG LINE! LOOK AT THE PARTITION NUMBER :(
#initrd /boot/kernel26-fallback.img
initrd /boot/kernel26.img
I confused sdb and sdc. If i use the standard Archlinux my system boots correctly but the raid with sdc1 and sda1 partition doesn't work anymore.
Maybe you are looking for
-
Windows 7 no longer boots after upgrade from Lion to Mountain Lion
I got a late 2011 MacBook Pro, on which I installed Windows 7 with Boot Camp. After I upgraded from Lion to Mountain Lion, I can no longer boot Windows. If I keep the option button pressed during boot I only get the OS X and recovery options, and if
-
T61 will not boot with nvidia quadro 140m driver
Hi all, A couple of weeks ago, after allowing MS update to install some FTDI driver updates, my system will not boot up and hangs shortly after the initial vista loading screen. The screen goes black with some HD activity and eventually reboots. Afte
-
Remove Green Screen with Adobe Photoshop Elements
Hi, I have setup a Green Screen in my home. I took some pictures of my wife with the Green Screen Background and want to remove the Green Screen and replace with a different background. I was able to do this via the Adobe Premiere Elements 7.0 but ne
-
Having trouble sending jpeg images as attachments in Mac email.....they go thru as images and PC users can't see the SAVE or QUICK LOOK boxes that Mac mail has. One friend scrolled over the image, right clicked on it and saved as a PNG file.
-
Update placed PDF files to recognize transparency
I have used Croptima InPlate to create an imposed cut and stack imposition of a large 3800 variable data project. Due to the size of the file, I've only imposed the black plate variable data. I want to use Acrobat's add background tool to add an impo