hello everyone,

 

i plugged in an older PCI controller for 1 more SATA port.

(the raidcontroller support told me, it works for every linux system with kernel 2.6+)

snapped my new SATA II drive on it and booted unraid again

 

 

parity 	WDC_WD20EARS-00J_WD-WCAYY0218484 	36°C 	1,953,514,552 	- 	2,902 	406 	0
disk1 	WDC_WD20EARS-00J_WD-WCAYY0217525 	33°C 	1,953,514,552 	10,694,996 	8,510 	5 	0
disk2 	[b]Not installed[/b] 	- 	1,953,514,552 	9,898,964 	- 	- 	-

 

starting took forever because one disc couldnt be recognized (one of the 3 existing discs)

after a while it said, the "disk2" uses 2.1 TB and has 0°C temperature and that it should be the parity disk because of its size?

and after a reboot it looked like my code quote above

(the new one could be recognized (spinnpoint F4 2TB))

 

i added the syslog, so i really hope, you can offer some hints

 

is it, that my unraid server has mixed up the new disc with one of the existing?

 

i never removed any drive, i only added one drive to power and SATA cable

the "disk2" that i talk about is only 3 month old and worked absolutely perfekt (including preclear)

 

 

edit: added more information about what happend exactly

syslog-2010-11-142.txt

- i powered down

- changed cables

- checked connections (in case one sata data cable wasnt plugged in perfectly)

- rebooted

- unraid tells me:

 

disk2 SAMSUNG_HD203WI_S1UYJ1KSC05206 33°C 1,953,514,552 - - - -

 

Stopped.

Disabled disk replaced.

 

Start will bring the array on-line, start Data-Rebuild, and then expand the file system (if possible).

 

 

well.. the disk is the same like before. but now it wants to rebuild all data?

is there a way to rebuild the index of this disk or telling unraid, it should check again if its the right one?

added syslog again and deleted some initial lines with no errors because only 128kb upload is allowed here.

syslog-2010-11-143.txt

- i powered down

- changed cables

- checked connections (in case one sata data cable wasnt plugged in perfectly)

- rebooted

- unraid tells me:

 

disk2 SAMSUNG_HD203WI_S1UYJ1KSC05206 33°C 1,953,514,552 - - - -

 

Stopped.

Disabled disk replaced.

 

Start will bring the array on-line, start Data-Rebuild, and then expand the file system (if possible).

 

 

well.. the disk is the same like before. but now it wants to rebuild all data?

is there a way to rebuild the index of this disk or telling unraid, it should check again if its the right one?

I cannot tell from your description if the disk2 it intends to rebuild is the new disk you just added, or the disk that was there originally?

 

A disk that is disabled is one whee a write to it failed.  From what I'm seeing, disk2 was not writable (possibly a loose connection to it) and is now recognized again and unRAID wants to re-construct it, including the content it could not originally write.

 

unRAID goes by the port a disk is connected to.  If you switched around ports then it might get confused as to which drive it want to re-construct disk2 onto.

 

So... Whch disk is the NEW disk, the one not yet assigned to your array, and which were your original disks?

 

If the disk it wants to rebuild is the original disk, then press "Start" to let it re-construct the contents.

thanks for the very fast reply.

 

the error producing disk is one of the initial disks in my server.

 

it produced errors after i plugged in a new one (which i removed until the error issue is solved)

from what i found when checking the connections, a loose connection really could be the reason here.

 

i hoped, there is a faster way, then reconstructing everything, since it only is a small information, that wasnt right.

 

 

Current position: 2,060,284 (0.1%)

Estimated speed: 17,637 KB/sec

Estimated finish: 1843.8 minutes

 

that makes 30 hours.

i really hope its done in 30hours, because in 50hours i'm already on a flight to the other side of the world

 

 

thanks again for the very quick response.

seems my new drive has to wait until vacation is over

Joe, while i was reading your answer again:

 

 

do i understand you right here?

 

i case i want to switch the motherboard for a bigger server or whatever, i will get some trouble because unraid is checking the motherboard slots and not the discs itsself?

 

 

Joe, while i was reading your answer again:

 

 

do i understand you right here?

 

i case i want to switch the motherboard for a bigger server or whatever, i will get some trouble because unraid is checking the motherboard slots and not the discs itsself?

 

 

If you change to a different MB, or plug the disks into different ports and/or different disk controllers YOU will need to use the "Devices" page to assign the disks to their correct slots int he array.  Once you do that the array will start.

 

The model/serial numbers of the disks are tracked too, but if disks swap around between existing ports the array will prompt you before starting to confirm it is your intention.    There is no issue in migrating to different hardware...  The only really critical disk to get right is the parity disk.  It must be assigned to the parity "slot" in the array.  The other disks can be assigned anywhere (but, of course, if you assign data disk1 to data slot 2 in the array, its contents will now be on disk2, not disk1.  You might then also need to update the  disk allocation rules for users shares to reflect you change in usage of the disks)

 

so basically,

 

if i really need to migrate

 

i write down every specific name of every storage device and highlight the parity disk.

i plug all of them randomly in the next hardware, boot

and make sure that the parity disk gets the right slot first - chosing it by its name

so basically,

 

if i really need to migrate

 

i write down every specific name of every storage device and highlight the parity disk.

i plug all of them randomly in the next hardware, boot

and make sure that the parity disk gets the right slot first - chosing it by its name

You assign the disks by their model/serial number to the same logical slots in the array on the new hardware on the "Devices" page.

Then you can just press "Start"

 

Joe L.

the recovery was done way faster then i fought (10h)

preclearing the new disk right now.

 

thanks again for the help Joe L.