Should I defragment disk after deleting BootCamp ?

1. I made a mistake - installed Windows on Mac via Boot Camp (Now I know that I won't need Windows anymore).
2. Then I deleted Windows and restored Boot Camp via BootCamp assistant. Hopefully.
3. To restore the normal boot speed I did PRAM reset
(Turn it on, immediately after the display turns gray, press and hold Command + Option + P + R. Continue holding until you've heard the system chime 3 times.)
4 Now. Should I optimize Mackintosh HD drive like disc defragmentation ? Since what happened is that by removing the boot camp partition, it has greatly altered the "optimization" of your mac.

alabanco wrote:
Yes. I have restored to one partition Mackintosh HD drive.
So. As far as the idea of cloning internal to an external drive and then restoring it back is concerned. Is there any special procedure for that ? Can I do that on one Mac or will I need another one ?
Unless you decide to clone frequently just use Disk Utility (DU) to make your clone:
1. Start up from your Snow install DVD by holding down C when starting up.
2. Choose your language and use the menus at the top of the next screen to start DU.
3. Start DU;
4. Drag your internal volume to the source box;
5. Drag your external partition (or volume) to the destination box;
6. Choose Erase Destination (if you are forced to do so to restore); and
7. Click restore.
8. Test your clone to make sure it is bootable.
It will take an hour, more or less. Then, reverse the process to get your OS X install "compacted" on your internal.

Similar Messages

Slow reboot after deleting bootcamp partition

Hello,
I was just told by a tech store that my bootcamp partition was slowing down my computer incredibly. I no longer need this partition so I went into Disk Utility, clicked the partition, and deleted it. I also had my RAM updated from 4GB to 8GB. I have an Early 2011 Macbook Pro, operating on Yosemite.
The only question I have is, when I rebooted my computer for the first time after deleting the partition, the restarting process took much longer than normal. Without the bootcamp startup, I figured the startup time would be less, when in reality, it was longer. Is there something I missed while deleting my partition, and is there a way to fix this and speed up the reboot time? If not, will this slow reboot be a one time issue?
Any comments would be appreciated!
Thanks,
Rachel

There is a hidden Recovery HD between the OS X and the deleted BC partition, which you can verify using
sudo gpt -vv -r show /dev/disk0
in OSX Terminal.
BCA does a better job by also relocating the Recovery HD appropriately and giving you a contiguous partition.
The only other method is to subsume Recovery HD in OS X partition and then re-install OS X which will rebuild Recovery HD. This does not modify any of you files, but just the OS.
You will also need to clean the Hybrid MBR which is now dangling and inappropriate for your case.

Unknown Firmware Password prompt after deleting Bootcamp

I bought a MacBook Pro second hand last year. The previous owner installed bootcamp on it and I tried getting rid of it to no avail. When I shut it down and tried to turn it back on I just got the folder with the question mark, presumably a startup disk issue. When I try the reset shortcuts and resetting pram it just shows a firmware password entry, of which I don't know. neither does the precious owner. Ive brought it to the apple store to see what they can do but they said they can't do anything without original proof of purchase. Neither I, nor the original owner has the receipt. So, I have a paperweight that runs and is a password away from working. Help?

Hi Boudewijn,
I personally haven't seent this behavior as of yet. I've done 6 upgraded on the SX300 series and 4 on the SX500 series. The good news is, there is nothing lost if you have the ability to console the unit.
If you console the unit there is a password bypass option
1)Bits per seconds: 115200
Databits: 8
Partiy: None
Stop bits:1
Flow control: None
2) Reboot the switch, just unplug the power and plug it back in
3) When prompted, press ESC
4.) I beleive it is option 6 that is "password recovery"
Once you choose this option, the switch should boot as normal and you may sign in without the admin password.
-Tom
Please rate helpful posts

Cannot delete files from hard disk (after deleting from playlists)!

all of a sudden itunes stopped allowing me to automatically delete (with the warning) a downloaded podcast so I would have to go to the hard disk manually to delte the posdcast.
How do I get the system back to what it was where I delete a podcast and then get the warning and say ok to delete from hard disk?
TIA!

Hi Chris:
2 part response:
I founf the problem--somehow my itunes folder was moved to a different part of my hard drive--once I moved it back I can delete.
I can delete as follows: when I right click and click on delete, I first delete the file from itunes library--then I get prompted if I want to delete from my hard disk by sending file to recycle bin--There is also a prompt if I do not want to see the warning--which I have on as a safety precaution. So I bet the default could remove from playlist and send file to recycle bin in one move.

