New storage harddrive has be mounted every boot ... SOLVED

I put a new hard drive in as a slave for data.. used gparted to format it and label it.. but everytime i reboot.. the links to the various folders are empty.. as if its not there.. i have to back to gparted, unmount it, then close gparted and its there and i have to re find the links for wallpapers, and my music to play music or to have switching wallpapers..
any ideas??? I thought once you named it, formated it, via gparted, it was just "there" every reboot?
am i missing something..
I just checked fstab, and it's not there.. just alot of UUID numbers.. how do i add a hard drive??? iread the posts.. and i have no clue what is meant or how to do it???
UUID=64cb2ee2-8132-4632-b1fd-661af630d315 / ext4 defaults 0 1
UUID=8bef63b2-e0d2-42a5-b747-7ff8710883a8 /home ext4 defaults 0 1
UUID=8ff88b2a-bc7b-42a8-8682-38d7f0c825f9 swap swap defaults 0 0
UUID=fd64e00d-457d-4c99-8ba7-c790402d66fd /boot ext2 defaults 0 1
I did the above by opening Kate and looking at fstab as a normal user..
the harddrive is working.. i'm playing music from it now.. so i did this command and got the following
-l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 10 Jul 16 06:59 579a08ea-3bb0-450c-a88e-cf248488c29e -> ../../sdb1
lrwxrwxrwx 1 root root 10 Jul 16 06:59 64cb2ee2-8132-4632-b1fd-661af630d315 -> ../../sda3
lrwxrwxrwx 1 root root 10 Jul 16 06:59 8bef63b2-e0d2-42a5-b747-7ff8710883a8 -> ../../sda4
lrwxrwxrwx 1 root root 10 Jul 16 06:59 8ff88b2a-bc7b-42a8-8682-38d7f0c825f9 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jul 16 06:59 fd64e00d-457d-4c99-8ba7-c790402d66fd -> ../../sda1
now I have no idea what to do with this information above and how to add it to fstab ?
do i just add (the sdb1 entry like this) UUID=579a08ea-3bb0-450c-a88e-cf248488c29e / ext4 defaults 0 1
to fstab? if "yes" , then do i put it at the top where it is with that command output, or on the bottom?
its mounted in dolphin as /media/%mystuff so will it look like this instead?
UUID=579a08ea-3bb0-450c-a88e-cf248488c29e /media/%mystuff ext4 defaults 0 1
or
UUID=579a08ea-3bb0-450c-a88e-cf248488c29e /%mystuff ext4 defaults 0 1
i'm totally lost, and i dont want to have to thru mount -a or opening up gparted everything I want to use this data drive with pics, music, documents, etc on it
I just installed autofs (said it automounts even those drives that dont show up in fstab) this didnt work..
i had to open up dolphin and add entry and i hit cancel and everything then showed up?
do i have to go thru this every reboot?
I FIXED IT, by reading the wiki and googling.. added this entry to fstab
UUID=579a08ea-3bb0-450c-a88e-cf248488c29e /media/%mystuff ext4 defaults 0 1
rebooted, voila.. i was about to have a meltdown.. i guess reading is funda-mental !!!
thanks
Last edited by binskipy2u (2010-07-16 14:25:12)

binskipy2u wrote:
should I have made that 1 a 2?? and why? just wondering?
but it seems to all work now.. at reboot..
2, you didn't read the wiki page I posted did you?
binskipy2u wrote:
i put the % there /media/%mystuff ext4 defaults 0 1
I have NO idea how that % got in there.. but now I cant rename it to just /media/mystuff
even in root..
why? what's your default shell? in bash:
mv /media/{%,}mystaff
EDIT: of course you have to unmount /media/%mystaff first.
Last edited by sisco311 (2010-07-16 23:17:16)

Similar Messages

Dhcpcd eth0 on every boot SOLVED

Hi, I just installed Duke on my IBM T30 and it won't connect to eth0 automatically.
I have to type "dhcpcd eth0" every boot and it connects OK.
Have I missed a setting somewhere?
Thanks for your help
Regards
Last edited by drum (2007-05-23 07:12:18)

Thanks
I read it and discovered there was a space between eth0 and the = sign.
Cheers mate all fixed

