SATA II Issues with 2004 G5

I'm replacing the original 250 GB Hard Drive in my Single 1.8 GHz G5 (Purchased in 2004). I've narrowed down my choice to a 250 GB Western Digital Caviar SE16 or 500 GB Maxtor MaxLine Pro, which are both SATA II .
I wanted to know if either drive would have an issue working in my G5 because they are SATA II. I haven't been able to find a clear answer to this question in other posts so I figured I would ask before I purchased either drive.
Steve
Power Mac G5 Single 1.8 Mac OS X (10.4.9)

I too would go with the Maxtor drive. Check out the drive compatibility database at http://forums.xlr8yourmac.com/drivedb/search.drivedb.lasso to see other users experience with the drive s your considering. That said SATA II drives work fine in older G5's, they'll just work at SATA I speed. Because of that backward compatibility SATA I drives are getting next to impossible to find.

Similar Messages

SATA Disks Issues with OEL 5.8 uek 64Bit

Hi Oracle Linux Experts/Tech Gurus!,
We are facing lot of issues with SATA disks at both Internal and External,
if we use any SATA USB External Disk it make server hang and sometimes restart
We face this issues with external SATA ARRAY connected at DS-3400
1. Files under this SATA disk partition is gone.
2. Disk free space not release after deleted files
3. Server got hang and restarted many times
4. Disk IO Performance is very slow
(hdparm -t result 70MB/secs earlier it was 130MB/secs with RHEL32)
This issues we are facing with this SATA disk array on SAN DS-3400 connected via QLA2460 Qlogic 4G Fiber HBA Card.
We are not faced any issues before with RHEL32Bit OS on this same HW Setup, once we changed to OEL5.8 64
Please help us to fix this issue with SATA Disks on this OEL 5.8.
Thanks & Regards,
Prabhakar.D
Edited by: dpprabhuindia on May 14, 2013 7:08 PM

And here is the output of scli -i (SANSurfer cli tool)
~]# scli -i
Host Name : xxxxxxxx
HBA Instance : 0
HBA Model : QLA2460
HBA Description : QLA2460 PCI-X 2.0 to 4Gb FC Single Channel
HBA ID : 0-QLA2460
HBA Alias :
HBA Port : 1
Port Alias :
Node Name : 20-00-00-E0-8B-8B-25-F8
Port Name : 21-00-00-E0-8B-8B-25-F8
Port ID : 61-09-13
Serial Number : GFC0640H84421
Driver Version : 8.03.07.08.32.1-k
BIOS Version : 1.12
Driver Firmware Version : 5.03.13 (496)
Flash BIOS Version : 1.12
Flash FCode Version : 1.16
Flash EFI Version : 1.04
Flash Firmware Version : 4.00.18
Actual Connection Mode : Point to Point
Actual Data Rate : 4 Gbps
PortType (Topology) : NPort
Target Count : 1
PCI Bus Number : 6
PCI Device Number : 1
HBA Status : Online
Host Name : xxxxxxxxxxxxx
HBA Instance : 1
HBA Model : QLA2460
HBA Description : QLA2460 PCI-X 2.0 to 4Gb FC Single Channel
HBA ID : 1-QLA2460
HBA Alias :
HBA Port : 1
Port Alias :
Node Name : 20-00-00-E0-8B-92-FB-B6
Port Name : 21-00-00-E0-8B-92-FB-B6
Port ID : 61-0B-13
Serial Number : RFC0641M26491
Driver Version : 8.03.07.08.32.1-k
BIOS Version : 1.12
Driver Firmware Version : 5.03.13 (496)
Flash BIOS Version : 1.12
Flash FCode Version : 1.16
Flash EFI Version : 1.04
Flash Firmware Version : 4.00.18
Actual Connection Mode : Point to Point
Actual Data Rate : 4 Gbps
PortType (Topology) : NPort
Target Count : 1
PCI Bus Number : 10
PCI Device Number : 1
HBA Status : Online
Please advice how to upgrade firmware for this HBA Card
Edited by: dpprabhuindia on May 14, 2013 7:14 PM

K8T Neo2 issues with 2004/9/24 Bios

Hi there.
I´ve upgraded my k8T Neo2 with the 2004/9/24 an am having now stability issues with my FX 53 due to inproper fan speed control.
I have no clue how the fan control works in this Mobo because my observations are really strange. The CPU is now always reaching 70 C and more under load and the fan control seems not to be able to get it keeped cooler. Tried several CPU coolers but it´s always the same.
If my case is closed, the fan control seems to work and is incrasing the RPMs of my coolers, but having the case opened the RPMs stay at the same level like on Idle.
However, in both situations the temperature is growing up to 70C and more which results in instabilities at this high temps.
So before you ask me. I´ve of course upgraded to the latest Core Center too, but it´s the same if it´s either loaded or not, so it´s the Bios if you ask me.
Also, had not these troubles with the previous Bios.
All I can say now is that the fan speed isn´t regulated by the CPU temperatutre but something else and it´s not calibrated to support hotter running FX CPUs, though the previous Bios obviously was.
Last but not least, Cool´n Quiet is also working now under Win2k, but the Legacy USB support isn´t completely fixed.
I can´t boot neither Win2k nor WInXP with it enabled.

