Dmraid ignores partitions on primary array

I have two RAID 0 arrays on my installation. One array is two OCZ SSDs (named Sigma) and the other is a 2TB array (named Chi) for storage purposes. Both arrays were build using the Intel Matrix Storage Manager tool on my motherboard (just above the BIOS), and partitioned with a live-session of GParted. Originally when I installed Arch, dmraid did not pick up on the partition of the 2TB array, just the drive itself. I decided to rebuild the 2TB array, and the problem has reversed; dmraid will pick up on the storage partition of the larger array, but ignores the two partitions on the SSD array (it still sees the other array though). This means that I cannot boot into my installation on the SSD array, and have to run a live-session off of a USB drive to troubleshoot. The SSD array has two partitions, one for Windows and another for Arch so I can dual boot for gaming and non-open source software purposes.
I am currently running a live session of Ubuntu, which acknowledges both arrays and all partitions just fine. All the commands listed below are from the live-install running, but chrooted into my install on the SSD array.
Here is the error I get in grub when trying to boot:
Activating dmraid arrays...
Waiting 10 seconds for device /dev/mapper/isw_cjcefcajfc_Sigmap2
Root device '/dev/mapper/isw_cjcefcajfc_Sigmap2' doesn't exist attempting to create it.
Error: Unable to determine major/minor number of root device '/dev/mapper/isw_cjcefcajfc_Sigmap2'
Here is the output of dmraid -tay on the Arch install (chrooted):
isw_bjcehbjhed_Chi: 0 3907039232 striped 2 256 /dev/sdc 0 /dev/sdd 0
isw_cjcefcajfc_Sigma: 0 250081280 striped 2 256 /dev/sda 0 /dev/sdb 0
isw_bjcehbjhed_Chip1: 0 3907037184 linear /dev/mapper/isw_bjcehbjhed_Chi 2048
Here is the output of dmraid -tay on the Ubuntu live session:
isw_bjcehbjhed_Chi: 0 3907039744 striped 2 256 /dev/sdc 0 /dev/sdd 0
isw_cjcefcajfc_Sigma: 0 250081792 striped 2 256 /dev/sda 0 /dev/sdb 0
isw_bjcehbjhed_Chi1: 0 3907037184 linear /dev/mapper/isw_bjcehbjhed_Chi 2048
isw_cjcefcajfc_Sigma1: 0 197650432 linear /dev/mapper/isw_cjcefcajfc_Sigma 2048
isw_cjcefcajfc_Sigma2: 0 52428800 linear /dev/mapper/isw_cjcefcajfc_Sigma 197652480
Here is the output of lspci:
00:00.0 Host bridge: Intel Corporation 5520/5500/X58 I/O Hub to ESI Port (rev 13)
00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 13)
00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 13)
00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 13)
00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers (rev 13)
00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 13)
00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 13)
00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev 13)
00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4
00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5
00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6
00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1
00:1c.2 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 3
00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 5
00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1
00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2
00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3
00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller
00:1f.2 RAID bus controller: Intel Corporation 82801 SATA RAID Controller
00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
02:00.0 VGA compatible controller: ATI Technologies Inc Radeon HD 5870 (Cypress)
02:00.1 Audio device: ATI Technologies Inc Cypress HDMI Audio [Radeon HD 5800 Series]
04:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6121 SATA II Controller (rev b2)
05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)
07:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0)
Thanks for taking the time to help me troubleshoot my install, I'm looking forward to getting my desktop to run Arch Linux.

Okay, I'm still not entirely sure whats going on here... but I did manage to fix it using the above idea. I destroyed the system array and rebuilt it from scratch - this gave it a device name higher alphabetically than the second array, and as such the correct set is activated by dmraid, allowing me to boot.
The bug still exists though - and indeed dmraid refuses to activate the partitions on the second array. I can access these partitions by running partprobe on the volume after boot.
Hope this helps someone, sorry i cant actually fix this or figure it more rigorously.
John

Similar Messages

