[SOLVED] RAID0 Array - Unknown Partition Table

I recently reinstalled my Arch system with a RAID0 array, and I've noticed something different this time around during boot.
When the mdadm hook is initialized it will stop the array, check it, then start it. Once it's started it will say,
md0: unknown partition table
And continue to the next array.
I believe this is fine since the system doesn't stall or anything during bootup. The concern I have is when the system then tries to activate the RAID arrays. It will show,
Activating RAID Arrays [FAIL]
I've looked this up, http://bbs.archlinux.org/viewtopic.php?id=90415 and apparently it's nothing to be worried about. However, it didn't do that when I had my system installed not 20 minutes before (up to date).
I've created the mdadm configuration file as such,
rm /mnt/etc/mdadm.conf
mdadm --examine --scan >> /mnt/etc/mdadm.conf
Apparently, this message can be removed so it doesn't show fail on startup by commenting out the part in /etc/rc.sysinit where it assembles the RAID, lines 121-123. I'm still uneasy with it though, I'm just looking for some further insight on this subject.
Why doesn't my md0 device have a partition table and what is the system doing that causes the assembly to fail?
Edit - It might be important to note that I'm trying to make 3 partitions of the following size,
/                      10GB
/home         ~4TB
/boot              50MB
Thanks!
Last edited by nerditup (2010-06-14 04:39:35)

Update: This behaviour is normal.
The partition table for a RAID array is not specified anywhere because the partition table is setup on the actual devices. In my case I have two partition tables set on /dev/sda and /dev/sdb, therefore /dev/md0 doesn't need any partition table.
The code,
#If necessary, find md devices and manually assemble RAID arrays
if [ -f /etc/mdadm.conf -a "$(/bin/grep ^ARRAY /etc/mdadm.conf 2>/dev/null)" ];
then
status "Activating RAID arrays" /sbin/mdadm --assemble --scan
fi
will check mdadm.conf for any arrays that are setup and try to assemble them. Since the arrays are assembled already by the mdadm hook, then the --assemble parameter will return an error. This is the reason for the [FAIL] message.
Since this is understood and not an actual "error", it is safe to comment out these lines in rc.sysinit. In fact, these lines are useless and should be taken out completely.
The reason why it didn't show up last time was because I didn't properly setup my mdadm.conf file on the previous install. This process made sure they were loaded, but if you follow the wiki and properly setup the mdadm.conf file then you don't need this line of code at all in your rc.sysinit.
Last edited by nerditup (2010-06-14 04:39:21)