The system was set up last week, so everything is up to date, also the AMD drivers.
However, the Bios date code is in the topic header (2004/9/24).
It was updated yesterday and since then the CPU isn´t cooled correctly, neither with the Boxed Cooler, nor a Thermaltake Silent Boost or a Zalman CNPS-7000B. No matter the case is closed or opened.
There is also no problem with the Cool´n Quiet driver or the Cool´n Quiet support anymore. There was just a problem under Win2k and the Bios the Mobo came with, but that´s fixed now with the newest Bios, exept the fan control that is working now incorrectly.
Don´t remember right now the date code of the previous Bios, but it was the first release and there the fan control worked correctly, so my Athlon 64 FX 53 didn´t heat up as much as now and got no stability problems, simply because it was always kept below the 70ties.
I don´t think the rest of my rig is of any importance because connecting the coolers to an other surce than the CPU FAN Header and so running them at full speed, doesn´t cause my CPU to become unstable as it doesn´t reach this high temperatures.
That´s the only problem I´m having now. Everything else is rock stable and up to date.
What´s about the Leagcy USB support not allowing me to boot the OS´s, I can live with that though it would be nice to get that fixed too.
So to be more specific. With the previous Bios the fan control kicked in earlier, way before the temperature reached 70C. Now it kicks in much later. Somwhere in the middle of the 70ties. To late for my FX 53.
So to speak with the previous Bios the fan control kicked in before the CPU reached the critical temperature and incrased the RPMs at least so far, that the CPU was cooled down to the 60ies. Now it´s just keeping the temperature at the reached level (73-74C ).
All I want is to get this fixed or even better to add an option into the Bios to select the temperature where the fan control kicks in and incrases the fan speed to keep the CPU temperature at the level you selected.

Few issues with BI 2004s

Hello there,
I am having few issues with BI 2004s system. Its a new implementation.
-         When you create Data source using DB connect in new system, it creates with old version. I could see the SMALL square box next to the Data source. I would expect the system to generate new 2004s datasource.
-         Obviously the generated D/S wont allow us to create New Transformations. We have to create old transfer rules/update rule. I do see the option to migrate the D/S when I right click on it. But I get short dump when I try that and then you have to discard the D/S and create new one.
-         Also, it wont allow you to delete the DBConnect D/S although you have option to do that?
Anyone has faced these issues?
Performance issue with reporting:
I understand that you have to have portal in order to execute reports which we dont have at this client. They dont have time and money to invest right now. So we have created reports using BW 3.5 BEx Q.designer/WAD to run the reports on web. The report takes long time when you try to drill down on Material/Customer with only 150,000 records in Cube. The cube has just three dimensions (two char each) and 4 key figures. Any suggestion to improve?
Thanks
Sudhakar

Yes, I noticed it too and was thinking the same thing, blueaura.
I'm sure they want to ensure the scan is reliable. I keep my screen at a lower brightness to save power, and sometimes Starbucks scanners take a bit longer for it to register.
2) is already fixed.
3) is a feature, not a bug. If you are updating an app you already have installed, it doesn't bother to ask you for the password. Nice!
For Google maps, just use maps.google.com in the browser.

Issue with Variants in 2004s

Hi BW Gurus,
We recently upgraded our system from 3.5 and 2004s and we are having issues with variants.
Issue1.
Variants created by one user is not visible by other users
Issue2.
Variants created for workbook is not saved.
Anyone encountered these issues ?
Rgds
Chan

Issue 1:
We created a program that converts the variant from local to global periodically.
This program was provided by sap which was modified and scheduled in the background.
REPORT Z_2004S_VARIANT_PERS_2_GLOBAL.
*& Report Z_2004S_VARIANT_PERS_2_GLOBAL
type-pools:
rs.
parameters:
2global radiobutton group gr1 default 'X',
2person radiobutton group gr1.
selection-screen uline /1(83).
parameters:
p_query like rsrrepdir-genuniid memory id gid,
p_varnt2 like rsrparametrizat-txtlg memory id zid.
data:
ls_rsrparametriza type rsrparametriza,
l_compid type rsrrepdir-compid,
l_appname type string,
l_apptype type rsappcompnm value '01',
lt_catalog type rsr_t_para_catalog,
lt_return type table of ddshretval,
ls_return type ddshretval,
l_paramnm type rsrparametriza-paramnm,
l_message type string.
F4 Help for parameters
at selection-screen on value-request for p_query.
call function 'RZ_QUERY_F4_GET'            "3.x
    exporting
      i_objtype = 'QU'
    importing
      e_genuniid = p_query.
set parameter id 'GID' field p_query.
at selection-screen on value-request for p_varnt2.
get parameter id 'GID' field p_query.
select single compid from rsrrepdir into l_compid
         where objvers   = rs_c_objvers-active
         and    genuniid = p_query.