New hard disk has blank Mount Point

I recently installed a new disk which I am now using as my main HD.
From within System Profiler and also Disk Utility I have noticed that the mount point is blank, whereas the old HD disk had a mount point of '/Volumes/Macintosh HD'.
Is this OK? All seems to be OK with the new disk but I would like to confirm if I have to do anything else with the new disk.
Thanks.

The standard mount point for a startup volume is '/'. This isn't blank but the Unix terminology for a startup volume if you are running Disk Utility from the startup volume.

Have to do alsaconf on every boot [SOLVED]

A couple days ago it told me something about my sound card stopped working and its going to default and i dont have sound on default but if i do alsaconf i get sound back. Problem is i have to do alsaconf every bootup.
I have done alsactl store and whatnot and looked through google for this and saw that someone had listed modules before alsaconf and after alsaconf and blacklisted the modules alsaconf didnt re-activate, but im not sure how to view the running modules.
Last edited by leercrak (2010-12-16 05:17:18)

i did alsactl -f /var/lib/alsa/asound.state store and it didnt save the settings.
my guess is theres a module thats doing it.
going to do an lsmod before alsaconf
lsmod during alsaconf
and an lsmod after to see what needs to die.
edit: ya..theres nothing happening with the modules before,during and after are exactly the same.
Last edited by leercrak (2010-12-14 23:00:01)

Hello, I have a 2009 iMac, and my harddrive has failed several times now, and now I need to re-install snow leopard but my install DVD is damaged and I have bought a new snow leopard disc. However my iMac will not read the disc at all ?

Hello, I have a 2009 iMac, and my harddrive has failed several times now.
I tired to reinstall snow leopard with the install DVD that came with my iMac. However the disc is damaged so I bought a new Snow Leopard but my iMac wont read the new disc, it just stays in the apple logo screen, I have tired safe boot, holding down the "C" key on startup and tried using disc utility but getting nowhere.
Please help. Thanks.

Might be related, if your hard drive is a 1TB drive,it could be a Seagate drive.
The drives are known to fail and your iMac maybe covered for free replacement under the Apple's Seagate hard drive replacement program until April 12 of this year.
I Believe the 2009 models are covered under this replacement warranty.
You can find out if you are eligible here.
http://www.apple.com/support/imac-harddrive/
Good Luck!

I just got my new iPhone4 set up today and it has pulled in every email that is in my desk top as being unread. Yet I have read all the emails. Still the iPhone thinks they are unread. Does anyone know how I can delete all of these at one time?

I just got my new iPhone4 set up today and it has pulled in every email that is in my desk top as being unread. Yet I have read all the emails. Still the iPhone thinks they are unread. Does anyone know how I can delete all of these emails at one time from the phone?

I have taken it back to the Apple store genius bar, but they say they don't see anything wrong. Well unless you use it all day and experience the problems when they happen, you wont see anything wrong. But there are lots wrong with it. But this would be the same store as I purchased the phone. And they backed up my old Iphone 4, but were not able to get anything to load back onto my new phone. So, I lost pretty much everything. But over time, some of my contacts have started showing up, although i am still missing over 800 of them.

Problem description: My macbook pro since this afteon has been slower, every application I open, it takes a long time to open, and shows the spinning beach ball for a while before it opens or performs some task, or responds to a click- EtreCheck

My computer
Problem description:
My macbook pro since this afternoon has been slower, every application I open, it takes a long time to open, and shows the spinning beach ball for a while before it opens or performs some task, or responds to a click…
EtreCheck version: 2.1.8 (121)
Report generated 31 de março de 2015 18:29:15 BRT
Download EtreCheck from http://etresoft.com/etrecheck
Click the [Click for support] links for help with non-Apple products.
Click the [Click for details] links for more information about that line.
Hardware Information: ℹ️
    MacBook Pro (13-inch, Early 2011) (Technical Specifications)
    MacBook Pro - model: MacBookPro8,1
    1 2.3 GHz Intel Core i5 CPU: 2-core
    16 GB RAM Upgradeable
        BANK 0/DIMM0
            8 GB DDR3 1333 MHz ok
        BANK 1/DIMM0
            8 GB DDR3 1333 MHz ok
    Bluetooth: Old - Handoff/Airdrop2 not supported
    Wireless: en1: 802.11 a/b/g/n
    Battery Health: Normal - Cycle count 250
