block134 Posted January 6, 2013 Share Posted January 6, 2013 I have been having some problems the past few days with my server so I removed my plugins, did a chkdsk on my flash drive and re installed the server software on the flash drive. The first thing I did was remove the plugins and do a reboot and after the reboot I had three disks show up as unformatted so I did a reboot since that has fixed the problem for me in the past but it didn't help this time. After that I did the chkdsk on the flash drive and re-installed the server software but that didn't help either so now I am asking for some help with this. I have all ready swapped cables and checked all the connection and tried running a reiserfsck on the drives showing unformatted but it tells me that the reiserfs superblock cannot be found and that it failed to open the file system. It also says to run it with the --rebuild-sb but I have not done that yet. I wanted to see if there was anything else that I can try before I do that. syslog.zip Quote Link to comment
Joe L. Posted January 7, 2013 Share Posted January 7, 2013 I have been having some problems the past few days with my server so I removed my plugins, did a chkdsk on my flash drive and re installed the server software on the flash drive. The first thing I did was remove the plugins and do a reboot and after the reboot I had three disks show up as unformatted so I did a reboot since that has fixed the problem for me in the past but it didn't help this time. After that I did the chkdsk on the flash drive and re-installed the server software but that didn't help either so now I am asking for some help with this. I have all ready swapped cables and checked all the connection and tried running a reiserfsck on the drives showing unformatted but it tells me that the reiserfs superblock cannot be found and that it failed to open the file system. It also says to run it with the --rebuild-sb but I have not done that yet. I wanted to see if there was anything else that I can try before I do that. DO NOT rebuild the superblock unless you know the partition is correct first, otherwise, you'll trash the drive's contents. 50% of those I help are running the reiserfsck on the WRONG device. Are you? What EXACT reiserfsck --check commands are you running, on which "device" All the errors in the syslog indicate an un-readable flash drive. (and a USB port that is constantly disconnecting ) That seems to be the root cause of your problems. You'll need to determine exactly how those disks were partitioned (4k-alligned, or not) and make sure the partitioning is still correct... Otherwise, the file-system superblock will exist, but not be located. Joe L. Quote Link to comment
block134 Posted January 7, 2013 Author Share Posted January 7, 2013 I am using reiserfsck --check /dev/md1 on Disk 1 since it is one of the ones that is showing unformatted. As far as rebuilding goes I have no intention of doing that yet unless directed to. For the USB problems I have noticed that but I haven't looked into it yet, I also have a USB keyboard/mouse and UPS plugged into USB. For the 4K aligned I will have to get back to you on that one when I get a chance to look at the server tomorrow. Quote Link to comment
Joe L. Posted January 7, 2013 Share Posted January 7, 2013 I am using reiserfsck --check /dev/md1 on Disk 1 since it is one of the ones that is showing unformatted. As far as rebuilding goes I have no intention of doing that yet unless directed to. For the USB problems I have noticed that but I haven't looked into it yet, I also have a USB keyboard/mouse and UPS plugged into USB. For the 4K aligned I will have to get back to you on that one when I get a chance to look at the server tomorrow. Performing the reiserfsck on /dev/md1 would work IF the first partition of the drive is pointing to the correct place. (you are one of the 50% who used the correct device) Now, you need to determine where the partition is pointing to... You can do that by running the following command on the disk affiliated with each of those reporting unformatted: fdisk -lu /dev/sdX It will report that the partition starts on either sector 63, sector 64, or (on drives > 2TB) sector 1. That may, or may not be correct, and if the actual partition is on sector 64, and you are pointing to sector 63, that would be the cause of it being reported as unformatted. I've not seen this class of error on 5.0, but it is a major bug on the 4.7 series when a super.dat file is un-readable. It might just be nobody has run into it on the 5.0 series just yet. (until you) We'll soon see. You can run this command on each of the drives affiliated with the "unformatted" disks. Notice it needs you to specify the Linux disk device. ( /dev/sdxX ) dd if=/dev/sdc count=195 | od -c -A d | sed '/R e I s E r 2 F s/q' You'll probably be better cutting and pasting the command, but if you type it in by hand, there are three spaces between letter in the string "R space space space e space space space I space space space s space space space E space space space r space space space 2 space space space F space space space s" If the string is on a line at address "0097840" like this 0097840 220 \0 002 \0 R e I s E r 2 F s \0 \0 \0 the file system is starting on sector 63. If the string is on a line at address "0098352" like this: 0098352 006 \0 001 \0 R e I s E r 2 F s \0 \0 \0 the file system is starting on sector 64. If the Reiserfs is not starting on the same sector as the partition, it will not mount. see this thread for further detail. http://lime-technology.com/forum/index.php?topic=23246.msg205414#msg205414 Joe L. Quote Link to comment
block134 Posted January 7, 2013 Author Share Posted January 7, 2013 With the fdisk -lu /dev/sdX command sdg starts at 64, sdb starts at 64, and sdc starts at 1. The first two are 2TB and the third is a 3TB. I haven't run the second command yet but I will do that when I get home from work today. Thanks for your time so far Joe. Quote Link to comment
block134 Posted January 7, 2013 Author Share Posted January 7, 2013 This is what I got when I copy and pasted in the comand dd if=/dev/sdg count=195 | od -c -A d | sed '/R e I s E r 2 F s/q' 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 0.00986858 s, 10.1 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 E F I P A R T \0 \0 001 \0 \ \0 \0 \0 0000528 S 256 223 # \0 \0 \0 \0 001 \0 \0 \0 \0 \0 \0 \0 0000544 257 210 340 350 \0 \0 \0 \0 " \0 \0 \0 \0 \0 \0 \0 0000560 216 210 340 350 \0 \0 \0 \0 206 223 024 @ 033 b 341 021 0000576 272 302 364 m 004 4 o 316 002 \0 \0 \0 \0 \0 \0 \0 0000592 200 \0 \0 \0 200 \0 \0 \0 224 \b d 206 \0 \0 \0 \0 0000608 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0001024 265 | n Q 317 n 326 021 217 370 \0 002 - \t q + 0001040 261 242 , @ 033 b 341 021 272 302 364 m 004 4 o 316 0001056 200 \0 \0 \0 \0 \0 \0 \0 177 \0 @ \0 \0 \0 \0 \0 0001072 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0001152 272 | n Q 317 n 326 021 217 370 \0 002 - \t q + 0001168 L 005 C @ 033 b 341 021 272 302 364 m 004 4 o 316 0001184 200 \0 @ \0 \0 \0 \0 \0 216 210 340 350 \0 \0 \0 \0 0001200 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0098304 \v S 001 \0 { S 001 \0 \v S 001 \0 { S 001 \0 * 0099696 \0 \0 \0 \0 " * 001 \0 * 025 \0 \0 351 \0 \0 \0 0099712 022 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 004 \0 \0 0099728 : p 030 a 204 003 \0 \0 036 \0 \0 \0 \0 \0 \0 \0 0099744 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 Quote Link to comment
Joe L. Posted January 7, 2013 Share Posted January 7, 2013 This is what I got when I copy and pasted in the comand dd if=/dev/sdg count=195 | od -c -A d | sed '/R e I s E r 2 F s/q' 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 0.00986858 s, 10.1 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 E F I P A R T \0 \0 001 \0 \ \0 \0 \0 0000528 S 256 223 # \0 \0 \0 \0 001 \0 \0 \0 \0 \0 \0 \0 0000544 257 210 340 350 \0 \0 \0 \0 " \0 \0 \0 \0 \0 \0 \0 0000560 216 210 340 350 \0 \0 \0 \0 206 223 024 @ 033 b 341 021 0000576 272 302 364 m 004 4 o 316 002 \0 \0 \0 \0 \0 \0 \0 0000592 200 \0 \0 \0 200 \0 \0 \0 224 \b d 206 \0 \0 \0 \0 0000608 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0001024 265 | n Q 317 n 326 021 217 370 \0 002 - \t q + 0001040 261 242 , @ 033 b 341 021 272 302 364 m 004 4 o 316 0001056 200 \0 \0 \0 \0 \0 \0 \0 177 \0 @ \0 \0 \0 \0 \0 0001072 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0001152 272 | n Q 317 n 326 021 217 370 \0 002 - \t q + 0001168 L 005 C @ 033 b 341 021 272 302 364 m 004 4 o 316 0001184 200 \0 @ \0 \0 \0 \0 \0 216 210 340 350 \0 \0 \0 \0 0001200 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0098304 \v S 001 \0 { S 001 \0 \v S 001 \0 { S 001 \0 * 0099696 \0 \0 \0 \0 " * 001 \0 * 025 \0 \0 351 \0 \0 \0 0099712 022 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 004 \0 \0 0099728 : p 030 a 204 003 \0 \0 036 \0 \0 \0 \0 \0 \0 \0 0099744 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 That must have been your 3TB drive? right? Quote Link to comment
block134 Posted January 7, 2013 Author Share Posted January 7, 2013 sdg is a 2TB sdb is my other 2TB and its report look pretty much identical to sdg. Sdc is my 3TB and its report looked different then the other two but it didnt contain the info in the address lines that you are looking for. sdg 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 0.00358255 s, 27.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 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 E F I P A R T \0 \0 001 \0 \ \0 \0 \0 0000528 S 256 223 # \0 \0 \0 \0 001 \0 \0 \0 \0 \0 \0 \0 0000544 257 210 340 350 \0 \0 \0 \0 " \0 \0 \0 \0 \0 \0 \0 0000560 216 210 340 350 \0 \0 \0 \0 206 223 024 @ 033 b 341 021 0000576 272 302 364 m 004 4 o 316 002 \0 \0 \0 \0 \0 \0 \0 0000592 200 \0 \0 \0 200 \0 \0 \0 224 \b d 206 \0 \0 \0 \0 0000608 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0001024 265 | n Q 317 n 326 021 217 370 \0 002 - \t q + 0001040 261 242 , @ 033 b 341 021 272 302 364 m 004 4 o 316 0001056 200 \0 \0 \0 \0 \0 \0 \0 177 \0 @ \0 \0 \0 \0 \0 0001072 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0001152 272 | n Q 317 n 326 021 217 370 \0 002 - \t q + 0001168 L 005 C @ 033 b 341 021 272 302 364 m 004 4 o 316 0001184 200 \0 @ \0 \0 \0 \0 \0 216 210 340 350 \0 \0 \0 \0 0001200 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0098304 \v S 001 \0 { S 001 \0 \v S 001 \0 { S 001 \0 * 0099696 \0 \0 \0 \0 " * 001 \0 * 025 \0 \0 351 \0 \0 \0 0099712 022 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 004 \0 \0 0099728 : p 030 a 204 003 \0 \0 036 \0 \0 \0 \0 \0 \0 \0 0099744 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 sdb 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 0.0104306 s, 9.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 E F I P A R T \0 \0 001 \0 \ \0 \0 \0 0000528 1 s 024 3 \0 \0 \0 \0 001 \0 \0 \0 \0 \0 \0 \0 0000544 257 210 340 350 \0 \0 \0 \0 " \0 \0 \0 \0 \0 \0 \0 0000560 216 210 340 350 \0 \0 \0 \0 C 275 I 7 9 211 273 A 0000576 201 " 255 244 236 243 216 Y 002 \0 \0 \0 \0 \0 \0 \0 0000592 200 \0 \0 \0 200 \0 \0 \0 207 \ , \t \0 \0 \0 \0 0000608 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0001024 026 343 311 343 \ \v 270 M 201 } 371 - 360 002 025 256 0001040 202 034 217 300 237 257 216 F 266 313 214 274 215 + 300 204 0001056 " \0 \0 \0 \0 \0 \0 \0 ! \0 004 \0 \0 \0 \0 \0 0001072 \0 \0 \0 \0 \0 \0 \0 \0 M \0 i \0 c \0 r \0 0001088 o \0 s \0 o \0 f \0 t \0 \0 r \0 e \0 0001104 s \0 e \0 r \0 v \0 e \0 d \0 \0 p \0 0001120 a \0 r \0 t \0 i \0 t \0 i \0 o \0 n \0 0001136 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0001152 242 240 320 353 345 271 3 D 207 300 h 266 267 & 231 307 0001168 H ^ l 220 Z O 207 F 260 311 202 033 344 j 217 220 0001184 \0 \b 004 \0 \0 \0 \0 \0 377 207 340 350 \0 \0 \0 \0 0001200 \0 \0 \0 \0 \0 \0 \0 \0 B \0 a \0 s \0 i \0 0001216 c \0 \0 d \0 a \0 t \0 a \0 \0 p \0 0001232 a \0 r \0 t \0 i \0 t \0 i \0 o \0 n \0 0001248 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0098304 237 210 \0 \0 347 211 \0 \0 237 210 \0 \0 347 211 \0 \0 * 0098352 237 210 001 \0 347 211 \0 \0 237 210 \0 \0 347 211 \0 \0 0098368 237 210 \0 \0 347 211 \0 \0 237 210 \0 \0 347 211 \0 \0 * 0099680 j 210 \0 \0 347 211 \0 \0 j 210 \0 \0 347 211 \0 \0 0099696 \0 \0 \0 \0 \r 232 \0 \0 223 \0 \0 \0 325 \0 \0 \0 0099712 022 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 004 \0 \0 0099728 364 004 s 7 204 003 \0 \0 036 \0 \0 \0 \0 \0 \0 \0 0099744 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * sdc the 3TB 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 0.00440371 s, 22.7 MB/s 0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000448 002 \0 356 377 377 377 001 \0 \0 \0 377 377 377 377 \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 E F I P A R T \0 \0 001 \0 \ \0 \0 \0 0000528 335 P } 020 \0 \0 \0 \0 001 \0 \0 \0 \0 \0 \0 \0 0000544 257 243 P ] 001 \0 \0 \0 " \0 \0 \0 \0 \0 \0 \0 0000560 216 243 P ] 001 \0 \0 \0 \r 306 363 367 4 265 222 M 0000576 257 301 306 . 351 k 026 y 002 \0 \0 \0 \0 \0 \0 \0 0000592 200 \0 \0 \0 200 \0 \0 \0 236 ~ 350 364 \0 \0 \0 \0 0000608 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0001024 257 = 306 017 203 204 r G 216 y = i 330 G } 344 0001040 210 357 > 332 263 207 027 I 276 361 377 025 6 236 260 373 0001056 @ \0 \0 \0 \0 \0 \0 \0 216 243 P ] 001 \0 \0 \0 0001072 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0098304 307 322 \0 \0 K 323 \0 \0 307 322 \0 \0 K 323 \0 \0 * 0098352 307 322 001 \0 K 323 \0 \0 307 322 \0 \0 K 323 \0 \0 0098368 307 322 \0 \0 K 323 \0 \0 307 322 \0 \0 K 323 \0 \0 * 0098400 307 322 \0 \0 K 323 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0098416 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099696 \0 \0 \0 \0 224 271 \0 \0 361 003 \0 \0 _ \0 \0 \0 0099712 022 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 004 \0 \0 0099728 272 @ ) ? 204 003 \0 \0 036 \0 \0 \0 \0 \0 \0 \0 0099744 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099840 Quote Link to comment
Joe L. Posted January 8, 2013 Share Posted January 8, 2013 All three disks seem to have the same string "EFI PART" indicating a GUID partition. Your situation is different than others I've helped. You did not find the "ReIsEr2Fs" string I expected to find in the first 195 blocks on the disk. (It is that same string of characters that helps to identify the superblock when mounting the drives, so it being missing on the two drives < 2.2TB is why they are not mounting.) I would send an e-mail to [email protected] and ask he look over this thread and your output. One thing you could do is change the command slightly to see if the reiserfs string exists further into the disk. Instead of limiting the "dd" command to 195 blocks, make it a larger number (1000 blocks perhaps) See if the string "ReIsEr2Fs" shows up anywhere. It almost looks as if your disk controller (or unRAID in the absence of a readable super.dat) has written a EFI PART signature at address 512 on the disks. Did you preclear these disks before putting them in the array, or were they used in a different OS? I've never seen a "EFI PART" identification string. If you run the "dd" command on those disks that do mount (and are under 2.2TB), does it also show a EFI PART string? Joe L. Quote Link to comment
block134 Posted January 8, 2013 Author Share Posted January 8, 2013 All of my disks were plecleared and Unraid seen them that way when I first installed them. I had a couple of them that didn't seem to clear right though. When I ran the script over night the window on my windows machine was closed the next day. I am not sure which drives those were though but it maybe the 2 TBs that I am having problems with. I will try to modify dd to show more information. One of the drives I tried, dont remember which one, i changed the device to sdx1 and I seen the Reiser info there. I will have t try that again when I get home today. Quote Link to comment
block134 Posted January 8, 2013 Author Share Posted January 8, 2013 With the DD command set to 1000 SDB 2TB 0110640 r \0 002 \0 R e I s E r 2 F s \0 \0 \0 SDC 3TB 0225328 006 \0 002 \0 R e I s E r 2 F s \0 \0 \0 SDG 2TB 0249904 002 \0 002 \0 R e I s E r 2 F s \0 \0 \0 Last night I ran your script Joe L, unraid partion disk, on SDB it said that it set the start to 63 vice 64 like it was but the drive still shows unformated. My other three drives that mount give me this 0098352 002 \0 001 \0 R e I s E r 2 F s \0 \0 \0 Quote Link to comment
block134 Posted January 13, 2013 Author Share Posted January 13, 2013 I am at a stand still right as to what else I can do for this. Everything I have found and tried hasn't helped to make the drives usable again. Right now I am fine with finding a way to pull the data off the drives and trying to preclear them again but I haven found anything that will help me with that either. I have also sent an email to [email protected] but haven't received a reply yet. So far what I have done is everything in this post. I have pulled the three drives giving me problems out of my main server and put them into another computer that I am using to troubleshoot this. I have also tried to use mkmbr and the utility that Joe L. made as is discussed here http://lime-technology.com/forum/index.php?topic=15385.msg144822#msg144822. I can change the partion start to either 63 or 64 but after a server reboot they still show unformatted. Right now I am only working with the two 2TB drives since all the guides I have found talk about working with 2.2TBs and smaller. Quote Link to comment
Joe L. Posted January 13, 2013 Share Posted January 13, 2013 I am at a stand still right as to what else I can do for this. Everything I have found and tried hasn't helped to make the drives usable again. Right now I am fine with finding a way to pull the data off the drives and trying to preclear them again but I haven found anything that will help me with that either. I have also sent an email to [email protected] but haven't received a reply yet. So far what I have done is everything in this post. I have pulled the three drives giving me problems out of my main server and put them into another computer that I am using to troubleshoot this. I have also tried to use mkmbr and the utility that Joe L. made as is discussed here http://lime-technology.com/forum/index.php?topic=15385.msg144822#msg144822. I can change the partion start to either 63 or 64 but after a server reboot they still show unformatted. Right now I am only working with the two 2TB drives since all the guides I have found talk about working with 2.2TBs and smaller. Have you made contact with Tom at limetech? To me, it seems like the MBRs have been re-written. The file-system is not what is expected. Do you have a spare disk, not in the array (of equivalent size) to make an exact copy for recovery experimentation? Quote Link to comment
block134 Posted January 13, 2013 Author Share Posted January 13, 2013 I have a 2TB that has been precleared and can be used for this. Quote Link to comment
Joe L. Posted January 13, 2013 Share Posted January 13, 2013 I have a 2TB that has been precleared and can be used for this. ok, the basic command to fully copy one disk to another is dd if=/dev/sdX of=/dev/sdZ bs=1M where sdX = the disk being copied from and sdZ = the disk being copied to (the precleared 2TB) Once the disk is copied we can experiment with the copy without risking the original. (it will take probably 6 or more hours to perform the copy) Just make absolutely certain you have the correct device name for the disk you are copying to. The "dd" command will completely wipe the target disk's contents and replace it with that of the source disk. (the target disk will not longer be pre-cleared) Perform the copy from the system console, or invoke it in a telnet session you can keep open. It will stop when completed with a message of how many blocks were copied. It does not show progress marks as it copies. You just not get a prompt back until it is done. Joe L. Quote Link to comment
block134 Posted January 14, 2013 Author Share Posted January 14, 2013 I have one of the 2TB drives coping to the precleared drive, it should hopefully be done in the morning. Quote Link to comment
block134 Posted January 14, 2013 Author Share Posted January 14, 2013 The copy is done. Quote Link to comment
Joe L. Posted January 14, 2013 Share Posted January 14, 2013 The copy is done. ok, now we can play with the copy. First step is to attempt to re-construct the superblock. I'd you like to reset the partition start to sector 63 first, UNLESS you are very sure it was created as 4k-aligned originally. (in which case, it should be set to sector 64) If you had originally pre-cleared the source data disk, the preclear_report should still be in your /boot/preclear_reports directory. This may help you to remember how it was originally partitioned. Then, we'll try first reiserfsck --check /dev/sdZ1 (the device name with a trailing "1" (/dev/sdZ1) is the first partition on the disk you copied to) It will probably complain of a missing superblock, Then, you re-build the superblock with reiserfsck --rebuild-sb /dev/sdZ1 the answers to its prompts should be as in this example: 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/sdZ1. what the version of ReiserFS do you use[1-4] (1) 3.6.x (2) >=3.5.9 (introduced in the middle of 1999) (if you use linux 2.2,choose this one) (3) < 3.5.9 converted to new format (don't choose if unsure) (4) < 3.5.9 (this is very old format, don't choose if unsure) (X) exit 1 Enter block size [4096]: 4096 No journal device was specified. (If journal is not available, re-run with --no-journal-available option specified). Is journal default? (y/n)[y]: y Did you use resizer(y/n)[n]: n rebuild-sb: no uuid found, a new uuid was generated (96a8d67e-755d-4702-a964-0f5df171320f) rebuild-sb: You either have a corrupted journal or have just changed the start of the partition with some partition table editor. If you are sure that the start of the partition is ok, rebuild the journal header. Do you want to rebuild the journal header? (y/n)[n]: y Then, you can try another reiserfsck --fix-fixable /dev/sdZ1 which will then hopefully tell you what to use next. (probably a --rebuild-tree) In any case, this will all be on the copy of the data disk, so your original is unchanged until you figure out what to do for recovery. Joe L. Quote Link to comment
block134 Posted January 14, 2013 Author Share Posted January 14, 2013 When I did reiserfsck --fix-fixable /dev/sda1 I got an error Bad root block 0. (--rebuild-tree did not complete) aborted reiserfsck --check /dev/md1 gives me the same error now. Quote Link to comment
Joe L. Posted January 15, 2013 Share Posted January 15, 2013 When I did reiserfsck --fix-fixable /dev/sda1 I got an error Bad root block 0. (--rebuild-tree did not complete) aborted reiserfsck --check /dev/md1 gives me the same error now. Did you rebuild the superblock first? Quote Link to comment
block134 Posted January 15, 2013 Author Share Posted January 15, 2013 The first thing I did was set the start to 64 and then did a reiserfsck --check /dev/sda1 which told me I had a bad super block so I did reiserfsck --rebuild-sb /dev/sda1 which came back with no errors. After that I did reiserfsck --fix-fixable /dev/sda1 which gave me the errors. If I run reiserfsck --check /dev/sda1 again I dont get a super block error anymore I get Bad root block 0. (--rebuild-tree did not complete) aborted Quote Link to comment
Joe L. Posted January 15, 2013 Share Posted January 15, 2013 The first thing I did was set the start to 64 and then did a reiserfsck --check /dev/sda1 which told me I had a bad super block so I did reiserfsck --rebuild-sb /dev/sda1 which came back with no errors. After that I did reiserfsck --fix-fixable /dev/sda1 which gave me the errors. If I run reiserfsck --check /dev/sda1 again I dont get a super block error anymore I get Bad root block 0. (--rebuild-tree did not complete) aborted ok, so I guess it is time to let a rebuild-tree complete. Let's try reiserfsck --rebuild-tree /dev/sda1 now. Quote Link to comment
block134 Posted January 16, 2013 Author Share Posted January 16, 2013 The reiserfsck --rebuild-tree /dev/sda1 command finished fixing the drive. Unraid can now mount that drive and see all the files that were there. I guess I should probably set the SB start on my other 2TB drive and follow that by a reiserfsck --rebuild-sb /dev/sdZ1. After that a reiserfsck --rebuild-tree /dev/sdX1 should finish fixing it. Not sure what I would do with my 3TB to set the SB start if it needs it since it suppose to start at 1 if I did my research right. Everything I have read talks about working with 2.2 TB and smaller and setting the start to either 63 or 64. Quote Link to comment
Joe L. Posted January 16, 2013 Share Posted January 16, 2013 The reiserfsck --rebuild-tree /dev/sda1 command finished fixing the drive. Unraid can now mount that drive and see all the files that were there. Excellent!!!! I guess I should probably set the SB start on my other 2TB drive and follow that by a reiserfsck --rebuild-sb /dev/sdZ1. After that a reiserfsck --rebuild-tree /dev/sdX1 should finish fixing it. Not sure what I would do with my 3TB to set the SB start if it needs it since it suppose to start at 1 if I did my research right. Corrrect. The 3TB we'll need to handle a bit differently. It is supposed to have a protective MBR starting at sector 1. (not 64, or 63) Everything I have read talks about working with 2.2 TB and smaller and setting the start to either 63 or 64. Correct. I'll go back and look at the "dd" output from it . In the interim, you can get the 2TB drives back to where they mount. What we'll probably need to do is use the GPT partition as it is. But... I have no experience in recovering from a 3TB drive. All we can do is get the partition correct first and then run the reiserfsck steps. Joe L. Quote Link to comment
gfjardim Posted January 17, 2013 Share Posted January 17, 2013 block134, did you use those disks elsewhere before using them on your unRAID server? I still have two GPT formatted 1TB drives on my array, initiated that way by an LSI RAID5 card. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.