l_appname = l_compid.
call method cl_rsr_para=>get_catalog
    exporting
      i_type      = l_apptype
      i_appnm     = l_appname
    receiving
      r_t_catalog = lt_catalog.
call function 'F4IF_INT_TABLE_VALUE_REQUEST'
    exporting
      ddic_structure = space
      retfield        = 'PARAMNM'
      value_org       = 'S'
    tables
      value_tab       = lt_catalog
      return_tab      = lt_return
    exceptions
      parameter_error = 1
      no_values_found = 2
      others          = 3.
read table lt_return into ls_return index 1.
select single txtlg from rsrparametrizat into p_varnt2
         where langu    = sy-langu
         and    paramnm = ls_return-fieldval
         and    objvers = rs_c_objvers-active.
export ls_return-fieldval to memory id 'PARAMNM'.
if p_varnt2 is not initial.
    set parameter id 'ZID' field p_varnt2.
endif.
start-of-selection.
import ls_return-fieldval from memory id 'PARAMNM'.
l_paramnm = ls_return-fieldval.
select single * from rsrparametriza into ls_rsrparametriza
         where paramnm = l_paramnm
         and    objvers = rs_c_objvers-active.
if 2global eq rs_c_true.
    clear ls_rsrparametriza-personal.
elseif 2person eq rs_c_true.
    if ls_rsrparametriza-owner eq sy-uname.
      ls_rsrparametriza-personal = rs_c_true.
    ELSE.
      l_message = 'You cannot make another users variant personal!'.
      message l_message type 'E'.
    endif.
endif.
update rsrparametriza from ls_rsrparametriza.
if sy-subrc eq 0.
    concatenate 'Variant' p_varnt2 'was converted successfully!' into
l_message
      separated by space.
    message l_message type 'S'.
else.
    l_message = 'Error during conversion!'.
    message l_message type 'E'.
endif.
commit work.
Issue 2:
SAP has to release the note yet.
Rgds
Dinesh

Sata issues with k8n-fsr

Hi list!
I have serious issues with my sata drive on my K8N Neo-FSR.
The SATA drive is connected on the SATA3 controller, and an IDE DVD is connected as master on IDE channel 1. The DVD is detected by the BIOS and can be booted...
BUT, the SATA hard drive is not detected by the BIOS, and so neither by WinXP or Linux installers...
I tried loads of configurations settings in the BIOS like SATA3/4 Enabled, RAID IDE enabled, ... Boot priority options do not show the HD...
Please help!!!!!!!
Here is my config:
MSI K8N Neo-FSR (NVIDIA nForce3 250Gb)
Hitachi 160 Go 7200 RPM 8 Mo Serial ATA (bulk)
Sapphire Radeon 9800 Pro
NEC ND-3500 - DVD(+/-)RW

hi zorloc,
looking at size of your new drives are they the new ncq capable seagates, in which case it may be a compatability issue. Maxtor 10 series users have had similar issues.
Try updating bios to the new officiial v1.5 which has Raid v4.6 & may be better for these drives.
You'd also be best upgrading to the latest Nvidia 5.1 drivers .
Other than this Try & see if any of the fixes that worked for the Maxtor users work for you.
see Maxtor 16Mb Cache HDDs & Neo2 Problems there are several more member €ric had some success at end of included thread.
Edit: This may also be of interest Ech a fellow Neo 754 user has had a long stuggle trying to get his maxtor 10 to work Updated Neo BIOS to fix Maxtor 16Mb problem?
luck

I have Snow Leopard 10.6 and I am having issues with M/S Word 2004 and G-mail. I can only open docs sent to me in g-mail on google doc?

Is there a compatability issue with Microsoft Word 2004 and Snow Leopard or is it G-Mail? I am using Safari with a G-mail account.

Will upgrading to 2011 correct my issue that I can not open a pdf or word doc in G-mail or could it be a g-mail setting? I can open these docs outside of G-mail, but I am also having issues sending them without the docs becoming slightly modified enroute.

Anyone have issues with Sata 3 SSD in the 2011 Macbook Pro

Hi Guys and Gals.
Does anyone have issues with the Macbook Pro 2011 Model with a Sata3 Solid State Drive ?
I have issues and have a Vertex3 made by OCZ. I am in active discussions with OCZ to find a resolution on their end. I have also contacted Apple Care and Intel and have run into dead ends.
However I am bringing my MBP for a repair, logic board replacement and will post the results after they change the logic board for me.
Check my thread on OCZ: http://www.ocztechnologyforum.com/forum/showthread.php?89970-A-call-to-all-Macbo ok-Pro-2011-Users-with-SATA3-Issues
Regards,
Jase