Video Information: ℹ️
    Intel HD Graphics 3000 - VRAM: 512 MB
        Color LCD 1280 x 800
System Software: ℹ️
    OS X 10.10.2 (14C1514) - Time since boot: 0:25:47
Disk Information: ℹ️
    Hitachi HTS545032B9A302 disk0 : (320,07 GB)
        EFI (disk0s1) <not mounted> : 210 MB
        Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB
        Macintosh HD (disk1) / : 318.84 GB (47.94 GB free) - 51 errors
            Core Storage: disk0s2 319.21 GB Online
    MATSHITADVD-R   UJ-898
USB Information: ℹ️
    Apple Inc. Apple Internal Keyboard / Trackpad
    Apple Inc. BRCM2070 Hub
        Apple Inc. Bluetooth USB Host Controller
    Apple Inc. FaceTime HD Camera (Built-in)
    Apple Computer, Inc. IR Receiver
Thunderbolt Information: ℹ️
    Apple Inc. thunderbolt_bus
Gatekeeper: ℹ️
    Mac App Store and identified developers
Launch Agents: ℹ️
    [not loaded]    com.adobe.AAM.Updater-1.0.plist [Click for support]
    [loaded]    com.oracle.java.Java-Updater.plist [Click for support]
    [running]    com.trusteer.rapport.rapportd.plist [Click for support]
Launch Daemons: ℹ️
    [loaded]    com.adobe.fpsaud.plist [Click for support]
    [loaded]    com.adobe.SwitchBoard.plist [Click for support]
    [loaded]    com.microsoft.office.licensing.helper.plist [Click for support]
    [loaded]    com.oracle.java.Helper-Tool.plist [Click for support]
    [loaded]    com.oracle.java.JavaUpdateHelper.plist [Click for support]
    [running]    com.trusteer.rooks.rooksd.plist [Click for support]
User Launch Agents: ℹ️
    [loaded]    com.adobe.AAM.Updater-1.0.plist [Click for support]
    [loaded]    com.adobe.ARM.[...].plist [Click for support]
    [loaded]    com.google.keystone.agent.plist [Click for support]
    [running]    com.spotify.webhelper.plist [Click for support]
User Login Items: ℹ️
    iTunesHelper    UNKNOWN Hidden (missing value)
    AdobeResourceSynchronizer    Application Hidden (/Applications/Adobe Reader.app/Contents/Support/AdobeResourceSynchronizer.app)
    Stickies    Application (/Applications/Stickies.app)
Internet Plug-ins: ℹ️
    JavaAppletPlugin: Version: Java 8 Update 31 Check version
    FlashPlayer-10.6: Version: 17.0.0.134 - SDK 10.6 [Click for support]
    Default Browser: Version: 600 - SDK 10.10
    AdobePDFViewerNPAPI: Version: 10.1.13 [Click for support]
    AdobePDFViewer: Version: 10.1.13 [Click for support]
    Flash Player: Version: 17.0.0.134 - SDK 10.6 [Click for support]
    QuickTime Plugin: Version: 7.7.3
    SharePointBrowserPlugin: Version: 14.4.8 - SDK 10.6 [Click for support]
    Google Earth Web Plug-in: Version: 7.1 [Click for support]
    Silverlight: Version: 5.1.30514.0 - SDK 10.6 [Click for support]
    iPhotoPhotocast: Version: 7.0 - SDK 10.8
User internet Plug-ins: ℹ️
    npsf_cef: Version: sf 3.3.1.1 [Click for support]
    Google Earth Web Plug-in: Version: Unknown
Safari Extensions: ℹ️
    DivX HiQ
    DivX Plus Web Player HTML5 <video>
3rd Party Preference Panes: ℹ️
    Flash Player [Click for support]
    Java [Click for support]
    MacFUSE [Click for support]
    Perian [Click for support]
    Trusteer Endpoint Protection [Click for support]
