44
edits
Drive Crash 2: The fscking: Difference between revisions
Jump to navigation
Jump to search
no edit summary
m (made conclusion grammer) |
Lloyd.wallis (talk | contribs) No edit summary |
||
| Line 25: | Line 25: | ||
== The Balls-up == | == The Balls-up == | ||
As fsrv posted, there was one immediate concern with the POST data - the RAID controller insisted that the existing array had failed, as all four of the drives connected to it were no longer there. However, they were replaced with four completely different drives, despite the fact they were identical down to the serial numbers. It was at the first stage of investigating this that a [[docs:Glossary | High Impedance Air Gap]] developed between the power cable providing power to backup and the power supply of backup, causing an | As fsrv posted, there was one immediate concern with the POST data - the RAID controller insisted that the existing array had failed, as all four of the drives connected to it were no longer there. However, they were replaced with four completely different drives, despite the fact they were identical down to the serial numbers. It was at the first stage of investigating this that a [[docs:Glossary | High Impedance Air Gap]] developed between the power cable providing power to backup and the power supply of backup, causing an unexpected power-down. At this time, it was not noticed that the noise heard was that of backup restarting, and was disregarded whilst fsrv was told to start building a new array on its "new" drives. | ||
Of course, once sufficient array building was done to fsrv to make it unlikely anything was ever coming back out of it, the source of the earlier electrical crackling noise was investigated. Once ystvbackup was brought back up, it was only natural for our worst fears to be correct - the backup of fsrv's recently wiped data was corrupt. | Of course, once sufficient array building was done to fsrv to make it unlikely anything was ever coming back out of it, the source of the earlier electrical crackling noise was investigated. Once ystvbackup was brought back up, it was only natural for our worst fears to be correct - the backup of fsrv's recently wiped data was corrupt. | ||