Lost HardDrive Space After Deleting Bootcamp Partiton

Hello, Everyone
I have a small issue i open finder window and it says that i have 398.18GB Available but when i go into Disk Utility and go to the top result which is called WDC WD6400AAKS-40H2B0 Media it says that my Total Capacity is 640.14 GB so i go to the Partition Tab and it says the following Available Space: 533.58 and the HD Size 639.66 so i go to my Desktop and Get Info on my Macintosh HD and it says my Capacity is 493.79GB and i don't understand where the rest of my space has gone the Macintosh HD says that i have only used 95.61 GB on disk so if you can help me get my rest of my space back it would be much appreciated.
I have tried repairing it in disk utility but it hasn't worked
Thanks, Sean

HI,
Try repairing disk permissions...
Quit any open applications/programs. Launch Disk Utility. (Applications/Utilities) Select MacintoshHD in the panel on the left, select the FirstAid tab. Click: Repair Disk Permissions. When it's finished from the Menu Bar, Quit Disk Utility and restart your Mac. If you see a long list of "messages" in the permissions window, it's ok. That can be ignored. As long as you see, "Permissions Repair Complete" when it's finished... you're done. Quit Disk Utility and *restart your Mac*.
Carolyn

Disk Space not restored after deleting iphone backup

Hi,
Today while restoring my iphone i realised that itunes had made multiple copies of ~3gb of my iphone data. Since my iphone was restored successfully I decided to remove all the backups and make a fresh new backup. After deleting the multiple backups I found that my available disk space had not increased at all. I even went to ~/Library/Application Support/MobileSync/Backup and ther was nothing in there. So I went ahead and made a new backup which consumed additional ~3gb. And just to test if it was only itunes that was doing this I deleted my photos from iphoto ~5gb and even that did not give me back my 5gb. I went to trash and I dont have anything there.
So, here I am confused as to where my deleted stuff is going to because it does not seem like its getting deleted.
Anything that i can do get my space back?
Thanks,
Yogi

Local snapshots are hidden copies of files that have been changed or deleted in between Time Machine snapshots. They are stored in free space that would otherwise be unused, and therefore wasted. The space occupied by the snapshots is managed automatically. When free space starts to run low, the snapshots are deleted. The Finder reports the space occupied by local snapshots as "Available," which it is.
If there are unwanted changes to your files in between Time Machine snapshots — which may be far apart when you're moving around with a portable computer — you may be able to revert the changes from a local snapshot. If you disable local snapshots, you lose that protection, and you gain nothing. There is no offsetting benefit whatsoever; merely added risk.
Empty storage space is simply wasted. You paid for it to be there, but it's doing you no good at all. Local snapshots put it to use.
Very rarely, if ever, you might need to delete the local snapshot store in order to add a large amount of data all at once. If that need ever arises, which it probably won't, all you have to do is turn Time Machine OFF in its preference pane, and then turn it back ON immediately.
You should ignore the bad advice that circulates on this site to disable local snapshots permanently by running a shell command. If you ran such a command, ask for instructions on how to reverse it.

Emergency disk full error, doesn't create room after deleting files

Oh, this seems like it could be bad. I got the error and even after deleting 800 MB of large files, I can't even download a 2.4 MB utility file to help figure this out.
What can I do?
I can't even upload a file to my server...!

1. Deleted hundreds of MB of my files.
2. Emptied the trash, yes.
3. Restarted.
4. Still can't copy 2 MB of data, says it's full.
I don't know where to look to check system resources or where to find any resident small utility file that could discover enormous files written in error to the disk (my guess). I was a Windows person in another, but recent, life.
Thanks for any help while I can still communicate...
GIna
P.S. Time Machine is running now with no error, so perhaps I'll have a full backup. Disaster for tomorrow noon deadline.

Free disk space not changing after deleting (large) photos