Well, my My Genius appointment went very much as anticipated - it might well be a SATA III connection but Apple they do not support SATA III drives - least of all other people's.
Furthermore, they do not actually support anything other than the original configuration as sold - so given that I bought a 750 GB HD version, that is what I am stuck with - I asked Apple (London Regent St) if they could upgrade it to one of their own SSDs if I paid for it - they could not. They can only repair the machine to its original condition. They could not even advise me as to what Apple co-branded SSD I should look for to be compatible with this model - 512 Gb drives do come up on Ebay - Apple / Toshiba seems to be the normal one - but they couldn't advise if that would work or not. So it could be good money after bad.
Anyhow, they finally agreed to swap the cable, for a charge, so that will take two or thee days, plus the 5mins to do the job. I will post the results of the cable swap when I have it. They could not tell me whether it would be a different version of the SATA cable to the one already in the machine - but I asked to keep the old one so I can see if there is any visible difference.
It does seem strange that Apple support thunderbolt drives - which you can't even buy yet, but don't support SATA III in either Mac Pro or MAcBook Pro given that the full 3.0 standard was released on May 27, 2009.
Two and a bit years is a long time in tech terms.
Stephen
eni wrote:
I, as so many others, are also facing issues with my SATA 3 SSD. I've been reading about people having issues on OCZ's forum, on Intel's forum and all over the web. I have a MBP 2011 13" bought last month with the 6/6 setup.
Hotjase, have you come to understand that the issue lies with the logic board? One would hope that Apple would owe up and come forward if there are in fact faulty logic borards. I have read that Apple have gone from 6/3 to 6/6 and then back to 6/3, though I do not know if this is applicable to all MBP models, or just some. As I sayed, I have the 13" model.
SdeS, what was the result of your talk with the Genius? Did you receive a new cable? If so what result?

Compatibility issues with Mac OSX Leopard 10.5 and Word 2004 11.6.3 on G5 PowerMac?

Are there compatibility issues with Mac OSX Leopard V. 10.5 and Word 2004 11.6.3 when installed on a PowerMac G5? I understand the Leopard upgrade is okay on the later Intel Mac, but what about my G5 PowerPC Mac?

I do not use Microsoft Excel much but when i do use it it works fine on my G5. my powerbook has excel to but sometimes freezes on the powerbook. but not the G5 so give it a try you can always uninstall it if it does not work good
anitabean wrote:
Thanks so much for your positive reply! Are you a big user of Excel? That's where I've heard people have had trouble, with cells locking up and so on.
Crossing my fingers and loading Leopard....
Cheers.

MSI K8T Neo2 issue with SATA drives....

I have a K8T Neo2 motherboard, with a 3700+ San Diego core, running Windows XP Service Pack 2. I don't have the version with the Promise SATA Raid - using the VIA SATA RAID. I am using the latest BIOS (according to the Live Monitor).
The machine was set up (the OS installed) on an IDE 40 gig drive. All was fine, but I noticed that my machine lagged at times (mostly games, under heavy disk load) so I decided to get a couple of Seagate 250 gig drives (they have NCQ, which I know is not supported by this MB, but they were on sale, and I'd read that the drive should still work ok).
I attached the drives, and enabled SATA in the bios. The machine boots fine. I created a single 500 gig striped array using the two new drives. Windows XP sees the array fine, but that I have to initialize it.
Every time I initialize it I get an error that says, "An error has occured" and tells me to check the event log (nothing there), and to either restart the Disk Manager or reboot my computer. The OS actually locks up a few times when I'm doing this (the mouse-cursor freezes).
I've tried using the disks as two single disks, same error (and it reported that they were only 137 gig each, though apparently it's a registry issue, and I used a util to change that setting, but I haven't tested to see if it changed anything.).
I got the latest VIA SATA drives from the MSI site, and installed them (though honestly, WindowsXP saw the card and the drives just fine). One weird thing is that the VIA SATA RAID is listed under SCSI devices in the Device Manager - there is no SATA category in there.
I'm at a loss here. I've searched the web, and this forum, without luck.
Any advice would be appreciated.
*Edit* I just unplugged two IDE disk drives from the computer, and when I started it up again, it found a Promise SATA Raid controller. I thought that wasn't included with the basic version of the board?
David.

Ok - thanks - I read through the stickies and updated my bios tonight to 9.20 (the latest).
Had some dry-mouth moments when WindowsXP decided to "discover" every piece of hardware I had, right down to the mouse, and again when core-center rebooted my computer.
Also, there was some time where my memory (OCZ 2-3-3-6 DDR3200) was being set to CAS2.5, which was kind of weird, but it fixed itself.
Unfort, I am unable to increase my FSB/HTT speed past about 205 before my computer does a reboot.
I have an ATI video card (X800 Plat Ed), and I'd read that some other people had issues with ATI card and the AGP-lock, so I got the CG-ICS950405 clock-gen, and it does state that my AGP is running at 66 (and PCI 33).
Going to bump up my settings via clockgen as soon as I post this (want to post before it potentially crashes).
Should I roll back to the 9.10 bios? Not a lot of discussion on the 9.2, and I'm wondering if it causes some issues.
Thanks again for all the help and info. I used to have a firm grasp on all the components of a system, way back in the P3 days, but things have changed quite a bit...
**EDIT**
Seems to be a Core-Center issue. Used ClockGen to o/c to 2600, with temp nice and low. Will run like this for a bit. Does Core-Center work with a 9.X bios?
I think all my problems are solved - copied a wack of files to my SATA drives, and there were no issues. I won't trust Live Monitor again for drivers or bios - it's still stuck way back at 3.30.
I'll pass the info I've learned off whenever I can.
Comments and criticisms welcome.
David.
Quote from: Puppetman on 26-September-05, 23:23:42
I looked at the motherboard page - they recommend 3.30 unless you have having issues (which I kind of guess I am). Funny that Live Monitor won't pick up those BIOS changes - wonder what else I'm missing.
So 9.1 fixes the AGP/HTT overclocking issue?
The stickies are great - thanks.
David.

P35 Neo2-FR issues with Pioneer DVR-212 SATA ODD on Intel ICH9R

I need some help here, guys, as I am having weirdest issues with Pioneer DVR-212 on my mobo. Everything else is working fine - 4GB Geil DDRII 800, C2D 4600, P35 Neo2-FR, stock settings. I allready updated the bios to the lates revision - 1.8 and drive's firmware to 1.24 - and it does not help.
Basically, drive just locks up and stops responding during writing or even reading a DVD when it's connected to Intel SATA. Tried ImgBurn, Nero, InfraRecorder - same issue happens in Linux, too. When connected to Marvell SATA port - drive behave better and at least this lock up issues stop.
Drive is currently connected to SATA 5 port (1 and 2 are ESATA, 3 and 4 are HDD's and they have 0 issues, 5 is burner - tested other ports and 6 is empty). Drive just stops to respond. In BIOS, Inte l controller is in AHCI mode, but I disabled the port on which Pioneer is - as I read that optical drives have issues with AHCI. Drive is visible in Vista (32 bit SP1) but locking issues happen all the time. Are there some known issues with my motherboard and it's SATA controler? Or issues with this particular drive? Or maybe issues with AHCI mode? I repeat, this lock up issues go away when I connect it to Marvel SATA port - although I don't have the feeling it's working properly, it appears to be working with almost zero issues. I had a lock even now, while writing this - on 32% on reading an image... The rig is prime stable 24h, and works without restarting for weeks. This is the only issue - no issues with hard drives (SEAGATE 320 Barracuda 7200.10 3320620AS and a Maxtor 160GB STM3160811AS). Any help or ideas appreciated!!!

Yes - here are details...
MSI P35 NEO2-FR v1.1 bios 1.8
Intel Core2Duo [email protected] - stock
XFX Nvidia Geforce 8600gt
GEIL Ultra 4x1 GB DDR800 - stock
Seagate Barracuda 320GB ST3320620AS SATA
Maxtor DiamondMax 160GB STM3160811AS SATA
Pioneer DVR-212 SATA firmware 1.24
Chieftec PSU 410W
Cooler Master CM690 Case
Windows Vista 32bit SP1 + Ubuntu 8.04 64 bit (with 2.6.25 hand compiled kernel)
What bugs me the most is that I can't find similar issues on the net - very, very few issues solved by setting the AHCI port to which burner is connnected to non-AHCI mode and that the optical drive behaves better when connected to Marvel SATA controller, rather then Intel SATA...
Issues repeats in Linux and in Windows...
Any thoughts appreciated...

Z77A-G43 issue with SATA drive

This is wierd
I have 4 Hitachi drives all of 1TB, perfectly working on old PC.
Today have decided to transfer them into new PC:
MB: Z77A-G43
BIOS: 1.20
CPU: Intel g2020
Primary drive is Intel SSD 120G series 330
I have attached 3 HITACHI drives successfully, they are all working fine.
but particular one forces MB to reboot before BIOS screen, last code seen on screen is A2?
Then I have decided to put dedicated controller 1st I took SilImage 3512 SATA/RAID Controller
- no changes computer reboots before post screen
After I took VIA VT6421 SATA/RAID Controller
- no changes computer reboots before post screen
searched web, found nothing useful.
any ideas what might causing this?
EDIT: tested controller SiI3512 on old PC and trouble HDD, everything works just fine :/
read AMIBIOS codes:
0xA0 IDE initialization is started
0xA1 IDE Reset
0xA2 IDE Detect
0xA3 IDE Enable
0xA4 SCSI initialization is started
0xA5 SCSI Reset
0xA6 SCSI Detect
0xA7 SCSI Enable
0xA8 Setup Verifying Password
A2 is ide ? what ide ? I give up.
it seams to me that this board is broken in several ways
- non working DVI
- faulting with valid SATA drive
what else awaits me on this road

Quote from: flobelix on 07-May-13, 04:27:27
using IDE previously and now AHCI might trouble Windows but system would none the less post. At least you should get past IDE detection but hanging at A2 means it doesn't.
I'm wondering about your statement you had been using SilImage 3512 SATA/RAID Controller and VIA VT6421 SATA/RAID Controller. Are these PCI add-on cards? Did you try all SATA ports controlled by the Z77 chipset. Are the drives used are all identical? Is the issue only happening with one particular drive or anytime you attach a fourth hdd no matter which one it is?
About the performance difference from AHCI to IDE the differences are minimal. Should be almost irrelevant for the hdds.
My discoveries:
Using sata mode IDE with windows installed in AHCI mode == windows hangs during loading (BSOD), probably missing drivers or similar.
Also I am unsure what A2 code means but I have noticed it is displayed while bios post screen shows up with the list of installed drives during normal boot.
And is also last code I see when I attach problematic drive resulting in reboot loop.
To be honest I haven't tried all SATA ports on board for sure I haven't tried SATA 1 (1st white) as there is my SSD drive.
But I have tried almost all other ports. I can try them all, but I don't think this will solve the problem.
I don't think problem is in what slot I put my drive, since same behavior is with SATA/RAID controllers.
And whit this SATA/RAID controllers this drive is working perfectly normal on other PC.
No not all drives are identical but I have exactly same drive as this one, and all drives are hitachi:
* HDT721010KLA330 working fine
* HDS721010SLA360 working fine
* HDS721010CLA332 (1) working fine
* HDS721010CLA332 (2) problematic drive == reboot loop (when its single drive or with others).
True I haven't tried to detach Intel SSD and leave problematic drive as only drive in system, I may try this tomorrow)
funny part is that HDS721010CLA332 (2) is working fine when I hot plug it.
Checked firmware version on both drives, and both drives have identical firmwares.
Only difference I know off is that working drive has 1 partition, and problematic drive has 2 partitions.
EDIT: forgot to say it passed SMART test, everything was green (hitachi sw), while hdd sentinel reported 1 bad sector but saying estimated drive working days > 900 days and degree was 98% I am guessing because of that 1 bad sector and too many working days (years) behind him.

My iPad 4 says not charging but it does slowly charge . I got it replaced on sat but the new one is the same . I have tried using a different power outlet and it is the same so it appears to be an issue with the new iPad

Can anyone help .my new iPad notes not charging when it is in fact slowly charging. I had it replaced 2 days ago but the new one has the same issue.it would appear this is a common issue with ipad4.can anyone advise on how to get over this problem. .thanks

Found this thread by searching the forum. I hope it helps.
https://discussions.apple.com/thread/5471311

Microsoft Entourage 2004 issues with MacBook Pro's??

Hi all,
I only post this question, cause I have three macbook pro's at my company having the same issue, and all the other intel based macs, behaving fine.
We have been experiencing very unstable behavior with Microsoft Entourage specifically on MacBook Pros. One users loses the ability to click on anything within Entourage, until he reboots his machine. Another couple of users ran into similar issue with not being able to open entourage without error messages. Is their something specifically in the Macbook Pros that cause Entourage to run bad in the Rosetta engine? My Black Macbook works fine with Office and so does our Intel iMacs. Any ideas why these issues revolve around Macbook Pros specifically? Any other users having problems?

Hi all,
I only post this question, cause I have three macbook
pro's at my company having the same issue, and all
the other intel based macs, behaving fine.
We have been experiencing very unstable behavior with
Microsoft Entourage specifically on MacBook Pros.
One users loses the ability to click on anything
within Entourage, until he reboots his machine.
Another couple of users ran into similar issue with
not being able to open entourage without error
messages. Is their something specifically in the
Macbook Pros that cause Entourage to run bad in the
Rosetta engine? My Black Macbook works fine with
Office and so does our Intel iMacs. Any ideas why
these issues revolve around Macbook Pros
specifically? Any other users having problems?
I have seen strange behavior as well on not my MBP but my Mac Pro...
I have applied all updates.
William

2008 R2: OS(systemState/C: Drive) backup issues with VSS - 0x80042316 & 0x81080101 & 0x80080005 & 2155348001

Hi-
Looked thru the thread related to my questions and found nothing that applies yet.
Example:
http://social.technet.microsoft.com/Forums/en-US/4e4472b9-8e6f-4fdc-a287-1cc8c0f6de09/windows-2008-r2-backup-fails-with-event-521-error-code-2155348001?forum=windowsbackup
http://social.technet.microsoft.com/Forums/en-US/e8c910f7-f0dd-4613-beae-b98894fb6f23/windows-server-2008-std-backup-fails-constantly-with-error-code-2155348001?forum=windowsbackup
Here are details of the issues....
Backup - OS error - system image:
External disk - USB
Mon - Fri @ 6PM.
Windows SystemState
OS(C:)
Last backup failure...
Start time: 8/11/2014 6:01:32 PM
End time: 8/12/2014 4:51:29 AM
Duration: 10:49:56.4414784
[Critical error WINIMAGE_UNABLE_VSS] Unable to create VSS snapshot
- Additional information: Refer to the log for more details
- Troubleshooting link:
http://kb.backupassist.com/errormap.php?BA2512
The backup operation stopped before completing.
Detailed error: ERROR - The shared restore point operation failed with error (0x81000101)
The creation of a shadow copy has timed out. Try this operation again.
Log of files successfully backed up:
C:\Windows\Logs\WindowsServerBackup\Backup-12-08-2014_04-41-00.log
Log of files for which backup failed:
C:\Windows\Logs\WindowsServerBackup\Backup_Error-12-08-2014_04-41-00.log
NOTE:
The errors logs are not there?
Windows Backup timed-out before the shared protection point was created.
ERROR - The shared restore point operation failed with error (0x81000101)
The creation of a shadow copy has timed out. Try this operation again.
Event Viewer Log:
Sequence of Events...
1.
The Block Level Backup Engine service has successfully started.
2.
Backup operation that started...
Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          8/12/2014 4:51:06 AM
Event ID:      521
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      mdnfile.Auxiant.local
Description:
The backup operation that started at '?2014?-?08?-?12T09:41:00.492000000Z' has failed because the
Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed
with following error code '2155348001'.
Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
--> Suggestion are to check Virus scanner or consult DPM forum...
3.
OS Job failed with errors...( Backup Assist is 3rd party backup - wrapper round Wbadmin/Win Backup)
Log Name:      Application
Source:        BackupAssist
Date:          8/12/2014 4:51:51 AM
Event ID:      5634
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
Backup job OS backup failed with errors.
Critical error: Unable to create VSS snapshot
Destination: External disk
Start time: 8/11/2014 6:01:32 PM
End time: 8/12/2014 4:51:29 AM
Duration: 10:49:56.4414784
Destination: External disk
Start time: 8/11/2014 6:01:32 PM
End time: 8/12/2014 4:51:29 AM
Duration: 10:49:56.4414784
4.
Backup Assist reports via Win backup - Snapshot in progress
Log Name:      Application
Source:        BackupAssist
Date:          8/12/2014 4:52:20 AM
Event ID:      5634
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
Backup job Data backup failed with errors.
Ultra critical error: Volume Shadow Copy Error 0x80042316 - snapshot set in progress
Destination: Local directory
Start time: 8/12/2014 4:52:10 AM
End time: 8/12/2014 4:52:12 AM
Duration: 00:00:02.7300000
5.
The Block Level Backup Engine service has stopped.
6.
Later...we tried manually stopping VSS and SWPRV services - only VSS had the issue.
WBengine was not running...
C:\>sc stop swprv
SERVICE_NAME: swprv
        TYPE               : 10 WIN32_OWN_PROCESS
        STATE              : 3 STOP_PENDING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
C:\>sc query swprv
SERVICE_NAME: swprv
        TYPE               : 10 WIN32_OWN_PROCESS
        STATE              : 1 STOPPED
        WIN32_EXIT_CODE    : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
C:\>sc query wbengine
SERVICE_NAME: wbengine
        TYPE               : 10 WIN32_OWN_PROCESS
        STATE              : 1 STOPPED
        WIN32_EXIT_CODE    : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
C:\>sc query vss
SERVICE_NAME: vss
        TYPE               : 10 WIN32_OWN_PROCESS
        STATE              : 3 STOP_PENDING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0 (0x0)
        SERVICE_EXIT_CODE : 0 (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
C:\>sc stop vss
[SC] ControlService FAILED 1061:
The service cannot accept control messages at this time.
Log Name:      Application
Source:        VSS
Date:          8/12/2014 9:20:33 AM
Event ID:      8225
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
The VSS service is shutting down due to shutdown event from the Service Control Manager.
7.
VSS still having issues here...not stopping!
Log Name:      Application
Source:        VSS
Date:          8/12/2014 9:42:33 AM
Event ID:      11
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
Volume Shadow Copy Service information:
The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name IVssCoordinatorEx2 cannot be started.
Most likely the CPU is under heavy load. [0x80080005, Server execution failed]
8.
Not sure why this is started again?
Plus a DCOM timeout...
Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          8/12/2014 9:31:13 AM
Event ID:      753
Task Category: None
Level:         Information
Keywords:
User:          SYSTEM
Computer:      mdnfile.Auxiant.local
Description:
The Block Level Backup Engine service has successfully started.
Event Xml:
Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          8/12/2014 9:31:43 AM
Event ID:      10010
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
The server {E579AB5F-1CC4-44B4-BED9-DE0991FF0623} did not register with DCOM within the required timeout.
9.
Lots more errors about VSS...repeating Event ID's 11 and 8193...
Log Name:      Application
Source:        VSS
Date:          8/12/2014 9:42:33 AM
Event ID:      8193
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      mdnfile.Auxiant.local
Description:
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.
hr = 0x80080005, Server execution failed
. Operation:
   Instantiating VSS server
10.
Then, finally stopping again...
Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          8/12/2014 9:51:13 AM
Event ID:      754
Task Category: None
Level:         Information
Keywords:
User:          SYSTEM
Computer:      mdnfile.Auxiant.local
Description:
The Block Level Backup Engine service has stopped.
11.
And still repeating 11 & 8193 at this point...as we write up this post.
12.
This was suggested by the Backup Assist - software vendor....
A.)
...for 0x81080101:
"ERROR - The shared restore point operation failed with error (0x81000101)
The creation of a shadow copy has timed out. Try again this operation."
If you receive the above error in your report, we have recently found a registry key which
contains the timeout value set by Microsoft for VSS and found that you can edit this to extend it.
To get to the registry key, open Regedit (Start > Run > Regedit) and browse to:
"HKLM\Software\\Microsoft\\Windows NT\\CurrentVersion\\SPP\\CreateTimeout".
Change value to 1200000 (2*10*60*1000 = 20 mins).
The default for the timeout period is 10 mins so hopefully doubling this will give enough time to
complete the snapshot.
If this isn't present, you'll need to manually enter the registry key. It's a DWORD 32-bit key.
--> NOTE: HAve not done this yet.
B.)
And for 0x80080005...
http://support.microsoft.com/kb/870655/en-gb
Our server does have high CPU load at times...
13.
Another post from technet mentions system volume size - here is our layout below:
A.)
OS/system Disk...
DISKPART> list disk
Disk ### Status         Size     Free     Dyn Gpt
Disk 0    Online          278 GB      0 B    (System Vol = C: Drive - OS w/ Programs and batch jobs)
Disk 1    Online         2791 GB      0 B        *    (Data drive - DFS, rsync,etc. run on D: Drive)
Disk 2    Online         1863 GB      0 B    (USB 2/3.0 - Enclosure w/ SATA disk = 2GB formatted w/ NTFS.)
DISKPART> detail disk
DELL PERC H710P SCSI Disk Device
Disk ID: CA0DEEA5
Type   : RAID
Status : Online
Path   : 1
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0100)#PCI(0000)#RAID(P01T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : Yes
Pagefile Disk : Yes
Hibernation File Disk : No
Crashdump Disk : Yes
Clustered Disk : No
Volume ### Ltr Label        Fs     Type        Size     Status     Info
Volume 1         RECOVERY     NTFS   Partition   3072 MB Healthy    System
Volume 2     C   OS           NTFS   Partition    275 GB Healthy    Boot
B.)
Backup disk...
ST320006 41AS USB Device
Disk ID: 801AF48C
Type   : USB
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : UNAVAILABLE
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No
Volume ### Ltr Label        Fs     Type        Size     Status     Info
Volume 4     F   BACKUPS      NTFS   Partition   1863 GB Healthy
C.)
NOTE:
Also on disk 0(system Disk) - we have a small OEM partition = 39MB and a Recovery Partition = 3GB.
D.)
Issues with WBAdmin now...
C:\>wbadmin get disks
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.
ERROR - A Volume Shadow Copy Service operation error has
occurred: (0x80042302)
A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.
14.
Ran "Check-Disk" -no errors...
C:\>chkdsk
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.
Volume label is OS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
116224 file records processed.
File verification completed.
654 large file records processed.
0 bad file records processed.
0 EA records processed.
76 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
156676 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
116224 file SDs/SIDs processed.
Security descriptor verification completed.
20227 data files processed.
CHKDSK is verifying Usn Journal...
35628352 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
289233919 KB total disk space.
100241492 KB in 85477 files.
     57380 KB in 20228 indexes.
         0 KB in bad sectors.
    226627 KB in use by the system.
     65536 KB occupied by the log file.
