u/WoonMySocket

I have a Mac Pro 2010 with two boot drives and two 3TB storage drives set up as a mirrored RAID. One of the two storage drives died, so I replaced it. However, the computer suffered a hardware failure as I was rebuilding the RAID, and although I repaired the computer, I can't seem to rebuild the RAID.

When booted into Snow Leopard, Disk Utility lists the RAID as degraded, the old drive as a working slice, and the new drive as a failed slice. Trying to select the RAID or the failed slice will make Disk Utility freeze/beachball.

When booted into High Sierra, Disk Utility never advances beyond the "Loading Disks" screen.

Using the "diskutil ar repairMirror <Raid-Name> <diskNsM>" command in Terminal will update the new disk from "Failed" to "0% (Rebuilding)" only for it to return to "Failed" shortly thereafter.

Note that I can still access the data (because the RAID has one working slice) and I have everything backed up to an external drive just in case I lose everything.

I have a Mac Pro with four drives installed, a boot drive for Snow Leopard, a boot drive for High Sierra, and two 3 TB drives used for storage, configured as a mirrored RAID using Disk Utility on Snow Leopard. One of the two RAID drives failed, so I replaced it. When I tried to rebuild the RAID in Disk Utility on Snow Leopard, it said it failed. The machine itself failed shortly thereafter.

I repaired the machine, but I can't rebuild the RAID. On Snow Leopard, Disk Utility freezes the instant I try to select the RAID or its failed slice. On High Sierra, Disk Utility never advances beyond the "Loading Disks" message. The "diskutil ar repairMirror <Raid-Name> <diskNsM>" command in Terminal updates the status of the new slice from "Failed" to "0% (Rebuilding)" but after a little while it returns to "Failed."

I'm hoping this is a relatively easy issue since no data are actually lost; all data on the RAID are accessible since one slice is still functional, and everything is backed up to an external drive as well.

So I had my Mac Pro 2010 die on me quite recently. Advice suggested the capacitors had failed, so I checked them. They were fine. However, in checking them I discovered that a wad of dust had lodged onto the side of the heatsink so I removed it, and now the machine seems happier (in the sense that it now boots and runs). However, some issues remain.

Chief among them, I can't seem to rebuild my RAID. I have four drives installed, a boot drive for Snow Leopard, a boot drive for High Sierra (originally Mavericks; since updated), and two 3 TB drives used for storage, configured as a RAID using Disk Utility on Snow Leopard. One of the two RAID drives failed, so I replaced it. When I tried to rebuild the RAID in Disk Utility on Snow Leopard, it said it failed. The general failure of the machine occurred shortly thereafter.

Though the tower itself is now freshly cleaned and booted, I can't seem to rebuild the RAID. On Snow Leopard, Disk Utility freezes the instant I try to select the RAID or its failed slice. On High Sierra, Disk Utility never advances beyond the "Loading Disks" message. The "diskutil ar repairMirror <Raid-Name> <diskNsM>" command in Terminal updated the status of the new slice from "Failed" to "0% (Rebuilding)" but after 30 minutes it returned to "Failed."

Luckily, this should be easier to address than a hardware problem. Does anyone know how to rebuild this RAID? Is there any chance there's an actual problem with the new disk? Right now, the RAID is still available, all data remain accessible on the surviving slice, and I have everything backed up to an external drive just in case.

My G4 Quicksilver 2002 can't turn on due to broken power supply. Does anyone have (or know where I can find) a replacement PSU that will let me use this machine (with its ADC monitor)?

I have been reading this subreddit for quite some time and played Episode 5 the day it came out, but I didn't actually join Reddit until today, so my customary whine/rant on Episode 5 is delayed accordingly.

Episode 5 exacerbated an issue I'd always had with TLD in general, namely that Survival has no story but Wintermute is aggressively linear and video-gamey with its assigned missions and goals. Then Episode 5 does episodes-within-episodes, making the linearity worse and all but forgetting the survival elements entirely.

Jace is an incredibly irritating character and the game would have been better off without her. Atwood is also incredibly irritating. On multiple occasions, I found myself yelling at the screen: "That is not how computers work." Seriously, you have to manually update the code on your laptop? To push the data out of the buffers? Come on. You have to use fake names and keep hidden while occupying a piece of major infrastructure? Come on again.

