November 16, 201312 yr Hi everybody, I have done searching to no avail. All of sudden I have noticed that my parity Drive has a red ball and 9 errors with disk one green ball but with 55 errors. I have tried to stop the array but lost the http connection to the server's GUI. Before losing the connection I tried to run a smart short test on my parity drive and got a line saying "smartctl: device read identity failed (not an ATA/ATAPI drive). A mandatory smart command failed, exiting". What should I do next? Please find attached my syslog. syslog.txt
November 16, 201312 yr Author Hi everybody, I have done searching to no avail. All of sudden I have noticed that my parity Drive has a red ball and 9 errors with disk one green ball but with 55 errors. I have tried to stop the array but lost the http connection to the server's GUI. Before losing the connection I tried to run a smart short test on my parity drive and got a line saying "smartctl: device read identity failed (not an ATA/ATAPI drive). A mandatory smart command failed, exiting". What should I do next? Please find attached my syslog. And the screenshot of the GUI screen.
November 16, 201312 yr Let's see... The parity disk has stopped responding. (and writes to it failed taking it off-line, making parity invalid) It could be 1. A bad drive 2. A bad cable to the drive (either POWER or DATA) 3. A loose cable to the drive (either POWER or DATA) 4. A bad disk controller port 5. A power supply insufficient to power all your drives (and the parity drive has shut itself down and will not respond) 6. A fan that has stopped working, and the parity disk has shut itself down after it overheated. See here: http://lime-technology.com/wiki/index.php/FAQ#What_does_the_Red_Ball_mean.3F Joe L.
November 18, 201312 yr Author Let's see... The parity disk has stopped responding. (and writes to it failed taking it off-line, making parity invalid) It could be 1. A bad drive 2. A bad cable to the drive (either POWER or DATA) 3. A loose cable to the drive (either POWER or DATA) 4. A bad disk controller port 5. A power supply insufficient to power all your drives (and the parity drive has shut itself down and will not respond) 6. A fan that has stopped working, and the parity disk has shut itself down after it overheated. See here: http://lime-technology.com/wiki/index.php/FAQ#What_does_the_Red_Ball_mean.3F Joe L. Thank you very much. I checked the cables and power, could not find anything wrong. Stopped the array, unassigned the parity disk, started, stopped the array, assigned the disk and let the parity build. Everything seems to be ok, some random check on the files turned out ok. The smart test on the disks (Disk 1 and parity) and the file check passed. I don't know what went wrong and feel a little bit uneasy know. Should I change the Disk 1 or the parity to be on the safer side, or just ignore what has happened, I don't know.
November 18, 201312 yr Disk 1 is set to read-only and reiserfsck is required to fix. See Check disk filesystems in my sig.
November 18, 201312 yr Author Disk 1 is set to read-only and reiserfsck is required to fix. See Check disk filesystems in my sig. Thanks for your help. I have run the reiserfsck as you have mentioned and I could not find anything wrong (the outcome as follows). Should I still run the command: "reiserfsck --fix-fixable /dev/md1" ? ....... Replaying journal: Done. Reiserfs journal '/dev/md1' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 300558 Internal nodes 1894 Directories 30775 Other files 303253 Data block pointers 245782186 (0 of them are zero) Safe links 0
Archived
This topic is now archived and is closed to further replies.