Time Machine: ℹ️
    Skip System Files: NO
    Auto backup: YES
    Volumes being backed up:
        Macintosh HD: Disk size: 318.84 GB Disk used: 270.90 GB
    Destinations:
        Time Machine Backups [Local]
        Total size: 999.86 GB
        Total number of backups: 60
        Oldest backup: 2012-07-15 01:16:54 +0000
        Last backup: 2015-03-29 19:28:06 +0000
        Size of backup disk: Excellent
            Backup size 999.86 GB > (Disk size 318.84 GB X 3)
Top Processes by CPU: ℹ️
        97%    rapportd
         3%    WindowServer
         1%    mds
         0%    fseventsd
         0%    distnoted
Top Processes by Memory: ℹ️
    155 MB    Safari
    120 MB    Finder
    86 MB    rapportd
    86 MB    WindowServer
    69 MB    mds_stores
Virtual Memory Information: ℹ️
    12.56 GB    Free RAM
    2.53 GB    Active RAM
    428 MB    Inactive RAM
    1.66 GB    Wired RAM
    1.04 GB    Page-ins
    0 B    Page-outs
Diagnostics Information: ℹ️
    Mar 31, 2015, 06:00:15 PM    Self test - passed
    Mar 31, 2015, 01:13:05 PM    /Users/[redacted]/Library/Logs/DiagnosticReports/Microsoft Error Reporting_2015-03-31-131305_[redacted].crash
    Mar 31, 2015, 01:05:42 PM    /Users/[redacted]/Library/Logs/DiagnosticReports/Microsoft Error Reporting_2015-03-31-130542_[redacted].crash
    Mar 31, 2015, 12:24:33 PM    /Users/[redacted]/Library/Logs/DiagnosticReports/Microsoft Error Reporting_2015-03-31-122433_[redacted].crash
    Mar 30, 2015, 05:45:38 PM    /Library/Logs/DiagnosticReports/Skype_2015-03-30-174538_[redacted].cpu_resource .diag [Click for details]
    Mar 30, 2015, 01:52:07 PM    /Users/[redacted]/Library/Logs/DiagnosticReports/Last.fm Scrobbler_2015-03-30-135207_[redacted].crash
    Mar 29, 2015, 05:55:05 PM    /Users/[redacted]/Library/Logs/DiagnosticReports/com.apple.WebKit.WebContent_20 15-03-29-175505_[redacted].crash
    Mar 29, 2015, 01:06:38 PM    /Library/Logs/DiagnosticReports/VLC_2015-03-29-130638_[redacted].hang
    Mar 29, 2015, 01:02:47 PM    /Library/Logs/DiagnosticReports/VLC_2015-03-29-130247_[redacted].hang

Open Activity Monitor and kill this process - rapportd.
Reinstalling OS X Without Erasing the Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Reinstalling OS X Without Erasing the Drive
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility and press the Continue button. After Disk Utility loads select the Macintosh HD entry from the the left side list. Click on the First Aid tab, then click on the Repair Disk button. If Disk Utility reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit Disk Utility and return to the main menu.
Reinstall OS X: Select Reinstall OS X and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
Alternatively, see:
Reinstall OS X Without Erasing the Drive
Choose the version you have installed now:
OS X Yosemite- Reinstall OS X
OS X Mavericks- Reinstall OS X
OS X Mountain Lion- Reinstall OS X
OS X Lion- Reinstall Mac OS X
     Note: You will need an active Internet connection. I suggest using Ethernet
                 if possible because it is three times faster than wireless.

Installing OSX after installing new internal harddrive in MacBook

I am installing new 250GB harddrive in my MacBook. After installation, do I have to reinstall OSX from the Leopard disc, or is there a way to do it from my backups on an external drive created with Time Machine?

First you need to prep your new drive:
Extended Hard Drive Preparation
1. Open Disk Utility in your Utilities folder. If you need to reformat your startup volume, then you must boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger or Leopard.)
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Set the number of partitions from the dropdown menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (only required for Intel Macs) then click on the OK button. Click on the Partition button and wait until the volume(s) mount on the Desktop.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
To restore from a TM backup see Restoring files from a Time Capsule backup. Note that the procedures are basically the same for restoring from a TM backup on a non-Time Capsule backup drive.

