May 22, 201214 yr So I have an issue. Unraid 4.7 I had disk 8 fail. I contacted WD and RMAed the drive (2 TB EARS). I received the WDEARX drive today and replaced disk8. Reassigned the new drive and started the array. The data rebuild was in progress and I got an update 1 hour into the process. I did not preclear the drive (possible mistake??) I normally do, but some of the data I lost was important and I wanted to recover it ASAP. At hour 2 I did not get an email update which I thought was odd. When I got home the unraid box had a kernel panic and would not accept any input from the keyboard. I power cycled the machine and at the time I was thinking about the 6gb/s capacity of the WDEARX drive versus the existing drive so I decided to put a jumper on pins 5 and 6 to set the WDEARX drive to 3 gb/s thinking this might have something to do with the issue. I then fired the machine back up and immediately the unraid webgui indicated the rebuild was in progress, however I saw a large volume of writes being made to the parity disk so I immediately stopped the parity rebuild. When I did this the disk 8 went back to missing and the parity turned blue. Any suggestions??? Thanks! Dan Edit: Tom Helped me out...thanks Tom!
May 22, 201214 yr So I have an issue. Unraid 4.7 I had disk 8 fail. I contacted WD and RMAed the drive (2 TB EARS). I received the WDEARX drive today and replaced disk8. Reassigned the new drive and started the array. The data rebuild was in progress and I got an update 1 hour into the process. I did not preclear the drive (possible mistake??) I normally do, but some of the data I lost was important and I wanted to recover it ASAP. At hour 2 I did not get an email update which I thought was odd. When I got home the unraid box had a kernel panic and would not accept any input from the keyboard. I power cycled the machine and at the time I was thinking about the 6gb/s capacity of the WDEARX drive versus the existing drive so I decided to put a jumper on pins 5 and 6 to set the WDEARX drive to 3 gb/s thinking this might have something to do with the issue. I then fired the machine back up and immediately the unraid webgui indicated the rebuild was in progress, however I saw a large volume of writes being made to the parity disk so I immediately stopped the parity rebuild. When I did this the disk 8 went back to missing and the parity turned blue. Any suggestions??? Thanks! Dan Capture the syslog. Send a plea to Tom at lime-tech for guidance.
May 23, 201214 yr Author Thanks Joe...attached is the syslog. I realize that I did something stupid that I did not list in my first email....I did a restart of unraid after I got the blue parity ball...and I did not save the syslog before I restarted...big mistake I now realize... The syslog below is obviously what resulted after my restart. I will contact Tom and point him to this thread. syslog-2012-05-22.txt
May 23, 201214 yr Author I forgot about the powerdown script....it saved the log automatically! I have attached a shortened version...similiar errors continued on an on for 274mb! This should give an idea of what happened. Dan syslog_shortened.txt
Archived
This topic is now archived and is closed to further replies.