Hi,
I wasn't sure whether to post this on the iPhoto board or on the MBA one, since it's not clear if it's a system-level issue or not. Anyway, I had about 30GB of free space on my 256GB MBA and the other day I deleted four or five albums of photos from my DSLR that I'd downloaded to my computer, after I made backups of them elsewhere. In total there were about 3,500 photos, roughly 24MB each on average. I made sure that after deleting them, I deleted my iPhoto Trash as well as the system Trash. Neverless, my level of free space hardly budged and if anything, it decreased slightly. I've read several threads saying to wait a while as sometimes the system takes a delay to adjust - that's fine.
It's now almost five days later and the situation remains the same, if not worse. I ran DaisyDisk and aside from the usual large folders (my movies in iTunes etc, none of which had been added to since I deleted all those photos), the only one I couldn't recognise was this folder iLifeAssetManagement (9GB). I know that there are a few threads about this one, and most people seem to suggest you can clear this if you're happy to lose the content in your Photo Stream. The thing is, I've looked through some of the images in this folder and I'm quite positive that a number of them are from the DSLR albums (there are CR2 files, which I believe is Canon's exclusive RAW format). Some of the others are definitely from my iCloud Photo stream. I'm more than glad to lose all the DSLR ones, though I'd like to keep the iCloud ones and I don't really want to have to sort through 5,000-odd files. I'm positive that this folder is related to why I never gained that free space.
Has anybody else had issues like this and any suggestions for clearing this folder of all the files I already meant to delete, whilst keeping the others? Or have you had issues relating to this? Any help much appreciated.
Thanks.

If you've installed third-party software called "Disk Drill," I suggest you remove it according to the developer'sinstructions. If you prefer to keep the software, refer to the developer for support. Otherwise, see below.
You may notice a difference in available space statistics between Disk Utility, Finder, and Get Info inspectors. This is expected and can be safely ignored. The Finder displays the available space on the disk without accounting for the local snapshots, because local snapshots will surrender their disk space if needed.
About Time Machine's "local snapshots" on portable Macs

How to recover the recovery partition after delete all hard disk partitions

hallo
how to recover the recovery partition after delete all hard disk partitions in toshiba satellite pro c850-1fn ?
note that : I did not work recovery disc or usb to my laptop.
I have need of your help.

Satellite Pro C850-1FN (PSCBXE-01700EEN)
Restore the hard disk to its original out-of-the-box contents using Toshiba recovery media. All of the original partitions will be restored, including the recovery partition.
If no recovery discs were created, you can obtain them from Toshiba.
Toshiba Europe Backup Media Online Shop
For instructions, see the section Restoring the pre-installed software from your created Recovery Media on p. 4-18 of the User's Manual (attached).
-Jerry

Should i run disk utility check after a restore onto a brand new drive?

My hard drive died on my daughter's macbook, just replaced it and did a restore.
i am wondering if i should do any disk utility check(permissions or repair) on a new hard drive because i have restored a time machine backup onto it.
I say this because any issues on the backup files are now placed onto a new hard drive.

Kappy wrote:
It can't hurt to repair permissions. Most likely you'll get a long stream of stuff most of which is irrelevant and can be ignored. If there are any repair issues this will fix them. Be sure to run DU from the system you just installed. No need to boot from an installer disc.
BTW, did you properly prep the drive? Partitioned GUID, Mac OS Extended, Journaled format, and one pass Zero Data?
I did partitiion the drive guid, os extended, journaled. but i dont remember a choice on the onepass zero data but i assume it happened with the partitioning.
i understand no need to boot from the disc for permission check but if i do a verify or repair of the disk, then dont i have to boot from the install disc?

Should I defrag HDD between SSD upgrading?