Similar Messages

  • Cloned harddrive has unknown partition table

    Hi all,
    I've followed this wiki article on how to clone a full disk: https://wiki.archlinux.org/index.php/Disk_Cloning.
    Specifically:
    dd if=/dev/sdb of=/dev/sdc bs=4096 conv=notrunc,noerror
    The drive itself only has one partition that is encrypted with LUKS.
    dd finished copying everything over so naturally I wanted to verify that everything works as expected on the cloned harddrive.
    Now I've rebooted the machine to make sure that the kernel detects the partition table changes, but there's still something strange going on.
    fdisk -l can see the partition table fine, but parted cannot. Here's the output:
    $ sudo fdisk -l
    Disk /dev/sdc: 931.5 GiB, 1000194400256 bytes, 1953504688 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
    Disklabel type: dos
    Disk identifier: 0x36948ce8
    Device Boot Start End Blocks Id System
    /dev/sdc1 2048 1953525167 976761560 83 Linux
    $ sudo parted /dev/sdc print
    Error: Can't have a partition outside the disk!
    Model: Samsung M3 Portable (scsi)
    Disk /dev/sdc: 1000GB
    Sector size (logical/physical): 512B/512B
    Partition Table: unknown
    Disk Flags:
    Strange as it is, I can open and mount the encrypted partition and see the files:
    $ sudo cryptsetup open --type luks /dev/sdc1 crypt2
    $ sudo mount -t xfs /dev/mapper/crypt2 /mnt/crypt2/
    $ ls -l /mnt/crypt2/
    I'm using XFS so I wanted to try and run a filesystem check on it. After unmounting the partition I run:
    $ sudo umount /mnt/crypt2/
    $ sudo xfs_repair -n /dev/mapper/crypt2
    Phase 1 - find and verify superblock...
    xfs_repair: error - read only 0 of 512 bytes
    Note that crypt2 is still open and shows up in fdisk -l. So XFS can't find the superblock to check the filesystem but I can somehow still mount it just fine? What am I missing here? I'm sure it's just a stupid oversight on my part, so apologies in advance...
    Oh, here's the output on xfs_repair -n  on the old harddrive:
    Phase 1 - find and verify superblock...
    Phase 2 - using internal log
    - scan filesystem freespace and inode maps...
    - found root inode chunk
    Phase 3 - for each AG...
    - scan (but don't clear) agi unlinked lists...
    - process known inodes and perform inode discovery...
    - agno = 0
    - agno = 1
    - agno = 2
    - agno = 3
    - process newly discovered inodes...
    Phase 4 - check for duplicate blocks...
    - setting up duplicate extent list...
    - check for inodes claiming duplicate blocks...
    - agno = 0
    - agno = 3
    - agno = 1
    - agno = 2
    No modify flag set, skipping phase 5
    Phase 6 - check inode connectivity...
    - traversing filesystem ...
    - traversal finished ...
    - moving disconnected inodes to lost+found ...
    Phase 7 - verify link counts...
    No modify flag set, skipping filesystem flush and exiting.

    Okay so I think I found the problem. I found this link when researching the error that parted threw at me: http://askubuntu.com/questions/48717/ho … tion-table
    And indeed, the new HDD has less sectors than the original, and the first partition ends outside of that.
    $ sudo fdisk -l
    Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 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
    Disklabel type: dos
    Disk identifier: 0x36948ce8
    Device Boot Start End Blocks Id System
    /dev/sdb1 2048 1953525167 976761560 83 Linux
    Disk /dev/sdc: 931.5 GiB, 1000194400256 bytes, 1953504688 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
    Disklabel type: dos
    Disk identifier: 0x36948ce8
    Device Boot Start End Blocks Id System
    /dev/sdc1 2048 1953525167 976761560 83 Linux
    Since the whole partition is encrypted, I don't want to risk simply resizing the partition. I think I'll just go ahead and make a new partition, encrypt it and copy the files manually. Unless anyone else has some input on this for me?

  • [Solved] corrupted partition table

    Yours truly was experimenting with alternative bootloaders today and ended up with a corrupted partition table. Yours truly had backed up the bootloader part of the MBR today but neglected to copy the rest. Guess who is feeling very stupid right now.
    Here is what fdisk has to say about my disk,
    root@sysresccd /root % fdisk -l /dev/sdb
    Warning: ignoring extra data in partition table 5
    Warning: ignoring extra data in partition table 5
    Warning: ignoring extra data in partition table 5
    Warning: invalid flag 0x2404 of partition table 5 will be corrected by w(rite)
    Disk /dev/sdb: 30.0 GB, 30020272128 bytes
    255 heads, 63 sectors/track, 3649 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x4b36bdea
    Device Boot Start End Blocks Id System
    /dev/sdb1 * 895 3444 20482875 7 HPFS/NTFS
    /dev/sdb2 1 894 7181023+ b W95 FAT32
    /dev/sdb3 3445 7476 32387040 5 Extended
    /dev/sdb5 ? 142349 151007 69551332+ 19 Unknown
    Partition table entries are not in disk order
    This looks somewhat promising. I had only three partitions on the disk (I don't remember if any were logical), one swap, one large thing for pacman stuff and of course root.
    By suggestion of this I will try testdisk (version 6.11 from Sys Resc CD).
    Last edited by fsckd (2011-09-17 21:22:59)

    Unfortunately my copy of sys resc cd does not have fixparts.
    testdisk worked like a charm and my partitions were recovered, one swap, one JFS and one ext4.
    (Incidentally it was Windows which damaged the MBR in the first place.)

  • [SOLVED] Corrupt partition table

    A couple days ago I was transferring large files to my 1TB external Seagate USB drive (NTFS).  It was going smooth then on one file it stopped and Thunar gave an error.
    When looking at the directory with ls -l the file's attributes were question marks (?)
    I was able to access all the other files fine, but was unable to delete or access the corrupt directory.
    Now, days later, I am unable to mount the USB drive.
    sudo fdisk -l gives this:
    Disk /dev/sdc: 931.5 GiB, 1000204885504 bytes, 1953525167 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
    Disklabel type: dos
    Disk identifier: 0x6e697373
    This doesn't look like a partition table. Probably you selected the wrong device.
    Device Boot Start End Blocks Id System
    /dev/sdc1 ? 1936269394 3772285809 918008208 4f QNX4.x 3rd part
    /dev/sdc2 ? 1917848077 2462285169 272218546+ 73 Unknown
    /dev/sdc3 ? 1818575915 2362751050 272087568 2b Unknown
    /dev/sdc4 ? 2844524554 2844579527 27487 61 SpeedStor
    Partition table entries are not in disk order.
    I run sudo ntfsck /dev/sdc:
    $ sudo ntfsck /dev/sdc
    file record corrupted at offset 3221225472 (0xc0000000).
    Loading $MFT runlist failed. Trying $MFTMirr.
    First attribute must be after the header (0).
    and it just seems to be stuck there, I've left it running for a few hours...
    Is my disk screwed?
    *edit*: I got it! Check my other post further down this thread
    Last edited by uberscientist (2014-12-16 19:15:57)

    I fixed it finally!
    I had set the drive aside and was sad about it for a while, and decided to give another shot at googling and repair, here's what I did to get it working:
    install testdisk: https://www.archlinux.org/packages/extr … /testdisk/
    sudo testdisk
    [ Create ] (new log file)
    selected the corrupted drive
    >[Proceed]
    >[Intel ] ( By default it picked None... I just guessed Intel/PC)
    >[Analyse]
    >[Quick Search]
    >[Continue]
    >[Deeper Search]
    >Stop (press enter to stop after it finds another entry)
    >Down arrow, then right arrow to set it Primary partition (non-bootable for my case)
    >[Write ]
    Mount your drive

  • [SOLVED] Deleted partition table on drive, how to rescue?

    Hello,
    I accidentally dd'd the first 512 bytes using:
    dd if=/dev/zero of=/dev/sdb bs=512 count=1
    and the partition table is now gone. Is there ANY way to re-create the partition table and rescue the still existing partition? I read up on parted's manual, and found the following commands:
    mklabel - to create a new label on the disk (but does it also create a new partition table?)
    rescue - to try and rescue the partition around the given START and END
    My hard drive is 500GB and has only 1 partition on it, in NTFS file format.
    Any help would be much appreciated.
    Silentz0r
    Last edited by silentz0r (2011-03-27 16:17:36)

    Thanks everyone for your help, I have managed to solve this. Here's what I did:
    (I had no backup of the MBR)
    I used:
    parted /dev/sdb
    sdb was my broken drive, and did the following:
    (parted) print
    Error: /dev/sdb: unrecognised disk label
    (parted) mklabel
    (parted) mklabel msdos
    (parted) rescue
    Start? 0
    End? 976773168 // This was just a random guess.
    Information: A ntfs primary partition was found at 32.3kB -> 500GB. Do you want to add it to the partition table?
    Yes/No/Cancel? yes
    (parted) quit
    Information: You may need to update /etc/fstab.
    And everything works now.
    For the record, I am making MBR backups for all my drives while I'm typing this.
    Hope this helps someone in the future! Marked as solved.

  • [SOLVED] The best way to recover a Partition Table. (LVM)

    I just did something really stupid I accidently had a typo in gdisk and changed the wrong hard drive partition table.
    So before I do something really stupid I post here.
    The hard drive is still mounted and I luckily have the output of the former partition table, this is it:
    fdisk -l /dev/sdb
    Festplatte /dev/sdb: 2,7 TiB, 3000558944256 Bytes, 732558336 Sektoren
    Einheiten: Sektoren von 1 * 4096 = 4096 Bytes
    Sektorgröße (logisch/physikalisch): 4096 Bytes / 4096 Bytes
    E/A-Größe (minimal/optimal): 4096 Bytes / 4096 Bytes
    Festplattenbezeichnungstyp: dos
    Festplattenbezeichner: 0x00028375
    Device Boot Start End Sectors Size Id Type
    /dev/sdb1 256 366211193 366210938 1,4T 83 Linux
    /dev/sdb2 366211194 732558335 366347142 1,4T 83 Linux
    The partition table was a LVM partition table.
    This is the current one:
    gdisk -l /dev/sdb
    GPT fdisk (gdisk) version 0.8.10
    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: present
    Found valid GPT with protective MBR; using GPT.
    Disk /dev/sdb: 732558336 sectors, 2.7 TiB
    Logical sector size: 4096 bytes
    Disk identifier (GUID): DA7956E1-B120-4F78-925A-B5DDE14E7C9C
    Partition table holds up to 128 entries
    First usable sector is 6, last usable sector is 732558330
    Partitions will be aligned on 256-sector boundaries
    Total free space is 250 sectors (1000.0 KiB)
    Number Start (sector) End (sector) Size Code Name
    1 256 131327 512.0 MiB EF00 EFI
    2 131328 13238527 50.0 GiB 8E00 Arch
    3 13238528 732558330 2.7 TiB 8300 EXT
    I really hope someone can help me with that, I'm currently a total nerve wrack.
    If its a more or less impossible task (well or there is no guarantee that it works) I will buy a new Drive tomorow to save the currently still mounted files.
    Thank You!
    [EDIT]
    Forget about copying the file system isn't really accessible, I can open a few folders but everything in there are 0byte files
    Last edited by theblackdog (2015-03-10 14:16:59)

    So because no one gave me a answer so far (ok it's already pretty late and I was a bit imatient) I took the leap of faith and used fdisk to recreate the partition sheme,  so far everything seems to work.
    There is only one thing that would interest me, as far as I know a GPT partition table is bigger than a dos partition table, how big is the risk that data got corrupted because of the bigger table?
    I will mark the thread as solved after that.

  • Create a GPT partition table and format with a large volume (solved)

    Hello,
    I'm having trouble creating a GPT partition table for a large volume (~6T). It is a RAID 5 (hardware) with 3 hard disk drives having a size of 3T each (thus the resulting 6T volume).
    I tried creating a GPT partition table with gdisk but it just fails at creating it, stopping here (I've let it run for like 3 hours...):
    Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
    PARTITIONS!!
    Do you want to proceed? (Y/N): y
    OK; writing new GUID partition table (GPT) to /dev/md126.
    I also tried with parted but I get the same result. Out of luck, I created a GPT partition table from Windows 7 and  2 NTFS partitions (15G and the rest of space for the other) and it worked just fine. I then tried to format the 15G partition as ext4 but, as for gdisk, mkfs.ext4 will just never stop.
    Some information:
    fdisk -l
    Disk /dev/sda: 256.1 GB, 256060514304 bytes, 500118192 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 label type: dos
    Disk identifier: 0xd9a6c0f5
    Device Boot Start End Blocks Id System
    /dev/sda1 * 2048 104861695 52429824 83 Linux
    /dev/sda2 104861696 466567167 180852736 83 Linux
    /dev/sda3 466567168 500117503 16775168 82 Linux swap / Solaris
    Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk label type: dos
    Disk identifier: 0x00000000
    Device Boot Start End Blocks Id System
    /dev/sdb1 1 4294967295 2147483647+ ee GPT
    Partition 1 does not start on physical sector boundary.
    Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk label type: dos
    Disk identifier: 0x00000000
    Device Boot Start End Blocks Id System
    /dev/sdd1 1 4294967295 2147483647+ ee GPT
    Partition 1 does not start on physical sector boundary.
    Disk /dev/sde: 320.1 GB, 320072933376 bytes, 625142448 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 label type: dos
    Disk identifier: 0x5ffb31fc
    Device Boot Start End Blocks Id System
    /dev/sde1 * 2048 625139711 312568832 7 HPFS/NTFS/exFAT
    Disk /dev/md126: 6001.1 GB, 6001143054336 bytes, 11720982528 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 65536 bytes / 131072 bytes
    Disk label type: dos
    Disk identifier: 0x00000000
    Device Boot Start End Blocks Id System
    /dev/md126p1 1 4294967295 2147483647+ ee GPT
    Partition 1 does not start on physical sector boundary.
    WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.
    gdisk -l on my RAID volume (/dev/md126):
    GPT fdisk (gdisk) version 0.8.7
    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: present
    Found valid GPT with protective MBR; using GPT.
    Disk /dev/md126: 11720982528 sectors, 5.5 TiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 8E7D03F1-8C3A-4FE6-B7BA-502D168E87D1
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 11720982494
    Partitions will be aligned on 8-sector boundaries
    Total free space is 6077 sectors (3.0 MiB)
    Number Start (sector) End (sector) Size Code Name
    1 34 262177 128.0 MiB 0C01 Microsoft reserved part
    2 264192 33032191 15.6 GiB 0700 Basic data partition
    3 33032192 11720978431 5.4 TiB 0700 Basic data partition
    To make things clear: sda is an SSD on which Archlinux has been freshly installed (sda1 for root, sda2 for home, sda3 for swap), sde is a hard disk drive having Windows 7 installed on it. My goal with the 15G partition is to format it so I can mount /var on the HDD rather than on the SSD. The large volume will be for storage.
    So if anyone has any suggestion that would help me out with this, I'd be glad to read.
    Cheers
    Last edited by Rolinh (2013-08-16 11:16:21)

    Well, I finally decided to use a software RAID as I will not share this partition with Windows anyway and it seems a better choice than the fake RAID.
    Therefore, I used the mdadm utility to create my RAID 5:
    # mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1
    # mkfs.ext4 -v -m .1 -b 4096 -E stride=32,stripe-width=64 /dev/md0
    It works like a charm.

  • [SOLVED] UEFI system booting from MBR partition table and GRUB legacy

    I'm trying to understand once and for all the process by which Arch can be booted from a system with UEFI firmware and an MBR partition table. Some of the information on the wiki seems conflictual / non-nonsensical at times. Apologies in advance if this has been answered time and time again, but I did search around and all I found was fixes to get Arch to boot rather than comprehensive explanations of the boot process.
    Now, the way I would imagine it works is that it's just completely identical to the way it would work with a BIOS firmware. The UEFI firmware detects an MBR partitioning scheme (or is configured to know it's an MBR partitioning scheme), activates some "legacy" mode and executes the MBR boot code, just like a BIOS firmware would.
    The wiki however, says different. From the Macbook article: "Do not install GRUB onto /dev/sda !!! Doing so is likely to lead to an unstable post-environment."?
    So what is there in the MBR boot sector? Nothing?
    How does the firmware know what to boot if there's no 0xEF BIOS boot partition and no Grub stage 1 in the MBR boot sector?
    Also, how does installing Grub stage 1 to a partition work? Does it have to be at the beginning of the partition? Wouldn't that overwrite some existing data?
    I'm especially puzzled since many guides to installing Vista on a macbook recommend simply formatting as MBR, and installing as normal, which I suppose entails having the Windows installation process write its boot code to the MBR, ie the equivalent of installing grub stage 1 to /dev/sda rather than to the /boot partition, as the Macbook article suggests.
    Any input is appreciated.
    P.S. I realize it's probably simpler, if I just want to dual boot Windows and Arch, to install Windows 7 in UEFI-GPT mode, let it create the EFI System Partition, and then install GRUB 2 to that partition, but I'm still curious about the UEFI-MBR boot process.
    Last edited by padavoine (2012-06-06 09:35:10)

    padavoine wrote:
    CSM in UEFI firmwares do the exact same job as normal BIOS firmware.
    So it's something specific to the Mac that it's able to boot from a partition's VBR while ignoring the MBR?
    The reason that warning is given is because grub-legacy modifies more than just the MBR boot code region.  It can overwrite some parts of GPT header.
    Not true, the instruction is given in the context of an MBR format, not in the context of a GPT format, so there's nothing to overwrite and Stage 1.5 should be safely embeddable in the post-MBR gap.
    In BIOS boot (normal case in non-UEFI firmwares or CSM in UEFI firmwares) does not read the partitition table (atleast it is supposed to be dumb in this regard), it simply launches whatever boot code exists in the 1st 440-byte of the MBR region.
    So again, you're saying it's specific to the Mac UEFI that it lets you choose a partition whose VBR to load, regardless of what's in the MBR?
    I haven't used Macs so I can't comment on Mac firmware behaviour. But normal BIOS firmwares (legacy and CSM) launch only the MBR boot code and not the partition boot code. We need some chainload capable boot manager in the MBR to launch the partition VBR.
    grub-legacy does not know anything about GPT. So when you install grub-legacy to /dev/sda, it install the MBR boot code (stage1) and stage 1.5 code to the (supposed) post MBR gap. Since there is no actual post MBR gap in GPT (which has been taken over by the header and partition table), grub-legacy does not check for GPT and it assumes the post MBR gap actually exists which is invalid in case of GPT. grub-legacy embeds the stage 1.5 code in GPT header and table region (which grub assumes to be unused post MBR gap) and thus corrupts it.
    0xEF is the MBR type code for UEFISYS partition. grub stage 1 (used in grub-legacy, not in grub2) is the 440-byte boot code stored in MBR for use in BIOS boot.
    That's precisely my point: with neither proper executable code in the MBR (since grub was installed to a partition, not to the MBR) nor a UEFI system partition, what does the firmware default to, and how does it know what partition to boot from?
    In that case it might fallback to UEFI Shell (if it exists)  or give an error similar to the case where BIOS does not find any bootable code in 440-byte MBR region.
    So even with bootcamp/CSM, the disk also needs to be MBR partitioned. So Macs use something called "Hybrid GPT/MBR" ( http://rodsbooks.com/gdisk/hybrid.html ) where the MBR table is synced to match the first 3 partitions in the GPT table.
    I know what Bootcamp does, and that's not what I was referring to. I was referring to standalone Vista installs. I wasn't puzzled at the fact that they were using MBR, I was puzzled at the fact that contrary to the recommendations for the standalone Arch install on the wiki (with MBR partitioning, not GPT), they didn't do anything to try and prevent Windows from writing to the MBR.
    You can't prevent Windows from overwriting the MBR region. You have to re-install the bootloader (grub2/syslinux etc.) after installing Windows. That is the reason why it is recommended to install Windows first and linux later.
    Thats not true. I actually find it is much easier to install Windows UEFI-GPT using USB rather than a DVD.
    I haven't done it since the only UEFI system I own has no DVD drive, but I was under the impression that it was simply a matter of choosing DVD UEFI boot in the firmware's boot menu.
    format the USB as FAT32 and extract the iso to it. That it.
    No, thats not it, precisely, it doesn't work out of the box with a standard Windows install USB, you need to fiddle around:
    2.3 Extract bootmgfw.efi from [WINDOWS_x86_64_ISO]/sources/install.wim => [INSTALL.WIM]/1/Windows/Boot/EFI/bootmgfw.efi (using 7-zip aka p7zip for both the files), or copy it from C:\Windows\Boot\EFI\bootmgfw.efi from a working Windows x86_64 installation.
    2.4 Copy the extracted bootmgfw.efi file to [MOUNTPOINT]/efi/microsoft/boot/bootmgfw.efi .
    Most of the Windows isos already have /EFI/BOOT/BOOTX64.EFI file, so no need to extract the bootmgfw.efi file.
    There is no difference between in BIOS booting in UEFI firmwares and BIOS booting with legacy firmware.
    There has to be a difference, at least in the Mac firmware (sorry, I keep switching), since legacy firmware, AFAIK, cannot chainload a bootloader in a partition's VBR without there being some sort of "stage1" code in the MBR.
    No idea about Mac EFI. Apple made a spagetti out of UEFI Spec. To actually understand how Mac firmwares work, read the blog posts by Matthew Garrett of Redhat, about his efforts in getting Fedora to boot in Macs.

  • [SOLVED] The best partition table for Archlinux?

    Hi.
    I am very confused whit the partition table which I sould use.
    So, which partition table is the best? Which you use?
    Have a nice day
    Last edited by feler (2008-10-19 10:41:20)

    I am a fan of reiserfs so I use it for everything except boot (where I use ext2).
    I strongly advice you to use ReiserFS for your /var/ because it is the fastest when dealing with small files, which greatly improves pacman performance.
    For everything else - it depends on what type of files does your system mostly hold...

  • Partition table messed up [SOLVED]

    So my problem is that the other one of my hard disks losed it's partition table after I installed Windows XP on it. I deleted partition to get space for XP and installed it on empy partition. Then in Arch I did grub-install. This got me into this so I can't view my partitons on either gParted or QTParted (which crashes when trying to watch hda). Also I can't use command "ls" in /home or it's subdirectories which is on different, fully working disk.
    So, I can use and mount these partitons which I can't see with gParted.
    fdisk tells me this:
    Disk /dev/hda: 203.9 GB, 203928109056 bytes
    255 heads, 63 sectors/track, 24792 cylinders, total 398297088 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Device Boot Start End Blocks Id System
    /dev/hda1 * 63 40965749 20482843+ 7 HPFS/NTFS
    /dev/hda2 40965750 398267414 178650832+ f W95 Ext'd (LBA)
    /dev/hda3 286728183 398267414 55769616 b W95 FAT32
    /dev/hda5 40965876 286728119 122881122 83 Linux
    hda3 should be ext3 like hda5.
    So is there any way to get my partitons back without losing any data?

    Harr1l wrote:But is there any help for that I can't use "ls" in certain directories?
    I don't know. Are you sure that filesystem has no errors? Did you do fsck?
    IIRC testdisk can rebuild filesystem from scratch.

  • Raid0 array sata on sas ports

    Hello and thanks for help
    I have a D partition on raid0 array made of four sata disks on sas ports of D10 under win 7.  Used to be ok, now I lost that D partition and lsi utility doesn't see the disks. I suppose I messed the configuration but don't remenber at all what to do in bios or elsewhere ...
    I have documents I need for yesterday
    Thanks for help
    Solved!
    Go to Solution.

    welcome to the forum!
    did you lose just the partition or the entire array?   can you see the partition in diskmgmt.msc?
    please understand that since RAID 0 has no redundancy, you may have lost everything forever.   it's next to impossible to recover data from RAID 0 because the data is spread across multiple drives in random chunks.
    ThinkStation C20
    ThinkPad X1C · X220 · X60T · s30 · 600

  • How can I create my own tag name while creating a partition table.

    I have X4500 running Solaris 10. I have formatted a disk and created partition table as given below.
    Specify disk (enter its number): 0
    selecting c0t0d0
    [disk formatted]
    /dev/dsk/c0t0d0s0 is part of active ZFS pool zpool1. Please see zpool(1M).
    FORMAT MENU:
    disk - select a disk
    type - select (define) a disk type
    partition - select (define) a partition table
    current - describe the current disk
    format - format and analyze the disk
    fdisk - run the fdisk program
    repair - repair a defective sector
    label - write label to the disk
    analyze - surface analysis
    defect - defect list management
    backup - search for backup labels
    verify - read and display labels
    inquiry - show vendor, product and revision
    volname - set 8-character volume name
    !<cmd> - execute <cmd>, then return
    quit
    format> partition
    PARTITION MENU:
    0 - change `0' partition
    1 - change `1' partition
    2 - change `2' partition
    3 - change `3' partition
    4 - change `4' partition
    5 - change `5' partition
    6 - change `6' partition
    select - select a predefined table
    modify - modify a predefined partition table
    name - name the current table
    print - display the current table
    label - write partition map and label to the disk
    !<cmd> - execute <cmd>, then return
    quit
    partition> print
    Current partition table (original):
    Total disk sectors available: 1953508749 + 16384 (reserved sectors)
    Part Tag Flag First Sector Size Last Sector
    0 usr wm 34 4.00GB 8388641
    1 usr wm 8388642 2.00GB 12582945
    2 usr wm 12582946 200.00GB 432013345
    3 usr wm 432013346 175.00GB 799014945
    4 usr wm 1166180386 375.43GB 1953508748
    5 usr wm 799014946 175.00GB 1166016545
    6 usr wm 1166016546 80.00MB 1166180385
    8 reserved wm 1953508749 8.00MB 1953525132
    partition>
    I am unable to specify my own tag name. How can I change the tag name to one of my interest.
    I need to create 3 partitions as told below
    partitions:
    /earth
    /mars
    /work
    /earth and /work should be roughly equal in size, /mars should be twice the size of the others, if that is possible. If not 3 partitions of equal size will do.
    Please, help me .
    Thank you.

    Exactly 1TB? Slightly under/slightly over?
    Traditional Solaris disk labels are in VTOC format, but this format cannot describe disks larger than 1TB. So EFI labels must be used on disks larger than 1TB. Setup is slightly different.
    Are these physical disks or LUNs from a SAN array? If they are array LUNS, it is often the case that they don't have a Sun label of any type. So...
    #1 Apply a Solaris label
    If the LUNS don't have a label (when selected in 'format', it gives a warning that no label is present and offers to apply a label immediately). When run non-interactively, format assumes "yes" for any questions. So all you'd have to do is select every disk to have it apply labels to any unlabled disk. Run 'format' once and find the highest number (maybe it's 50 for you). Create a text file that looks like this:
    disk 1
    disk 2
    disk 3
    disk 50Then feed that to format like this:
    # format -f /tmp/disklist or whatever you've named the file.
    #2 Apply the partition layout to all disks you want.
    You asked if you should do the same procedure, but I don't see that you've actually done anything above other than print out the existing layout. Take one of your 48 drives and partition it the way you want manually (set the slices to the sizes that you want). Then you can copy the layout of that disk to others. You only want to do this between disks/LUNs of the same size. As an example, if you've explicitly partitioned c1t0d0 and you want to apply this to c1t1d0, do this:
    # prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2Repeat for all of your other disks.
    Darren

  • How to fix a faulty partition table, How to fix a faulty partition table

    I have a 400gb partition on my 500gb HD, the remaining 100gb was split up in 3 partitions. I deleted 2 of these partitions, restarted and now Disk Utility claims my 400gb drive is now 53gb, accessing files has become impossible.
    I can still see all the files listed but am unable to open them or copy them, I get a -36 error.
    I have thrown Disk Utility, DiskWarrior, TechTool Pro and some lesser known tools at it but none of them wants to repair the volume.
    Sounds to me like a busted partition table, after all that was all that was altered, in theory I should be able to access my files. Does anyone have any suggestions on how to fix this?

    Problem solved, I used iPartition to resize the partition back to its original size after which I could copy all data off.

  • Non-Partitioned Global Index on Range-Partitioned Table.

    Hi All,
    Is it possible to create Non-Partitioned Global Index on Range-Partitioned Table?
    We have 4 indexes on CS_BILLING range-partitioned table, in which one is CBS_CLIENT_CODE(*local partitioned index*) and others are unknown types of index to me??
    Means other 3 indexes are what type indexes ...either non-partitioned global index OR non-partitioned normal index??
    Also if we create index as :(create index i_name on t_name(c_name)) By default it will create Global index. Please correct me......
    Please help me in identifying other 3 indexes types by referring below ouputs!!!
    select INDEX_NAME,TABLE_NAME,PARTITIONING_TYPE,LOCALITY from dba_part_indexes where TABLE_NAME='CS_BILLING';
    INDEX_NAME TABLE_NAME PARTITI LOCALI
    CSB_CLIENT_CODE CS_BILLING RANGE LOCAL
    select index_name,index_type,table_name,table_type,PARTITIONED from dba_indexes where table_name='CS_BILLING';
    INDEX_NAME INDEX_TYPE TABLE_NAME TABLE_TYPE PAR
    CSB_CREATE_DATE NORMAL CS_BILLING TABLE NO
    CSB_SUBMIT_ORDER NORMAL CS_BILLING TABLE NO
    CSB_CLIENT_CODE NORMAL CS_BILLING TABLE YES
    CSB_ORDER_NBR NORMAL CS_BILLING TABLE NO
    select INDEX_OWNER,INDEX_NAME,TABLE_NAME,COLUMN_NAME from dba_ind_columns where TABLE_NAME='CS_BILLING';
    INDEX_OWNER INDEX_NAME TABLE_NAME COLUMN_NAME
    RPADMIN CSB_CREATE_DATE CS_BILLING CREATE_DATE
    RPADMIN CSB_SUBMIT_ORDER CS_BILLING SUBMIT_TO_INVOICE
    RPADMIN CSB_SUBMIT_ORDER CS_BILLING ORDER_NBR
    RPADMIN CSB_CLIENT_CODE CS_BILLING CLIENT_CODE
    RPADMIN CSB_ORDER_NBR CS_BILLING ORDER_NBR
    select dip.index_name, dpi.locality, dip.partition_name, dip.status
    from dba_part_indexes dpi, dba_ind_partitions dip
    where dpi.table_name ='CS_BILLING'
    and dpi.index_name = dip.index_name;
    INDEX_NAME LOCALI PARTITION_NAME STATUS
    CSB_CLIENT_CODE LOCAL CSB_2006_4Q USABLE
    CSB_CLIENT_CODE LOCAL CSB_2006_3Q USABLE
    CSB_CLIENT_CODE LOCAL CSB_2007_1Q USABLE
    CSB_CLIENT_CODE LOCAL CSB_2007_2Q USABLE
    CSB_CLIENT_CODE LOCAL CSB_2007_3Q USABLE
    CSB_CLIENT_CODE LOCAL CSB_2007_4Q USABLE
    CSB_CLIENT_CODE LOCAL CSB_2008_1Q USABLE
    CSB_CLIENT_CODE LOCAL CSB_2008_2Q USABLE
    CSB_CLIENT_CODE LOCAL CSB_2008_3Q USABLE
    CSB_CLIENT_CODE LOCAL CSB_2008_4Q USABLE
    CSB_CLIENT_CODE LOCAL CSB_2009_1Q USABLE
    CSB_CLIENT_CODE LOCAL CSB_2009_2Q USABLE
    CSB_CLIENT_CODE LOCAL CSB_2009_3Q USABLE
    CSB_CLIENT_CODE LOCAL CSB_2009_4Q USABLE
    select * from dba_part_indexes
    where table_name ='CS_BILLING'
    and locality = 'GLOBAL';
    no rows selected
    -Yasser
    Edited by: YasserRACDBA on Mar 5, 2009 11:45 PM

    Yaseer,
    Is it possible to create Non-Partitioned and Global Index on Range-Partitioned Table?
    Yes
    We have 4 indexes on CS_BILLING range-partitioned table, in which one is CBS_CLIENT_CODE(*local partitioned index*) and others are unknown types of index to me??
    Means other 3 indexes are what type indexes ...either non-partitioned global index OR non-partitioned normal index??
    You got local index and 3 non-partitioned "NORMAL" b-tree tyep indexes
    Also if we create index as :(create index i_name on t_name(c_name)) By default it will create Global index. Please correct me......
    Above staement will create non-partitioned index
    Here is an example of creating global partitioned indexes
    CREATE INDEX month_ix ON sales(sales_month)
       GLOBAL PARTITION BY RANGE(sales_month)
          (PARTITION pm1_ix VALUES LESS THAN (2)
           PARTITION pm2_ix VALUES LESS THAN (3)
           PARTITION pm3_ix VALUES LESS THAN (4)
            PARTITION pm12_ix VALUES LESS THAN (MAXVALUE));Regards

  • Partition Table Looks Different Between OSX and Windows 7

    Hey all,
    I recently replaced the hard drive on my 2007 iMac, going from the 320GB drive to a 1 TB drive. It actually worked! The previous drive was failing in very odd ways, though booting into the Windows side (more on dual boot later) always seemed to work, and S.M.A.R.T. always reported that the physical drive seemed OK.
    The previous drive (320 GB) had around 200GB devoted to OSX and 100GB partitioned off for a working Windows 7 installation (custom installed x64 Win7 Ultimate). I had the Windows system image backed up to my NAS, and had a Windows system bootable disc to restore that image.
    After replacing the drive (and almost crying that I had actually done it right), I first restored OSX from a Time Machine backup, and let it take the full 1TB of space as Journalled HFS+. Then, I used Disk Utility to shrink OSX down to 500GB, and created a second partition (formatted to NTFS) with the remaining 500GB.
    Now, restoring a Windows system image is an odd thing, as it tries to do a lot of partition work as opposed to simply restoring the Windows install to a partition. I tried Macrium Reflect first (made a backup in that, too), and it looked like it was going to let me restore to the second partition. It completed the restore...and the entire hard drive was hosed. Partitions had been moved, renamed, resized, and nothing was bootable. I had to use Recovery from an external USB thumb drive to go back to the single, full-drive install of OSX.
    Then I tried again. Made the second NTFS partition and used the basic Windows System Restore disk to restore from the standard system image I had on the NAS. I was not expecting this to work. But it did. Windows started showing up in Startup Manager when "option" was pressed on bootup, and both OSX and Windows booted properly and ran fine. This is where I (finally) get to the supreme oddities:
    OSX Disk Utility still reports two 500GB partitions, one for OSX and one for Windows.
    In OSX the Windows partition shows as having NO DATA on it. Not sure what would happen if I tried to write a file to it when mounted, but there is no data on it when viewed from OSX (I was always able to see the Windows files when I mounted that partition on the previous drive).
    The Windows partition does not show up as a valid bootable system in System Prefs --> Startup Disk (naturally, I suppose, since OSX doesn't think there is anything there).
    From the WINDOWS side, Windows still sees the old partition table: 200GB for the "unknown" HFS partition, and then the rest of the space can be devoted to Windows (started as 100GB, but I was ablt to expand it to use the remaining ~750GB!).  Windows thinks it can have 750GB of space even though I know its partition is only 500GB in size!
    Windows cannot see the OSX HFS partition data using HFSExplorer. It CAN see the HFS partition on the attached backup drive (the drive I use for Time Machine).
    GParted (a partition program on a Linux bootabld CD-ROM) shows the same partitions as OSX Disk Utility (2x500GB), and also thinks the Windows NTFS partition is empty (all space reports as "unused").
    Did I mention both OSX and Windows work fine???
    There are, of course, two other partitions on the drive: the first partition is the 200MB one I always see (EFI/GUID portion?), and then between the HFS and NTFS partitions is the 600MB recovery partition (which also shows at option-pressed boot time). OSX, GParted, and Windows see all four partitions, and in the same order. It is just that Windows sees the wrong sizes, and OSX cannot see any data in the Windows partition.
    Surely this is all going to break spectacularly at some point, isn't it? What if I ever did write a file to the Windows side from OSX, or what if OSX starts taking more space than the 200GB Windows thinks is the max for that partition? What if I try to make Windows use more than 500GB because it thinks it has almost 800GB to use? What if I defrag the Windows drive?
    I had no idea a partition table could look this goofy and yet still have everything be bootable and workable. Is there something I can do to get everything in sync? Basically, I am assuming I need to get Windows to do some low-level kung fu in Disk Manager in order to properly get everything lined up with the "right" partitions as reported by both GParted and OSX Disk Utility. But how do I do that?
    By the way, any ideas that totally nuke the drive and start from scratch are completely fine (if it seems like they are doing something different enough that I'd give it a try). I have good backups of both OSX and Windows and have restored them about a half dozen times already as I dealt with the previous failing hard drive and with trying to get dual-boot working again. Not to mention, this iMac is now my secondary machine to the new Mac Mini I got a couple weeks back when I wasn't sure how much more life I was going to get from this 6+ year old iMac.
    Thanks for listening to me ramble about this very odd issue, and a huge THANK YOU in advance to anyone who has ideas to help.
    Thanks,
    sutekh138

    Update:
    I am pretty sure the issue is a simple GPT/MBR discrepancy.
    I installed rEFIt and used it's partitioning tool (gptsync built in) upon bootup. It was able to show the GPT table and the MBR table, but it thinks the second partition of the drive (the Mac OSX bootable partition) is "extended" in the MBR table and says "will not touch this disk."
    However, it does look like an MBR sync should be straightforward, as there four partitions in the GPT table and four in the MBR (and MBR allows a max of four, AFAIK). I just need gptsync to relax some rules. I found a link to a supposedly newer version of gptsync compiled for OSX, so I will try that later.
    First, I will try Partition Wizard, a free tool I found for the Windows side. It has a "Repair MBR" option that I would have tried last night if I weren't running a new Windows Image Backup in case all of this goes haywire.  *smile*  The PW tool also has an option to change the MBR over to GPT entirely. That might work, but then I am not sure Windows 7 will boot (from what I read, x64 Win7 running on EFI-enabled hardware should work, but who knows).
    Anyway, I will try the following things, in order, until something works, when I get home tonight:
    From Windows, run Partition Wizard and try "Repair MBR".
    From OSX, download recent gptsync and try to run it.
    From Windows, use Partition Wizard to do a full MBR --> GPT conversion.
    Nuke the Windows partition in OSX Disk Utility, expand the HFS partition to take up the whole drive, and then add a Windows-bootable partition via Boot Camp-ish command line commands (diskutil). Because if nothing else works, I have to assume I just created the partitions wrong in the first place such that a Windows restore miraculously works, but the partition weirdness is just a timebomb waiting to happen.
    Finally, if none of the above work, I'll just get things back to the way they now work and wait for the timebomb to (possibly never) go off.  *smile*
    I'll update this thread if I get something figured out, in case anyone else stumbles upon it...
    Thanks,
    sutekh138

Maybe you are looking for

  • Lost i-Tunes and need to get all my music back onto it

    Hi everybody, I really need some help! Last week my computer crashed and I lost every files I have had, so basically I have bought a new computer with nothing on it. The last two days I have been installing new files and other things. Now the thing i

  • Recovery Partition missing on Mac HD with OSX Mavericks

    When the Mac HDD/SSD was erased from the Mavericks Installer, rather than the Recovery Partition being upgraded to Mavericks, it was instead erased, and because the installer was meant to upgrade the Recovery Parittion, rather than create a Recovery

  • Bridge with Linksys

    Im looking to buy the Airport Extreme. Im told it can bridge to another wireless router/Access Point. In my basement I have a cable modem connected to a Linksys WRT300N. But it will not reach my whole house, so I need to add another Access point. Due

  • Question on ITable interface on extension points...

    Hi, I am trying to go through the cells of the table in the report body?  how do i do that.  I am getting table.getReportElementCount() as 0 even though I know the table has cells (rows and columns). I get the right name for the table.getName() . Tha

  • Hashing with jTable

    hi, I am doing a media player project and I have got stuck when trying to code for the option "Remove Duplicate Entries". I am using jTable, and I have written the code to add it to the hash, but I dont know how to get it back... My code is as follow