On Thu, 26 Feb 2015 13:40, greg.freemyer wrote:

On February 26, 2015 2:17:01 AM EST, Felix Miata wrote:

...

Thomas Taylor composed on 2015-02-25 23:02 (UTC-0800):

...

I performed an fresh install of OS 13.2 but ran into a problem when trying to get a dual boot system. The 13.2 install apparently requires a GPT partition scheme so I used PartedMagic to create that.

...

When I tried to install Windows 7 it balked at the GPT partition as it seems not able to use that scheme, requiring a DOS type partition table.

W7 supports GPT disks, but maybe not as configured by every instance by every partitioner.

My memory is W7 only supports GPT on data disks, not the boot disk.

And even then only on native (in case) sas or sata, not really via usb. Using a 3TB or bigger external disk via usb on W7 is asking for trouble and data loss. Yes, you can connect, you can even read, but you loose the moment you write. GPT on W7 is an attempt by M$ with many but!s. IMHO, do not attempt, not even with that compat-MBR stuff, tears, ulcer, and anger is all you will get. I'd like to get back those tree month work-time I've lost with trying to get GPT working on W7, internal and external. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, 26 Feb 2015 15:07, greg.freemyer wrote:

On February 26, 2015 7:58:45 AM EST, Yamaban wrote:

...

And even then only on native (in case) sas or sata, not really via usb.

Using a 3TB or bigger external disk via usb on W7 is asking for trouble and data loss. Yes, you can connect, you can even read, but you loose the moment you write.

I hope/pray that is an exaggeration.

I have a w7 box that had 4 3TB usb drives and a 4TB usb drive connected for the last week. Quite a bit of writing going on (several TB worth). I have not noticed any corruption. I really care about most of that data.

I have the md5 hash calculated and preserved for most of that data while the drives were connected to Linux. I may need to run a bunch verifies and see if I've destroyed anything.

I truly hope not, but thanks for the heads up.

Greg

Well, AFAIK, whether or not data-corruption occurs is mostly a matter of the Mainboard (Hardware), UEFI (BIOS does NOT work), and Drivers. If your MB has a UEFI, and you boot with it, you can try, with BIOS forget it, at least under Windows 7. With boards and firmware that is certified for W8 it works as long you boot in UEFI mode, so ca. second half 2012 and newer are OK. An other key-point is USB3. Native (chipset) USB3 works much more often than those on PCIe-cards or extra-chips (e.g. Renesas) onboard. Intel Series 7-Chipset(Panther Point) or newer, AMD Hudson M3/A68M/A70M see: http://en.wikipedia.org/wiki/List_of_AMD_chipsets http://en.wikipedia.org/wiki/List_of_Intel_chipsets Frustrating? Oh, yes! And: Exceptions are the Rule. Murphy LOVES you. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 27/02/15 03:03, Greg Freemyer wrote:

On Thu, Feb 26, 2015 at 10:28 AM, Yamaban wrote:

...

On Thu, 26 Feb 2015 15:07, greg.freemyer wrote:

...

On February 26, 2015 7:58:45 AM EST, Yamaban wrote:

...

And even then only on native (in case) sas or sata, not really via usb.

Using a 3TB or bigger external disk via usb on W7 is asking for trouble and data loss. Yes, you can connect, you can even read, but you loose the moment you write.

I hope/pray that is an exaggeration.

I have a w7 box that had 4 3TB usb drives and a 4TB usb drive connected for the last week. Quite a bit of writing going on (several TB worth). I have not noticed any corruption. I really care about most of that data.

I have the md5 hash calculated and preserved for most of that data while the drives were connected to Linux. I may need to run a bunch verifies and see if I've destroyed anything.

I truly hope not, but thanks for the heads up.

Greg

Well, AFAIK, whether or not data-corruption occurs is mostly a matter of the Mainboard (Hardware), UEFI (BIOS does NOT work), and Drivers.

If your MB has a UEFI, and you boot with it, you can try, with BIOS forget it, at least under Windows 7.

With boards and firmware that is certified for W8 it works as long you boot in UEFI mode, so ca. second half 2012 and newer are OK.

An other key-point is USB3. Native (chipset) USB3 works much more often than those on PCIe-cards or extra-chips (e.g. Renesas) onboard. Intel Series 7-Chipset(Panther Point) or newer, AMD Hudson M3/A68M/A70M see: http://en.wikipedia.org/wiki/List_of_AMD_chipsets http://en.wikipedia.org/wiki/List_of_Intel_chipsets

Frustrating? Oh, yes! And: Exceptions are the Rule. Murphy LOVES you. Since this is Windows related, I'm taking it to a different list to ask questions. You have got me fairly concerned that I have corrupted a bunch of data.

