Partition appearing twice in "startup volume menu"

I have two partitions on my MacBook : Macintosh HD 1 and Macintosh HD 2.
But when i'm booting holding the option (alt) key to select a startup volume the partitions Macintosh HD 1 and Recovery are ok but the volume "Macintosh HD 2" appears twice (basically i have from left to right : MHD 1, MHD 2, MHD 2, Recovery).
I've repaired my hard-drive, permissions... using Disk Utility but it didn't solve the issue.
I've tried to boot on both MHD 2 partitions and they are exactly the same, i think one of them is just an alias or something but i don't know how to delete it.
It's not a big deal but it's awkward !
Any idea ?

The duplicate Macintosh HD 2 appears only when i'm booting holding the option key not in Disk Utility !
I'm getting this :

Similar Messages

ITunes helper and qttask do not appear in my startup files menu

Troubleshooting iTunes not recognizing my iPhone anymore (always worked in the past), after downloading the new iTunes and new iPhone software. Have uninstalled and reinstalled iTunes twice and followed as much of the online troubleshooting as I could. Could not find iTunes helper and qttask in my startup files menu. This must be what is keeping iTunes from recognizing my iPhone. How do I get these files back?

Many thanks.
That can indicate trouble with your Apple Application Support. (Apple Mobile Device Support uses some AAS program files too, so it's consistent with your recognition issue, too.)
I'd try the following instructions:
http://discussions.apple.com/thread.jspa?messageID=11901253&#11901253
(Although those instructions are for a 32-bit Vista, they're pretty much identical for XP. Just read "Uninstall a program control panel" as "Add or Remove Programs control panel" and "Computer" as "My Computer".)

Why does 'Minimize' and 'Zoom' appear twice in the Window menu? They appear under the rule, where all the open windows are listed.

Running FF 6.02 on Mac OS 10.6.8.
Window menu reads:
Minimize
Zoom
Minimize
Zoom
[open window 1]
[open window 2, etc.]

Thanks for your response. However, I see no mention of "layer-xxxxxx" appearing in the Window menu on the Mac menu bar in Firefox ''and'' that link says it only applies to Windows and Linux. May I ask what led you to that theory? Thanks...

SCCM 2012 SP1 - Software Center appears twice in Start Menu

Hi guys,
i just finished implementing a fresh SCCM 2012 SP1 Installation for a customer. The whole OSD works like a charm (except some issues with the latest Windows updates breaking the whole OSD, will open a separate thread for this soon), but after the deployment
the Software Center is appearing twice in the Start Menu (We're using Win7 Enterprise SP1 x86 English with 5 integrated language packs). I first thought this has something to do with the integrated language packs, but both Start Menu entries
are always in the same language.
The strange Thing is, that one entry for the SCCM Software Center is called "Software Center" and the other one "SoftwareCenter" (without a space). We configured 2 Client policies, one with EP-enabled and one without EP. We
deployed the Client Settings to different collections so i don't think that this is causing the Problem?Do you guys have any idea why this is Happening?
Has anyone ever seen this? See a screenshot below:
Thank you.
Cheers
Stefan

Thanks for your Response Thomas.
I don't think it is related to the upgrade to SP1.I think it might be a General issue in SP1. I started with a fresh SCCM 2012 SP1 Installation and i also have 2 Software Center entries in my start menu. If i check the shortcut i can see that one shortcut
was created when i captured my base Image, the other one was created during the Install OS Task Sequence.

DropBox on non-startup volume

Is it possible to create a guest accessible drop box that is accessible via a networked connection, but does not reside on the startup volume of the host? I'm running 10.4.11 with an 80Gb HD. It is partitioned with an 8Gb startup volume and the remainder is for files. I want networked guests to upload files by default to the non-startup volume.
Thanks

Hi, on 10.4.x you'll need Sharepoints to add the other drive as a Normal Share, you can also use it to set Users & Groups that you want to have access...
http://www.hornware.com/sharepoints/

Partitioning startup volume

hi,
i'm a newbie on Mac OS X and I want to partition my HD, which has the startup volume on it. the HD is freshly formatted since there was an error in the header of the volume (?) and the Disk Utility couldn't repair it (Repair button disabled).
so, in the Disk Utility, I used the Partition section of my HD and tried to create 2 partitions, but the Utility wouldn't let me do so because "it's the startup volume".
so how the **** am I suppose to partition the only drive in my notebook?
i'd like to have 2 partitions of 54 GB and 20 GB (total 74).
aaaaaaaaaaaahhhhhhhh please teach me!
NOTE: maybe I used some wrong technical terms because I had to translate them from my OS X French version.

You must do the following:
1. Boot from your Tiger DVD. After the installer loads select your language and click on the Continue button, then select Disk Utility from the Utilities menu.
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. 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 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 will take 30 minutes to an hour or more depending upon the drive size.
This is a destructive process so your hard drive will be completely erased.

Time Capsule appears twice in Airport drop down menu

Menu Bar > Airport drop-down menu: My Time Capsule's wireless name shows up twice in my list of wifi sources. Once in the group with all the other routers and again in a group called "Devices".
Long story short…
I start with a perfectly functional, WPA/WPA2 password-protected Time Capsule: Over a year old. Two MbP's using it for Time Machine backup. Connected to a 1.5TB MyBook external HD via usb. Doubles as my wifi router. Everything's connected to it, including my wifi-enabled printer. Works great. No issues.
I get this idea in my head that I need to hide my wifi signal. I figure it out and ¡Viola! Hidden. Then I try to add my wifi-enabled printer to the list of allowed devices in "Access Control". I hit a big snag and can't figure out how to get it to connect (btw, don't buy a Brother printer. Pure crap). So, I give up and revert permissions back to visible, password-protected state.
Skipping irrelevant issues that I already resolved, I now have the wireless name of my Time Capsule appearing twice in the airport drop down menu. It appears with all the other wifi sources my machine detects AND appears at the bottom under a new category called "Devices".
All I want is to have things back the way they were and this anomaly in the drop down menu is a constant reminder that I #1 failed and #2 bought a crap printer.
(Long story long, I guess. Sorry.) How do I delete this "Devices" group from the airport drop down menu?

Stilts McCoy wrote:
Menu Bar > Airport drop-down menu: My Time Capsule's wireless name shows up twice in my list of wifi sources. Once in the group with all the other routers and again in a group called "Devices".
You might find useful advice in this thread:
http://discussions.apple.com/message.jspa?messageID=12156248
If you want to post a reply, please do so to this thread, not the other one.

Startup Volume screen keeps on appearing - no keys pressed though

I've had this problem since I've had my Mac mini (about a year now). Sometimes the startup volume screen appears despite not having any other Hard Drives connected apart from the boot drive (which is the internal Hard drive) and despite not pressing any keyboard keys on startup.
I am using 10.5.2 with the latest mini firmware and am unable to think what could be causing this? I have selected my main hard-drive in the startup disk preferences and have no permissions/hard drive problems (so says disk utility) but the problem persists. It's a minor annoyance but one I would welcome any help with.
Many thanks,
Paul
Message was edited by: Paul Woodford

Hi and many thanks for the reply.
The only drive I attach is a firewire one to do time machine backups but I always disconnect it once I've finished backing up (the firewire lead is still attached to my Mac though, just not to the drive).
The SMART status of the drive in Disk Utility is verified.
I've taken this Mac back once to be repaired for this problem but they found nothing wrong with it. It is a very intermittent problem though and only occurs rarely. A small, but annoying niggle. I am also using a KVM switch but I didn't have this problem with my last Mac, another mini, connected to the same KVM.

Word 2007, Add-ins menu, items appear twice ...

Hi
I'm using win7 word 2007 and OPM 10.1.
I'm attending a course in OPA/OPM and we have seen that the Add-ins menu appear weird.
Several students that attend the course are seeing the same phenomena.
If I select the add-in tab in word, the OPM short cuts appear twice, first one set, then when I scroll further to the right a second set appears.
It is only the right most set that works.
If I hover the mouse over the first set smiley face, the tooltip says "Haley Office Rules: Compile (Alt+R) ". If I check the tooltip of the rightmost set it says, "Oracle Policy Modeling: Compile (Alt+R)"
I have only installed OPM 10.1 on this pc. Not any older version (like old Haley versions)
kind regards,
Michael

Hi
Try these 3 tips to restore the toolbar to how it should display:
1. With your project open in Oracle Policy Modeling, run Update Oracle Policy Templates from the Tools menu. This will attempt to make sure the correct Word template is attached to each project Word document that is not currently excluded from the build. Open a Word document to see if the toolbar/ribbon is now displayed correctly. If not, continue to step 2.
2. Try resetting the UI language for your project. To do this, choose Options from the Tools menu in Oracle Policy Modeling. Select Environment. Select General. Under Authoring UI Language, choose a language other than your preferred UI language, and click OK. Then repeat these steps to revert to your preferred language. Open a Word document to see if the toolbar/ribbon is now displayed correctly. If not, continue to step 3.
3. Open one of the Word documents in your Policy Modeling project. Run the macro UpdateToolbar: In Word 2007, choose the View ribbon, then select Macros/View Macros, highlight the UpdateToolbar macro, then choose Run.
Regards
Matthew Bickham
Applications Consulting Project Manager, Phone: +447787 570634
Email: [email protected], Oracle Policy Automation, United Kingdom

Help menu appears twice

I upgraded to the latest release of quicktime yesterday and now when I open QT the help menu appears twice at the top. Has anyone else seen this?

Hi there,
Exactly the same thing happend to me. I posted it on this forum the other day, I was adivised to upgrade my DivX component to version 6, and this got rid of my double help menu's.
Very strange, but it did the trick!
www.divx.com
Stephen

Volume appears twice

When booting and holding down the option key, my primary volume appears twice. I'm sure it's not supposed to and looking for help on removing one instance of it.

After removing the external drive, diskutil list produces the following result:
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                  Apple_HFS Momentus XT             386.0 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data BOOTCAMP               113.2 GB   disk0s4
I have attached a screenshot of the volumes that appear when I hold down option during start. The first two volumes are both named, "Momentus XT".

Same volume name twice in Startup Manager

I have several (bootable) volumes on my LaCie External Firewire drive. One volume (my primary startup volume) is OS 10.3.9. Another volume is an older installation of OS 10.2.8 that I just can't seem to part with. When I use the Startup Manager (pressing Option as the machine starts), I get two volumes labeled "LaCie 10.3" (my primary startup volume name). If I click the LaCie 10.2 volume to start with, I get the gray screen with the Apple logo, and the nothing...no spinning sprocket, no progress, no crash. TechTool Pro tells me that the "StartupFile" on that volume is "Not Present".
How can I permanently rename the OS 10.2 volume so that it shows up in the Startup Manager as LaCie 10.2 (or anything else, for that matter? Or should I just let go of the past and delete the System folder on that volume, sinc I never use OS 10.2 anymore?
Message was edited by: jtcluck

Hi if clients are having communication issue it could be the DNS issue. Both entries are Static or Dynamic.
Also are both entries of same time i.e. Host (A) , NS or CNAME etc.
Thanks

Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff path

$ dmesg -l err
[ 6.330201] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache2
[ 6.332384] systemd[1]: Device dev-disk-by\x2dlabel-raid0.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache2 and /sys/devices/virtual/block/bcache1
[ 6.334041] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache1
[ 6.730564] systemd[1]: Device dev-disk-by\x2dlabel-raid0.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache2 and /sys/devices/virtual/block/bcache3
[ 6.732213] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache3
[ 6.997304] systemd[1]: Device dev-disk-by\x2dlabel-jabod.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf3
[ 6.999960] systemd[1]: Device dev-disk-by\x2duuid-0d19cfc3\x2d7588\x2d4c19\x2db85e\x2dbf3a3db2d4a0.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf3
[ 7.003235] systemd[1]: Device dev-disk-by\x2dlabel-raid1.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf1
[ 7.005881] systemd[1]: Device dev-disk-by\x2duuid-99fd7889\x2dde7a\x2d4b30\x2d9745\x2d8ccb2b1ee75d.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf1
[ 7.194594] systemd[1]: Device dev-disk-by\x2dlabel-aroot.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde1
[ 7.197369] systemd[1]: Device dev-disk-by\x2duuid-3873d8ba\x2d9472\x2d4d92\x2dab0d\x2de94574bd0eae.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde1
[ 7.207859] systemd[1]: Device dev-disk-by\x2dlabel-raid1.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde3
[ 7.210477] systemd[1]: Device dev-disk-by\x2duuid-99fd7889\x2dde7a\x2d4b30\x2d9745\x2d8ccb2b1ee75d.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde3
[ 7.240459] systemd[1]: Device dev-disk-by\x2dlabel-aroot.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2
[ 7.243114] systemd[1]: Device dev-disk-by\x2duuid-3873d8ba\x2d9472\x2d4d92\x2dab0d\x2de94574bd0eae.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2
[ 8.062829] systemd[1]: Device dev-disk-by\x2dlabel-jabod.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb4
[ 8.065328] systemd[1]: Device dev-disk-by\x2duuid-0d19cfc3\x2d7588\x2d4c19\x2db85e\x2dbf3a3db2d4a0.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb4
I've been getting this since I upgraded systemd last week. I tried fixing some of these by removing partitions with the same label that I wasn't using, which worked. The reason I have so many partitions with the same label is due to btrfs. Each partition that makes up a volume in btrfs has the same label. Apparently systemd doesn't like this.
Everything on my system seems to be working fine, however I would like to stop these errors since they are annoying/scary, but without having to reduce all my volumes to single.
Last edited by nstgc (2015-04-26 15:53:20)

I'm running with a wired-only set up. I'll have to wait for the weekend to look into the wireless angle, however I doubt that is the cause for me.
Following dront78's example below is the output of "# hwinfo --partitions"
75: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: bdUI.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda1
Device Files: /dev/sda1, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part1, /dev/disk/by-id/wwn-0x6829766019904589826x-part1, /dev/disk/by-partuuid/77f1354c-3b20-454d-ba60-9dbab9bc8640, /dev/disk/by-uuid/ff387510-d0ad-498f-8d1b-576b26ed103e
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
76: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 2pkM.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda2
Device Files: /dev/sda2, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part2, /dev/disk/by-id/wwn-0x6829766019904589826x-part2, /dev/disk/by-partuuid/44596381-4cfe-4a2d-8e7b-f6427cc089d0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
77: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: W__Q.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda3
Device Files: /dev/sda3, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part3, /dev/disk/by-id/wwn-0x6829766019904589826x-part3, /dev/disk/by-partuuid/c9b404ec-f407-4081-a69c-9b10360d4cf7
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
78: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: z9FV.SE1wIdpsiiC
Parent ID: 3OOL.7ppt9e3ai+9
SysFS ID: /class/block/sda/sda4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sda4
Device Files: /dev/sda4, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part4, /dev/disk/by-id/wwn-0x6829766019904589826x-part4, /dev/disk/by-partuuid/69c0972d-51ed-429c-acea-6e1afd7ebb1f
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #74 (Disk)
80: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: h4pj.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb1
Device Files: /dev/sdb1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part1, /dev/disk/by-id/wwn-0x17950130428369588225x-part1, /dev/disk/by-uuid/2c0f1039-2d4b-4f75-8fa4-529d19cd18fc
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
81: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 8G3o.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb2
Device Files: /dev/sdb2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part2, /dev/disk/by-id/wwn-0x17950130428369588225x-part2, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
82: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: bRJs.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb3
Device Files: /dev/sdb3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part3, /dev/disk/by-id/wwn-0x17950130428369588225x-part3, /dev/disk/by-label/old-raid1, /dev/disk/by-uuid/dfa989d8-edac-4c7e-b6fc-45237e6a0ebc
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
83: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 2dZw.SE1wIdpsiiC
Parent ID: WZeP.bTSLTpVNGx8
SysFS ID: /class/block/sdb/sdb4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdb4
Device Files: /dev/sdb4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part4, /dev/disk/by-id/wwn-0x17950130428369588225x-part4, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #79 (Disk)
85: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: mX79.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc1
Device Files: /dev/sdc1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part1, /dev/disk/by-id/wwn-0x4611505914592251905x-part1, /dev/disk/by-uuid/80780835-de4b-462c-b7f0-2b389d3e2c2f
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
86: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: DjND.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc2
Device Files: /dev/sdc2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part2, /dev/disk/by-id/wwn-0x4611505914592251905x-part2, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
87: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: gudH.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc3
Device Files: /dev/sdc3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part3, /dev/disk/by-id/wwn-0x4611505914592251905x-part3, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
88: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 74uL.SE1wIdpsiiC
Parent ID: _kuT.rgQvtxWxfg6
SysFS ID: /class/block/sdc/sdc4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdc4
Device Files: /dev/sdc4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part4, /dev/disk/by-id/wwn-0x4611505914592251905x-part4, /dev/disk/by-label/old-aroot, /dev/disk/by-uuid/b396dd50-e3f1-4b74-8cac-7d8d79a75386
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #84 (Disk)
90: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: r_Ra.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd1
Device Files: /dev/sdd1, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part1, /dev/disk/by-id/wwn-0x14865109125905272832x-part1, /dev/disk/by-partlabel/Microsoft\x20reserved\x20partition, /dev/disk/by-partuuid/f3e9ce24-988d-40ef-bd5c-6313c808bef2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
91: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: IAie.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd2
Device Files: /dev/sdd2, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part2, /dev/disk/by-id/wwn-0x14865109125905272832x-part2, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/f3344931-99c3-11e4-8601-806e6f6e6963, /dev/disk/by-uuid/30F403F0F403B75E
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
92: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: lLyi.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd3
Device Files: /dev/sdd3, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part3, /dev/disk/by-id/wwn-0x14865109125905272832x-part3, /dev/disk/by-partlabel/EFI\x20system\x20partition, /dev/disk/by-partuuid/ffbaa0cc-99c7-11e4-8625-806e6f6e6963, /dev/disk/by-uuid/0DE5-0CB0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
93: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: CXCn.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd4
Device Files: /dev/sdd4, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part4, /dev/disk/by-id/wwn-0x14865109125905272832x-part4, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/ffbaa0b6-99c7-11e4-8625-806e6f6e6963, /dev/disk/by-uuid/FE2648382647EFE7
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
94: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: fiSr.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd5
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd5
Device Files: /dev/sdd5, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part5, /dev/disk/by-id/wwn-0x14865109125905272832x-part5, /dev/disk/by-label/flbck, /dev/disk/by-partuuid/bd84f197-066e-4b9e-bf9b-b0b3a4090cde, /dev/disk/by-uuid/832bcc8d-836e-4b4e-8d9c-0a19f5bcf7dd
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
95: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: 6uiv.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd6
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd6
Device Files: /dev/sdd6, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part6, /dev/disk/by-id/wwn-0x14865109125905272832x-part6, /dev/disk/by-partuuid/8f77bc79-ba57-462e-8beb-d09db5c77490
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
96: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: oKuO.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd7
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd7
Device Files: /dev/sdd7, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part7, /dev/disk/by-id/wwn-0x14865109125905272832x-part7, /dev/disk/by-partuuid/7ca3eb27-d198-4915-9c71-e96fa7a34d8b, /dev/disk/by-uuid/fd43f1bd-9f52-41b7-badc-4ab7881473ee
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
97: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: GW8T.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd8
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd8
Device Files: /dev/sdd8, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part8, /dev/disk/by-id/wwn-0x14865109125905272832x-part8, /dev/disk/by-partuuid/550f9e19-c0ec-4474-9e98-84c727854158
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
98: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: cPdt.SE1wIdpsiiC
Parent ID: Rw8Y.lfY9_MpZuK1
SysFS ID: /class/block/sdd/sdd10
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdd10
Device Files: /dev/sdd10, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part10, /dev/disk/by-id/wwn-0x14865109125905272832x-part10, /dev/disk/by-label/bckup, /dev/disk/by-partuuid/de7eaa1e-66b0-4058-ad71-d0f8ea470b2f, /dev/disk/by-uuid/723d7788-8514-4777-8e07-e0faa48c9a83
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #89 (Disk)
100: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: wRm+.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde1
Device Files: /dev/sde1, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part1, /dev/disk/by-id/wwn-0x9832618751734861824x-part1, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
101: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: Nd04.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde2
Device Files: /dev/sde2, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part2, /dev/disk/by-id/wwn-0x9832618751734861824x-part2, /dev/disk/by-uuid/aa19d2cf-e59d-4277-a5e6-d0078ede6d3b
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
102: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: qoG8.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde3
Device Files: /dev/sde3, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part3, /dev/disk/by-id/wwn-0x9832618751734861824x-part3, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
103: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: H_WC.SE1wIdpsiiC
Parent ID: u5Pc.jfv0tLKpnVA
SysFS ID: /class/block/sde/sde4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sde4
Device Files: /dev/sde4, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part4, /dev/disk/by-id/wwn-0x9832618751734861824x-part4
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #99 (Disk)
105: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: +u4R.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf1
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf1
Device Files: /dev/sdf1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part1, /dev/disk/by-id/wwn-0x8355873293896667137x-part1, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
106: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: S4LV.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf2
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf2
Device Files: /dev/sdf2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part2, /dev/disk/by-id/wwn-0x8355873293896667137x-part2, /dev/disk/by-uuid/96fa47c5-061d-4849-8582-7186cc1695d2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
107: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: vFbZ.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf3
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf3
Device Files: /dev/sdf3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part3, /dev/disk/by-id/wwn-0x8355873293896667137x-part3, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
108: None 00.0: 11300 Partition
[Created at block.414]
Unique ID: NRrd.SE1wIdpsiiC
Parent ID: LHfg.eZsVjjzwg10
SysFS ID: /class/block/sdf/sdf4
Hardware Class: partition
Model: "Partition"
Device File: /dev/sdf4
Device Files: /dev/sdf4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part4, /dev/disk/by-id/wwn-0x8355873293896667137x-part4, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #104 (Disk)
i don't have time to look at this in detail this morning, but I will this afternoon.
Thank you for all the replies. Have any of you found this to actually be damaging?
[edit] In an effort to not be completely lazy, and because I was curious, I did check a bit into netctl. Running "$ netctl list" returned exactly nothing. I have no profiles.
[edit2]
I just ran "$ dmesg -l err" on my laptop and I'm not getting any errors.
Last edited by nstgc (2015-04-27 15:09:46)

Bootcamp partition appears empty to mac after restore...

I recently chose to upgrade the HD in my 2007 macbook, in order to squeeze another year or 2 out of it. Setting up the mac part was no problem - just used superduper to copy the old disk to the new one while it was temporarily mounted in an external drive, then replaced the disk - worked perfectly.
The bootcamp partition is another story. I did a bunch of research on how to best transfer my old windows 7 setup, and found the windows system backup and restore method was advised, and easy, so went with that method. Ran boot camp assistant, had it create the new ntfs partition the same as the old one, and ran the system restore from the windows setup disk, and it worked fine. Windows 7 works just as it once did, and I ran the bootcamp driver setup again just in case. Everything appears hunky dory on the windows side of things, and I can easily boot back into the mac os from it.
So everything appears ok, but here's the problem - once I return to mac os, the bootcamp partition appears empty, and I don't have the option to boot to it via the Startup Disk in System Preferences, which is how I always used to boot to windows. I can still get into windows via the bootcamp assistant, but that's a really tedious affair that involves inserting the windows disk.
Edit - I should add that I can also get into windows by using the option key during startup, that seems to work ok. But I still can't access the files in the bootcamp partition, which is a big problem - can this be fixed?
Any ideas?
Message was edited by: sduck409

Thanks for the many ideas Hatter. I think you jogged my brain in the right direction. I tried the convert to ntfs thing, but the windows install already thinks it's ntfs. And since the disk is actually formatted as fat32, the fat is screwed up. I actually knew that thing about boot camp assistant only creating fat32 (once, a while ago), but forgot that detail in my hurry.
So I ran bootcamp assistant, and deleted the bootcamp partition, with the idea of starting again. Ran bootcamp assistant again to restart the process, but this time it said Bootcamp assistant can not run - this disk is not supported. Hmmm. I had already inserted the windows disk and my windows backup volume.
SO I figured I'd try restarting my computer; maybe that'd reinitialize the disk or something and bootcamp assistant would work. Hey, stranger things have worked in the past. But, for some reason the windows disk started up! And started copying files. I aborted it, but it was too late - it had somehow mangled my mac disk - it was now a empty fat32 disk - I had to reboot from the mac os x setup disk and run disk utility to find this out. So now I'm restoring from my time machine backup (I absolutely love time machine btw).
The backup is going to take another 3 hours, so to get some stuff done I resurrected an old sony vaio win xp laptop that dates from 2000 I think. Holey moley, this thing is crappy.
Anyway, thanks for the help. Once I get the machine back up and running, I'll try it again, and this time make sure the disk is actually ntfs before restoring to it.

Startup Disk menu can no longer detect the hard drive

I am trying to boot my dvd from the startup disk menu (the screen when you press alt and brings up Mac or Windows) as Paragon CamptuneX has adjusted my directory files when I expanded the partition size and it is required to boot from the windows DVD to reorder the directory. But for some reason, the startup disk menu cannot find the dvd drive? I can hear it spinning and there is no problem detecting the DVD once I boot into Mac OSX.......
Any ideas what I should do? I'm trying to avoid cleaning out Bootcamp, and reinstalling it all over again....

Okay, second question: How does this forum software work? According to the thread list, someone named MacWizard has replied to this thread, but I can't see it.
MacWizard, if you could email your reply to spearbrave at gmail point c0m so I can read it there, I'd appreciate it.
15" MacBook Pro C2D Mac OS X (10.4.8)

Partition appearing twice in "startup volume menu"

Similar Messages

Maybe you are looking for