justellmewynn

Members
  • Posts

    1
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

justellmewynn's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I'm looking for options and next steps, after attempting to add an additional drive to my unRAID array. I am running version 5.0b13. Below is a list of what actually happened and what I did. It probably also shows where I screwed up big time, but I am an unRAID noob, so any advice would be great. 1. First, I went ahead and installed the drive in an empty SATA slot, powered the server, and started the array. (without adding the new drive to the array) All was intact. 2. I pre-cleared the new drive using the preclear_disk.sh script and all seemed to have went well. 3. After it pre-cleared, I stopped the array, and powered down the server. (Why did I power down the server? Idk, maybe for extra precaution) 4. I then powered the server back up, expecting the array to start automatically before having to stop it to add the new drive. But, it was showing that disk3 was unformatted. Ugghhh!!!! 5. After looking around at a number of "unformatted" threads, I decided to run "reiserfsck --check" on md3 6. It returned and said that I needed to rebuild the superblock (rebuild-sb) 7. I gathered all the answers, mostly from Brian's post on running rebuild-sb, and ran "reiserfsck --rebuild-sb" 8. After it completed, and gave me virtually the same output as Brian, I went to restart the array just with the 3 original drives. (still hadn't added the new drive) 9. Drive still could not mount and showed unformatted. I ran "resiserfsck --check" again. This time it told me to run --rebuild-tree. Which I wasn't sure about. 10. After reading a couple posts, I started to think the drive was failing and/or was all screwed up at this point. So, I decided to just replace the "bad" drive (disk3) with the new drive and rebuild the data on there. I put the "new" drive in the slot of the "old" disk3 drive. (Was this a bad idea???) 11. After a couple of hours of rebuilding, the "new" drive is now showing Unformatted. That is where I'm stuck. Should I go through the same process of running reiserfsck --check? I previously read (after I already ran the command) that running reiserfsck may not be the best thing to do if you want to keep your data. So, I'm asking for help on next steps, especially if the reiserfsck returns with --rebuild-sb again. Attached is my syslog. Hopefully, there is another option that helps get my array back up and running, and data safe. Thanks!!! -Clae syslog-2012-12-11.txt