188708420 KB available on disk.
      4096 bytes in each allocation unit.
72308479 total allocation units on disk.
47177105 allocation units available on disk.
15.
There are no backup error logs here - only .etl files...
C:\Windows\Logs\WindowsServerBackup\
Wbadmin.1.etl = 9:42AM on 8/12
Wbadmin.2.etl = 4:51AM on 8/12
Per windows Win troubleshooting:
http://technet.microsoft.com/en-us/library/ee692290(WS.10).aspx
http://blogs.technet.com/b/filecab/archive/2009/09/16/diagnosing-failures-in-windows-server-backup-part-1-vss-spp-errors.aspx
--> Related to Windows backup and not VSS?
2155348001 - 0x80780021 - Windows Backup timed-out before the shared protection point was created.
Should we run the "FIXVSS08.BAT" script - restarts services and re-registers DLL's - does this ever help?
Will this server need a reboot since VSS is in a state and we can't even test backups?
Is there a tool we can use to debug VSS or troubleshoot or OS backups further?
MSReport/Diag, VSS debugging, or another way of helping fix our OS(SystemState/C: drive) backup issues?
Any help is greatly appreciated - thx.
-SP
Scot Pichelman

Hi Scot,
Sometimes a third party backup application will change the default VSS provider adding VSS writers which causes Windows Server Backup using an incorrect component in doing backup, that's why I suggest to delete it for a test. Anyway you can reinstall it
after testing.
And as you said a high-load CPU could also be the cause of the issue so you may need to first rule hardware effective out.
If issue still exists, please try the steps below as well:
1. Please check DCOM Server Process Launcher service is started.
2. If not, try to change RPC service to run as SYSTEM account. To do this please modify the following key:
Note: Backup the key before edit incase it cause any issue.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\RpcSs\
Find "ObjectName" and change the value to LocalSystem.
Reboot to see if DCOM back to work and if Windows Server Backup starts working. If not, please provide the result if there is any new error occurs.
If DCOM still not work, please compare the content of the following key with a working server:
HKEY_LOCAL_MACHINE\Software\Microsoft\OLE
Edit if there is any difference and make sure you created a backup of the key before editing.
If you have any feedback on our support, please send to [email protected]

SATA II Issues with 2004 G5

Similar Messages

Maybe you are looking for