I am in the process of changing from a Crucial 256GB M4 SATA SSD to a Crucial 240GB M500 SSD. (I'm unable to upgrade the M4 firmware as laptop has UEFI BIOS). I have imaged the M4 to an HDD and find that the C: partition is 12% defragmented and the recovery partition Q: is 99% defragmented. I have a Lenovo T430s laptop running Windows 7 Professional.
Should I defrag both partitions before installing the new SSD, or not bother?
Also the Q partition had only 2GB free on the M4. Should I increase this when I change to the M500?
Solved!
Go to Solution.

If you click on Q in Windows Explorer, you should see menu pop up with two options: burn recovery disks and reclaim space. I can't remember exactly as it's been a while since I did it, but it's possible that the second option doesn't appear until you complete the first.
You can run the recovery during startup by interrupting the boot process by pressing F11 repeatedly. Do so will give you a menu to restore your drive to the factory state. It does this from the recovery image stored on Q. You don't need to do this if you've burned the disks because, well, you have the disks that do the same thing. So, after you burn the disks and delete Q, the F11 option won't work any more. Just so you know.
Edit: DVDs!!!! Unless you like feeding dozens of CDs to the burner!
SSDs are like RAM sticks. They don't do anything if they're not powered up. Open Power Options in Control Panel and edit the advanced settings for power. You'll find a setting for hard disks, for when plugged in and when on battery. Set "turn off disks" to never for both. You don't want an SSD powering down while you're using the PC.

Problems after installing Bootcamp 3.1

Hello everyone.
I had installed Windows 7 64 bit Ultimate in a Bootcamp partition. I used the SL disk to install Bootcamp 3.0 which, with some audio related problems which were solved by changing the drivers, worked well. All sounds played, the graphics card behaved normally, etc.
Recently I got the alert of a Bootcamp update, 3.1, as we all know. After installing it without a hitch, small problems began to pop up.
First, no Windows startup sound played anymore, and there has been no way for me to make it work again. I've gone to countless forums and gone through an endless barrage of suggestions, including a complete formatting, but it always leads back to the same, isolated problem: Startup sound plays in BT 3.0, doesn't play anymore in BT 3.1.
But more importantly, after pretty much giving up with the startup sound issue (it's only that particular sound, in the login screen, so I decided to ignore it's absence), more problems appeared. Initially, all system tray icons appeared swiftly. Now the main ones, Sound, Wireless Connection and Battery appear fast, but the rest take at least 5 minutes to appear. This is again something that wasn't present in Bootcamp 3.0.
Yet another problem, this one I consider is the most important, and the real reason for this post of mine, is that Bootcamp 3.1 brought a serious driver problem with my Macbook Pro's 9400M video card. Doing the most stupid of tasks such as opening the video card's control panel from the Desktop gives me the following error:
"The NVIDIA Display Panel extension cannot be created.
Possible reasons include:
Version mismatch. Reinstalling the drivers may solve this problem."
Now, the Device Manager shows no errors in hardware-driver smoothness in any aspect, yet it's clear that the driver that BT 3.1 installs for the video card was either faulty or old, or for another OS. I went to NVIDIA's site to manually get the driver, but it turns out that they offer no NVIDIA GeForce 9400M drivers for Windows 7 64 bit. So I wonder, how come it worked before? Because in Bootcamp 3.0 the Control Panel would open flawlessly.
So this is serious. Gaming has also turned into a nightmare, since the problem with the video card negatively affects the smoothness of the gameplay. Apple, things weren't working 100% with BT 3.0, but BT 3.1 far from making things better just got everything worse.
I ask everyone here if there is a known solution. Should I install the NVIDIA GeForce 9400M drivers for Windows 7 32 bit? Why doesn't the driver installed by BT 3.1 function as it should when it's supposed to be covering Windows 7 compatibility? Why are the barrage of audio errors present in BT 3.1 and not in BT 3.0? What happened with my startup sound?
Apple, you're offering the possibility for your users to user Windows for compatibility and gaming. You market your Macs are fully compatible and flawless even running Windows. Don't come about saying this is not your problem, it is. It's your drivers, you develop them, you give them to us. If they don't work, you must do something about it. If not, then stop offering the Bootcamp service completely. If you're gonna do something, do it well.

http://www.nvidia.com/object/notebookwinvista_win7_x64_195.62whql.html

[Solved] Can't boot into Arch after deleting some partitons

About 6 months ago I installed Arch on a machine that used to run Ubuntu. Had some trouble at the time getting to boot into Arch but somehow managed. Now eventually decided to delete the old Ubuntu partitons to free up some space using gparted. Arch partition number changed from sda12 to sda6.
On rebooting after deleting ubuntu partitions with gparted, I got an ubuntu splash screen and a whole lot of ubuntu boot options. Somehow these were all contained in my Arch's /boot/grub/menu.lst. Arch is all on one partition and no separate boot partition (which I had with Ubuntu - maybe I haven't deleted that and this is the problem?). Will need to check that out.
I can chroot into Arch and did the following -
grub> find /boot/grub/stage1
(hd0,5)
grub> root (hd0,5)
Filesystem type is ext2fs, partition type 0x83
grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,5)/boot/grub/stage2 /boot/grub/menu.lst"... succeed
ed
Done.
grub>
The Arch /boot/grub/menu.lst had a whole lot of ubuntu stuff in it but I edited to the following -
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
# examples
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,3)
title Arch uuid
#root (hd0,5)
uuid d15cf4f9-18ca-4ec5-95bc-db0f6f264736
kernel /boot/vmlinuz26 root=/dev/sda6 ro vga=775
intrd /boot/kernel26.img
title Arch hd
root (hd0,5)
kernel /boot/vmlinuz26 root=/dev/sda6
intrd /boot/kernel26.img
I have a bootinfo script which gives the following (from the chroot environment) -
Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ==============================
=> Grub 0.97 is installed in the MBR of /dev/sda and looks on the same drive
in partition #6 for /boot/grub/stage2 and /boot/grub/menu.lst.
=> No boot loader is installed in the MBR of /dev/sdb
sda1: _________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
sda2: _________________________________________________________________________
File system: Extended Partition
Boot sector type: -
Boot sector info:
sda5: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
mount: /dev/sda5 already mounted or sda5 busy
sda6: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
mount: /dev/sda5 already mounted or sda5 busy
mount: /dev/sda6 already mounted or sda6 busy
sda7: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:
sda3: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 10.04.1 LTS
Boot files/dirs: /etc/fstab
sda4: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs: /grub/menu.lst /grub/grub.cfg /grub/core.img
sdb1: _________________________________________________________________________
File system: xfs
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:
=========================== Drive/Partition Info: =============================
Drive: sda ___________________ _____________________________________________________
Disk /dev/sda: 750.2 GB, 750155292160 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start End Size Id System
/dev/sda1 417,690 6,554,519 6,136,830 82 Linux swap / Solaris
/dev/sda2 25,414,954 1,465,144,064 1,439,729,111 5 Extended
/dev/sda5 25,414,956 1,360,287,809 1,334,872,854 83 Linux
/dev/sda6 1,360,287,873 1,423,198,349 62,910,477 83 Linux
/dev/sda7 1,423,198,413 1,465,144,064 41,945,652 83 Linux
/dev/sda3 6,554,520 25,414,829 18,860,310 83 Linux
/dev/sda4 * 63 417,689 417,627 83 Linux
Drive: sdb ___________________ _____________________________________________________
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
Partition Boot Start End Size Id System
/dev/sdb1 2,048 1,953,523,711 1,953,521,664 83 Linux
blkid -c /dev/null: ____________________________________________________________
Device UUID TYPE LABEL
/dev/loop0 squashfs
/dev/sda1 2a95d85a-45fe-4584-88dd-0ee20e651ec5 swap
/dev/sda2: PTTYPE="dos" PART_ENTRY_SCHEME="dos" PART_ENTRY_TYPE="0x5" PART_ENTRY_NUMBER="2"
/dev/sda3 32495e1a-227c-4d23-9f63-b1319def0dd9 ext3
/dev/sda4 d6dc69b0-967d-4886-b62d-8c0d6be06b41 ext3
/dev/sda5 37971286-b8d3-4a1b-9f94-4008288fed6d ext3 data
/dev/sda6 d15cf4f9-18ca-4ec5-95bc-db0f6f264736 ext3 30GB-02
/dev/sda7 eb736131-b558-4404-9b83-7f1e6d9e76ae ext3 var
/dev/sda: PTTYPE="dos"
/dev/sdb1 0e83045d-a0bd-4d36-b61d-bdb905130dc2 xfs 1TB-04
/dev/sdb: PTTYPE="dos"
============================ "mount | grep ^/dev output: ===========================
Device Mount_Point Type Options
/dev/sda12 / ext3 (rw,commit=0)
=============================== sda3/etc/fstab: ===============================
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1 = swap
/dev/sda1 none swap sw 0 0
# /dev/sda3 = root
#UUID=32495e1a-227c-4d23-9f63-b1319def0dd9
/dev/sda3 / ext3 relatime,errors=remount-ro 0 1
# /dev/sda4 = boot
# UUID=d6dc69b0-967d-4886-b62d-8c0d6be06b41
/dev/sda4 /boot ext3 relatime 0 2
# /dev/sda5 = home
# UUID=670eee83-0a3e-429c-863f-b9ecced9f97e
/dev/sda5 /home ext3 relatime 0 2
#/dev/sda6
#UUID=37971286-b8d3-4a1b-9f94-4008288fed6d
/dev/sda6 /home/ben/Data ext3 defaults,relatime 0 0
# /dev/sda7
# UUID=fdb14ca4-d71d-489f-a00e-6e608770674c
/dev/sda7 /var ext3 relatime 0 2
# /dev/sda8
/dev/sda8 /opt ext3 relatime 0 2
# /dev/sda10 - Arch
/dev/sda10 /mnt/arch ext3 relatime 0 2
# Not sure what this is doing here
# Have commented it out - May be the reason why xbmc and mythtv were crashing on dvd insert and play
# /dev/hda /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
# /dev/sde1
# uuid appears to be 644406B3570C1846 -> ../../sde1
#/dev/sde1 /home/ben/Data/TVRecordings-1TB01 xfs defaults,relatime 0 0
#1TB-01
UUID=76f3823a-81dc-45c9-a0b7-2bc6c3beb2f8 /media/1TB-01 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 1TB-02
UUID=59cbf7a1-7008-40d0-96ed-c6f231823d4f /media/1TB-02 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 1TB-03
UUID=0e936800-3c53-4b87-abc8-19be0ffca7f9 /media/1TB-03 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 750GB-02 ext3 Partition
# UUID giving problems, trying with dev
# UUID=c23b9c9a-66fc-4256-9211-73156c1ac64a /media/750GB-02_ext3 ext3 defaults,relatime 0 0
/dev/sde2 /media/750GB-02_ext3 ext3 defaults,relatime 0 0
============================= sda4/grub/menu.lst: =============================
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
# examples
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,3)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash
## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=
## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false
## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false
## ## End Default Options ##
title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-26-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-26-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-24-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-24-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-23-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-23-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-22-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-22-generic
title Ubuntu 10.04.1 LTS, memtest86+
root (hd0,3)
kernel /memtest86+.bin
quiet
### END DEBIAN AUTOMAGIC KERNELS LIST
============================= sda4/grub/grub.cfg: =============================
# DO NOT EDIT THIS FILE
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
function recordfail {
set recordfail=1
if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set 32495e1a-227c-4d23-9f63-b1319def0dd9
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
set locale_dir=($root)/grub/locale
set lang=en
insmod gettext
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.32-26-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-26-generic
menuentry 'Ubuntu, with Linux 2.6.32-26-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-26-generic ...'
linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-26-generic
menuentry 'Ubuntu, with Linux 2.6.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-24-generic
menuentry 'Ubuntu, with Linux 2.6.32-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-24-generic ...'
linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-24-generic
menuentry 'Ubuntu, with Linux 2.6.32-23-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-23-generic
menuentry 'Ubuntu, with Linux 2.6.32-23-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-23-generic ...'
linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-23-generic
menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-22-generic
menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-22-generic ...'
linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-22-generic
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux16 /memtest86+.bin
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux16 /memtest86+.bin console=ttyS0,115200n8
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Arch Linux (on /dev/sda10)" {
insmod ext2
set root='(hd0,10)'
search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
linux /boot/vmlinuz26 root=/dev/sda10 ro
initrd /boot/kernel26.img
menuentry "Arch Linux Fallback (on /dev/sda10)" {
insmod ext2
set root='(hd0,10)'
search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
linux /boot/vmlinuz26 root=/dev/sda10 ro
initrd /boot/kernel26-fallback.img
#### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
# From Arch grub menu.lst
# (0) Arch Linux
#title Arch Linux [/boot/vmlinuz26]
#root (hd0,0)
#kernel /vmlinuz26 root=/dev/sda3 ro
#initrd /kernel26.img
#Note: With a separate boot partition, omit /boot from the path, (i.e. type set prefix=(hdX,Y)/grub and insmod
(hdX,Y)/grub/linux.mod).
#This introduces the "linux" and "initrd" commands, which should be familiar (see #Configuration).
#An example, booting Arch Linux:
#set root=(hd0,5)
#linux /boot/vmlinuz26 root=/dev/sda5
#initrd /boot/kernel26.img
#boot
###menuentry "Arch1" {
###insmod ext2
###set root='(hd0,10)'
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
###search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UU
ID
###linux /boot/vmlinuz-26 root=635d7d02-3f5b-4af6-9c74-16b2af8cc7fd ro quiet splash # ARCH'S ROOT UUID
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
###menuentry "Arch2" {
###insmod ext2
###set root='(hd0,4)' #= TRYING UBUNTU'S BOOT
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
###menuentry "Arch3" {
###insmod ext2
###set root='(hd0,10)' #= TRYING UBUNTU'S BOOT IN HD FORMAT
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
### END /etc/grub.d/40_custom ###
=================== sda4: Location of files loaded by Grub: ===================
.0GB: grub/core.img
.0GB: grub/grub.cfg
.0GB: grub/menu.lst
.0GB: grub/stage2
.0GB: initrd.img-2.6.32-22-generic
.0GB: initrd.img-2.6.32-23-generic
.1GB: initrd.img-2.6.32-24-generic
.1GB: initrd.img-2.6.32-26-generic
.0GB: vmlinuz26
.0GB: vmlinuz-2.6.32-22-generic
.0GB: vmlinuz-2.6.32-23-generic
.1GB: vmlinuz-2.6.32-24-generic
.0GB: vmlinuz-2.6.32-26-generic
=============================== StdErr Messages: ===============================
No volume groups found
mdadm: No arrays found in config file or automatically
[/quote]
Output of fdisk -l from chroot is -
[quote]Disk /dev/sda: 750.2 GB, 750155292160 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000b084
Device Boot Start End Blocks Id System
/dev/sda1 417690 6554519 3068415 82 Linux swap / Solaris
/dev/sda2 25414954 1465144064 719864555+ 5 Extended
/dev/sda3 6554520 25414829 9430155 83 Linux
/dev/sda4 * 63 417689 208813+ 83 Linux
/dev/sda5 25414956 1360287809 667436427 83 Linux
/dev/sda6 1360287873 1423198349 31455238+ 83 Linux
/dev/sda7 1423198413 1465144064 20972826 83 Linux
Partition table entries are not in disk order
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00025bd3
Device Boot Start End Blocks Id System
/dev/sdb1 2048 1953523711 976760832 83 Linux
I need to post this now and come back from a different machine to note the error messages I am now getting on boot. ...
Note that when I boot and press esc to get the menu I get the menu.lst I created (in the second quote) above in /dev/sda6, ie the one with the Arch hd and uuid entries - so grub is looking there and finding that menu.lst, but something goes wrong after that.
OK. Have now booted the machine and after pressing esc and selecting the uuid entry (the same thing happens with the hd entry) I get a whole lot of stuff, but what seems relevant is (typing it out) -
List of all partitions:
No filesystem could mount root, tried:
Kernel panic - not syncing: VS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper Not tainted 2.6.39-Arch #1
If anyone can help I'd really appreciate it. This is my MythTV machine so the WAF is about to take a big dive!
If I could just install grub to the MBR as if this was a new installation of Arch that would be great.
I am really lost as to what is going on, which I'm sure is evident.
Thanks a lot
belbo
Last edited by belbo (2011-08-12 13:31:23)

Hi. Unfortunately that didn't help.
So next, based on this post https://wiki.archlinux.org/index.php/Ke … el_version I chrooted into Arch and (a) rolled back and (b) reinstalled my kernel but that didn't help either. I suspected it wouldn't because the kernel was working fine before I deleted the partitions in question.
[2011-08-08 23:32] ==> Image generation successful
[2011-08-08 23:32] upgraded kernel26 (2.6.39.3-1 -> 2.6.39.3-1)
I then did a pacman -Suy and the linux package has now replaced kernel26. ( See this wiki entry http://www.archlinux.org/news/changes-t … filenames/). I didn't change anything in menu.lst owing to this and it seems there is no need to. Unfortunately this hasn't helped either - still getting the kernel panic.
Pacman.log relating to the new kernel package below -
[2011-08-09 00:22] Running 'pacman -Suy'
[2011-08-09 00:22] synchronizing package lists
[2011-08-09 00:23] starting full system upgrade
[2011-08-09 00:23] Running 'pacman -Suy'
[2011-08-09 00:23] synchronizing package lists
[2011-08-09 00:23] starting full system upgrade
[2011-08-09 00:26] removed python-mygpoclient (1.5-1)
[2011-08-09 00:26] removed kernel26 (2.6.39.3-1)
[2011-08-09 00:26] warning: /boot/grub/menu.lst installed as /boot/grub/menu.lst.pacnew
[2011-08-09 00:26] upgraded grub (0.97-17 -> 0.97-19)
[2011-08-09 00:26] upgraded icu (4.8-1 -> 4.8.1-1)
[2011-08-09 00:26] upgraded linux-firmware (20110512-2 -> 20110727-1)
[2011-08-09 00:26] >>> Updating module dependencies. Please wait ...
[2011-08-09 00:26] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2011-08-09 00:26] ==> Building image from preset: 'default'
[2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2011-08-09 00:26] ==> Starting build: 3.0-ARCH
[2011-08-09 00:26] -> Parsing hook: [base]
[2011-08-09 00:26] -> Parsing hook: [udev]
[2011-08-09 00:26] -> Parsing hook: [autodetect]
[2011-08-09 00:26] -> Parsing hook: [pata]
[2011-08-09 00:26] -> Parsing hook: [scsi]
[2011-08-09 00:26] -> Parsing hook: [sata]
[2011-08-09 00:26] -> Parsing hook: [filesystems]
[2011-08-09 00:26] -> Parsing hook: [usbinput]
[2011-08-09 00:26] ==> Generating module dependencies
[2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2011-08-09 00:26] 7079 blocks
[2011-08-09 00:26] ==> Image generation successful
[2011-08-09 00:26] ==> Building image from preset: 'fallback'
[2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2011-08-09 00:26] ==> Starting build: 3.0-ARCH
[2011-08-09 00:26] -> Parsing hook: [base]
[2011-08-09 00:26] -> Parsing hook: [udev]
[2011-08-09 00:26] -> Parsing hook: [pata]
[2011-08-09 00:26] -> Parsing hook: [scsi]
[2011-08-09 00:26] -> Parsing hook: [sata]
[2011-08-09 00:26] -> Parsing hook: [filesystems]
[2011-08-09 00:26] -> Parsing hook: [usbinput]
[2011-08-09 00:26] ==> Generating module dependencies
[2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2011-08-09 00:26] 23360 blocks
[2011-08-09 00:26] ==> Image generation successful
[2011-08-09 00:26] installed linux (3.0.1-1)
I don't think I've mentioned that my old menu.lst seems to have disappeared and so must have been on one of the partitions that were deleted. I did have 2 Arch installations when I was setting things up months ago and that menu.lst may have been on the other partition but pointing to this partiton's kernel for booting. Presumably that's possible since this partiton is definitely the one I have been using for the last several months (confirmed by log and other files updated in the last few days etc). Even so, I suppose that probably wouldn't be relevant to this issue, since grub is finding the menu.lst on this partition when it boots so it is looking in the intended place now.
It seems I'm at a bit of a dead end. It seems these kernel panics are usually because there is something wrong with the kernel - which there wasn't with mine (and presumably the kernel in the new linux package is fine) or there is a typo in menu.lst (I can't see one and nobody has pointed one out yet) or menu.lst is pointing to the wrong partition (mine is pointing to the same partition and /boot directory that is found by grub - which is where my boot image is located - so it seems to be correct). I have nevertheless tried editing the menu.lst entry when booting to boot from different partitions but so far that hasn't worked either.
If anybody has other ideas I'd really appreciate it.
If not, some suggestions on re-installing would also be appreciated. I have a recent tar archive of the partition, but presumably reinstalling that wouldn't be of much use since it would just put back what is currently there. I guess that I need to format the partition, create a separate boot partition, do a fresh install of Arch into the formatted partition (and with boot in the new boot partition). And then restore my tar backup (excluding the boot directory) into the formatted partition?
Any assistance greatly appreciated.
Thanks
belbo
Last edited by belbo (2011-08-08 23:17:49)

How can i change back to os after using bootcamp

Hi, Im the proud owner of a early 2008 mac, I installed windows 7 on my mac using bootcamp. I wanted to clean up my mac by resetting it, there was nothing I really wanted to keep so thats why I wanted to reset. I went to the setting screen you know the one if you can choose when your starting the mac. I had 2 disks one with os x one with windows after using bootcamp you can seperate your disk in 2 new ones. But after I deleted the one with os x, I was ready to re install os x mountain lion. It seemed to work but after restarting my mac, I couldnt change to os x anymore. And cant remember my password for windows and cant even get a new password (Im supposed to have a password disk for windows or something like that?) So Im really stuck here.
Can you help me please?

Try rebooting with the Option key depressed and see if this brings up the bootable devices which includes OS X which you can then select to boot from.

How to keep items on ATV after deleting them on iTunes library

does anyone know how to delete movies/tv shows on the computer's hard disk/i tunes library without loosing them on the ATV after the next sync. My problem is that I am only using a Laptop and my HD is already full and I want to delete some of my movies/tv shows on it and I want to keep them on the ATV. However even if I go to manual sync and uncheck the specific items ATV will delete these movies from its storage upon the next sync process. So is there a way to keep items on the ATV after deleting them in the iTunes library?

Unfortunately, that's not how it's supposed to work.
The important thing to appreciate is that AppleTV is not like an external storage/backup device as you cannot ordinarily get files from it should you need to transfer them elsewhere or you lose the originals. You must back up anything you'd hate to lose in some other way.
Many of us attach an external USB drive to the computer, migrate the iTunes library to that, and stream most content, however that is less practical with a laptop if you need the laptop to be mobile and to use AppleTv when it's on the move.
One thing you could try is to test delete a file from the iTunes library manually. In that way iTunes still holds a reference to the file but complains it can't find it. Not sure if this still causes file deletion from AppleTV as the item is still referenced in the database but you could try it and see (make sure you copy the file somewhere safe first!).
AC
Message was edited by: Alley_Cat

Should I defragment disk after deleting BootCamp ?

Similar Messages

Maybe you are looking for