Everything has been running great for the last 6 to 8 months, and I needed to install a new drive. Before I stopped the array everything was green. I then shutdown, installed the new drive, and booted back up. When the server came back on line, I noticed the web interface was extremely slow. Once I got into the Main Tab, I noticed I had a red ball next to disk 2. After reading the Wiki, the red ball should mean the disk is disabled. The odd thing is I can still browse the disk. At the same time, I noticed my new SATA drive is showing up as hda instead of sb(x). This new drive has not had anything done to it yet. I have checked all the cables to make sure I didn't bump anything lose, and have removed the new drive.

 

I just find it odd that this drive starting having problems due to a reboot.

 

Since I do not see any errors, I am not sure what is going on.

 

root@Tower:~# smartctl --scan-open

/dev/hda -d ata [ATA] (opened)

/dev/sdb [sAT] -d sat [ATA] (opened)

/dev/sdc [sAT] -d sat [ATA] (opened)

/dev/sdd [sAT] -d sat [ATA] (opened)

/dev/sde [sAT] -d sat [ATA] (opened)

Segmentation fault

root@Tower:~#

 

 

unRAID Server Pro

version: 5.0-beta7

 

Mobo: ASROCK 880GM-LE

 

log.txt

smart_disk_info.txt

Is the SMART report from disk 2? If so, the disk looks ok. It may be having a small power issue. Check the power connection to it and replace any splitters it uses.

 

The contents of disk2 are being simulated by unRAID.

 

Check the BIOS setting of the SATA ports. The should be AHCI only, not IDE, and not Combined mode.

 

I suggest rebuilding disk2:

[*]Stop the array and unassign disk2

[*]Start the array and stop the array (unRAID will "forget" the serial number of disk2.)

[*]Assign disk2 and start the array

Disk2 will be rebuilt.