x64 Vista SP1 and Win2008 corrupts large NTFS disk volumes

Discussion in 'Windows 64bit' started by UncleVic, Aug 4, 2008.

  1. UncleVic

    UncleVic Guest

    ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    SERVER 2008.

    On my multi-boot development server, I'm seeing corruption of my NTFS
    file system when using or installing upon large partitions using x64
    Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    (CHKDSK) of the volumes does not work, unless I boot to an x86
    edition O/S like Windows Server 2003 SP2 or Windows XP SP3.

    Anyone else see this behavior, or know why I'm experiencing this
    headache?

    -----------------------------------

    Layout of my paritions as follows:

    Disk 0 - ICH9R (RAID10) VOL0
    - Volume 0 - Primary Partition (active) 40GB, system partition
    - Extended Logical Partition (none)
    Disk 1 - ICH9R (RAID10) VOL1
    - Primary Partition (active) 40GB (x64 Windows Server 2008)
    - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    - Primary Partition 813GB (x64 Windows Vista SP1)
    - Extended Logical Partition (none)
    Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    - Primary Partition 40GB (x64 Windows Vista SP1)
    - Extended Logical Partition (none)
    Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    - Primary Partition (active) 698GB
    - Extended Logical Partition (none)

    Volumes susceptible to corruption: the 813GB and 698GB volumes

    All HDDs SATA
    DVD on JMB363 PATA port

    ICH9R RAID status is normal (healthy mode, not degraded)
    JMB363 RAID capable, but only AHCI features used

    Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)

    All OS'es are bootable (last install was x64 Vista SP1)
    -----------------------------------

    OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    CPU: Intel Q6600 Quad Core
    Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst Drivers.
    NIC: Marvell 88E8052 Gigabyte LAN PCIe
    Mobo: DFI LP UT P35-T2R
    Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    ....and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure, eSATA)
    Raid: ICH9R 4xHDD RAID10 = 1TB
    Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE mode)
    DVD: HP DVD Writer 1040r (IDE)
     
    UncleVic, Aug 4, 2008
    #1
    1. Advertising

  2. UncleVic

    Carlos Guest

    Hi,
    I would start by installing the latest drivers.
    Jmicron
    ftp://driver.jmicron.com.tw/jmb36x
    Intel ICH9R
    http://downloadcenter.intel.com/fil...dows Vista* 64&lang=eng&strOSs=150&submit=Go!
    Carlos

    "UncleVic" wrote:

    > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    > SERVER 2008.
    >
    > On my multi-boot development server, I'm seeing corruption of my NTFS
    > file system when using or installing upon large partitions using x64
    > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    > (CHKDSK) of the volumes does not work, unless I boot to an x86
    > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    >
    > Anyone else see this behavior, or know why I'm experiencing this
    > headache?
    >
    > -----------------------------------
    >
    > Layout of my paritions as follows:
    >
    > Disk 0 - ICH9R (RAID10) VOL0
    > - Volume 0 - Primary Partition (active) 40GB, system partition
    > - Extended Logical Partition (none)
    > Disk 1 - ICH9R (RAID10) VOL1
    > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    > - Primary Partition 813GB (x64 Windows Vista SP1)
    > - Extended Logical Partition (none)
    > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    > - Primary Partition 40GB (x64 Windows Vista SP1)
    > - Extended Logical Partition (none)
    > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > - Primary Partition (active) 698GB
    > - Extended Logical Partition (none)
    >
    > Volumes susceptible to corruption: the 813GB and 698GB volumes
    >
    > All HDDs SATA
    > DVD on JMB363 PATA port
    >
    > ICH9R RAID status is normal (healthy mode, not degraded)
    > JMB363 RAID capable, but only AHCI features used
    >
    > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    >
    > All OS'es are bootable (last install was x64 Vista SP1)
    > -----------------------------------
    >
    > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    > CPU: Intel Q6600 Quad Core
    > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst Drivers.
    > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    > Mobo: DFI LP UT P35-T2R
    > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure, eSATA)
    > Raid: ICH9R 4xHDD RAID10 = 1TB
    > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE mode)
    > DVD: HP DVD Writer 1040r (IDE)
    >
     
    Carlos, Aug 4, 2008
    #2
    1. Advertising

  3. Carlos is pointing you in the right direction. I've seen reports of issues
    with Intel based RAID controllers and large file movements. Updating the
    BIOS for the controller, and making sure you have the latest drivers, is the
    right way to go.

    FWIW, I've run partitions of up to 2 GB without issue on Server 2k8 x64.

    The other thing you might consider is using GPT for those larger volumes.
    You can't use it for the boot volume, but the other two could easily be
    converted to GPT. And it's a better way to go for really large volumes.

    --
    Charlie.
    "UncleVic" <> wrote in message
    news:...
    > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    > SERVER 2008.
    >
    > On my multi-boot development server, I'm seeing corruption of my NTFS
    > file system when using or installing upon large partitions using x64
    > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    > (CHKDSK) of the volumes does not work, unless I boot to an x86
    > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    >
    > Anyone else see this behavior, or know why I'm experiencing this
    > headache?
    >
    > -----------------------------------
    >
    > Layout of my paritions as follows:
    >
    > Disk 0 - ICH9R (RAID10) VOL0
    > - Volume 0 - Primary Partition (active) 40GB, system partition
    > - Extended Logical Partition (none)
    > Disk 1 - ICH9R (RAID10) VOL1
    > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    > - Primary Partition 813GB (x64 Windows Vista SP1)
    > - Extended Logical Partition (none)
    > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    > - Primary Partition 40GB (x64 Windows Vista SP1)
    > - Extended Logical Partition (none)
    > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > - Primary Partition (active) 698GB
    > - Extended Logical Partition (none)
    >
    > Volumes susceptible to corruption: the 813GB and 698GB volumes
    >
    > All HDDs SATA
    > DVD on JMB363 PATA port
    >
    > ICH9R RAID status is normal (healthy mode, not degraded)
    > JMB363 RAID capable, but only AHCI features used
    >
    > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    >
    > All OS'es are bootable (last install was x64 Vista SP1)
    > -----------------------------------
    >
    > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    > CPU: Intel Q6600 Quad Core
    > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst Drivers.
    > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    > Mobo: DFI LP UT P35-T2R
    > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure, eSATA)
    > Raid: ICH9R 4xHDD RAID10 = 1TB
    > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE mode)
    > DVD: HP DVD Writer 1040r (IDE)
    >
     
    Charlie Russel - MVP, Aug 5, 2008
    #3
  4. I use Vista Business x64 and have also noticed corruption issues though not
    of the entire volume, only with large archive and iso files that I know
    woked fine but now give errors. I am on the latest drivers and also with the
    Intel ICH9R Raid controller. I have noticed it in both 1TB raid 0 and 750GB
    raid 1 arrays.

    OS: Vista Business x64 SP1
    CPU: Intel Q6600 Quad Core
    Video: Gigabyte 8800GTS 512MB
    Mobo: Gigabyte P35-DS4
    Mem: 8GB 4x2GB PNYatriot Viper PC2-8500, 5-5-5-15)
    Disks: 3 x WD 500GB SATA2 16Mb cache
    2 x Samsung 750GB SATA2 16Mb cache

    "UncleVic" <> wrote in message
    news:...
    > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    > SERVER 2008.
    >
    > On my multi-boot development server, I'm seeing corruption of my NTFS
    > file system when using or installing upon large partitions using x64
    > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    > (CHKDSK) of the volumes does not work, unless I boot to an x86
    > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    >
    > Anyone else see this behavior, or know why I'm experiencing this
    > headache?
    >
    > -----------------------------------
    >
    > Layout of my paritions as follows:
    >
    > Disk 0 - ICH9R (RAID10) VOL0
    > - Volume 0 - Primary Partition (active) 40GB, system partition
    > - Extended Logical Partition (none)
    > Disk 1 - ICH9R (RAID10) VOL1
    > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    > - Primary Partition 813GB (x64 Windows Vista SP1)
    > - Extended Logical Partition (none)
    > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    > - Primary Partition 40GB (x64 Windows Vista SP1)
    > - Extended Logical Partition (none)
    > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > - Primary Partition (active) 698GB
    > - Extended Logical Partition (none)
    >
    > Volumes susceptible to corruption: the 813GB and 698GB volumes
    >
    > All HDDs SATA
    > DVD on JMB363 PATA port
    >
    > ICH9R RAID status is normal (healthy mode, not degraded)
    > JMB363 RAID capable, but only AHCI features used
    >
    > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    >
    > All OS'es are bootable (last install was x64 Vista SP1)
    > -----------------------------------
    >
    > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    > CPU: Intel Q6600 Quad Core
    > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst Drivers.
    > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    > Mobo: DFI LP UT P35-T2R
    > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure, eSATA)
    > Raid: ICH9R 4xHDD RAID10 = 1TB
    > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE mode)
    > DVD: HP DVD Writer 1040r (IDE)
    >
     
    Robert McMillan, Aug 5, 2008
    #4
  5. UncleVic

    Carlos Guest

    Charlie,
    I have also found an unresolved funny thing with jmicron based RAID
    partitions.
    Randomly after a reboot a partition (but not the boot one) may start in
    read-only mode not allowing you to modify or write anything there.
    This happens in Vista x64 SP1 and seems to be a Vista bug.
    Workaround is to use the fsutil command in an elevated window to unmount the
    problematic partition without rebooting. On the next access to that partition
    things should be normal again.
    :)
    Carlos


    "Charlie Russel - MVP" wrote:

    > Carlos is pointing you in the right direction. I've seen reports of issues
    > with Intel based RAID controllers and large file movements. Updating the
    > BIOS for the controller, and making sure you have the latest drivers, is the
    > right way to go.
    >
    > FWIW, I've run partitions of up to 2 GB without issue on Server 2k8 x64.
    >
    > The other thing you might consider is using GPT for those larger volumes.
    > You can't use it for the boot volume, but the other two could easily be
    > converted to GPT. And it's a better way to go for really large volumes.
    >
    > --
    > Charlie.
    > "UncleVic" <> wrote in message
    > news:...
    > > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    > > SERVER 2008.
    > >
    > > On my multi-boot development server, I'm seeing corruption of my NTFS
    > > file system when using or installing upon large partitions using x64
    > > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    > > (CHKDSK) of the volumes does not work, unless I boot to an x86
    > > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    > >
    > > Anyone else see this behavior, or know why I'm experiencing this
    > > headache?
    > >
    > > -----------------------------------
    > >
    > > Layout of my paritions as follows:
    > >
    > > Disk 0 - ICH9R (RAID10) VOL0
    > > - Volume 0 - Primary Partition (active) 40GB, system partition
    > > - Extended Logical Partition (none)
    > > Disk 1 - ICH9R (RAID10) VOL1
    > > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    > > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    > > - Primary Partition 813GB (x64 Windows Vista SP1)
    > > - Extended Logical Partition (none)
    > > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    > > - Primary Partition 40GB (x64 Windows Vista SP1)
    > > - Extended Logical Partition (none)
    > > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > > - Primary Partition (active) 698GB
    > > - Extended Logical Partition (none)
    > >
    > > Volumes susceptible to corruption: the 813GB and 698GB volumes
    > >
    > > All HDDs SATA
    > > DVD on JMB363 PATA port
    > >
    > > ICH9R RAID status is normal (healthy mode, not degraded)
    > > JMB363 RAID capable, but only AHCI features used
    > >
    > > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    > > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    > >
    > > All OS'es are bootable (last install was x64 Vista SP1)
    > > -----------------------------------
    > >
    > > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    > > CPU: Intel Q6600 Quad Core
    > > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst Drivers.
    > > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    > > Mobo: DFI LP UT P35-T2R
    > > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    > > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    > > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure, eSATA)
    > > Raid: ICH9R 4xHDD RAID10 = 1TB
    > > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE mode)
    > > DVD: HP DVD Writer 1040r (IDE)
    > >

    >
    >
     
    Carlos, Aug 5, 2008
    #5
  6. Well, I'd say it's a driver bug, not a Vista bug from your description.
    Though apparently one not surfaced until Vista SP1.

    --
    Charlie.
    "Carlos" <> wrote in message
    news:...
    > Charlie,
    > I have also found an unresolved funny thing with jmicron based RAID
    > partitions.
    > Randomly after a reboot a partition (but not the boot one) may start in
    > read-only mode not allowing you to modify or write anything there.
    > This happens in Vista x64 SP1 and seems to be a Vista bug.
    > Workaround is to use the fsutil command in an elevated window to unmount
    > the
    > problematic partition without rebooting. On the next access to that
    > partition
    > things should be normal again.
    > :)
    > Carlos
    >
    >
    > "Charlie Russel - MVP" wrote:
    >
    >> Carlos is pointing you in the right direction. I've seen reports of
    >> issues
    >> with Intel based RAID controllers and large file movements. Updating the
    >> BIOS for the controller, and making sure you have the latest drivers, is
    >> the
    >> right way to go.
    >>
    >> FWIW, I've run partitions of up to 2 GB without issue on Server 2k8 x64.
    >>
    >> The other thing you might consider is using GPT for those larger volumes.
    >> You can't use it for the boot volume, but the other two could easily be
    >> converted to GPT. And it's a better way to go for really large volumes.
    >>
    >> --
    >> Charlie.
    >> "UncleVic" <> wrote in message
    >> news:...
    >> > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    >> > SERVER 2008.
    >> >
    >> > On my multi-boot development server, I'm seeing corruption of my NTFS
    >> > file system when using or installing upon large partitions using x64
    >> > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    >> > (CHKDSK) of the volumes does not work, unless I boot to an x86
    >> > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    >> >
    >> > Anyone else see this behavior, or know why I'm experiencing this
    >> > headache?
    >> >
    >> > -----------------------------------
    >> >
    >> > Layout of my paritions as follows:
    >> >
    >> > Disk 0 - ICH9R (RAID10) VOL0
    >> > - Volume 0 - Primary Partition (active) 40GB, system partition
    >> > - Extended Logical Partition (none)
    >> > Disk 1 - ICH9R (RAID10) VOL1
    >> > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    >> > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    >> > - Primary Partition 813GB (x64 Windows Vista SP1)
    >> > - Extended Logical Partition (none)
    >> > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    >> > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    >> > - Primary Partition 40GB (x64 Windows Vista SP1)
    >> > - Extended Logical Partition (none)
    >> > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    >> > - Primary Partition (active) 698GB
    >> > - Extended Logical Partition (none)
    >> >
    >> > Volumes susceptible to corruption: the 813GB and 698GB volumes
    >> >
    >> > All HDDs SATA
    >> > DVD on JMB363 PATA port
    >> >
    >> > ICH9R RAID status is normal (healthy mode, not degraded)
    >> > JMB363 RAID capable, but only AHCI features used
    >> >
    >> > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    >> > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    >> >
    >> > All OS'es are bootable (last install was x64 Vista SP1)
    >> > -----------------------------------
    >> >
    >> > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    >> > CPU: Intel Q6600 Quad Core
    >> > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst Drivers.
    >> > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    >> > Mobo: DFI LP UT P35-T2R
    >> > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    >> > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    >> > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure, eSATA)
    >> > Raid: ICH9R 4xHDD RAID10 = 1TB
    >> > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE mode)
    >> > DVD: HP DVD Writer 1040r (IDE)
    >> >

    >>
    >>
     
    Charlie Russel - MVP, Aug 5, 2008
    #6
  7. UncleVic

    Kerry Brown Guest

    Do you run iTunes? ITunes and Intel RAID have had problems for a while.

    http://www.google.com/search?hl=en&q=itunes intel raid&meta=

    --
    Kerry Brown
    MS-MVP - Windows Desktop Experience: Systems Administration
    http://www.vistahelp.ca/phpBB2/
    http://vistahelpca.blogspot.com/


    "Robert McMillan" <> wrote in message
    news:...
    >I use Vista Business x64 and have also noticed corruption issues though not
    >of the entire volume, only with large archive and iso files that I know
    >woked fine but now give errors. I am on the latest drivers and also with
    >the Intel ICH9R Raid controller. I have noticed it in both 1TB raid 0 and
    >750GB raid 1 arrays.
    >
    > OS: Vista Business x64 SP1
    > CPU: Intel Q6600 Quad Core
    > Video: Gigabyte 8800GTS 512MB
    > Mobo: Gigabyte P35-DS4
    > Mem: 8GB 4x2GB PNYatriot Viper PC2-8500, 5-5-5-15)
    > Disks: 3 x WD 500GB SATA2 16Mb cache
    > 2 x Samsung 750GB SATA2 16Mb cache
    >
    > "UncleVic" <> wrote in message
    > news:...
    >> ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    >> SERVER 2008.
    >>
    >> On my multi-boot development server, I'm seeing corruption of my NTFS
    >> file system when using or installing upon large partitions using x64
    >> Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    >> (CHKDSK) of the volumes does not work, unless I boot to an x86
    >> edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    >>
    >> Anyone else see this behavior, or know why I'm experiencing this
    >> headache?
    >>
    >> -----------------------------------
    >>
    >> Layout of my paritions as follows:
    >>
    >> Disk 0 - ICH9R (RAID10) VOL0
    >> - Volume 0 - Primary Partition (active) 40GB, system partition
    >> - Extended Logical Partition (none)
    >> Disk 1 - ICH9R (RAID10) VOL1
    >> - Primary Partition (active) 40GB (x64 Windows Server 2008)
    >> - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    >> - Primary Partition 813GB (x64 Windows Vista SP1)
    >> - Extended Logical Partition (none)
    >> Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    >> - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    >> - Primary Partition 40GB (x64 Windows Vista SP1)
    >> - Extended Logical Partition (none)
    >> Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    >> - Primary Partition (active) 698GB
    >> - Extended Logical Partition (none)
    >>
    >> Volumes susceptible to corruption: the 813GB and 698GB volumes
    >>
    >> All HDDs SATA
    >> DVD on JMB363 PATA port
    >>
    >> ICH9R RAID status is normal (healthy mode, not degraded)
    >> JMB363 RAID capable, but only AHCI features used
    >>
    >> Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    >> JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    >>
    >> All OS'es are bootable (last install was x64 Vista SP1)
    >> -----------------------------------
    >>
    >> OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    >> CPU: Intel Q6600 Quad Core
    >> Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst Drivers.
    >> NIC: Marvell 88E8052 Gigabyte LAN PCIe
    >> Mobo: DFI LP UT P35-T2R
    >> Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    >> Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    >> ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure, eSATA)
    >> Raid: ICH9R 4xHDD RAID10 = 1TB
    >> Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE mode)
    >> DVD: HP DVD Writer 1040r (IDE)
    >>

    >
     
    Kerry Brown, Aug 5, 2008
    #7
  8. UncleVic

    Carlos Guest

    Charlie,
    I found the workaround in an MSFT forum (think it was on technet) where an
    MVP affirmed that this was a Vista SP1 bug and that it might not be corrected
    until SP2.
    Sadly I have lost the link where I find it so I can't quote it exactly.
    The workaround survived, which is the most important part for me.
    :)
    Carlos

    "Charlie Russel - MVP" wrote:

    > Well, I'd say it's a driver bug, not a Vista bug from your description.
    > Though apparently one not surfaced until Vista SP1.
    >
    > --
    > Charlie.
    > "Carlos" <> wrote in message
    > news:...
    > > Charlie,
    > > I have also found an unresolved funny thing with jmicron based RAID
    > > partitions.
    > > Randomly after a reboot a partition (but not the boot one) may start in
    > > read-only mode not allowing you to modify or write anything there.
    > > This happens in Vista x64 SP1 and seems to be a Vista bug.
    > > Workaround is to use the fsutil command in an elevated window to unmount
    > > the
    > > problematic partition without rebooting. On the next access to that
    > > partition
    > > things should be normal again.
    > > :)
    > > Carlos
    > >
    > >
    > > "Charlie Russel - MVP" wrote:
    > >
    > >> Carlos is pointing you in the right direction. I've seen reports of
    > >> issues
    > >> with Intel based RAID controllers and large file movements. Updating the
    > >> BIOS for the controller, and making sure you have the latest drivers, is
    > >> the
    > >> right way to go.
    > >>
    > >> FWIW, I've run partitions of up to 2 GB without issue on Server 2k8 x64.
    > >>
    > >> The other thing you might consider is using GPT for those larger volumes.
    > >> You can't use it for the boot volume, but the other two could easily be
    > >> converted to GPT. And it's a better way to go for really large volumes.
    > >>
    > >> --
    > >> Charlie.
    > >> "UncleVic" <> wrote in message
    > >> news:...
    > >> > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    > >> > SERVER 2008.
    > >> >
    > >> > On my multi-boot development server, I'm seeing corruption of my NTFS
    > >> > file system when using or installing upon large partitions using x64
    > >> > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    > >> > (CHKDSK) of the volumes does not work, unless I boot to an x86
    > >> > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    > >> >
    > >> > Anyone else see this behavior, or know why I'm experiencing this
    > >> > headache?
    > >> >
    > >> > -----------------------------------
    > >> >
    > >> > Layout of my paritions as follows:
    > >> >
    > >> > Disk 0 - ICH9R (RAID10) VOL0
    > >> > - Volume 0 - Primary Partition (active) 40GB, system partition
    > >> > - Extended Logical Partition (none)
    > >> > Disk 1 - ICH9R (RAID10) VOL1
    > >> > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    > >> > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    > >> > - Primary Partition 813GB (x64 Windows Vista SP1)
    > >> > - Extended Logical Partition (none)
    > >> > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > >> > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    > >> > - Primary Partition 40GB (x64 Windows Vista SP1)
    > >> > - Extended Logical Partition (none)
    > >> > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > >> > - Primary Partition (active) 698GB
    > >> > - Extended Logical Partition (none)
    > >> >
    > >> > Volumes susceptible to corruption: the 813GB and 698GB volumes
    > >> >
    > >> > All HDDs SATA
    > >> > DVD on JMB363 PATA port
    > >> >
    > >> > ICH9R RAID status is normal (healthy mode, not degraded)
    > >> > JMB363 RAID capable, but only AHCI features used
    > >> >
    > >> > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    > >> > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    > >> >
    > >> > All OS'es are bootable (last install was x64 Vista SP1)
    > >> > -----------------------------------
    > >> >
    > >> > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    > >> > CPU: Intel Q6600 Quad Core
    > >> > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst Drivers.
    > >> > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    > >> > Mobo: DFI LP UT P35-T2R
    > >> > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    > >> > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    > >> > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure, eSATA)
    > >> > Raid: ICH9R 4xHDD RAID10 = 1TB
    > >> > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE mode)
    > >> > DVD: HP DVD Writer 1040r (IDE)
    > >> >
    > >>
    > >>

    >
    >
     
    Carlos, Aug 5, 2008
    #8
  9. UncleVic

    Carlos Guest

    Charlie,
    Here's the technet forum reference I mentioned:
    http://forums.microsoft.com/technet...5&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=2
    Greg Knight from Microsoft (not an MVP) says:
    "I think the issue lies in how we're mounting the filesystem - about 5% of
    the remounts leave the volume in "read-only" mode. I suspect that the system
    volume is immune due to a necessarily different mounting procedure. The
    appearance of "randomly" going into this state could be explained by the
    system dismounting the volume after a brief period of disuse or a flush, for
    power or data integrity reasons; I am not immediately familiar with this
    component so I cannot speak with certainty on it.
    I'm filing a bug and will try to have this addressed in Vista SP2; I do not
    think we will package a fix for this before then, I'm sorry to say."

    :)
    Carlos

    "Charlie Russel - MVP" wrote:

    > Well, I'd say it's a driver bug, not a Vista bug from your description.
    > Though apparently one not surfaced until Vista SP1.
    >
    > --
    > Charlie.
    > "Carlos" <> wrote in message
    > news:...
    > > Charlie,
    > > I have also found an unresolved funny thing with jmicron based RAID
    > > partitions.
    > > Randomly after a reboot a partition (but not the boot one) may start in
    > > read-only mode not allowing you to modify or write anything there.
    > > This happens in Vista x64 SP1 and seems to be a Vista bug.
    > > Workaround is to use the fsutil command in an elevated window to unmount
    > > the
    > > problematic partition without rebooting. On the next access to that
    > > partition
    > > things should be normal again.
    > > :)
    > > Carlos
    > >
    > >
    > > "Charlie Russel - MVP" wrote:
    > >
    > >> Carlos is pointing you in the right direction. I've seen reports of
    > >> issues
    > >> with Intel based RAID controllers and large file movements. Updating the
    > >> BIOS for the controller, and making sure you have the latest drivers, is
    > >> the
    > >> right way to go.
    > >>
    > >> FWIW, I've run partitions of up to 2 GB without issue on Server 2k8 x64.
    > >>
    > >> The other thing you might consider is using GPT for those larger volumes.
    > >> You can't use it for the boot volume, but the other two could easily be
    > >> converted to GPT. And it's a better way to go for really large volumes.
    > >>
    > >> --
    > >> Charlie.
    > >> "UncleVic" <> wrote in message
    > >> news:...
    > >> > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    > >> > SERVER 2008.
    > >> >
    > >> > On my multi-boot development server, I'm seeing corruption of my NTFS
    > >> > file system when using or installing upon large partitions using x64
    > >> > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    > >> > (CHKDSK) of the volumes does not work, unless I boot to an x86
    > >> > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    > >> >
    > >> > Anyone else see this behavior, or know why I'm experiencing this
    > >> > headache?
    > >> >
    > >> > -----------------------------------
    > >> >
    > >> > Layout of my paritions as follows:
    > >> >
    > >> > Disk 0 - ICH9R (RAID10) VOL0
    > >> > - Volume 0 - Primary Partition (active) 40GB, system partition
    > >> > - Extended Logical Partition (none)
    > >> > Disk 1 - ICH9R (RAID10) VOL1
    > >> > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    > >> > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    > >> > - Primary Partition 813GB (x64 Windows Vista SP1)
    > >> > - Extended Logical Partition (none)
    > >> > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > >> > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    > >> > - Primary Partition 40GB (x64 Windows Vista SP1)
    > >> > - Extended Logical Partition (none)
    > >> > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > >> > - Primary Partition (active) 698GB
    > >> > - Extended Logical Partition (none)
    > >> >
    > >> > Volumes susceptible to corruption: the 813GB and 698GB volumes
    > >> >
    > >> > All HDDs SATA
    > >> > DVD on JMB363 PATA port
    > >> >
    > >> > ICH9R RAID status is normal (healthy mode, not degraded)
    > >> > JMB363 RAID capable, but only AHCI features used
    > >> >
    > >> > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    > >> > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    > >> >
    > >> > All OS'es are bootable (last install was x64 Vista SP1)
    > >> > -----------------------------------
    > >> >
    > >> > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    > >> > CPU: Intel Q6600 Quad Core
    > >> > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst Drivers.
    > >> > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    > >> > Mobo: DFI LP UT P35-T2R
    > >> > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    > >> > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    > >> > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure, eSATA)
    > >> > Raid: ICH9R 4xHDD RAID10 = 1TB
    > >> > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE mode)
    > >> > DVD: HP DVD Writer 1040r (IDE)
    > >> >
    > >>
    > >>

    >
    >
     
    Carlos, Aug 5, 2008
    #9
  10. I'd still say it's a driver bug - since it doesn't exist except with certain
    hardware and drivers. The problem seems to me to be one that I certainly
    don't see on any of my hardware here, but then I never thought much of Intel
    RAID controllers and have avoided them over the years.

    --
    Charlie.
    http://msmvps.com/blogs/xperts64
    http://mvp.support.microsoft.com/profile/charlie.russel


    "Carlos" <> wrote in message
    news:...
    > Charlie,
    > Here's the technet forum reference I mentioned:
    > http://forums.microsoft.com/technet...5&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=2
    > Greg Knight from Microsoft (not an MVP) says:
    > "I think the issue lies in how we're mounting the filesystem - about 5% of
    > the remounts leave the volume in "read-only" mode. I suspect that the
    > system
    > volume is immune due to a necessarily different mounting procedure. The
    > appearance of "randomly" going into this state could be explained by the
    > system dismounting the volume after a brief period of disuse or a flush,
    > for
    > power or data integrity reasons; I am not immediately familiar with this
    > component so I cannot speak with certainty on it.
    > I'm filing a bug and will try to have this addressed in Vista SP2; I do
    > not
    > think we will package a fix for this before then, I'm sorry to say."
    >
    > :)
    > Carlos
    >
    > "Charlie Russel - MVP" wrote:
    >
    >> Well, I'd say it's a driver bug, not a Vista bug from your description.
    >> Though apparently one not surfaced until Vista SP1.
    >>
    >> --
    >> Charlie.
    >> "Carlos" <> wrote in message
    >> news:...
    >> > Charlie,
    >> > I have also found an unresolved funny thing with jmicron based RAID
    >> > partitions.
    >> > Randomly after a reboot a partition (but not the boot one) may start in
    >> > read-only mode not allowing you to modify or write anything there.
    >> > This happens in Vista x64 SP1 and seems to be a Vista bug.
    >> > Workaround is to use the fsutil command in an elevated window to
    >> > unmount
    >> > the
    >> > problematic partition without rebooting. On the next access to that
    >> > partition
    >> > things should be normal again.
    >> > :)
    >> > Carlos
    >> >
    >> >
    >> > "Charlie Russel - MVP" wrote:
    >> >
    >> >> Carlos is pointing you in the right direction. I've seen reports of
    >> >> issues
    >> >> with Intel based RAID controllers and large file movements. Updating
    >> >> the
    >> >> BIOS for the controller, and making sure you have the latest drivers,
    >> >> is
    >> >> the
    >> >> right way to go.
    >> >>
    >> >> FWIW, I've run partitions of up to 2 GB without issue on Server 2k8
    >> >> x64.
    >> >>
    >> >> The other thing you might consider is using GPT for those larger
    >> >> volumes.
    >> >> You can't use it for the boot volume, but the other two could easily
    >> >> be
    >> >> converted to GPT. And it's a better way to go for really large
    >> >> volumes.
    >> >>
    >> >> --
    >> >> Charlie.
    >> >> "UncleVic" <> wrote in message
    >> >> news:...
    >> >> > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    >> >> > SERVER 2008.
    >> >> >
    >> >> > On my multi-boot development server, I'm seeing corruption of my
    >> >> > NTFS
    >> >> > file system when using or installing upon large partitions using x64
    >> >> > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    >> >> > (CHKDSK) of the volumes does not work, unless I boot to an x86
    >> >> > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    >> >> >
    >> >> > Anyone else see this behavior, or know why I'm experiencing this
    >> >> > headache?
    >> >> >
    >> >> > -----------------------------------
    >> >> >
    >> >> > Layout of my paritions as follows:
    >> >> >
    >> >> > Disk 0 - ICH9R (RAID10) VOL0
    >> >> > - Volume 0 - Primary Partition (active) 40GB, system partition
    >> >> > - Extended Logical Partition (none)
    >> >> > Disk 1 - ICH9R (RAID10) VOL1
    >> >> > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    >> >> > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    >> >> > - Primary Partition 813GB (x64 Windows Vista SP1)
    >> >> > - Extended Logical Partition (none)
    >> >> > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    >> >> > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    >> >> > - Primary Partition 40GB (x64 Windows Vista SP1)
    >> >> > - Extended Logical Partition (none)
    >> >> > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    >> >> > - Primary Partition (active) 698GB
    >> >> > - Extended Logical Partition (none)
    >> >> >
    >> >> > Volumes susceptible to corruption: the 813GB and 698GB volumes
    >> >> >
    >> >> > All HDDs SATA
    >> >> > DVD on JMB363 PATA port
    >> >> >
    >> >> > ICH9R RAID status is normal (healthy mode, not degraded)
    >> >> > JMB363 RAID capable, but only AHCI features used
    >> >> >
    >> >> > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    >> >> > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    >> >> >
    >> >> > All OS'es are bootable (last install was x64 Vista SP1)
    >> >> > -----------------------------------
    >> >> >
    >> >> > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    >> >> > CPU: Intel Q6600 Quad Core
    >> >> > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst
    >> >> > Drivers.
    >> >> > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    >> >> > Mobo: DFI LP UT P35-T2R
    >> >> > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    >> >> > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    >> >> > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure,
    >> >> > eSATA)
    >> >> > Raid: ICH9R 4xHDD RAID10 = 1TB
    >> >> > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE
    >> >> > mode)
    >> >> > DVD: HP DVD Writer 1040r (IDE)
    >> >> >
    >> >>
    >> >>

    >>
    >>
     
    Charlie Russel - MVP, Aug 5, 2008
    #10
  11. UncleVic

    Carlos Guest

    NVidia controllers rock!!!
    :))))))

    "Charlie Russel - MVP" wrote:

    > I'd still say it's a driver bug - since it doesn't exist except with certain
    > hardware and drivers. The problem seems to me to be one that I certainly
    > don't see on any of my hardware here, but then I never thought much of Intel
    > RAID controllers and have avoided them over the years.
    >
    > --
    > Charlie.
    > http://msmvps.com/blogs/xperts64
    > http://mvp.support.microsoft.com/profile/charlie.russel
    >
    >
    > "Carlos" <> wrote in message
    > news:...
    > > Charlie,
    > > Here's the technet forum reference I mentioned:
    > > http://forums.microsoft.com/technet...5&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=2
    > > Greg Knight from Microsoft (not an MVP) says:
    > > "I think the issue lies in how we're mounting the filesystem - about 5% of
    > > the remounts leave the volume in "read-only" mode. I suspect that the
    > > system
    > > volume is immune due to a necessarily different mounting procedure. The
    > > appearance of "randomly" going into this state could be explained by the
    > > system dismounting the volume after a brief period of disuse or a flush,
    > > for
    > > power or data integrity reasons; I am not immediately familiar with this
    > > component so I cannot speak with certainty on it.
    > > I'm filing a bug and will try to have this addressed in Vista SP2; I do
    > > not
    > > think we will package a fix for this before then, I'm sorry to say."
    > >
    > > :)
    > > Carlos
    > >
    > > "Charlie Russel - MVP" wrote:
    > >
    > >> Well, I'd say it's a driver bug, not a Vista bug from your description.
    > >> Though apparently one not surfaced until Vista SP1.
    > >>
    > >> --
    > >> Charlie.
    > >> "Carlos" <> wrote in message
    > >> news:...
    > >> > Charlie,
    > >> > I have also found an unresolved funny thing with jmicron based RAID
    > >> > partitions.
    > >> > Randomly after a reboot a partition (but not the boot one) may start in
    > >> > read-only mode not allowing you to modify or write anything there.
    > >> > This happens in Vista x64 SP1 and seems to be a Vista bug.
    > >> > Workaround is to use the fsutil command in an elevated window to
    > >> > unmount
    > >> > the
    > >> > problematic partition without rebooting. On the next access to that
    > >> > partition
    > >> > things should be normal again.
    > >> > :)
    > >> > Carlos
    > >> >
    > >> >
    > >> > "Charlie Russel - MVP" wrote:
    > >> >
    > >> >> Carlos is pointing you in the right direction. I've seen reports of
    > >> >> issues
    > >> >> with Intel based RAID controllers and large file movements. Updating
    > >> >> the
    > >> >> BIOS for the controller, and making sure you have the latest drivers,
    > >> >> is
    > >> >> the
    > >> >> right way to go.
    > >> >>
    > >> >> FWIW, I've run partitions of up to 2 GB without issue on Server 2k8
    > >> >> x64.
    > >> >>
    > >> >> The other thing you might consider is using GPT for those larger
    > >> >> volumes.
    > >> >> You can't use it for the boot volume, but the other two could easily
    > >> >> be
    > >> >> converted to GPT. And it's a better way to go for really large
    > >> >> volumes.
    > >> >>
    > >> >> --
    > >> >> Charlie.
    > >> >> "UncleVic" <> wrote in message
    > >> >> news:...
    > >> >> > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    > >> >> > SERVER 2008.
    > >> >> >
    > >> >> > On my multi-boot development server, I'm seeing corruption of my
    > >> >> > NTFS
    > >> >> > file system when using or installing upon large partitions using x64
    > >> >> > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    > >> >> > (CHKDSK) of the volumes does not work, unless I boot to an x86
    > >> >> > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    > >> >> >
    > >> >> > Anyone else see this behavior, or know why I'm experiencing this
    > >> >> > headache?
    > >> >> >
    > >> >> > -----------------------------------
    > >> >> >
    > >> >> > Layout of my paritions as follows:
    > >> >> >
    > >> >> > Disk 0 - ICH9R (RAID10) VOL0
    > >> >> > - Volume 0 - Primary Partition (active) 40GB, system partition
    > >> >> > - Extended Logical Partition (none)
    > >> >> > Disk 1 - ICH9R (RAID10) VOL1
    > >> >> > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    > >> >> > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    > >> >> > - Primary Partition 813GB (x64 Windows Vista SP1)
    > >> >> > - Extended Logical Partition (none)
    > >> >> > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > >> >> > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    > >> >> > - Primary Partition 40GB (x64 Windows Vista SP1)
    > >> >> > - Extended Logical Partition (none)
    > >> >> > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > >> >> > - Primary Partition (active) 698GB
    > >> >> > - Extended Logical Partition (none)
    > >> >> >
    > >> >> > Volumes susceptible to corruption: the 813GB and 698GB volumes
    > >> >> >
    > >> >> > All HDDs SATA
    > >> >> > DVD on JMB363 PATA port
    > >> >> >
    > >> >> > ICH9R RAID status is normal (healthy mode, not degraded)
    > >> >> > JMB363 RAID capable, but only AHCI features used
    > >> >> >
    > >> >> > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    > >> >> > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    > >> >> >
    > >> >> > All OS'es are bootable (last install was x64 Vista SP1)
    > >> >> > -----------------------------------
    > >> >> >
    > >> >> > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    > >> >> > CPU: Intel Q6600 Quad Core
    > >> >> > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst
    > >> >> > Drivers.
    > >> >> > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    > >> >> > Mobo: DFI LP UT P35-T2R
    > >> >> > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    > >> >> > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    > >> >> > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure,
    > >> >> > eSATA)
    > >> >> > Raid: ICH9R 4xHDD RAID10 = 1TB
    > >> >> > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE
    > >> >> > mode)
    > >> >> > DVD: HP DVD Writer 1040r (IDE)
    > >> >> >
    > >> >>
    > >> >>
    > >>
    > >>

    >
    >
     
    Carlos, Aug 5, 2008
    #11
  12. UncleVic

    UncleVic Guest

    I have tried the latest Intel 8.2.0.1001 (6/2/2008) driver, but it didn't
    seem to change anything. The condition is most likely to happen when I must
    do a hard reset while the machine is is up. In that scenario, restart to
    either x64 Vista SP1 or x64 Windows Server 2008 will automatically attempt a
    CHKDSK (which seems to run through, with just a few fixes reported); but the
    next restart will always continue this automatic CHKDSK procedure--it never
    really gets fixed, it seems--until I restart to an x86 O/S like Windows
    Server 2003 or Windows XP.

    On the JMicron (JMB363) side of things, I attempted install of x64 Vista SP1
    to the 698GB partition, and it seemed to go well at first, but quickly became
    unstable after application of Windows Update patches. And this was when it
    was running in IDE mode (not RAID) so no special driver was needed. Once
    corruption set in, the machine repeated the behavior outlined in the previous
    paragraph. With failure in two different environments (one with ICH9R RAID,
    another with just IDE), the common denominator seemed to be that the boot
    partitions were particularly large. Something sure seems flakey with x64
    here.

    "Carlos" wrote:

    > Hi,
    > I would start by installing the latest drivers.
    > Jmicron
    > ftp://driver.jmicron.com.tw/jmb36x
    > Intel ICH9R
    > http://downloadcenter.intel.com/fil...dows Vista* 64&lang=eng&strOSs=150&submit=Go!
    > Carlos
    >
    > "UncleVic" wrote:
    >
    > > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    > > SERVER 2008.
    > >
    > > On my multi-boot development server, I'm seeing corruption of my NTFS
    > > file system when using or installing upon large partitions using x64
    > > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    > > (CHKDSK) of the volumes does not work, unless I boot to an x86
    > > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    > >
    > > Anyone else see this behavior, or know why I'm experiencing this
    > > headache?
    > >
    > > -----------------------------------
    > >
    > > Layout of my paritions as follows:
    > >
    > > Disk 0 - ICH9R (RAID10) VOL0
    > > - Volume 0 - Primary Partition (active) 40GB, system partition
    > > - Extended Logical Partition (none)
    > > Disk 1 - ICH9R (RAID10) VOL1
    > > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    > > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    > > - Primary Partition 813GB (x64 Windows Vista SP1)
    > > - Extended Logical Partition (none)
    > > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    > > - Primary Partition 40GB (x64 Windows Vista SP1)
    > > - Extended Logical Partition (none)
    > > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > > - Primary Partition (active) 698GB
    > > - Extended Logical Partition (none)
    > >
    > > Volumes susceptible to corruption: the 813GB and 698GB volumes
    > >
    > > All HDDs SATA
    > > DVD on JMB363 PATA port
    > >
    > > ICH9R RAID status is normal (healthy mode, not degraded)
    > > JMB363 RAID capable, but only AHCI features used
    > >
    > > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    > > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    > >
    > > All OS'es are bootable (last install was x64 Vista SP1)
    > > -----------------------------------
    > >
    > > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    > > CPU: Intel Q6600 Quad Core
    > > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst Drivers.
    > > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    > > Mobo: DFI LP UT P35-T2R
    > > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    > > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    > > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure, eSATA)
    > > Raid: ICH9R 4xHDD RAID10 = 1TB
    > > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE mode)
    > > DVD: HP DVD Writer 1040r (IDE)
    > >
     
    UncleVic, Aug 5, 2008
    #12
  13. UncleVic

    UncleVic Guest

    I've also seen the behavior as described in your link below. Occasionally, a
    partition will fail to mount in the normal read+write mode, and I typically
    use the "Safely Remove Hardware" option in the system tray to remove the
    drive, then reboot to fix it. So far, this has only happened on the HDDs
    attached to the JMicron controller.

    JMicron's FTP download site has release notes on various recent releases
    that deal wth changes in how it should handle so-called removable SATA/eSATA
    drives; I'm thinking that they haven't yet worked out all the kinks.

    "Carlos" wrote:

    > Charlie,
    > Here's the technet forum reference I mentioned:
    > http://forums.microsoft.com/technet...5&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=2
    > Greg Knight from Microsoft (not an MVP) says:
    > "I think the issue lies in how we're mounting the filesystem - about 5% of
    > the remounts leave the volume in "read-only" mode. I suspect that the system
    > volume is immune due to a necessarily different mounting procedure. The
    > appearance of "randomly" going into this state could be explained by the
    > system dismounting the volume after a brief period of disuse or a flush, for
    > power or data integrity reasons; I am not immediately familiar with this
    > component so I cannot speak with certainty on it.
    > I'm filing a bug and will try to have this addressed in Vista SP2; I do not
    > think we will package a fix for this before then, I'm sorry to say."
    >
    > :)
    > Carlos
    >
    > "Charlie Russel - MVP" wrote:
    >
    > > Well, I'd say it's a driver bug, not a Vista bug from your description.
    > > Though apparently one not surfaced until Vista SP1.
    > >
    > > --
    > > Charlie.
    > > "Carlos" <> wrote in message
    > > news:...
    > > > Charlie,
    > > > I have also found an unresolved funny thing with jmicron based RAID
    > > > partitions.
    > > > Randomly after a reboot a partition (but not the boot one) may start in
    > > > read-only mode not allowing you to modify or write anything there.
    > > > This happens in Vista x64 SP1 and seems to be a Vista bug.
    > > > Workaround is to use the fsutil command in an elevated window to unmount
    > > > the
    > > > problematic partition without rebooting. On the next access to that
    > > > partition
    > > > things should be normal again.
    > > > :)
    > > > Carlos
    > > >
    > > >
    > > > "Charlie Russel - MVP" wrote:
    > > >
    > > >> Carlos is pointing you in the right direction. I've seen reports of
    > > >> issues
    > > >> with Intel based RAID controllers and large file movements. Updating the
    > > >> BIOS for the controller, and making sure you have the latest drivers, is
    > > >> the
    > > >> right way to go.
    > > >>
    > > >> FWIW, I've run partitions of up to 2 GB without issue on Server 2k8 x64.
    > > >>
    > > >> The other thing you might consider is using GPT for those larger volumes.
    > > >> You can't use it for the boot volume, but the other two could easily be
    > > >> converted to GPT. And it's a better way to go for really large volumes.
    > > >>
    > > >> --
    > > >> Charlie.
    > > >> "UncleVic" <> wrote in message
    > > >> news:...
    > > >> > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    > > >> > SERVER 2008.
    > > >> >
    > > >> > On my multi-boot development server, I'm seeing corruption of my NTFS
    > > >> > file system when using or installing upon large partitions using x64
    > > >> > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    > > >> > (CHKDSK) of the volumes does not work, unless I boot to an x86
    > > >> > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    > > >> >
    > > >> > Anyone else see this behavior, or know why I'm experiencing this
    > > >> > headache?
    > > >> >
    > > >> > -----------------------------------
    > > >> >
    > > >> > Layout of my paritions as follows:
    > > >> >
    > > >> > Disk 0 - ICH9R (RAID10) VOL0
    > > >> > - Volume 0 - Primary Partition (active) 40GB, system partition
    > > >> > - Extended Logical Partition (none)
    > > >> > Disk 1 - ICH9R (RAID10) VOL1
    > > >> > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    > > >> > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    > > >> > - Primary Partition 813GB (x64 Windows Vista SP1)
    > > >> > - Extended Logical Partition (none)
    > > >> > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > > >> > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    > > >> > - Primary Partition 40GB (x64 Windows Vista SP1)
    > > >> > - Extended Logical Partition (none)
    > > >> > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > > >> > - Primary Partition (active) 698GB
    > > >> > - Extended Logical Partition (none)
    > > >> >
    > > >> > Volumes susceptible to corruption: the 813GB and 698GB volumes
    > > >> >
    > > >> > All HDDs SATA
    > > >> > DVD on JMB363 PATA port
    > > >> >
    > > >> > ICH9R RAID status is normal (healthy mode, not degraded)
    > > >> > JMB363 RAID capable, but only AHCI features used
    > > >> >
    > > >> > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    > > >> > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    > > >> >
    > > >> > All OS'es are bootable (last install was x64 Vista SP1)
    > > >> > -----------------------------------
    > > >> >
    > > >> > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    > > >> > CPU: Intel Q6600 Quad Core
    > > >> > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst Drivers.
    > > >> > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    > > >> > Mobo: DFI LP UT P35-T2R
    > > >> > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    > > >> > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    > > >> > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure, eSATA)
    > > >> > Raid: ICH9R 4xHDD RAID10 = 1TB
    > > >> > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE mode)
    > > >> > DVD: HP DVD Writer 1040r (IDE)
    > > >> >
    > > >>
    > > >>

    > >
    > >
     
    UncleVic, Aug 5, 2008
    #13
  14. LOL.

    Not what I would have said, certainly. And I seem to recall some corruption
    issues with their drivers a while back as well. ;-)

    But IAC, I suspect the need for updated firmware, at a minimum, with the
    ICHR controllers.

    --
    Charlie.
    http://msmvps.com/blogs/xperts64
    http://mvp.support.microsoft.com/profile/charlie.russel


    "Carlos" <> wrote in message
    news:...
    > NVidia controllers rock!!!
    > :))))))
    >
    > "Charlie Russel - MVP" wrote:
    >
    >> I'd still say it's a driver bug - since it doesn't exist except with
    >> certain
    >> hardware and drivers. The problem seems to me to be one that I certainly
    >> don't see on any of my hardware here, but then I never thought much of
    >> Intel
    >> RAID controllers and have avoided them over the years.
    >>
    >> --
    >> Charlie.
    >> http://msmvps.com/blogs/xperts64
    >> http://mvp.support.microsoft.com/profile/charlie.russel
    >>
    >>
    >> "Carlos" <> wrote in message
    >> news:...
    >> > Charlie,
    >> > Here's the technet forum reference I mentioned:
    >> > http://forums.microsoft.com/technet...5&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=2
    >> > Greg Knight from Microsoft (not an MVP) says:
    >> > "I think the issue lies in how we're mounting the filesystem - about 5%
    >> > of
    >> > the remounts leave the volume in "read-only" mode. I suspect that the
    >> > system
    >> > volume is immune due to a necessarily different mounting procedure. The
    >> > appearance of "randomly" going into this state could be explained by
    >> > the
    >> > system dismounting the volume after a brief period of disuse or a
    >> > flush,
    >> > for
    >> > power or data integrity reasons; I am not immediately familiar with
    >> > this
    >> > component so I cannot speak with certainty on it.
    >> > I'm filing a bug and will try to have this addressed in Vista SP2; I do
    >> > not
    >> > think we will package a fix for this before then, I'm sorry to say."
    >> >
    >> > :)
    >> > Carlos
    >> >
    >> > "Charlie Russel - MVP" wrote:
    >> >
    >> >> Well, I'd say it's a driver bug, not a Vista bug from your
    >> >> description.
    >> >> Though apparently one not surfaced until Vista SP1.
    >> >>
    >> >> --
    >> >> Charlie.
    >> >> "Carlos" <> wrote in message
    >> >> news:...
    >> >> > Charlie,
    >> >> > I have also found an unresolved funny thing with jmicron based RAID
    >> >> > partitions.
    >> >> > Randomly after a reboot a partition (but not the boot one) may start
    >> >> > in
    >> >> > read-only mode not allowing you to modify or write anything there.
    >> >> > This happens in Vista x64 SP1 and seems to be a Vista bug.
    >> >> > Workaround is to use the fsutil command in an elevated window to
    >> >> > unmount
    >> >> > the
    >> >> > problematic partition without rebooting. On the next access to that
    >> >> > partition
    >> >> > things should be normal again.
    >> >> > :)
    >> >> > Carlos
    >> >> >
    >> >> >
    >> >> > "Charlie Russel - MVP" wrote:
    >> >> >
    >> >> >> Carlos is pointing you in the right direction. I've seen reports of
    >> >> >> issues
    >> >> >> with Intel based RAID controllers and large file movements.
    >> >> >> Updating
    >> >> >> the
    >> >> >> BIOS for the controller, and making sure you have the latest
    >> >> >> drivers,
    >> >> >> is
    >> >> >> the
    >> >> >> right way to go.
    >> >> >>
    >> >> >> FWIW, I've run partitions of up to 2 GB without issue on Server 2k8
    >> >> >> x64.
    >> >> >>
    >> >> >> The other thing you might consider is using GPT for those larger
    >> >> >> volumes.
    >> >> >> You can't use it for the boot volume, but the other two could
    >> >> >> easily
    >> >> >> be
    >> >> >> converted to GPT. And it's a better way to go for really large
    >> >> >> volumes.
    >> >> >>
    >> >> >> --
    >> >> >> Charlie.
    >> >> >> "UncleVic" <> wrote in message
    >> >> >> news:...
    >> >> >> > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    >> >> >> > SERVER 2008.
    >> >> >> >
    >> >> >> > On my multi-boot development server, I'm seeing corruption of my
    >> >> >> > NTFS
    >> >> >> > file system when using or installing upon large partitions using
    >> >> >> > x64
    >> >> >> > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior).
    >> >> >> > Repair
    >> >> >> > (CHKDSK) of the volumes does not work, unless I boot to an x86
    >> >> >> > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    >> >> >> >
    >> >> >> > Anyone else see this behavior, or know why I'm experiencing this
    >> >> >> > headache?
    >> >> >> >
    >> >> >> > -----------------------------------
    >> >> >> >
    >> >> >> > Layout of my paritions as follows:
    >> >> >> >
    >> >> >> > Disk 0 - ICH9R (RAID10) VOL0
    >> >> >> > - Volume 0 - Primary Partition (active) 40GB, system partition
    >> >> >> > - Extended Logical Partition (none)
    >> >> >> > Disk 1 - ICH9R (RAID10) VOL1
    >> >> >> > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    >> >> >> > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    >> >> >> > - Primary Partition 813GB (x64 Windows Vista SP1)
    >> >> >> > - Extended Logical Partition (none)
    >> >> >> > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    >> >> >> > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    >> >> >> > - Primary Partition 40GB (x64 Windows Vista SP1)
    >> >> >> > - Extended Logical Partition (none)
    >> >> >> > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    >> >> >> > - Primary Partition (active) 698GB
    >> >> >> > - Extended Logical Partition (none)
    >> >> >> >
    >> >> >> > Volumes susceptible to corruption: the 813GB and 698GB volumes
    >> >> >> >
    >> >> >> > All HDDs SATA
    >> >> >> > DVD on JMB363 PATA port
    >> >> >> >
    >> >> >> > ICH9R RAID status is normal (healthy mode, not degraded)
    >> >> >> > JMB363 RAID capable, but only AHCI features used
    >> >> >> >
    >> >> >> > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    >> >> >> > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    >> >> >> >
    >> >> >> > All OS'es are bootable (last install was x64 Vista SP1)
    >> >> >> > -----------------------------------
    >> >> >> >
    >> >> >> > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64
    >> >> >> > SP1
    >> >> >> > CPU: Intel Q6600 Quad Core
    >> >> >> > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst
    >> >> >> > Drivers.
    >> >> >> > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    >> >> >> > Mobo: DFI LP UT P35-T2R
    >> >> >> > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    >> >> >> > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    >> >> >> > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure,
    >> >> >> > eSATA)
    >> >> >> > Raid: ICH9R 4xHDD RAID10 = 1TB
    >> >> >> > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE
    >> >> >> > mode)
    >> >> >> > DVD: HP DVD Writer 1040r (IDE)
    >> >> >> >
    >> >> >>
    >> >> >>
    >> >>
    >> >>

    >>
    >>
     
    Charlie Russel - MVP, Aug 5, 2008
    #14
  15. UncleVic

    Carlos Guest

    Hi,
    No need to reboot when you have the "jmicron read only" virus.
    Close all open Explorer Windows.
    Open an elevated command prompt and type:
    C:\path\to\anywhere> fsutil volume dismount h:

    (replace "h:" with the appropriate drive letter.)
    Next time you open that partition in Windows explorer, things should be
    normal.
    Sometimes I have to run the command twice.
    Carlos

    "UncleVic" wrote:

    > I've also seen the behavior as described in your link below. Occasionally, a
    > partition will fail to mount in the normal read+write mode, and I typically
    > use the "Safely Remove Hardware" option in the system tray to remove the
    > drive, then reboot to fix it. So far, this has only happened on the HDDs
    > attached to the JMicron controller.
    >
    > JMicron's FTP download site has release notes on various recent releases
    > that deal wth changes in how it should handle so-called removable SATA/eSATA
    > drives; I'm thinking that they haven't yet worked out all the kinks.
    >
    > "Carlos" wrote:
    >
    > > Charlie,
    > > Here's the technet forum reference I mentioned:
    > > http://forums.microsoft.com/technet...5&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=2
    > > Greg Knight from Microsoft (not an MVP) says:
    > > "I think the issue lies in how we're mounting the filesystem - about 5% of
    > > the remounts leave the volume in "read-only" mode. I suspect that the system
    > > volume is immune due to a necessarily different mounting procedure. The
    > > appearance of "randomly" going into this state could be explained by the
    > > system dismounting the volume after a brief period of disuse or a flush, for
    > > power or data integrity reasons; I am not immediately familiar with this
    > > component so I cannot speak with certainty on it.
    > > I'm filing a bug and will try to have this addressed in Vista SP2; I do not
    > > think we will package a fix for this before then, I'm sorry to say."
    > >
    > > :)
    > > Carlos
    > >
    > > "Charlie Russel - MVP" wrote:
    > >
    > > > Well, I'd say it's a driver bug, not a Vista bug from your description.
    > > > Though apparently one not surfaced until Vista SP1.
    > > >
    > > > --
    > > > Charlie.
    > > > "Carlos" <> wrote in message
    > > > news:...
    > > > > Charlie,
    > > > > I have also found an unresolved funny thing with jmicron based RAID
    > > > > partitions.
    > > > > Randomly after a reboot a partition (but not the boot one) may start in
    > > > > read-only mode not allowing you to modify or write anything there.
    > > > > This happens in Vista x64 SP1 and seems to be a Vista bug.
    > > > > Workaround is to use the fsutil command in an elevated window to unmount
    > > > > the
    > > > > problematic partition without rebooting. On the next access to that
    > > > > partition
    > > > > things should be normal again.
    > > > > :)
    > > > > Carlos
    > > > >
    > > > >
    > > > > "Charlie Russel - MVP" wrote:
    > > > >
    > > > >> Carlos is pointing you in the right direction. I've seen reports of
    > > > >> issues
    > > > >> with Intel based RAID controllers and large file movements. Updating the
    > > > >> BIOS for the controller, and making sure you have the latest drivers, is
    > > > >> the
    > > > >> right way to go.
    > > > >>
    > > > >> FWIW, I've run partitions of up to 2 GB without issue on Server 2k8 x64.
    > > > >>
    > > > >> The other thing you might consider is using GPT for those larger volumes.
    > > > >> You can't use it for the boot volume, but the other two could easily be
    > > > >> converted to GPT. And it's a better way to go for really large volumes.
    > > > >>
    > > > >> --
    > > > >> Charlie.
    > > > >> "UncleVic" <> wrote in message
    > > > >> news:...
    > > > >> > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    > > > >> > SERVER 2008.
    > > > >> >
    > > > >> > On my multi-boot development server, I'm seeing corruption of my NTFS
    > > > >> > file system when using or installing upon large partitions using x64
    > > > >> > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    > > > >> > (CHKDSK) of the volumes does not work, unless I boot to an x86
    > > > >> > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    > > > >> >
    > > > >> > Anyone else see this behavior, or know why I'm experiencing this
    > > > >> > headache?
    > > > >> >
    > > > >> > -----------------------------------
    > > > >> >
    > > > >> > Layout of my paritions as follows:
    > > > >> >
    > > > >> > Disk 0 - ICH9R (RAID10) VOL0
    > > > >> > - Volume 0 - Primary Partition (active) 40GB, system partition
    > > > >> > - Extended Logical Partition (none)
    > > > >> > Disk 1 - ICH9R (RAID10) VOL1
    > > > >> > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    > > > >> > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    > > > >> > - Primary Partition 813GB (x64 Windows Vista SP1)
    > > > >> > - Extended Logical Partition (none)
    > > > >> > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > > > >> > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    > > > >> > - Primary Partition 40GB (x64 Windows Vista SP1)
    > > > >> > - Extended Logical Partition (none)
    > > > >> > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > > > >> > - Primary Partition (active) 698GB
    > > > >> > - Extended Logical Partition (none)
    > > > >> >
    > > > >> > Volumes susceptible to corruption: the 813GB and 698GB volumes
    > > > >> >
    > > > >> > All HDDs SATA
    > > > >> > DVD on JMB363 PATA port
    > > > >> >
    > > > >> > ICH9R RAID status is normal (healthy mode, not degraded)
    > > > >> > JMB363 RAID capable, but only AHCI features used
    > > > >> >
    > > > >> > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    > > > >> > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    > > > >> >
    > > > >> > All OS'es are bootable (last install was x64 Vista SP1)
    > > > >> > -----------------------------------
    > > > >> >
    > > > >> > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    > > > >> > CPU: Intel Q6600 Quad Core
    > > > >> > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst Drivers.
    > > > >> > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    > > > >> > Mobo: DFI LP UT P35-T2R
    > > > >> > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    > > > >> > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    > > > >> > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure, eSATA)
    > > > >> > Raid: ICH9R 4xHDD RAID10 = 1TB
    > > > >> > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE mode)
    > > > >> > DVD: HP DVD Writer 1040r (IDE)
    > > > >> >
    > > > >>
    > > > >>
    > > >
    > > >
     
    Carlos, Aug 6, 2008
    #15
  16. Thanks for the heads up on the iTunes problem but unfortunatly its not to
    blame as I dont have it installed.

    Robert

    "Kerry Brown" <*a*m> wrote in message
    news:...
    > Do you run iTunes? ITunes and Intel RAID have had problems for a while.
    >
    > http://www.google.com/search?hl=en&q=itunes intel raid&meta=
    >
    > --
    > Kerry Brown
    > MS-MVP - Windows Desktop Experience: Systems Administration
    > http://www.vistahelp.ca/phpBB2/
    > http://vistahelpca.blogspot.com/
    >
    >
    > "Robert McMillan" <> wrote in message
    > news:...
    >>I use Vista Business x64 and have also noticed corruption issues though
    >>not of the entire volume, only with large archive and iso files that I
    >>know woked fine but now give errors. I am on the latest drivers and also
    >>with the Intel ICH9R Raid controller. I have noticed it in both 1TB raid 0
    >>and 750GB raid 1 arrays.
    >>
    >> OS: Vista Business x64 SP1
    >> CPU: Intel Q6600 Quad Core
    >> Video: Gigabyte 8800GTS 512MB
    >> Mobo: Gigabyte P35-DS4
    >> Mem: 8GB 4x2GB PNYatriot Viper PC2-8500, 5-5-5-15)
    >> Disks: 3 x WD 500GB SATA2 16Mb cache
    >> 2 x Samsung 750GB SATA2 16Mb cache
    >>
    >> "UncleVic" <> wrote in message
    >> news:...
    >>> ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    >>> SERVER 2008.
    >>>
    >>> On my multi-boot development server, I'm seeing corruption of my NTFS
    >>> file system when using or installing upon large partitions using x64
    >>> Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    >>> (CHKDSK) of the volumes does not work, unless I boot to an x86
    >>> edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    >>>
    >>> Anyone else see this behavior, or know why I'm experiencing this
    >>> headache?
    >>>
    >>> -----------------------------------
    >>>
    >>> Layout of my paritions as follows:
    >>>
    >>> Disk 0 - ICH9R (RAID10) VOL0
    >>> - Volume 0 - Primary Partition (active) 40GB, system partition
    >>> - Extended Logical Partition (none)
    >>> Disk 1 - ICH9R (RAID10) VOL1
    >>> - Primary Partition (active) 40GB (x64 Windows Server 2008)
    >>> - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    >>> - Primary Partition 813GB (x64 Windows Vista SP1)
    >>> - Extended Logical Partition (none)
    >>> Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    >>> - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    >>> - Primary Partition 40GB (x64 Windows Vista SP1)
    >>> - Extended Logical Partition (none)
    >>> Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    >>> - Primary Partition (active) 698GB
    >>> - Extended Logical Partition (none)
    >>>
    >>> Volumes susceptible to corruption: the 813GB and 698GB volumes
    >>>
    >>> All HDDs SATA
    >>> DVD on JMB363 PATA port
    >>>
    >>> ICH9R RAID status is normal (healthy mode, not degraded)
    >>> JMB363 RAID capable, but only AHCI features used
    >>>
    >>> Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    >>> JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    >>>
    >>> All OS'es are bootable (last install was x64 Vista SP1)
    >>> -----------------------------------
    >>>
    >>> OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    >>> CPU: Intel Q6600 Quad Core
    >>> Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst Drivers.
    >>> NIC: Marvell 88E8052 Gigabyte LAN PCIe
    >>> Mobo: DFI LP UT P35-T2R
    >>> Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    >>> Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    >>> ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure, eSATA)
    >>> Raid: ICH9R 4xHDD RAID10 = 1TB
    >>> Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE mode)
    >>> DVD: HP DVD Writer 1040r (IDE)
    >>>

    >>

    >
     
    Robert McMillan, Aug 6, 2008
    #16
  17. UncleVic

    UncleVic Guest

    It seems that this issue has affected others, since Feb 2008. I just
    located an article on
    http://www.vistax64.com/vista-hardware-devices/133770-my-disk-getting-corrupt-all-time.html
    titled "My disk is geting corrupt all the time", with no apparent
    resolution. Anybody else experiencing this?


    "Charlie Russel - MVP" wrote:

    > Carlos is pointing you in the right direction. I've seen reports of issues
    > with Intel based RAID controllers and large file movements. Updating the
    > BIOS for the controller, and making sure you have the latest drivers, is the
    > right way to go.
    >
    > FWIW, I've run partitions of up to 2 GB without issue on Server 2k8 x64.
    >
    > The other thing you might consider is using GPT for those larger volumes.
    > You can't use it for the boot volume, but the other two could easily be
    > converted to GPT. And it's a better way to go for really large volumes.
    >
    > --
    > Charlie.
    > "UncleVic" <> wrote in message
    > news:...
    > > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    > > SERVER 2008.
    > >
    > > On my multi-boot development server, I'm seeing corruption of my NTFS
    > > file system when using or installing upon large partitions using x64
    > > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    > > (CHKDSK) of the volumes does not work, unless I boot to an x86
    > > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    > >
    > > Anyone else see this behavior, or know why I'm experiencing this
    > > headache?
    > >
    > > -----------------------------------
    > >
    > > Layout of my paritions as follows:
    > >
    > > Disk 0 - ICH9R (RAID10) VOL0
    > > - Volume 0 - Primary Partition (active) 40GB, system partition
    > > - Extended Logical Partition (none)
    > > Disk 1 - ICH9R (RAID10) VOL1
    > > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    > > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    > > - Primary Partition 813GB (x64 Windows Vista SP1)
    > > - Extended Logical Partition (none)
    > > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    > > - Primary Partition 40GB (x64 Windows Vista SP1)
    > > - Extended Logical Partition (none)
    > > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > > - Primary Partition (active) 698GB
    > > - Extended Logical Partition (none)
    > >
    > > Volumes susceptible to corruption: the 813GB and 698GB volumes
    > >
    > > All HDDs SATA
    > > DVD on JMB363 PATA port
    > >
    > > ICH9R RAID status is normal (healthy mode, not degraded)
    > > JMB363 RAID capable, but only AHCI features used
    > >
    > > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    > > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    > >
    > > All OS'es are bootable (last install was x64 Vista SP1)
    > > -----------------------------------
    > >
    > > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    > > CPU: Intel Q6600 Quad Core
    > > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst Drivers.
    > > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    > > Mobo: DFI LP UT P35-T2R
    > > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    > > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    > > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure, eSATA)
    > > Raid: ICH9R 4xHDD RAID10 = 1TB
    > > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE mode)
    > > DVD: HP DVD Writer 1040r (IDE)
    > >

    >
    >
     
    UncleVic, Aug 6, 2008
    #17
  18. UncleVic

    UncleVic Guest

    At the moment, I AM running the JMicron drivers (Jraid.sys), because
    I want the full AHCI features (NCQ, hot swap) available. This also
    requires that my mobo be setup with "RAID+IDE" mode for the
    JMicron controller. I've seem some impressive performance with
    my SATA and eSATA drives, using this feature.

    The controller also features "Native IDE" mode, which I under-
    stand means that I should be able to use just the standard
    IDE drivers built-in to the distribution; I just won't get advanced
    performance features.

    I'm wondering though, I've set cache policies on both JMicron-
    connected SATA drives to "Enable write caching on the disk"
    CHECKED and "Enable advanced performance" UNCHECKED.
    The current policies are UNCHECKED for both volumes on the
    ICH9R RAIDsets. Could these be the reason that preboot
    CHKDSK cannot work right?


    "N Brown" wrote:
    >
    > "UncleVic" <> wrote in message
    > news:...
    > >I have tried the latest Intel 8.2.0.1001 (6/2/2008) driver, but it didn't
    > > seem to change anything. The condition is most likely to happen when I
    > > must
    > > do a hard reset while the machine is is up. In that scenario, restart to
    > > either x64 Vista SP1 or x64 Windows Server 2008 will automatically attempt
    > > a
    > > CHKDSK (which seems to run through, with just a few fixes reported); but
    > > the
    > > next restart will always continue this automatic CHKDSK procedure--it
    > > never
    > > really gets fixed, it seems--until I restart to an x86 O/S like Windows
    > > Server 2003 or Windows XP.
    > >
    > > On the JMicron (JMB363) side of things, I attempted install of x64 Vista
    > > SP1
    > > to the 698GB partition, and it seemed to go well at first, but quickly
    > > became
    > > unstable after application of Windows Update patches. And this was when
    > > it
    > > was running in IDE mode (not RAID) so no special driver was needed. Once
    > > corruption set in, the machine repeated the behavior outlined in the
    > > previous
    > > paragraph. With failure in two different environments (one with ICH9R
    > > RAID,
    > > another with just IDE), the common denominator seemed to be that the boot
    > > partitions were particularly large. Something sure seems flakey with x64
    > > here.
    > >
    > > "Carlos" wrote:

    >
    > Jmicron drivers DO need to be installed for IDE mode. If your not installing
    > them that may be the trouble.
    >
    > N Brown
    >
    > >> Hi,
    > >> I would start by installing the latest drivers.
    > >> Jmicron
    > >> ftp://driver.jmicron.com.tw/jmb36x
    > >> Intel ICH9R
    > >> http://downloadcenter.intel.com/fil...dows Vista* 64&lang=eng&strOSs=150&submit=Go!
    > >> Carlos
    > >>
    > >> "UncleVic" wrote:
    > >>
    > >> > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    > >> > SERVER 2008.
    > >> >
    > >> > On my multi-boot development server, I'm seeing corruption of my NTFS
    > >> > file system when using or installing upon large partitions using x64
    > >> > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    > >> > (CHKDSK) of the volumes does not work, unless I boot to an x86
    > >> > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    > >> >
    > >> > Anyone else see this behavior, or know why I'm experiencing this
    > >> > headache?
    > >> >
    > >> > -----------------------------------
    > >> >
    > >> > Layout of my paritions as follows:
    > >> >
    > >> > Disk 0 - ICH9R (RAID10) VOL0
    > >> > - Volume 0 - Primary Partition (active) 40GB, system partition
    > >> > - Extended Logical Partition (none)
    > >> > Disk 1 - ICH9R (RAID10) VOL1
    > >> > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    > >> > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    > >> > - Primary Partition 813GB (x64 Windows Vista SP1)
    > >> > - Extended Logical Partition (none)
    > >> > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > >> > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    > >> > - Primary Partition 40GB (x64 Windows Vista SP1)
    > >> > - Extended Logical Partition (none)
    > >> > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > >> > - Primary Partition (active) 698GB
    > >> > - Extended Logical Partition (none)
    > >> >
    > >> > Volumes susceptible to corruption: the 813GB and 698GB volumes
    > >> >
    > >> > All HDDs SATA
    > >> > DVD on JMB363 PATA port
    > >> >
    > >> > ICH9R RAID status is normal (healthy mode, not degraded)
    > >> > JMB363 RAID capable, but only AHCI features used
    > >> >
    > >> > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    > >> > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    > >> >
    > >> > All OS'es are bootable (last install was x64 Vista SP1)
    > >> > -----------------------------------
    > >> >
    > >> > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    > >> > CPU: Intel Q6600 Quad Core
    > >> > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst Drivers.
    > >> > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    > >> > Mobo: DFI LP UT P35-T2R
    > >> > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    > >> > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    > >> > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure, eSATA)
    > >> > Raid: ICH9R 4xHDD RAID10 = 1TB
    > >> > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE mode)
    > >> > DVD: HP DVD Writer 1040r (IDE)
    > >> >

    >
     
    UncleVic, Aug 6, 2008
    #18
  19. UncleVic

    N Brown Guest

    My Jmicron controller on Asus P5K will NOT recognize HDD drives or
    optical drives without the driver installed.
    I only use for 2 optical drives because when I had my primary partition
    setup on it in Vista my sound was skipping occasionaly on my
    X-Fi Elite Pro. It wasn't resolved a month ago but I haven't checked
    lately. Asus probably put a basterized version of the controller.


    "UncleVic" <> wrote in message
    news:...
    > At the moment, I AM running the JMicron drivers (Jraid.sys), because
    > I want the full AHCI features (NCQ, hot swap) available. This also
    > requires that my mobo be setup with "RAID+IDE" mode for the
    > JMicron controller. I've seem some impressive performance with
    > my SATA and eSATA drives, using this feature.
    >
    > The controller also features "Native IDE" mode, which I under-
    > stand means that I should be able to use just the standard
    > IDE drivers built-in to the distribution; I just won't get advanced
    > performance features.
    >
    > I'm wondering though, I've set cache policies on both JMicron-
    > connected SATA drives to "Enable write caching on the disk"
    > CHECKED and "Enable advanced performance" UNCHECKED.
    > The current policies are UNCHECKED for both volumes on the
    > ICH9R RAIDsets. Could these be the reason that preboot
    > CHKDSK cannot work right?
    >
    >
    > "N Brown" wrote:
    >>
    >> "UncleVic" <> wrote in message
    >> news:...
    >> >I have tried the latest Intel 8.2.0.1001 (6/2/2008) driver, but it
    >> >didn't
    >> > seem to change anything. The condition is most likely to happen when I
    >> > must
    >> > do a hard reset while the machine is is up. In that scenario, restart
    >> > to
    >> > either x64 Vista SP1 or x64 Windows Server 2008 will automatically
    >> > attempt
    >> > a
    >> > CHKDSK (which seems to run through, with just a few fixes reported);
    >> > but
    >> > the
    >> > next restart will always continue this automatic CHKDSK procedure--it
    >> > never
    >> > really gets fixed, it seems--until I restart to an x86 O/S like Windows
    >> > Server 2003 or Windows XP.
    >> >
    >> > On the JMicron (JMB363) side of things, I attempted install of x64
    >> > Vista
    >> > SP1
    >> > to the 698GB partition, and it seemed to go well at first, but quickly
    >> > became
    >> > unstable after application of Windows Update patches. And this was
    >> > when
    >> > it
    >> > was running in IDE mode (not RAID) so no special driver was needed.
    >> > Once
    >> > corruption set in, the machine repeated the behavior outlined in the
    >> > previous
    >> > paragraph. With failure in two different environments (one with ICH9R
    >> > RAID,
    >> > another with just IDE), the common denominator seemed to be that the
    >> > boot
    >> > partitions were particularly large. Something sure seems flakey with
    >> > x64
    >> > here.
    >> >
    >> > "Carlos" wrote:

    >>
    >> Jmicron drivers DO need to be installed for IDE mode. If your not
    >> installing
    >> them that may be the trouble.
    >>
    >> N Brown
    >>
    >> >> Hi,
    >> >> I would start by installing the latest drivers.
    >> >> Jmicron
    >> >> ftp://driver.jmicron.com.tw/jmb36x
    >> >> Intel ICH9R
    >> >> http://downloadcenter.intel.com/fil...dows Vista* 64&lang=eng&strOSs=150&submit=Go!
    >> >> Carlos
    >> >>
    >> >> "UncleVic" wrote:
    >> >>
    >> >> > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    >> >> > SERVER 2008.
    >> >> >
    >> >> > On my multi-boot development server, I'm seeing corruption of my
    >> >> > NTFS
    >> >> > file system when using or installing upon large partitions using x64
    >> >> > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    >> >> > (CHKDSK) of the volumes does not work, unless I boot to an x86
    >> >> > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    >> >> >
    >> >> > Anyone else see this behavior, or know why I'm experiencing this
    >> >> > headache?
    >> >> >
    >> >> > -----------------------------------
    >> >> >
    >> >> > Layout of my paritions as follows:
    >> >> >
    >> >> > Disk 0 - ICH9R (RAID10) VOL0
    >> >> > - Volume 0 - Primary Partition (active) 40GB, system partition
    >> >> > - Extended Logical Partition (none)
    >> >> > Disk 1 - ICH9R (RAID10) VOL1
    >> >> > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    >> >> > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    >> >> > - Primary Partition 813GB (x64 Windows Vista SP1)
    >> >> > - Extended Logical Partition (none)
    >> >> > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    >> >> > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    >> >> > - Primary Partition 40GB (x64 Windows Vista SP1)
    >> >> > - Extended Logical Partition (none)
    >> >> > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    >> >> > - Primary Partition (active) 698GB
    >> >> > - Extended Logical Partition (none)
    >> >> >
    >> >> > Volumes susceptible to corruption: the 813GB and 698GB volumes
    >> >> >
    >> >> > All HDDs SATA
    >> >> > DVD on JMB363 PATA port
    >> >> >
    >> >> > ICH9R RAID status is normal (healthy mode, not degraded)
    >> >> > JMB363 RAID capable, but only AHCI features used
    >> >> >
    >> >> > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    >> >> > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    >> >> >
    >> >> > All OS'es are bootable (last install was x64 Vista SP1)
    >> >> > -----------------------------------
    >> >> >
    >> >> > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    >> >> > CPU: Intel Q6600 Quad Core
    >> >> > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst
    >> >> > Drivers.
    >> >> > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    >> >> > Mobo: DFI LP UT P35-T2R
    >> >> > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    >> >> > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    >> >> > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure,
    >> >> > eSATA)
    >> >> > Raid: ICH9R 4xHDD RAID10 = 1TB
    >> >> > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE
    >> >> > mode)
    >> >> > DVD: HP DVD Writer 1040r (IDE)
    >> >> >

    >>
     
    N Brown, Aug 6, 2008
    #19
  20. UncleVic

    Carlos Guest

    Unchecked is the way to go if you are forcing those hard resets.
    Write caching is what it says: delayed writes. If you hard reset before the
    writing gets done, you will have errors.
    Enable advanced performance assumes that you have an UPS backing up
    everything.
    Carlos

    "UncleVic" wrote:

    > At the moment, I AM running the JMicron drivers (Jraid.sys), because
    > I want the full AHCI features (NCQ, hot swap) available. This also
    > requires that my mobo be setup with "RAID+IDE" mode for the
    > JMicron controller. I've seem some impressive performance with
    > my SATA and eSATA drives, using this feature.
    >
    > The controller also features "Native IDE" mode, which I under-
    > stand means that I should be able to use just the standard
    > IDE drivers built-in to the distribution; I just won't get advanced
    > performance features.
    >
    > I'm wondering though, I've set cache policies on both JMicron-
    > connected SATA drives to "Enable write caching on the disk"
    > CHECKED and "Enable advanced performance" UNCHECKED.
    > The current policies are UNCHECKED for both volumes on the
    > ICH9R RAIDsets. Could these be the reason that preboot
    > CHKDSK cannot work right?
    >
    >
    > "N Brown" wrote:
    > >
    > > "UncleVic" <> wrote in message
    > > news:...
    > > >I have tried the latest Intel 8.2.0.1001 (6/2/2008) driver, but it didn't
    > > > seem to change anything. The condition is most likely to happen when I
    > > > must
    > > > do a hard reset while the machine is is up. In that scenario, restart to
    > > > either x64 Vista SP1 or x64 Windows Server 2008 will automatically attempt
    > > > a
    > > > CHKDSK (which seems to run through, with just a few fixes reported); but
    > > > the
    > > > next restart will always continue this automatic CHKDSK procedure--it
    > > > never
    > > > really gets fixed, it seems--until I restart to an x86 O/S like Windows
    > > > Server 2003 or Windows XP.
    > > >
    > > > On the JMicron (JMB363) side of things, I attempted install of x64 Vista
    > > > SP1
    > > > to the 698GB partition, and it seemed to go well at first, but quickly
    > > > became
    > > > unstable after application of Windows Update patches. And this was when
    > > > it
    > > > was running in IDE mode (not RAID) so no special driver was needed. Once
    > > > corruption set in, the machine repeated the behavior outlined in the
    > > > previous
    > > > paragraph. With failure in two different environments (one with ICH9R
    > > > RAID,
    > > > another with just IDE), the common denominator seemed to be that the boot
    > > > partitions were particularly large. Something sure seems flakey with x64
    > > > here.
    > > >
    > > > "Carlos" wrote:

    > >
    > > Jmicron drivers DO need to be installed for IDE mode. If your not installing
    > > them that may be the trouble.
    > >
    > > N Brown
    > >
    > > >> Hi,
    > > >> I would start by installing the latest drivers.
    > > >> Jmicron
    > > >> ftp://driver.jmicron.com.tw/jmb36x
    > > >> Intel ICH9R
    > > >> http://downloadcenter.intel.com/fil...dows Vista* 64&lang=eng&strOSs=150&submit=Go!
    > > >> Carlos
    > > >>
    > > >> "UncleVic" wrote:
    > > >>
    > > >> > ISSUE AFFECTS ONLY x64 EDITIONS OF WINDOWS VISTA SP1 OR WINDOWS
    > > >> > SERVER 2008.
    > > >> >
    > > >> > On my multi-boot development server, I'm seeing corruption of my NTFS
    > > >> > file system when using or installing upon large partitions using x64
    > > >> > Vista SP1 (or x64 Windows Server 2008 SP1, same behavior). Repair
    > > >> > (CHKDSK) of the volumes does not work, unless I boot to an x86
    > > >> > edition O/S like Windows Server 2003 SP2 or Windows XP SP3.
    > > >> >
    > > >> > Anyone else see this behavior, or know why I'm experiencing this
    > > >> > headache?
    > > >> >
    > > >> > -----------------------------------
    > > >> >
    > > >> > Layout of my paritions as follows:
    > > >> >
    > > >> > Disk 0 - ICH9R (RAID10) VOL0
    > > >> > - Volume 0 - Primary Partition (active) 40GB, system partition
    > > >> > - Extended Logical Partition (none)
    > > >> > Disk 1 - ICH9R (RAID10) VOL1
    > > >> > - Primary Partition (active) 40GB (x64 Windows Server 2008)
    > > >> > - Primary Partition 40GB (x86 Windows Server 2003 SP2)
    > > >> > - Primary Partition 813GB (x64 Windows Vista SP1)
    > > >> > - Extended Logical Partition (none)
    > > >> > Disk 2 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > > >> > - Primary Partition (active) 40GB (x64 Windows Server 2003 SP2)
    > > >> > - Primary Partition 40GB (x64 Windows Vista SP1)
    > > >> > - Extended Logical Partition (none)
    > > >> > Disk 3 - JMB363 (RAID mode, SATA, AHCI, non-RAID config)
    > > >> > - Primary Partition (active) 698GB
    > > >> > - Extended Logical Partition (none)
    > > >> >
    > > >> > Volumes susceptible to corruption: the 813GB and 698GB volumes
    > > >> >
    > > >> > All HDDs SATA
    > > >> > DVD on JMB363 PATA port
    > > >> >
    > > >> > ICH9R RAID status is normal (healthy mode, not degraded)
    > > >> > JMB363 RAID capable, but only AHCI features used
    > > >> >
    > > >> > Microsoft driver for ICH9R controller (iaStorV.sys, 6.2.0.1019)
    > > >> > JMicron driver for JMB363 controller (Jraid.sys, 1.17.38.5)
    > > >> >
    > > >> > All OS'es are bootable (last install was x64 Vista SP1)
    > > >> > -----------------------------------
    > > >> >
    > > >> > OS: WinXP SP3 x86, Win2003 SP2 x64 & x86, Win2008 x64, Vista x64 SP1
    > > >> > CPU: Intel Q6600 Quad Core
    > > >> > Video: ATI HD 3450 PCIe with 512MB, with latest ATI Catalyst Drivers.
    > > >> > NIC: Marvell 88E8052 Gigabyte LAN PCIe
    > > >> > Mobo: DFI LP UT P35-T2R
    > > >> > Mem: 8GB (4x2GB Patriot Viper PC2-8500, 5-5-5-15)
    > > >> > Disks: 5 x WD 5001ABYS Caviar RE2, 500 GB each;
    > > >> > ...and Samsung Spinpoint F1 HD753LJ, 750GB (external enclosure, eSATA)
    > > >> > Raid: ICH9R 4xHDD RAID10 = 1TB
    > > >> > Other HDD: non-RAID config on JMicron SATA (running in RAID+IDE mode)
    > > >> > DVD: HP DVD Writer 1040r (IDE)
    > > >> >

    > >
     
    Carlos, Aug 6, 2008
    #20
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. dennis

    pwer off corrupts boot disk (pavilion xt938)

    dennis, Apr 17, 2004, in forum: Computer Information
    Replies:
    4
    Views:
    945
    dennis
    Apr 18, 2004
  2. Mr. G D Geen

    Vista corrupts RAW images

    Mr. G D Geen, Sep 7, 2007, in forum: Digital Photography
    Replies:
    10
    Views:
    479
    Thomas T. Veldhouse
    Sep 11, 2007
  3. Fabio Martins

    Is there MCSA on Win2008?

    Fabio Martins, Apr 20, 2008, in forum: Microsoft Certification
    Replies:
    5
    Views:
    428
    John R
    Apr 24, 2008
  4. Russell
    Replies:
    1
    Views:
    1,421
    Russell
    Aug 12, 2009
  5. Turtle

    Basic volumes and dynamic volumes

    Turtle, Aug 6, 2010, in forum: Windows 64bit
    Replies:
    6
    Views:
    837
    Charlie Russel-MVP
    Aug 6, 2010
Loading...

Share This Page