Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fume - Pull failed disk #26

Closed
Firefishy opened this issue Mar 16, 2015 · 4 comments
Closed

Fume - Pull failed disk #26

Firefishy opened this issue Mar 16, 2015 · 4 comments
Labels

Comments

@Firefishy
Copy link
Member

Fume's disk port 1I:box 1:bay 8 is stuck in a fail, OK, rebuild cycle.

The disk should be pulled to allow a hot-spare to take over.

Disks 2I:1:4 and 1I:1:6 should also be pulled due later (after rebuild) due to flagged SMART Predictive Failure.

@gravitystorm
Copy link
Collaborator

Has this been tackled?

It looks like there's another failed disk on fume, we get the following report each day:

/dev/cciss/c0d0: (Smart Array P400) RAID 1 Volume 0 status: OK.   At least one spare drive designated.
/dev/cciss/c0d0: (Smart Array P400) RAID 1 Volume 1 status: OK.   At least one spare drive designated.  At least one activated on-line spare drive is completely rebuilt on this logical drive.  At least one spare drive activated.
  Failed drives:
         connector 2I box 1 bay 4                 HP      EG0146FAWHU                          6SD0JKPA0000B04918RR     HPDD

  Drives currently substituted for by spares:
         connector 2I box 1 bay 2                 HP      DG0146BALVN                          3SD0V0BJ00009001MGVY     HPD4

    Total of 1 failed physical drives detected on this logical drive.

What needs to be done to sort this out?

@tomhughes
Copy link
Member

@Firefishy did chase them, and he claimed to have pulled the failed disks, but the mails started up again fairly quickly thereafter,

@Firefishy
Copy link
Member Author

I'll follow up. I think this might be another disk the machine that has failed.

@Firefishy
Copy link
Member Author

I've rebuilt the raid on fume without the faulty disk. We should stop getting error reports now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants