Adam PAPAI writes: > Greg Oster wrote: > > Adam PAPAI writes: > > > >>After reboot my dmesg end: > >> > >>rootdev=0x400 rrootdev=0xd00 rawdev=0xd02 > >>Hosed component: /dev/sd0d. > >>raid0: Ignoring /dev/sd0d. > >>raid0: Component /dev/sd1d being configured at row: 0 col: 1 > >> Row: 0 Column: 1 Num Rows: 1 Num Columns: 2 > >> Version: 2 Serial Number: 100 Mod Counter: 27 > >> Clean: No Status: 0 > >>/dev/sd1d is not clean ! > >>raid0 (root)raid0: no disk label > >>raid0: Error re-writing parity! > >> > >>dd if=/dev/rsd0d of=/dev/null bs=10m & > >>dd if=/dev/rsd1d of=/dev/null bs=10m & > >> > >>was successfully ended. > >> > >># raidctl -iv raid0 > > > > > > wha does 'raidctl -s raid0' say? It probably says that 'sd0d' is > > failed. You can't initialize parity with 'raidctl -iv' on a set with > > a failed component. You can do 'raidctl -vR /dev/sd1d raid0' to get > > it to reconstruct back onto the failed component. After that you can > > do a 'raidctl -iv' (though by that point it's strictly not necessary). > > Interesting. I tried with 3 full reinstall and all raidctl -iv raid0 > fails, but with raidctl -vR /dev/sd0d solved the problem. > > But why?
It didn't solve the "Media Error"... the "Media Error" just didn't show up again. > Will it be good from now? If I had to pick from one of "Yes" or "No", I'd pick "No". > I'm fraid the raid will collapse again. I hope not. > > I going to continue the setup on my server. Thanks anyway. I hope I > won't get more errors... I hope so too... but nothing in 'raidctl -vR' really fixes media errors... (Since 'raidctl -R' is going to write to sd0, it's possible that the drive has now re-mapped whatever bad block was on sd0, and sd0 may work fine now... but it's unusual to see the same error on 2 different drives... makes me maybe suspect cabling too..) Later... Greg Oster