Every boot: Superblock last access time in future. HARDWARECLOCK bug?

Hi,
Recently (about the last month or so?) every time I boot my Arch, the boot process stops with "superblock last access time in future (time1), now it is (time2)", and a check is forced. The check never finds or corrects any error, but when I reboot it starts normally. This happens at every boot, but only some of the reboots.
The weirdest thing is what is the value of time1: I'm at GMT+8, and time2 always shows the current local time, while time1 is a bit less then 8 hours in the future.... It looks like at some point of the boot the timezones are applied in a weird way. In rc.conf I have HARDWARECLOCK="localtime" because the windows dual-boot needs that, unfortunately. So maybe the hardware clock is first treated as "UTC" and the time zone is added, then a few seconds later it is treated as "localtime" correctly...
Is there a way to diagnose this? Check what exactly happens during the boot? Or someone has a solution?
Cheers,
Greg

I had a similar problem only on rare occasions though, you could try setting the last mount time with
tune2fs -T now /dev/sda1
or what ever your hard drive partitions numbers happen to be.
Not sure if this was necessary but i also commented out the sections saving system clock in /etc/rc.shutdown
I am running on localtime and have openntpd adjusting the system clock as it seems to fall behind time if i don't, and have not had any problems since

Install: Error Message from mount, invalid boot interface"

Hi,
I'm booting into installation from CD1, and after the configuration assistant screen, I select the CD as the boot device, then get the error screen:
"Error Message from mount, invalid boot interface".
I've tried re-burning a new CD, but get the same error.
Any ideas to resolve this? Thanks in advance
Solaris 9 x86 12/02. AMD Duron 1300, EIDE CD Drive / 40Gb internal HD

Not up on my x86 here, and it has been a long time since I was installing from CD, but shouldn't your book device be the disk where you want the installation to go (in your case the presumable 2nd partition on your 40Gb disk).

External drive does not mount on boot

I have a Toshiba MK5055GSX 500GB external drive which I use for Time Machine but for some reason it does not automatically mount from a cold boot. Before I started to use it for Time Machine (it was formatted as NTFS at the time) I had not problems with it. All other external drives correctly mount on boot.
I had thought it might be a problem with the drive itself but if I disconnect it and reconnect it with my iMac running it mounts every time without fail. If I reboot after it has mounted it also mounts at boot. Only if I start the iMac using the power button with the drive already connected does it fail to mount and the results are consistently repeatable.
Does anyone have any ideas why this might be happening and how to fix it?

Does this drive have a separate power brick? If it does I suggest using it to see if that fixes the problem. If the enclosure has both USB and Firewire ports try using the drive on a Firewire port instead of a USB port.
It sounds like the drive is not spinning up early enough in the startup process to be detected.
Not knowing how you prepared the drive for the Mac, you should re-prep the drive as follows:
Extended Hard Drive Preparation
1. Open Disk Utility in your Utilities folder.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.

New storage node not taking any traffic

Hi all,
I have a strange situation where we introduced a few new storage nodes into a cluster that already had about 190 storage nodes running. From what I can tell, the nodes joined the cluster just fine (I see them listed as part of the cluster according to the JMX node, and their logs indicate as much).
The problem is that they don't seem to take any traffic. Their get and put counts are at 0, their size is at 0. They have the exact same configuration as every other node running in the cluster, and are even running on the same box as other storage nodes (so shouldn't be networking related).
Any ideas as to what could cause this to happen? They nodes have been up for days now and nothing has changed. There isn't anything along the lines of errors in the storage node logs or anything that seems to be related or would indicate a problem.
Thanks,
Chris

Hi Chris,
What is your partition count set to, is it still the default of 257? If it is then this could be your problem, I have had issues in the past with partition counts too close to the cluster size. For a cluster of 190 nodes you really need a big partition size, we have 8191 on a 170 node cluster.
JK

Prevent Encrypted Partition From Mounting at Boot