Mathis feels like a piece of fundamentally broken writing. When writing a villain, it is imperative to explain why people work for him. Mathis has no particular survival skills, and no infrastructure of power outside of his fellow Blackrock inmates who have no reason to remain loyal to him. Wintermute as a whole could be improved greatly by rewriting Episodes 4 and 5 to remove him, but barring that, it could be improved simply by making Mathis green. Honestly, I'd forgive a lot of Mathis had the green sheen of Affliction: Aurora. Isn't the whole point that "it's affecting our minds?"

Except that my biggest gripe about Episode 5 (and easily fixed, no less) is that TLD in general has been the story of Great Bear Island. Survival Mode has amazing environmental storytelling. Everywhere you go tells the story that Great Bear Island has been ravaged by extractive industries for decades, said industries built only the bare minimum infrastructure they needed to function, by the 1980s, they were gone and let that infrastructure decay, and tourism only partially filled the gap and even then, only temporarily. Everything about TLD, from the environmental designs in Survival to the dialogue in the first three episodes of Wintermute emphasized that Great Bear Island was a place on the brink, a place that didn't require much to absolutely devastate it.

And then Episode 5 tries to make this a global apocalypse. Technology has failed the world over. Modernity as we know it is dead. The aurora wasn't the cut that killed a place that had already suffered 999, it was a single world-shaking event.

I'm pretty sure that there was no overt statement that places other than GBI were impacted by the aurora prior to Episode 5. There's scarcely any mention of the wider world anywhere in game. The story of Great Bear Island does not need to suddenly be about a global apocalypse in its final episode after the previous four (and survival mode) worked to emphasize just how isolated the place is and how little the outside world is relevant to its residents.

Were I in charge of Hinterland (or even just a very skilled modder) I would make an alternate story mode, which eschews the episodic format in favour of direct integration of story and open-world survival gameplay, and omits assigned missions and goals entirely, resulting in a version of survival mode that organically progresses through a story over time as you go. Barring that, I'd rewrite Episode 4 and 5 alike. I'm still not getting over Episode 4 asking me to murder Donner when nobody could explain what he'd actually done wrong ("in prison" isn't a crime; "he would" isn't "he did") and Episode 5 revealing him to be a bespectacled soft boy was just too on point.

I was obliged to downsize my vintage Mac collection a few years ago due to moving, but I still have:

-An iMac G3, 1998 (I think).

-An eMac 2002 (I think; it runs Jaguar)

-A PowerMac G3 Blue & White

-A PowerMac G4 Quicksilver 2002 (the dual 1 GHz version).

The Quicksilver doesn't turn on (likely due to a broken power supply). If anyone has any idea how to repair this, I'd be willing to give it a try, though my repair skills have their limit. I doubt there's anywhere I can get a new power supply (especially one that will let me continue to use my ADC monitor).

I have a Mac Pro 2010 that I have been using quite regularly for 13 years (and it was used when I got it). It is, unfortunately, now failing, and it's hard to diagnose the problem because multiple issues are stacking at the same time.

About a year ago, it would occasionally fail to start; if I pressed the power button, it would whir with some volume (sounding like the fans in high gear) and I'd need to hold the power button to shut it down and try again. It would usually start eventually.

A few weeks ago, one of the hard drives I had installed failed. This did not impede the function of the tower overall, since I had four drives (boot for Snow Leopard, boot for Mavericks, and two storage drives as a mirrored RAID; one of the two RAID slices died, so nothing was lost). I shut down the machine, ordered a replacement drive, installed it, and the machine booted fine. When I tried to rebuild the RAID, though, the entire machine froze (no kernel panic; it just froze). I had to hold the power button to shut it down, and now, it rarely starts. Sometimes, it does the loud whir; sometimes it just doesn't start (the power light turns on and I hear a few soft clicks, but nothing else). On a few occasions, it'll start but freeze again after a few minutes.

These problems started at the same time I tried to rebuild my RAID with a new drive, but that's just correlation not causation. I suspect the failure to rebuild the RAID was caused by the computer dying, rather than the other way around, but I can't be certain since everything is basically happening at the same time.

Any assistance would be appreciated, and I will happily provide clarification and additional information as need be.

Edit: None of the capacitors are blown.