February 19, 201214 yr Ok here is a fresh thread at Joe L's request and will describe everything i did, A while ago disk 7 started to give me errors at power up, and i had read somewhere that if a drive would vibrate it could cause this, and because the drive wasnt secured properly in my case i ordered a new on and a new drive to replace it just in case. Yesterday i swapped everything to the new case making sure that all the drives were put back to the same ports and booted unraid, at the web ui it said disk 3 was missing, so i shutdown unraid and replaced the sata cable and made sure the power connector was properly seated and booted unraid. Now disk 3 was there but it said drive 4 was missing so i shut down unraid and replaced the sata cable for drive 4 and booted up. Now drive 4 was seen and all the drives had a green ball next to them so i started a parity check, it failed after 2-3 hours and i had a red ball next to drive 7 and 4 so i shutdown rechecked all the connections, everything seemed fine, and restarted unraid. At this point both disk 4 and disk 7 showed as unformatted in the web ui, so looking on the forums i ran the following commands. For disk4 fdisk -lu /dev/sdk and disk7 fdisk -lu /dev/sdb here is what i got: Disk /dev/sdk: 1500.3 GB, 1500301910016 bytes 1 heads, 63 sectors/track, 46512336 cylinders, total 2930277168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdk1 64 2930277167 1465138552 83 Linux Partition 1 does not end on cylinder boundary. Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 64 3907029167 1953514552 83 Linux Partition 1 does not end on cylinder boundary. Only ever used unraid 4.7 edit: ran this dd if=/dev/sdk count=195 | od -c -A d | sed 30q and got : Device Boot Start End Blocks Id System /dev/sdb1 64 3907029167 1953514552 83 Linux Partition 1 does not end on cylinder boundary. root@Tower:~# root@Tower:~# dd if=/dev/sdk count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 0.00126486 s, 78.9 MB/s 0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000448 \0 \0 203 \0 \0 \0 @ \0 \0 \0 360 z 250 256 \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0098304 ^ 017 325 025 243 \f t \0 220 002 301 \0 022 \0 \0 \0 0098320 \0 \0 \0 \0 \0 \0 \0 \0 004 \0 \0 247 375 242 0098336 204 003 \0 \0 036 \0 \0 \0 \0 \0 \0 \0 \0 020 314 003 0098352 020 \0 002 \0 R e I s E r 2 F s \0 \0 \0 0098368 003 \0 \0 \0 005 \0 253 + 002 \0 \0 \0 J 001 \0 \0 0098384 001 \0 \0 \0 c 221 206 231 Q < J 232 255 1 305 v 0098400 313 R 303 343 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0098416 \0 \0 \0 \0 6 \0 036 \0 L u ~ M \0 N 355 \0 0098432 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0098496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 001 \0 \0 \0 0098512 035 1 \0 \0 , 1 \0 \0 242 1 \0 \0 257 1 \0 \0 0098528 024 8 \0 \0 8 \0 \0 * 8 \0 \0 - 8 \0 \0 0098544 G 9 \0 \0 I 9 \0 \0 K 9 \0 \0 ~ 9 \0 \0 0098560 364 : \0 \0 371 : \0 \0 341 ; \0 \0 371 : \0 \0 0098576 341 ; \0 \0 324 7 \0 \0 306 8 \0 \0 324 7 \0 \0 0098592 306 8 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0098608 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099840 ran this: dd if=/dev/sdb count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 0.0279884 s, 3.6 MB/s 0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000448 \0 \0 203 \0 \0 \0 @ \0 \0 \0 p 210 340 350 \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0098304 016 021 034 035 343 I { 016 n \0 \f 031 022 \0 \0 \0 0098320 \0 \0 \0 \0 \0 \0 \0 \0 004 \0 \0 272 374 m 022 0098336 204 003 \0 \0 036 \0 \0 \0 \0 \0 \0 \0 \0 020 314 003 0098352 002 \0 002 \0 R e I s E r 2 F s \0 \0 \0 0098368 003 \0 \0 \0 005 \0 9 : 002 \0 \0 \0 \0 002 \0 \0 0098384 001 \0 \0 \0 L 350 M 022 M 376 E 304 227 341 026 225 0098400 271 325 y 231 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0098416 \0 \0 \0 \0 \r \0 036 \0 i 2 317 N \0 N 355 \0 0098432 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0098496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 001 \0 \0 \0 0098512 346 033 \0 \0 = 031 \0 \0 > 031 \0 \0 = 031 \0 \0 0098528 > 031 \0 \0 006 025 \0 \0 006 025 \0 \0 \v 025 \0 \0 0098544 \v 025 \0 \0 023 025 \0 \0 023 025 \0 \0 022 025 \0 \0 0098560 023 025 \0 \0 022 025 \0 \0 023 025 \0 \0 021 025 \0 \0 0098576 023 025 \0 \0 305 024 \0 \0 023 025 \0 \0 305 024 \0 \0 * 0098608 023 025 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0098624 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099840 So after that i ran this command, reiserfsck --check /dev/sdk1 and it came back with no error so reading this post http://lime-technology.com/forum/index.php?topic=15385.0 it said that if it seemed fine you could run initconfig, so i did (assuming that disk 7 was fine also, huge mistake...) after running initcofig all the balls were blue and i started the array and it started a parity check. It said parity check invalid and started to write to disk 4 so i panicked and stopped the parity check almost instantly. Now both disk 4 and 7 show as unformatted and there is a yellow/orange ball next to the parity drive... then i ran this command for disk 7: reiserfsck --check /dev/md7 The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (2): (Input/output error). Aborted ran the same command for disk 4: reiserfsck --check /dev/md4 Will read-only check consistency of the filesystem on /dev/sdk1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes reiserfs_open: the reiserfs superblock cannot be found on /dev/sdk1. Failed to open the filesystem. If the partition table has not been changed, and the partition is valid and it really contains a reiserfs partition, then the superblock is corrupted and you need to run this utility with --rebuild-sb. And now if i run dd if=/dev/sdk count=195 | od -c -A d | sed 30q and here is what it said: root@Tower:~# dd if=/dev/sdk count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 6.37156 s, 15.7 kB/s 0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000448 \0 \0 203 \0 \0 \0 @ \0 \0 \0 360 z 250 256 \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0098304 001 \0 001 \0 \0 \0 - 302 { 274 \ } b 240 i 353 0098320 271 247 025 355 312 277 236 331 317 ; \0 \0 337 ; \0 \0 0098336 001 020 / 4 001 \0 \0 020 \0 \0 320 017 0 \0 001 \0 0098352 265 K , 022 266 K , 022 267 K , 022 270 K , 022 0098368 271 K , 022 272 K , 022 273 K , 022 274 K , 022 0098384 275 K , 022 276 K , 022 277 K , 022 300 K , 022 0098400 301 K , 022 302 K , 022 303 K , 022 304 K , 022 0098416 305 K , 022 306 K , 022 307 K , 022 310 K , 022 0098432 311 K , 022 312 K , 022 313 K , 022 314 K , 022 0098448 315 K , 022 316 K , 022 317 K , 022 320 K , 022 0098464 321 K , 022 322 K , 022 323 K , 022 324 K , 022 0098480 325 K , 022 326 K , 022 327 K , 022 330 K , 022 0098496 331 K , 022 332 K , 022 333 K , 022 334 K , 022 0098512 335 K , 022 336 K , 022 337 K , 022 340 K , 022 0098528 341 K , 022 342 K , 022 343 K , 022 344 K , 022 0098544 345 K , 022 346 K , 022 347 K , 022 350 K , 022 0098560 351 K , 022 352 K , 022 353 K , 022 354 K , 022 0098576 355 K , 022 356 K , 022 357 K , 022 360 K , 022 0098592 361 K , 022 362 K , 022 363 K , 022 364 K , 022 0098608 365 K , 022 366 K , 022 367 K , 022 370 K , 022 0098624 371 K , 022 372 K , 022 373 K , 022 374 K , 022 0098640 375 K , 022 376 K , 022 377 K , 022 \0 L , 022 Last night i started to preclear a drive to replace disk7 and that should be done tonight, so what would be my next step? Run rebuild-sd on disk 4 and then replace disk 7 with new disk? or the other way around? Thank you so much for all the help, kinda panicking here...
February 19, 201214 yr Author and here is two syslogs, one from the beginning and one from now Thank you for any help syslog.zip syslog_now.zip
February 19, 201214 yr Author ran the commands from this thread http://lime-technology.com/forum/index.php?topic=5072.15 (i dont know if its pertinent to my problem but might as well give as much info as possible) and here is what it gives me root@Tower:~# sfdisk -g /dev/sdK /dev/sdK: No such file or directory sfdisk: cannot open /dev/sdK for reading root@Tower:~# sfdisk -g /dev/sdk /dev/sdk: 182401 cylinders, 255 heads, 63 sectors/track root@Tower:~# blockdev --getsz /dev/sdk 2930277168 root@Tower:~# fdisk -l -u /dev/sdk Disk /dev/sdk: 1500.3 GB, 1500301910016 bytes 1 heads, 63 sectors/track, 46512336 cylinders, total 2930277168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdk1 64 2930277167 1465138552 83 Linux Partition 1 does not end on cylinder boundary. root@Tower:~# od -x -A d /dev/sdk | head 0000000 0000 0000 0000 0000 0000 0000 0000 0000 * 0000448 0000 0083 0000 0040 0000 7af0 aea8 0000 0000464 0000 0000 0000 0000 0000 0000 0000 0000 * 0000496 0000 0000 0000 0000 0000 0000 0000 aa55 0000512 0000 0000 0000 0000 0000 0000 0000 0000 * 0098304 0001 0001 0000 c22d bc7b 7d5c a062 eb69 0098320 a7b9 ed15 bfca d99e 3bcf 0000 3bdf 0000
February 19, 201214 yr Author Just remembered that after the parity failed, the web ui became unresponsive and i couldn't telnet in to perform a reboot, so i had to do a shutdown with power button and then the drives came back as unformated ...
February 20, 201214 yr Author Ok my new disk just finished the preclear and its ready to replace disk 7, i would just like to know what to do first? Thanks for any help because im completly lost with this...
February 21, 201214 yr Author i was reading this thread , http://lime-technology.com/forum/index.php?topic=1483 and it mentionned using hdd regenerator to fix a bad block, would it help with the problem on disk 7 even if just temporary to get the data off of it? Also should i try to run the rebuild-sb option on disk 4 to try and fix the file system? Thank you for any help...
February 22, 201214 yr Author Managed to bring disk 4 back to life, i did a rebuild-sb on it and then it completed successfully. So i started a reiserfs check on it and it said failed rebuild-tree. So i ran --rebuild-tree and let it go all night, this morning when i came back it was finished so i stopped the array and then restarted it and disk 4 was back online and NOT saying unformated. So i looked at my shares and all my files were back and nothing in the lost+found! On to disk 7 now
February 22, 201214 yr Author tried a rebuild-sb and rebuild-tree on disk 7 but still gives me the same bad block error as before, so i have now removed it from my array and put in a new disk in its place, but now i wanna see if i can get the data from the disk with bad blocks, i found this website with how to move bad blocks (hxxp://www.krazyworks.com/dealing-with-reiserfs-bad-blocks/), so im gonna give that a try and hook that drive up to windows and use YAReG to try and get the files from it...
February 22, 201214 yr Author because somehow i unassigned the parity drive and reassigned it and when i started the array i didnt realized it would calculate a new parity and my parity got wiped... anyways doesnt matter because i have the data that was on disk 7 elsewhere, i just wanna try to see if i can get the data back, it would save me the time to rerip the disks...
February 25, 201214 yr Author just another update, i ran hdd regenerator on disk 7, it found and repaired all the bad blocks, i now hooked up disk 7 to a windows pc and with YAreg i am now able to recover all the data that was on disk 7. After it is done i will rma disk 7 back to hitachi. Took a while but its all back to normal! Tried to put solved in thread title but it wont let me so if one of the mods could do it...
Archived
This topic is now archived and is closed to further replies.