I have an external USB HDD partitioned into two. Both partitons are encrypted. I use partition A for a time machine backup for my mac, and the other (when pluged in to a different macbook) is used similarly for that machine. Every time I boot up, or plug the drive in, I get 2 dialogue boxes asking me to enter passwords - one for each partiton.
I'd like is to set my OS to not mount the second partition on boot at all (no password dialogue / no disk in finder). If I need to mount it, I'd like to be able to do so via Disk Utility.
I've tried using the method described here: https://discussions.apple.com/thread/4271735?start=0&tstart=0, but it does not work - perhaps because my partiton is encrypted? Is there perhaps a different fs type for encrypted disks? (not "hfs").
I've also followed this thread: https://discussions.apple.com/thread/4870225 , but I'm reticent to switch off automounting totally because I use other encrypted disks for work and need them to mount at boot.
Any thoughts?

Linc Davis wrote:
It seems that the fstab method doesn't work with CoreStorage volumes.
Yes, that's correct. Core Storage doesn't look at fstab at all.
If the only Core Storage volumes you have are encrypted containers, you can achieve the desired outcome by disabling boot time invocation of the Core Storage daemon. Please note that Apple's Fusion Drive technology relies on Core Storage, so if you have a system with Fusion Drive, this workaround may break your computer.
Linc Davis wrote:
There is no way I know of to prevent automounting of CoreStorage volumes selectively. You may be able to prevent all CS volumes from automounting by deleting or commenting out the "LaunchEvents" key in this file:
That's the idea, but good heavens, don't comment things out in launch plists! Do it right, use launchctl.
The Core Storage daemon normally runs at boot, and manages logical volumes assigned to Core Storage—specifically, in the OP's case, encrypted containers. If you have no other mission-critical Core Storage volumes, you may use the launchctl command to disable the Core Storage daemon, using the unload -w argument, as per the launchctl man page:
unload [-w] [-S sessiontype] [-D domain] paths ...
              Unload the specified configuration files or directories of con-
              figuration files. This will also stop the job if it is running.
              -w       Overrides the Disabled key and sets it to true. In pre-
                       vious versions, this option would modify the configura-
                       tion file. Now the state of the Disabled key is stored
                       elsewhere on-disk.
So, in Terminal, the command to prevent Core Storage from running at boot time would be as follows:
$ sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.corestorage.corestoraged.plist
Please note again that Apple's Fusion Drive technology relies on Core Storage, so if you have a system with Fusion Drive, this workaround may break your computer.
After disabling the Core Storage daemon, you may still mount encrypted volumes using Disk Utility, or the command line (hdiutil attach /dev/diskX where /dev/diskX is the encrypted container).
Hope this helps.

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

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

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

External HDD won't mount at boot. [Solved]

Edit:
I've noticed that this is an issue regarding my NTFS partition being on an external drive. Please check post #8 by me to get further details.
Hello guys, I'm having some problems getting my external NTFS HDD to mount automatically at boot. I have installed HAL and NTFS-3G, but I'm still getting problems. Mounting once the computer has finished booting is no problem using the simple mount command (sudo mount /media/pebble). I see no reason why this should be having problems mounting at boot with my fstab entry, but no errors occur when mounting manually.
Fstab entry:
/dev/sdc1 /media/pebble ntfs-3g fmask=022 1 0
rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="America/Vancouver"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(fuse)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="r3-desktop-arch"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
eth0="eth0 192.168.0.23 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng network netfs crond dbus hal alsa)
Do I need to load HAL earlier? What am I doing wrong?
Last edited by ryeguy146 (2009-11-05 10:04:32)

I just noticed something, I don't think that this is an issue with the partition being NTFS, but rather with it being on an external hard drive (/dev/sdc). I say this because I just rebooted and noticed another NTFS partition that I have in my fstab is mounting (/dev/sda5). It's an internal HDD, and I didn't notice that it mounted up because I rarely use it. But there it is.
I suppose that I should define /dev/sdc. It is a Western Digital External HDD running off of a USB 2.0 cable. I don't know why this makes a difference, but it apparently does. Both entries in the fstab are identical for their respective devices and mount points.
Now that we have that figured out, I think that I'll change the title of the thread. So any ideas on how to solve this one?

New storage harddrive has be mounted every boot ... SOLVED

Similar Messages

Maybe you are looking for