Fortunately any large original data I create is written via openSUSE, but I do perform smaller steps with Windows 7, so I could have corrupted a lot of data in the last week. :(

Thanks for the very important heads up, Greg

I dual-boot with Windows 7 (ie, openSUSE 13.1/13.2/TW and Windows 7). The mobo has UEFI - but I have disabled it. The BIOS is set to boot in legacy mode. The HDDs which I use are 1TB and 2TB in size (they are all sitting in mobile racks so switch between 1TB and 2TB depending on which set of OSs I want to run). All the HDDs are formatted in ext4 for Linux (openSUSE) and in ntfs for Windows. I have no hassles of any kind with this setup. But I guess I would need to start using GPT formatted HDDs if I start using bigger HDDs to what I have now. BC -- Using openSUSE 13.2, KDE 4.14.4 & kernel 3.19.0-2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 28/02/15 00:43, greg.freemyer@gmail.com wrote:

On February 26, 2015 11:55:03 PM EST, Basil Chupin wrote:

...

On 27/02/15 03:03, Greg Freemyer wrote:

...

On Thu, Feb 26, 2015 at 10:28 AM, Yamaban wrote:

...

On Thu, 26 Feb 2015 15:07, greg.freemyer wrote:

...

On February 26, 2015 7:58:45 AM EST, Yamaban wrote:

...

And even then only on native (in case) sas or sata, not really via

usb.

...

Using a 3TB or bigger external disk via usb on W7 is asking for trouble and data loss. Yes, you can connect, you can even read, but you loose the moment you write. I hope/pray that is an exaggeration.

I have a w7 box that had 4 3TB usb drives and a 4TB usb drive connected for the last week. Quite a bit of writing going on (several TB worth). I have not noticed any corruption. I really care about most of that data. I have the md5 hash calculated and preserved for most of that data while the drives were connected to Linux. I may need to run a bunch verifies and see if I've destroyed anything.

I truly hope not, but thanks for the heads up.

Greg Well, AFAIK, whether or not data-corruption occurs is mostly a matter of the Mainboard (Hardware), UEFI (BIOS does NOT work), and Drivers.

If your MB has a UEFI, and you boot with it, you can try, with BIOS forget it, at least under Windows 7.

With boards and firmware that is certified for W8 it works as long you boot in UEFI mode, so ca. second half 2012 and newer are OK.

An other key-point is USB3. Native (chipset) USB3 works much more often than those on PCIe-cards or extra-chips (e.g. Renesas) onboard. Intel Series 7-Chipset(Panther Point) or newer, AMD Hudson M3/A68M/A70M see: http://en.wikipedia.org/wiki/List_of_AMD_chipsets http://en.wikipedia.org/wiki/List_of_Intel_chipsets

Frustrating? Oh, yes! And: Exceptions are the Rule. Murphy LOVES you. Since this is Windows related, I'm taking it to a different list to ask questions. You have got me fairly concerned that I have corrupted a bunch of data.

Fortunately any large original data I create is written via openSUSE, but I do perform smaller steps with Windows 7, so I could have corrupted a lot of data in the last week. :(

Thanks for the very important heads up, Greg I dual-boot with Windows 7 (ie, openSUSE 13.1/13.2/TW and Windows 7).

The mobo has UEFI - but I have disabled it. The BIOS is set to boot in legacy mode.

The HDDs which I use are 1TB and 2TB in size (they are all sitting in mobile racks so switch between 1TB and 2TB depending on which set of OSs I want to run).

All the HDDs are formatted in ext4 for Linux (openSUSE) and in ntfs for

Windows.

I have no hassles of any kind with this setup.

But I guess I would need to start using GPT formatted HDDs if I start using bigger HDDs to what I have now.

BC Basil,

The traditional MBR based partition table stores the partition start sector as a 32 bit value. The maximum unsigned 32 bit number is roughly 4 billion (4 * 1024 * 1024 * 1024). Most devices still use 512 byte logical sectors, so that gives you 2 TiB as the largest offset from the start of the disk that can be handled.

GPT can handle bigger drives.

Yamaban is implying there are drivers/firmware in the USB communications path that also only pass 32 bits, or so I understand his comment. With those, a write to Ox0100001000 will actually go to 0x00000010000.

Thus for my larger drives that have more than 2 TiB of data on them, the new data may have overwritten older data. As I said I maintain md5 hashes for my core files (evidence files) so I can run a integrity test on some of the old data on those drives.

Greg

Yes, I know all that Greg which is why I specifically stated that my HDDs are no bigger than 2T and that even though I have UEFI I don't have GPT and dual-boot between oS and Windows 7 with ease. If I recall correctly the OP didn't have HDDs over 2T but someone took the thread in the direction of having bigger drives and GPTs - which didn't answer the OP's question (at least this is what I think I remember). BC -- Using openSUSE 13.2, KDE 4.14.4 & kernel 3.19.0-3 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org