Logical standby stopped when trying to create partitions on primary(Urgent

RDBMS Version: 10.2.0.3
Operating System and Version: Solaris 5.9
Error Number (if applicable): ORA-1119
Product (i.e. SQL*Loader, Import, etc.): Data Guard on RAC
Product Version: 10.2.0.3
logical standby stopped when trying to create partitions on primary(Urgent)
Primary is a 2node RAC ON ASM, we implemented partitions on primar.
Logical standby stopped appling logs.
Below is the alert.log for logical stdby:
Current log# 4 seq# 860 mem# 0: +RT06_DATA/rt06/onlinelog/group_4.477.635601281
Current log# 4 seq# 860 mem# 1: +RECO/rt06/onlinelog/group_4.280.635601287
Fri Oct 19 10:41:34 2007
create tablespace INVACC200740 logging datafile '+OT06_DATA' size 10M AUTOEXTEND ON NEXT 5M MAXSIZE 1000M EXTENT MANAGEMENT LOCAL
Fri Oct 19 10:41:34 2007
ORA-1119 signalled during: create tablespace INVACC200740 logging datafile '+OT06_DATA' size 10M AUTOEXTEND ON NEXT 5M MAXSIZE 1000M EXTENT MANAGEMENT LOCAL...
LOGSTDBY status: ORA-01119: error in creating database file '+OT06_DATA'
ORA-17502: ksfdcre:4 Failed to create file +OT06_DATA
ORA-15001: diskgroup "OT06_DATA" does not exist or is not mounted
ORA-15001: diskgroup "OT06_DATA" does not exist or is not mounted
LOGSTDBY Apply process P004 pid=49 OS id=16403 stopped
Fri Oct 19 10:41:34 2007
Errors in file /u01/app/oracle/admin/RT06/bdump/rt06_lsp0_16387.trc:
ORA-12801: error signaled in parallel query server P004
ORA-01119: error in creating database file '+OT06_DATA'
ORA-17502: ksfdcre:4 Failed to create file +OT06_DATA
ORA-15001: diskgroup "OT06_DATA" does not exist or is not mounted
ORA-15001: diskgroup "OT06_DATA" does not exist or
Here is the trace file info:
/u01/app/oracle/admin/RT06/bdump/rt06_lsp0_16387.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /u01/app/oracle/product/10.2.0
System name: SunOS
Node name: iscsv341.newbreed.com
Release: 5.9
Version: Generic_118558-28
Machine: sun4u
Instance name: RT06
Redo thread mounted by this instance: 1
Oracle process number: 16
Unix process pid: 16387, image: [email protected] (LSP0)
*** 2007-10-19 10:41:34.804
*** SERVICE NAME:(SYS$BACKGROUND) 2007-10-19 10:41:34.802
*** SESSION ID:(1614.205) 2007-10-19 10:41:34.802
knahcapplymain: encountered error=12801
*** 2007-10-19 10:41:34.804
ksedmp: internal or fatal error
ORA-12801: error signaled in parallel query server P004
ORA-01119: error in creating database file '+OT06_DATA'
ORA-17502: ksfdcre:4 Failed to create file +OT06_DATA
ORA-15001: diskgroup "OT06_DATA" does not exist or is not mounted
ORA-15001: diskgroup "OT06_DATA" does not exist or
KNACDMP: *******************************************************
KNACDMP: Dumping apply coordinator's context at 7fffd9e8
KNACDMP: Apply Engine # 0
KNACDMP: Apply Engine name
KNACDMP: Coordinator's Watermarks ------------------------------
KNACDMP: Apply High Watermark = 0x0000.0132b0bc
Sorry our primary database file structure is different from stdby, we used db_file_name_convert in the init.ora, it look like this:
*.db_file_multiblock_read_count=16
*.db_file_name_convert='+OT06_DATA/OT06TSG001/','+RT06_DATA/RT06/','+RECO/OT06TSG001','+RECO/RT06'
*.db_files=2000
*.db_name='OT06'
*.db_recovery_file_dest='+RECO'
Is there any thing wrong in this parameter.
I tried this parameter before for cloning using rman backup. This din't work.
What exactly must be done? for db_file_name_convert to work.
Even in this case i think this is the problem its not converting the location and the logical halts.
help me out.....
let me know if you have any questions.
Thanks Regards
Raghavendra rao Yella.

Hi reega,
Thanks for your reply, our logical stdby has '+RT06_DATA/RT06'
and primary has '+OT06_DATA/OT06TSG001'
so we are using db_file_name_convert init parameter but it doesn't work.
Is there any thing particular steps hiding to use this parameter? as i tried this parameter for rman cloning it din't work, as a workaround i used rman set new name command for clonning.
Let me know if you have any questions.
Thanks in advance.

Partitions on raid-array not recognized on boot

Hey there,
I already had my share of problems with my raid setup and kernel/udev updates, but this one is new:
I have a raid1 setup with several partitions on the array which get recognized as /dev/md0p1, /dev/md0p2, etc.
My root-device is on /dev/md0p2 by the way.
After the last kernel-update I get dropped in the rescue shell at boot because the message "waiting 10 seconds for device /dev/md0p2" timed out. In the rescue shell I can see, that indeed the array is properly assembled (cat /proc/mdstat) is fine, but somehow the corresponding partitions (md0p1, sda1, sdb2, etc) are not linked in /dev or recognized at all (/proc/partitions).
However one execution of "blkid" seems to trigger some udev-event and afterwards all partitions and links magically appeared.
Has anyone any idea what causes this behaviour and how to fix it? It would be very enlightening to know which part of my system is actually responsible for setting up the partition-links (udev?).

Sorry guys, I've been inundated with problems lately.
Anyway, to answer your questions, yes I've swapped out everything.
As it stands right now, I have green lights on everything both sides even show up on IP and in ARD. The only issue now is that I can't see half of my RAID in DiskUtilities from my Xserve. I can format one side and not the other.
My server is an older G5 single 2GHz, build 7W98 and 2.5GB memory, (for reference).
Thank you for your input. I appreciate it.
DaveB

Ignoring partition

Can we ignore partition while inserting records from one server to another server.
I am getting error "ORA-14400: inserted partition key does not map to any partition " while trying to insert data into one table from other table which is there on other server using DBLINK

Hi,
Yes, you can do that using "When Others" sort of partition.
Here's an example:
CREATE TABLE big_table2 (
id            NUMBER(10),
created_date DATE,
lookup_id     NUMBER(10),
data          VARCHAR2(50)
PARTITION BY RANGE (created_date)
(PARTITION big_table_2003 VALUES LESS THAN (TO_DATE('01/01/2004', 'DD/MM/YYYY')),
PARTITION big_table_2004 VALUES LESS THAN (TO_DATE('01/01/2005', 'DD/MM/YYYY')),
PARTITION big_table_2005 VALUES LESS THAN (MAXVALUE));Regards
Asif Momen
http://momendba.blogspot.com

Unable to add partition on raid array, device or resource busy.

Greetings,
I want to be able to create a disk image of a software raid of one of my arch box.
I'm able to create my image with G4U successfully. I'm also able to restore my image without error on my new box.
When my system boot up, I make sure that my raid array are up by doing cat /proc/mdstat.
I can see that md1 and md2 are 2 of 2 and active raid 1. But, when I look at md0 this is what I got:
md0 : active raid1 sdb3[1]
6289344 blocks [2/1] [_/U]
I try to add the partition sda3 to md0 array with this command:
mdadm --manage /dev/md0 --add /dev/sda3
The output of this command give me this :
mdadm: Cannot open /dev/sda3: Device or resource busy.
It seems that this error only occurs on /dev/md0 (/) array. I'm 100% sure that both, my image and my drive (vmware hdd) are good.
This is my partition table:
/dev/sda1 /dev/sdb1 = /boot (md1) 100MB
/dev/sda2 /dev/sdb2 = swap (md2) 2048MB
/dev/sda3 /dev/sdb3 = / (md0) 8GB
I have also tried the image creation with Acronis... same error.

I solved my issue.
My menu.lst was wrong..
kernel /kernel26 root=/dev/md0 ro
I should add this to my menu.lst:
kernel /kernel26 root=/dev/md0 ro md=0,/dev/sda3,/dev/sdb3
Now it work.
I followed the archlinux raid guide who's telling this:
Nowadays (2009.02), with the mdadm hook in the initrd it it no longer necessary to add kernel parameters concerning the RAID array(s).
Which is wrong because my distro is 2009.02, if someone can add a note to the wiki it can be usefull.
Thanks for your support

Cfdisk fails on partitioning- bad primary partition

Hello. I'm trying to install Arch Linux on my notebook- Asmobile S96SP.
If I try to use manual disk partitioning, then I see black screen of cfdisk with this error:
FATAL ERROR: Bad primary partition 3: Partitions ends in the final partical cylinder.
Press any key to exit cfdisk.
I've got just one disk (250GB SATA), and 4 partitions on it.
I want to install Linux on E:.
What's wrong? Someone know how to resolve this problem?
Thanks!

Ok, I fixed it by remove E: partition to make free space (unattached).
Now i've got the second problem. I hear "peep" from my notebook all the time. It's problem with ACPI, becouse if I disable acpi on startup, then i don't hear nothing. I found this: http://www.inliniac.net/blog/2008/07/25 … state.html
but i don't know how can i add to "options" file 2 processors, and how to update initrd on Arch.
/proc/acpi/processor/CPU1/
/proc/acpi/processor/CPU2/
Thanks for reply.

Partitioning on T3 arrays

We are in the process of implementing T3 storedge arrays. can anyone advice how to oragainise partitions on that any document which can help? any information on building RAID on T3.
thanks

http://www.sun.com/blueprints/browsesubject.html
several useful documents there, enough for you to
install/admin:
* Sun StorEdge[tm] T3 Array: Installation, Configuration and Monitoring Best Practices (October 2001)
-by Ted Gregg
In order to fully realize the benefits of the capabilities built into the Sun StorEdge[tm] T3 array, it must be installed, configured, and monitored with best practices for RAS. This article details these best practices. It includes both Sun StorEdge T3 array configuration and host system configuration recommendations, along with brief descriptions of some of the available software installation and monitoring tools.
* Sun StorEdge[tm] T3 Dual Storage Array Part 3 - Basic Management (April 2001)
-by Mark Garner
The final article in the series looks at the configuration of basic management and monitoring functions on the T3 array. It concludes with example Expect scripts that could be used as a starting point for automating your own T3 installations.
* Sun StorEdge[tm] T3 Dual Storage Array Part 2 - Configuration (March 2001)
-by Mark Garner
This second article in the series addresses the installation and configuration of a T3 array partner group. It covers how two single arrays would be reconfigured to form a partner group, how the new devices are created on the host and how VERITAS Volume Manager integrates into the solution.
* Sun StorEdge[tm] T3 Dual Storage Array Part 1 - Installation, Planning and Design (February 2001)
-by Mark Garner
This article looks at the planning and design requirements for the installation of a Sun StorEdge T3 Array partner group. It is the first of three articles which address planning and design, configuration and basic management of a Sun StorEdge T3 Array.

Partition exchange with Primary Key Enabled : is it possible ?

Hello everybody.
I have succeeded "exchange...INCLUDING INDEXES WITH VALIDATION" a single table with a partition when primary key of the single table and the partitioned table are both Disabled and Validated.
I am trying now to do the same thing but with the 2 primary keys Enabled. Because of the global index générated by the Enabled PK, i "exchange ... including indexes with validation update global indexes" : it doesn't work : "ORA-14098: index mismatch for tables in ALTER TABLE EXCHANGE PARTITION".
But indexes are the same (thanks OEM) that in the previous test, all attributes of the 2 PKs are the same.
Thanks in advance for your help.

For those interested. I finally found the solution elsewhere in the documentation.
If the PK of the partitioned is enabled, the primary key of the single table has to be Disabled and Validated.

Dmraid error on initramfs: no block devices found

After updating a system running dmraid mkinitcpio fails to create an image with the following:
==> ERROR: binary dependency `libudev.so.1' not found for `dmraid'
[2012-08-30 14:07] ==> ERROR: binary dependency `libudev.so.1' not found for `dmsetup'
[2012-08-30 14:07] ==> ERROR: binary dependency `libudev.so.1' not found for `dmsetup'
I foolishly rebooted without checking pacman.log, so I am unable to boot because my root partition is on the fakeraid. I get an error like:
dmraid: error while loading shared libraries: libudev.so.1: cannot open shared object file: No such file or directory
unable to find root device '/dev/mapper/sil_bgbgdjaddicbp1'
I've created a liveusb with the latest media and mounted my dmraid partitions, so I need to resolve this dependency and rebuild the image. I checked and libudev.so.1 is present in my dmraid root partition's filesystem, so any ideas why it's failing? I know udev and systemd merged, so that probably has something to do with it.
Also my HOOKS array in mkinitcpio.conf is:
HOOKS="base autodetect pata scsi sata dmraid filesystems"
and MODULES is
MODULES="dm_mod"
Last edited by DarksideEE7 (2012-08-31 14:44:22)

redplug wrote:I have exactly the same Problem. Do you use an ext4 device?
Yes, my setup was:
boot ext2 /dev/sdd1
root ext4 dm-0
home ext4 dm-1
var reiserfs /dev/sdd4
Now I just reinstalled, setup two mdadm RAID0 arrays, created a logical volume group with LVM, paritioned root and home on these arrays, then kept the rest the same as my previous config. I really didn't feel like figuring out the problem (if it even could have been fixed). Also dmraid is apparently not being developed anymore. I was also on GRUB legacy still, which needed to go. Lastly systemd isn't going to play nicely (or at all) with dmraid.
My advice would be to migrate your existing setup to the newer, better supported packages. It's actually a much more elegant solution for software RAID. A good guide to do this is:
https://wiki.archlinux.org/index.php/So … ID_and_LVM
Last edited by DarksideEE7 (2012-09-04 18:37:23)

Installing arch on extended partition/logical drive

hi there. i am a newbie to linux and about to install arch as my first linux installation.
i am using vaio AR laptop already running xp and would like to keep it and have double boot without reinstalling xp.
have 200gb hdd with recovery primary partition, system primary partition (where xp installed) and extended partition with one logical drive (D: ) of 100gb.
i was considering deleting the logical drive (and the extended partition if necessary), which if i understand correctly should give me 100gb of unallocated space.
i would then like to install arch on the 100gb of unallocated space.
i would like to know if the way i am planning to go about it is possible, and whether i can install arch completely on one extended partition devided into logical drives.
any comments or sugestions would be much appreciated...
Last edited by o12357 (2009-09-04 12:45:18)

I believe that is correct. Grub has to have a reference to the md0 raid for booting.
Please see
http://bbs.archlinux.org/viewtopic.php?id=79306
This solution to the boot problem with md0 should be helpful for your case since grub must be modified to accomodate the raid.
I am not sure the data in your raid0 is appropo for your use in booting archlinux, however. If I understand correctly, it is windows related data and not applicable to linux.
If your raid0 is partitioned, it would be possible to establish a boot for each system using grub partition references differing for linux and windows systems.
Thus, you would have grub entries complete for linux and another set complete for windows.
I think AFAICT windows has to be first in the usual dual booting but am not an expert on that, not having used dual boot. It may be somewhat different when using raid for booting dual systems.
I suggest you read the wiki on dual boots.
Perhaps you will get advice from others on the subject also.
EDIT: Your asumption that all OS'es will recognize the raid0 devices as a single drive does not apply to archlinux which does not autodetect raid arrays but must have initramfs populated with the raid data established by mdadm and initiated into initramfs by mkinitcpio. Then during boot sequences , the array is assembled and enabled as a single drive,i.e., md0. The boot sequence assembles all drives having identical UUID's in the raid array.
Last edited by lilsirecho (2009-09-05 18:23:36)

[SOLVED] Cloning boot and var partitions to a new drive for booting

Ok first of all here's my setup:
fakeraid (dmraid) / and home on an OCZ Revodrive
boot with GRUB on a flash drive (since fakeraid doesn't support grub)
var and downloads/media folder on a 500GB WD Caviar drive
When I originally installed Arch I had the Caviar drive in my home server in a RAID5 array, so that's why I opted to install boot and grub on a flash drive simply for booting. Now that I have the drive in my desktop I've cloned the flash drive's partitions and MBR using dd:
#dd if=/dev/sde of=~/MBR.img bs=512 count=1
#dd if=/dev/sde1 of=~/boot.img
#dd if=/dev/sdc1 of=~/var.img
I then backed up my downloads/media partition, then removed the partition table, then used dd to put the img files on the Caviar drive.
#dd if=~/MBR.img of=/dev/sdc bs=512 count=1
#dd of=~/boot.img of=/dev/sdc1
#dd of=~/var.img of=/dev/sdc2
I also created labels for the filesystems and put those in fstab.
I'm able to mount both partitions, however I can't boot from the drive. I get a 'grub hard disk error' (no error number) when I put it as my first drive in the BIOS.
I can still use the flash drive as the first hard drive in the BIOS and boot from it, then it mounts the dmraid root partition and boots successfully. It is also able to mount the var and boot partitions in fstab.
Basically the only problem is that the MBR is somehow wrong. I then tried booting back into an Arch live USB and installing GRUB from the prompt:
grub
grub>setup (hd4,0) (in this case the Caviar drive's boot partition was /dev/sde1
So essentially what I'm asking is how GRUB handles the MBR. Is it specific to the partition table of the drive in which it resides when it's originally installed? For instance, since I had an 8GB flash drive with 2 partitions when I installed GRUB, is the backed up MBR no good for a 500GB drive with 3 partitions?
I have everything backed up so I can start with a fresh /boot and /var if need be....I'm just not sure where to start.
Thanks in advance.
Last edited by DarksideEE7 (2011-02-13 23:25:31)

Sorry, I forgot to mention that I tried to install GRUB from the GRUB shell in a live Arch USB. It failed on a few non-critical parts, and succeeded on the last part. I'm going to try again shortly, possibly I did something wrong. GRUB is able to find the stage files using:
#grub
grub>find /grub/stage1
grub> find /grub/stage1
(hd0,0)
(hd5,0)
grub>
(hd0,0) is the desired boot drive, while (hd5,0) is the current bootable flash drive with /boot and GRUB installed.
Here is the output of fdisk -l:
WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders, total 3907029168 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: 0x00000000
Device Boot Start End Blocks Id System
/dev/sde1 1 3907029167 1953514583+ ee GPT
Disk /dev/sdb: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117231408 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: 0xedb72db9
Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 206847 102400 7 HPFS/NTFS
/dev/sdb2 206848 117227519 58510336 7 HPFS/NTFS
Disk /dev/sdd: 40.0 GB, 40018599936 bytes
255 heads, 63 sectors/track, 4865 cylinders, total 78161328 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: 0x00000000
Disk /dev/sdd doesn't contain a valid partition table
Disk /dev/sdc: 40.0 GB, 40018599936 bytes
32 heads, 32 sectors/track, 76329 cylinders, total 78161328 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: 0xb8372fcd
Device Boot Start End Blocks Id System
/dev/sdc1 32 21484543 10742256 83 Linux
/dev/sdc2 21484544 156317695 67416576 83 Linux
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 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: 0x8497e059
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 206847 102400 83 Linux
/dev/sda2 206848 42149887 20971520 83 Linux
/dev/sda3 42149888 976773167 467311640 83 Linux
Disk /dev/dm-0: 80.0 GB, 80035053568 bytes
32 heads, 32 sectors/track, 152654 cylinders, total 156318464 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk identifier: 0xb8372fcd
Device Boot Start End Blocks Id System
/dev/dm-0p1 32 21484543 10742256 83 Linux
Partition 1 does not start on physical sector boundary.
/dev/dm-0p2 21484544 156317695 67416576 83 Linux
Disk /dev/dm-1: 11.0 GB, 11000070144 bytes
255 heads, 63 sectors/track, 1337 cylinders, total 21484512 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Alignment offset: 49152 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2: 69.0 GB, 69034573824 bytes
255 heads, 63 sectors/track, 8392 cylinders, total 134833152 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk identifier: 0x00000000
Disk /dev/dm-2 doesn't contain a valid partition table
Disk /dev/sdf: 8086 MB, 8086618112 bytes
249 heads, 62 sectors/track, 1023 cylinders, total 15794176 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: 0x8497e059
Device Boot Start End Blocks Id System
/dev/sdf1 * 62 200693 100316 83 Linux
/dev/sdf2 200694 15794175 7796741 83 Linux
I'm using dmraid, so just to be clear I've configured the raid using:
#modprobe dm_mod
#dmraid -ay
Then I saw the array stored in /dev/mapper/silXXXXX. I then created partitions for /boot, /, and home. At that time I was hoping to get GRUB working with the AUR package grub2-dmraid. I wasn't able to get it working for some time, so I just went ahead and installed boot and GRUB to a separate USB flash drive.
Here is the output of df -h:
Filesystem Size Used Avail Use% Mounted on
udev 10M 268K 9.8M 3% /dev
/dev/mapper/sil_bgbgdjaddicbp1
11G 5.3G 4.3G 56% /
shm 6.0G 584K 6.0G 1% /dev/shm
/dev/mapper/sil_bgbgdjaddicbp2
64G 38G 23G 63% /home
/dev/sda1 95M 16M 75M 18% /boot
/dev/sda2 19G 142M 19G 1% /var
/dev/sda3 439G 148G 269G 36% /home/l33/Torrents
none 1000M 132K 1000M 1% /tmp
shm 6.0G 584K 6.0G 1% /dev/shm
/dev/sde1 1.8T 1.1T 665G 62% /mnt/Green
and cat /etc/mtab
proc /proc proc rw,nosuid,nodev,noexec,relatime
sys /sys sysfs rw,nosuid,nodev,noexec,relatime
udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=1022975,mode=755
/dev/mapper/sil_bgbgdjaddicbp1 / ext4 rw,noatime,barrier=1,stripe=32,data=ordered
devpts /dev/pts devpts rw 0 0
shm /dev/shm tmpfs rw,nosuid,nodev 0 0
/dev/mapper/sil_bgbgdjaddicbp2 /home ext4 rw,noatime 0 0
/dev/sda1 /boot ext2 rw 0 0
/dev/sda2 /var reiserfs rw,noatime 0 0
/dev/sda3 /home/l33/Torrents ext4 rw,noatime 0 0
none /tmp tmpfs rw,nosuid,nodev,noatime,size=1000M,mode=1777 0 0
shm /dev/shm tmpfs rw,nosuid,nodev,size=6G 0 0
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
nfsd /proc/fs/nfsd nfsd rw,noexec,nosuid,nodev 0 0
/dev/sde1 /mnt/Green ext4 rw 0 0
Also I don't have a /proc/mdstat. That's only for mdadm RAID setups, right? It's been quite some time since I've used mdadm so I can't remember.
EDIT:
So I booted into a live Arch USB and entered the grub shell. I ran:
#grub
grub> root (hd3,0)
Filesystem type is ext2fs, partition type 0x83
grub> setup (hd3)
Checking if "/boot/grub/stage1" exists.....no
Checking if "/grub/stage1 exists.......yes
Checking if "/grub/stage2 exists.......yes
Checking if "/grub/e2fs_stage1_5 exists....yes
Running "embed /grub/e2fs_stage1_5 (hd3)".....25 sectors are embedded.
succeeded
Running "install /grub/stage1 (hd3) (hd3))1+25 p (hd3,0)/grub/stage2 /grub/menu.lst".......succeeded
Done.
Last time I recall more errors than this, then it reporting that one was a non-critical error, so I think the problem may be solved. More to come.
Last edited by DarksideEE7 (2011-02-13 23:18:44)

Tutorial - How to triple boot OSX, Linux and Windows 8.1 with a shared Data Partition without any third party Win / OSX softwares

This is not a question, but rather a personal guide that has proved to be running successfully.
I would like to thank numerous sources, including Christopher Murphy's suggestions at:
Re: Repairing Boot Camp after creating new partition
Before proceeding, there are certain concepts needs to know:
Why Boot Camp does NOT allow further partitioning of drives after Windows has installed?
Answer: Because the way Apple configures the Mac to be recognized as non UEFI capable system on Windows.
Quote from Christopher Murphy based on the above line:
However, Windows on Macs right now use CSM-BIOS mode in Mac firmware that presents BIOS to Windows rather than EFI. Windows thinks it's on a BIOS computer, and therefore mandates the use of MBR for boot disks, rather than GPT. So that's why we have this hybrid MBR+GPT approach on Mac with Windows on it. You inherit the limitations of MBR, which is four primary partitions.
So what does it means?
It means that OSX + EFI + Recovery HD + Boot Camp partition = 4 primary partitions and thus any attempt to modify the disk will render booting issues of either system.
For more info on GPT (GUID Partition Table disks VS Master Boot Record or MBR in short, you may visit: http://msdn.microsoft.com/en-us/library/windows/hardware/dn640535%28v=vs.85%29.a spx)
So, how to overcome it?
The general guideline is to install ALL GPT ready OS first then create a Data partition, before installing Windows (Which is again, NOT supported GPT due to EFI configuration by Apple where end-users are not able to modify it).
Interestingly, since Mac Pro 2013 Late supports only Windows 8 and above, thus it is not known if this CSM-BIOS applies to it or not.
Do take note that GPT disks in Windows can only be booted when the system meets the 2 requirements:
http://msdn.microsoft.com/en-us/library/windows/hardware/dn640535%28v=vs.85%29.a spx#gpt_faq_win7_boot
1) Windows x64 version (Which is a must for newer Macs. If you cannot go to Boot Camp 5, then you need Windows 7 x86 or 32bit version)
2) UEFI system. However, Windows sees all Macs (With the possibility of Mac Pro 2013 Late is an exception. To be determined) as BIOS, or rather NON-UEFI system.
In short, booting on GPT disks is not possible for Mac in Windows.
Summary,
It is tested that a combination of the following will not work:
- OSX + Windows + Linux
- Windows + OSX + Linux
- Windows + Linux + OSX
Usually it can create the system un-bootable or OSX refused to install due to the system does not recognize such partitions and / or Disk Utility refused to format a free space. An example screen-shot is provided below:
The error message is shown as
Title: "Failed to erase volume" Message: "Failed to wipe volume, as an error occurred: MediaKit has reported that the device does not have enough free space to execute the requested operations."
The second thing is about the preparations we need.
1) 1X Windows 7 or 8 DVD or USB thumbdrive
1A) If you uses a DVD to install, you will need another thumbdrive to load the BootCamp drivers for Windows as well as may requires an external DVD drive for newer Macs
2) 1X Linux DVD of your choice. Personally I choose Fedora 20.
So ready? Let's go.
1. Using Disk Utility, shrink the OSX's partition size to what is needed. For me, I give OSX 150GB. Do NOT create any new partition.
Disk Utility should see something like below whereby only OSX partition is left with desired disk space. The remaining space are to be unused disk space for the moment.
Note: Click on the top most item that should start with the size of your HDD / SSD. Then clicked on "Partition" and specify the desired OSX size. Hit "Apply" after that.
2: Download Boot Camp drivers only via Boot Camp Assistant. The USB thumbdrive shall be used later after Linux's installation.
Boot Camp Assistant should see this:
I have only selected "Download latest Windows Support Files from Apple"
3. Insert Linux DVD, reboot Mac into EFI mode (The left most first "EFI mode").
Note 1: Before rebooting, please plugged in an Ethernet adapter because Wi-Fi drivers is not installed.
Note 2: For Thunderbolt adapters, it must be plugged in before reboot as hot-swapping is not supported under Linux. More on the tips at the end of this article.
Note 3: Press and hold "Option" after the screen turns black. Release Option key after you see the image as below:

For the unfortunate part that did not make it on time to edit the images:
9. Install the Windows Support software from your CD/USB drive to gain full functionality of your computer. Reboot and go to Windows again.
Note 1: You may choose to eject disc at this point of time. For Apple SuperDrive users, you will need to wait until the drivers (i.e. Boot Camp support files) is installed and rebooted before ejecting is reasonably possible (As I failed to figured out how to right click without the drivers)
Note 2: Unlike Windows 7 on KBase article TS4599 Keyboard/trackpad inoperative, black screen, or alert messages when installing Windows 7, USB stick can be plugged in after the Windows installation is done. This is because Windows 7 (And probably Windows 7 with SP1 DVD) does not have a built in USB 3 drivers when it was released back in 2009 where USB3 has not arrived then.
Note 3: Due to TPM, Bitlocker is not supported without the use of thumbdrives.
10. Using Disk Management to determine the given drive letter for the DATA partition (DO NOT DELETE and RECREATE partition or else you can goodbye to booting Linux and OSX). Disk Management will not allow you to format it as exFAT / FAT32 in graphical way.
Note: You may remove or modify some of the disk letters in Disk Management. However, do NOT remove / modfify the drive letter for the partition with 200MB size in HFS. This is because it will disallow booting of Linux and neither could Windows nor OSX can do anything EXCEPT to reinstall Linux only.
11. Open Command Prompt in Administrator Mode (Important!!), and key in the following command:
format F: /FS:exFAT
Give this volume a label after it has successfully formatted before hitting "Enter" again.
Note: Mine Data partition was assigned as F drive. Please make necessary adjustment to "F:" should your Data partition is assigned to other letters.
12. After that, Setup your Data partition structure as you like.
Tip: Minimally create the important folders such as:
- Music
- Documents
- Movie (Videos)
- Downloads
- Pictures
All these folders are commonly used by the 3 OSes. I do NOT recommend changing of /home (OSX and / or Linux) and / or user home directory (Windows) either partially or as a whole.
This is because of compatibility issue.
On a side note, iTunes Media Library used in OSX and Windows are NOT able to be use interchangably due to hard-coded path used.
13. Useful troubleshooting in Fedora / Linux:
With references to these:
http://chaidarun.com/fedora-mbp
http://anderson.the-silvas.com/2014/02/14/fedora-20-on-a-macbook-pro-13-late-201 3-retina-display/
http://unencumberedbyfacts.com/2013/08/16/linux-on-a-macbook-pro-101/
I would like to highlight a few important points:
1) Wi-Fi driver:
http://rpmfusion.org/Configuration
Note 1: The sound driver should be installed at Out of Box Experience. However, the Wi-Fi is not.
Note 2: Install both free and non-free repository. By the way, some other software like VLC can only be found after the Free Repository is installed.
Search for "akmod-wl" in Gnome-Package-Installer in order to install Wi-Fi drivers
Note 3: For those who do not have Ethernet adapters and their Mac does NOT have a built-in Ethernet port, it is recommended to get one. This is because Fedora 20 does not have a good support for iPhone USB tethering. Unsure for Andriod / Blackberry / Windows Phone users.
2) Grub Menu:
It will show several options to boot into OSX, even of the capability to boot into x86 or x64 mode. However, neither of them is bootable except Linux and the rescue.
Hence, it is recommended to remove the items by hand in this file:
/boot/efi/EFI/fedora/grub.cfg
Command to be used:
"sudo gedit /boot/efi/EFI/fedora/grub.cfg"
Parts to be removed:
- For any extra kernels, delete the target entry by locating the line "menuentry" under "/etc/grub.d/10_linux" sector to one line above the next "menuentry".
It is recommended to keep one main kernel, and one recovery at the minimal.
- For other OS, delete all the entry (Since neither it can works) under "/etc/grub.d/30_os-prober" sector without removing the lines starts with ###.
Auto Mount exFAT partition:
- After installing extra packages for exFAT support (Since it is not supported by Fedora 20 from a default installation), you may wish to edit "/etc/fstab" in order to mount the exFAT partition during boot time.
Command to be used:
"sudo gedit /etc/fstab"
Add the following line in gedit:
UUID=702D-912D /run/media/Samuel/DATA exfat defaults 1 2
Note 1: For DATA partition, OSX & Boot Camp partition, Fedora defaults mounts under: "/run/medua/<Username with case sensitive>/<Partition Label Name>"
Note 2: UUID is unique ID. You can find out the UUID by:
Step 1: First determine the DATA partition number:
"sudo gdisk /dev/sda"
Step 2: Determine the UUID of this partition number:
"sudo blkid /dev/sda8"
Reference 1: http://manpages.courier-mta.org/htmlman5/fstab.5.html
Reference 2: http://liquidat.wordpress.com/2007/10/15/short-tip-get-uuid-of-hard-disks/
3) Overheating CPU
Solution is to issue the following command in Linux terminal: su -c "echo -n 1 > /sys/devices/system/cpu/intel_pstate/no_turbo"
4) System resumes immediately after suspend
Solution is to issue the following command in Linux terminal: su -c "echo XHC1 > /proc/acpi/wakeup"
5) What does not works well out of box:
- Both GNOME and KDE's fonts are too small to be readable for out of box experience. Additional configuration is a need. (Some of the info can be found on "More Tips" later)
- Thunderbolt hotplugging is NOT supported under Windows and Linux so far. Neither FaceTime HD camera works as well.
- The red light in Headphone jack is always on. I do not have luck in switching off the light without losing the sound.
Note 1: It is determined that the module "snd_hda_intel" is used by both cards (HDMI and normal output)
Note 2: It is also known that blacklisting it can switch off the redlight at the price of muting the system.
Note: Based on this article, http://support.apple.com/kb/TS1574
A Mac (Except Mac Pro) needs servicing when there is a red light while the system fails to detect internal speakers. However, this article does NOT applies to this issue.
5A) More Tips:
Install gnome-tweak-tool for more customization
Search for: "gnome-package" to install:
Install Gnome Package Installer for advanced package repository
Install Gnome Package Updater for advanced updates to be install (Whereby Fedora's App Store alike might not show the relevant updates)
14. Verify if disk is still GPT:
Use Gdisk to determine if the disk is pure GPT:
http://ubuntuforums.org/showthread.php?t=1742682
Command: sudo gdisk -l /dev/sda (The entire hard drive)
You should see the MBR is "Protective" instead of anything else.
15. Congrats, the system is ready for triple boot. (I forgot to eject my Windows DVD when the photo was taken)
Note 1: You cannot set the default startup disk in Linux due to the lack of Boot Camp Control Panel in Linux.
Neither is changing startup disk recommended in Windows due to the inability to display correctly.
For me, I click "Cancel" whenever I am on this tab (Feel free to make other Boot Camp adjustments in other tabs).
Only OSX I know that can show the startup disk options correctly.
Note 2: For some reason, OSX likes to auto mount the EFI partition everytime it boots up. It is not known to have any issue for ejecting other disks or mounting disks via Disk Utility.
Note 3: It is not determined if any Firmware or System upgrades will cause issues. It is only known that all 3 OS's regular updates should not be an issue.
System Updates excludes Mac OSX 10.9.3 updates to OSX 10.9.4 type as I had done it on a OSX 10.9.4 Mac or Windows 8.1 to Windows 8.1 Update 1 since my Windows DVD comes with Update 1.
System Upgrades refers to OSX Mavericks to Yosemite, Fedora 20 to Fedora 21, Windows 8.1 Update 1 to Windows 8.2 / Windows 9 for that matter.
Note 4: Reset SMC and / or PRAM will NOT affect your ability to boot any of the OS (OSX, Recovery HD, Fedora & Windows 8)
Yup, that is it!

Is it possible to create a Windows 7 Partition via Bootcamp while having an internal RAID 0 Setup ?

Is it possible to create a Windows 7 Partition via Bootcamp while having an internal RAID 0 Setup ?

Yes, just not on the RAID. Boot Camp Assistant will only partition a single drive containing OS X. You cannot partition a RAID array.

MDT 2012 U1 LTI Format incorrect partition

Hi, everyone:
I recently update for xp to Win7 use MDT 2012 Update 1. Everything looks can be, but except for some individual strange question.
Details are follows:
The original xp partition C: is Primary partition, also system disk; other is extended partition, including D and E drive.
After performing MDT task sequence (disabled "format and partition disk" step for only format C:), this machine D drive formatted and put wim applied to the D drive.
On xp running wmic results are as follows:
C:\>wmic path win32_diskpartition get bootable,bootpartition,caption,description
Bootable BootPartition Caption Description
FALSE Disk #0, Partition #0 Extended w/Extended Int 13
TRUE TRUE Disk #0, Partition #1 Installable File System
diskpart:
DISKPART> list part
Partition ### Type Size Offset
Partition 1 Primary 24 GB 32 KB
Partition 2 Extended 125 GB 24 GB
Partition 3 Logical 49 GB 24 GB
Partition 4 Logical 76 GB 73 GB
Finally, I found that if the disk 0,partition #1 is C driver, the task sequence will fail.
Anyone have a solution? Thanks.

espero y te ayude estas opciones dentro de MDT
http://blogs.itpro.es/octaviordz/2013/09/27/crear-particiones-de-windows-con-mdt-2012/
Freelance-IT http://www.freelance-it.com.mx

How to make a new recovery partition on a 600 series

Well I thought this was worth a mention as nobody seems to have said it could be done.
Having just got the cheep 600 series unit working I wanted to restore the RESTORE PARTITION.
Mostly to get the F11 function working as it should after fitting a Brand new HDD.
The OS is WIN7x64 but I would guess the same could be said for others.
It is actually quite simple and perhaps has been described in better detail elsewhere but here we go.
Oh, I actually did this a few different ways and got some very interesting results,
including one that needed the F11 pressing before boot or it would fail to load windows after the recovery.
Nice little hidden security function.! But breaks the restore ability !!!
If you want to disable the F11 recovery option then you need to rename a file.
Perhaps not disable but MakeFail !
So the way it seemed to work goes like this.
You will need your Original Restore DVD's (Cd's) for this if I did not assume that already.
With your new hard disk you need to partition it into three parts.
Either do it in the machine with a bootdisk (BartsPE) or similar
or for quickest results pop the drive into a caddy and do it on a live machine.
If you need to be told how to partition the disk then ask. (Right click My Computer, select Manage)
OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
NOTICE: >> THIS IS GOING TO DESTROY ANY DATA ON THAT DRIVE ...
OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
Make these in order.
partition 1 = 100 meg PRIMARY, UNFORMATTED, NO LABEL, NO DRIVE LETTER.
partition 2 = ??? PRIMARY, UNFORMATTED, NO LABEL, NO DRIVE LETTER
(calculate size from remaining space less partition3 size)
partition 3 = PRIMARY, NTFS, ANY LABEL, ANY DRIVE LETTER.
(This needs to be large enough for ALL your recovery disks plus a little more.)
So if you only have one Restore DVD make the third partition about 5gigs.
If you have two 10 gigs and 3Dvd's perhaps 14 or 15 Gigs.
Add some more space if you want to store more stuff on that partition.
Format the 3rd partition, then copy in order ALL the restore disks to the NEW drive.
You can also copy other files to this partition if you want.
Best to keep it tidy and make a new folder for your own stuff.
Stuff like AV installers, Updates, Application installers.
The Recovery process will HIDE ALL folders on the recovery drive but they will still be there.
So that should be it.
You have got 3 partitions?,
You copied all the DVD's to the 3rd one,?
NOW..
Reinstall the drive to the machine.
Put in the "Recovery 1 DVD" and boot the machine.
When asked if you want to use the recovery from disk or harddrive,, select DVD Disk.
Once the install is complete the F11 button on bootup should now work error free.
Well ,, it did for me...
Brand new hard drive with a full system recovery option made from only the Restore DVD's.
I did another system restore via the F11 button just for the fun of it.
Just so you know the system restore takes less than a quarter of the time from HDD over DVD.
I was going to check the process of making another NEW set of DVD recovery disks from the NEW drive,
but perhaps someone else will do that and report back on their progress.
Hv.
I never knew who HP were until my workshop got filled with faulty equipment. !! I know who Apple are now too.

Depending on the software you use to clone will it copy the recovery partition or not ex SuperDuper does not.
You can always reinstall the OS on top of what you have. This will re-create the recovery partition without touching your user files, documents, photos, bookmarks etc. After that you may have to run the software update to get the latest OSX update 10.10.1
One draw back to no recovery partition is iCloud>Find my Mac will not be functional.
From option command R on start or from an installer SD card you created.
Recovery http://support.apple.com/kb/HT4718

Dmraid ignores partitions on primary array

Similar Messages

Maybe you are looking for