Critical Posted June 9, 2013 Share Posted June 9, 2013 I upgraded one of my drives and now it is showing as unformatted. I have rebooted the server it shows the same thing. All of the drives are green including parity. I am using unraid v5rc13. The disk is not showing up in explorer but all others are. Anyone have any suggestions on how to get the drive working. The disk settings show as mbr unaligned and file system type as unknown... Quote Link to comment
Joe L. Posted June 10, 2013 Share Posted June 10, 2013 I upgraded one of my drives and now it is showing as unformatted. I have rebooted the server it shows the same thing. All of the drives are green including parity. I am using unraid v5rc13. The disk is not showing up in explorer but all others are. Anyone have any suggestions on how to get the drive working. The disk settings show as mbr unaligned and file system type as unknown... Attach a syslog to your next post. DO NOT format the disk. To unRAID, any disk it cannot mount is unformatted. You'll probably need t check the file-system on the disk that will not mount. something like this (pretending the disk is disk5 for this example) reiserfsck --check /dev/md5 use /dev/md1 if disk1, /dev/md9 if disk9, /dev/md20 if disk20, etc Quote Link to comment
Critical Posted June 10, 2013 Author Share Posted June 10, 2013 I upgraded one of my drives and now it is showing as unformatted. I have rebooted the server it shows the same thing. All of the drives are green including parity. I am using unraid v5rc13. The disk is not showing up in explorer but all others are. Anyone have any suggestions on how to get the drive working. The disk settings show as mbr unaligned and file system type as unknown... Attach a syslog to your next post. DO NOT format the disk. To unRAID, any disk it cannot mount is unformatted. You'll probably need t check the file-system on the disk that will not mount. something like this (pretending the disk is disk5 for this example) reiserfsck --check /dev/md5 use /dev/md1 if disk1, /dev/md9 if disk9, /dev/md20 if disk20, etc I have attached my system log... The reiserfsck states: reiserfs_open: the reiserfs superblock cannot be found on /dev/md3. Failed to open the filesystem. Any ideas? syslog.txt Quote Link to comment
Joe L. Posted June 10, 2013 Share Posted June 10, 2013 It appears as if disk 3 is: Jun 9 19:37:22 Tower kernel: md: import disk3: [8,112] (sdh) WDC_WD20EARX-00PASB0_WD-WCAZAK100188 size: 1953514552 You said the disk setting shows mbr-unalligned... Let's see what is actually there on the disk by typing the following: dd if=/dev/sdh count=195 | od -c -A d | sed 30q The output should look a lot like this... Note where the string "R e I s E r 2 F s" appears.... Let's see if yours is at the same address, or one sector further. Output on one of my drives looks like this (it has a file-system starting on sector 63): 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 0.00169403 s, 58.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 361 _ 8 : \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 * 0097792 376 \v G \a e \a - \0 \a 212 267 001 022 \0 \0 \0 0097808 \0 \0 \0 \0 \0 \0 \0 \0 004 \0 \0 % 254 227 \ 0097824 204 003 \0 \0 036 \0 \0 \0 \0 \0 \0 \0 \0 020 314 003 0097840 220 \0 002 \0 R e I s E r 2 F s \0 \0 \0 0097856 003 \0 \0 \0 005 \0 217 016 002 \0 \0 \0 204 ] \0 \0 0097872 001 \0 \0 \0 353 300 256 263 242 347 N 347 264 362 315 364 0097888 345 V 253 366 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0097904 \0 \0 \0 \0 \a \0 036 \0 255 262 303 M \0 N 355 \0 0097920 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 We are expecting the line with R e I s E r 2 F s to appear at address 0097840 (if MBR-un-alligned) or 512 bytes further (if MBR-4k-alligned) To assist in the analysis, also post the output of fdisk -lu /dev/sdh Joe L. Quote Link to comment
Critical Posted June 11, 2013 Author Share Posted June 11, 2013 Here is the output from the command line entries... I dont see the reiserf2 statement anywhere.. Is my data still safe since my parity drive is in tact? output.txt Quote Link to comment
Critical Posted June 11, 2013 Author Share Posted June 11, 2013 Also ran with this command dd if=/dev/sdh count=1000 | od -c -A d | sed '/R e I s E r 2 F s/q' and found the reiser2fs at the location at the bottom of this: 0123184 275 004 267 342 276 262 q 261 232 361 { 305 j 257 m x 0123200 360 207 261 232 361 Y 272 312 o 210 376 276 3 ~ 331 j 0123216 270 243 227 305 037 316 0 f + 022 303 326 330 l 021 327 0123232 227 212 003 357 264 3 025 367 236 025 357 ~ " 024 261 / 0123248 376 342 217 212 ? ~ > b 025 212 335 363 034 f ( 350 0123264 351 212 305 342 200 325 8 240 305 ~ h 376 M ^ 273 257 0123280 306 \b E b 274 Q 266 | 276 P 247 023 353 234 361 F 0123296 364 356 361 G 327 E 021 237 9 373 245 357 216 375 z 342 0123312 ! = 373 365 023 004 367 247 w 373 234 H S U 266 355 0123328 212 357 305 006 332 373 202 321 ! 001 / S v x 341 b 0123344 341 234 a 270 } 230 252 l 204 364 300 212 036 030 255 0123360 336 370 022 : _ % 321 336 374 327 031 R 032 235 230 e 0123376 226 373 { 017 224 m 3 S 036 255 v 0 016 246 \r 261 0123392 1 203 334 311 034 ) 323 F 244 \t 177 315 225 233 370 331 0123408 223 221 r x T f 340 377 247 337 p r | 325 327 340 0123424 224 * 024 313 3 366 266 262 W 255 354 \n \a z 227 375 0123440 301 9 006 t 301 325 324 332 206 266 x \0 367 366 R Q 0123456 F 373 230 q Z 8 372 217 r 254 020 306 g \0 003 342 0123472 265 035 ^ 311 8 317 352 264 237 207 262 377 \r 210 030 330 0123488 ` | 231 357 036 371 375 n 267 323 H 330 233 312 362 | 0123504 270 333 \ @ 361 232 E 216 [ < 9 326 323 s 224 323 0123520 U 315 262 \f c 024 ; 270 253 274 334 275 y 205 214 243 0123536 321 237 226 g 353 331 o 362 F k 313 215 326 374 ^ 371 0123552 020 314 Q 351 266 037 > # 9 | 272 273 x ~ 210 336 0123568 < 226 251 365 034 o 343 $ { 347 274 i 017 177 226 220 0123584 332 < 345 034 e 1 @ 307 037 [ 341 6 224 315 005 203 0123600 031 \b 023 001 006 033 017 ! 312 4 340 207 323 321 \0 0123616 001 I c 200 017 w / 331 204 257 ; 243 + 305 262 V 0123632 202 300 376 037 031 j ) 254 P 033 272 205 301 352 375 0123648 j 006 247 374 254 257 271 8 S 025 336 372 212 373 376 364 0123664 022 355 357 334 ~ 343 210 . 357 212 323 326 325 227 ; 005 0123680 032 } 027 z 211 324 254 U ? u 311 220 023 342 ? g 0123696 ~ 374 321 236 252 374 _ 333 ~ 343 8 217 276 375 q q 0123712 003 374 a 212 233 " 346 314 | 315 234 277 L ~ 252 267 0123728 ] 372 223 366 z b 274 346 \b 326 265 274 P 032 ~ Q 0123744 ! 033 / 372 247 255 313 031 ] 305 k 323 335 T 264 342 0123760 \a " 273 357 s 377 342 374 203 1 ' 365 s y 256 317 0123776 257 E 031 226 2 u 335 361 @ u L P 177 + " 367 0123792 c 310 ) 257 ~ v % i 367 273 377 306 o 313 J 335 0123808 361 F _ 271 305 361 f 020 j 237 273 251 255 { 325 276 0123824 242 1 Z O 321 \ 027 003 220 200 216 373 275 ] 300 230 0123840 233 . 006 240 + F ` 330 023 303 303 $ \v 002 267 233 0123856 214 326 0 035 x 255 324 354 320 030 . 244 036 # 370 X 0123872 351 212 ; Q # 222 W C 022 ` R 341 q C \r H 0123888 376 e 337 371 e _ X 3 ^ 263 315 277 Q 213 e O 0123904 A - u 303 243 205 323 270 Q 342 _ # 030 , 220 0123920 036 8 322 - N 233 O K 273 245 n d \ 203 ) O 0123936 236 K 212 325 324 230 273 245 365 031 b 261 316 177 ' 250 0123952 271 ) 232 ; h 364 Q 016 016 7 306 ) 2 271 c 1 0123968 C | \ H ~ ( g 314 S 027 6 O 205 = 275 r 0123984 374 I 357 302 336 / 361 s 204 G 253 U ] 267 { 367 0124000 302 344 035 b 203 | \ W 275 311 231 330 R 205 353 027 0124016 n 372 236 / 357 325 265 035 031 h z / $ e 003 337 0124032 & 322 , 031 375 267 313 307 350 315 270 ^ 226 [ 031 001 0124048 230 [ 031 001 231 [ 031 001 232 [ 031 001 233 [ 031 001 0124064 234 [ 031 001 235 [ 031 001 236 [ 031 001 237 [ 031 001 0124080 240 [ 031 001 241 [ 031 001 242 [ 031 001 243 [ 031 001 0124096 244 [ 031 001 245 [ 031 001 246 [ 031 001 247 [ 031 001 0124112 250 [ 031 001 251 [ 031 001 252 [ 031 001 253 [ 031 001 0124128 254 [ 031 001 255 [ 031 001 256 [ 031 001 257 [ 031 001 0124144 260 [ 031 001 261 [ 031 001 262 [ 031 001 263 [ 031 001 0124160 264 [ 031 001 265 [ 031 001 266 [ 031 001 267 [ 031 001 0124176 270 [ 031 001 271 [ 031 001 272 [ 031 001 273 [ 031 001 0124192 274 [ 031 001 275 [ 031 001 276 [ 031 001 277 [ 031 001 0124208 300 [ 031 001 301 [ 031 001 302 [ 031 001 303 [ 031 001 0124224 304 [ 031 001 305 [ 031 001 306 [ 031 001 307 [ 031 001 0124240 310 [ 031 001 311 [ 031 001 312 [ 031 001 313 [ 031 001 0124256 314 [ 031 001 315 [ 031 001 316 [ 031 001 317 [ 031 001 0124272 320 [ 031 001 321 [ 031 001 322 [ 031 001 323 [ 031 001 0124288 324 [ 031 001 325 [ 031 001 326 [ 031 001 327 [ 031 001 0124304 330 [ 031 001 331 [ 031 001 332 [ 031 001 333 [ 031 001 0124320 334 [ 031 001 335 [ 031 001 336 [ 031 001 337 [ 031 001 0124336 340 [ 031 001 341 [ 031 001 342 [ 031 001 343 [ 031 001 0124352 344 [ 031 001 345 [ 031 001 346 [ 031 001 347 [ 031 001 0124368 350 [ 031 001 351 [ 031 001 352 [ 031 001 353 [ 031 001 0124384 354 [ 031 001 355 [ 031 001 356 [ 031 001 357 [ 031 001 0124400 360 [ 031 001 361 [ 031 001 362 [ 031 001 363 [ 031 001 0124416 364 [ 031 001 365 [ 031 001 366 [ 031 001 367 [ 031 001 0124432 370 [ 031 001 371 [ 031 001 372 [ 031 001 373 [ 031 001 0124448 374 [ 031 001 375 [ 031 001 376 [ 031 001 377 [ 031 001 0124464 \0 \ 031 001 001 \ 031 001 002 \ 031 001 003 \ 031 001 0124480 004 \ 031 001 005 \ 031 001 006 \ 031 001 \a \ 031 001 0124496 \b \ 031 001 \t \ 031 001 \n \ 031 001 \v \ 031 001 0124512 \f \ 031 001 \r \ 031 001 016 \ 031 001 017 \ 031 001 0124528 020 \ 031 001 021 \ 031 001 022 \ 031 001 023 \ 031 001 0124544 024 \ 031 001 025 \ 031 001 026 \ 031 001 027 \ 031 001 0124560 030 \ 031 001 031 \ 031 001 032 \ 031 001 033 \ 031 001 0124576 034 \ 031 001 035 \ 031 001 036 \ 031 001 037 \ 031 001 0124592 \ 031 001 ! \ 031 001 " \ 031 001 # \ 031 001 0124608 $ \ 031 001 % \ 031 001 & \ 031 001 ' \ 031 001 0124624 ( \ 031 001 ) \ 031 001 * \ 031 001 + \ 031 001 0124640 , \ 031 001 - \ 031 001 . \ 031 001 / \ 031 001 0124656 0 \ 031 001 1 \ 031 001 2 \ 031 001 3 \ 031 001 0124672 4 \ 031 001 5 \ 031 001 6 \ 031 001 7 \ 031 001 0124688 8 \ 031 001 9 \ 031 001 : \ 031 001 ; \ 031 001 0124704 < \ 031 001 = \ 031 001 > \ 031 001 ? \ 031 001 0124720 @ \ 031 001 A \ 031 001 B \ 031 001 C \ 031 001 0124736 D \ 031 001 E \ 031 001 F \ 031 001 G \ 031 001 0124752 H \ 031 001 I \ 031 001 J \ 031 001 K \ 031 001 0124768 L \ 031 001 M \ 031 001 N \ 031 001 O \ 031 001 0124784 P \ 031 001 Q \ 031 001 R \ 031 001 S \ 031 001 0124800 T \ 031 001 U \ 031 001 V \ 031 001 W \ 031 001 0124816 X \ 031 001 Y \ 031 001 Z \ 031 001 [ \ 031 001 0124832 \ \ 031 001 ] \ 031 001 ^ \ 031 001 _ \ 031 001 0124848 ` \ 031 001 a \ 031 001 b \ 031 001 c \ 031 001 0124864 d \ 031 001 e \ 031 001 f \ 031 001 g \ 031 001 0124880 h \ 031 001 i \ 031 001 j \ 031 001 k \ 031 001 0124896 l \ 031 001 m \ 031 001 n \ 031 001 o \ 031 001 0124912 p \ 031 001 q \ 031 001 r \ 031 001 s \ 031 001 0124928 t \ 031 001 u \ 031 001 v \ 031 001 w \ 031 001 0124944 x \ 031 001 y \ 031 001 z \ 031 001 { \ 031 001 0124960 | \ 031 001 } \ 031 001 ~ \ 031 001 177 \ 031 001 0124976 200 \ 031 001 201 \ 031 001 202 \ 031 001 203 \ 031 001 0124992 204 \ 031 001 205 \ 031 001 206 \ 031 001 207 \ 031 001 0125008 210 \ 031 001 211 \ 031 001 212 \ 031 001 213 \ 031 001 0125024 214 \ 031 001 215 \ 031 001 216 \ 031 001 217 \ 031 001 0125040 220 \ 031 001 221 \ 031 001 222 \ 031 001 223 \ 031 001 0125056 224 \ 031 001 225 \ 031 001 226 \ 031 001 227 \ 031 001 0125072 230 \ 031 001 231 \ 031 001 232 \ 031 001 233 \ 031 001 0125088 234 \ 031 001 235 \ 031 001 236 \ 031 001 237 \ 031 001 0125104 240 \ 031 001 241 \ 031 001 242 \ 031 001 243 \ 031 001 0125120 244 \ 031 001 245 \ 031 001 246 \ 031 001 247 \ 031 001 0125136 250 \ 031 001 251 \ 031 001 252 \ 031 001 253 \ 031 001 0125152 254 \ 031 001 255 \ 031 001 256 \ 031 001 257 \ 031 001 0125168 260 \ 031 001 261 \ 031 001 262 \ 031 001 263 \ 031 001 0125184 264 \ 031 001 265 \ 031 001 266 \ 031 001 267 \ 031 001 0125200 270 \ 031 001 271 \ 031 001 272 \ 031 001 273 \ 031 001 0125216 274 \ 031 001 275 \ 031 001 276 \ 031 001 277 \ 031 001 0125232 300 \ 031 001 301 \ 031 001 302 \ 031 001 303 \ 031 001 0125248 304 \ 031 001 305 \ 031 001 306 \ 031 001 307 \ 031 001 0125264 310 \ 031 001 311 \ 031 001 312 \ 031 001 313 \ 031 001 0125280 314 \ 031 001 315 \ 031 001 316 \ 031 001 317 \ 031 001 0125296 320 \ 031 001 321 \ 031 001 322 \ 031 001 323 \ 031 001 0125312 324 \ 031 001 325 \ 031 001 326 \ 031 001 327 \ 031 001 0125328 330 \ 031 001 331 \ 031 001 332 \ 031 001 333 \ 031 001 0125344 334 \ 031 001 335 \ 031 001 336 \ 031 001 337 \ 031 001 0125360 340 \ 031 001 341 \ 031 001 342 \ 031 001 343 \ 031 001 0125376 344 \ 031 001 345 \ 031 001 346 \ 031 001 347 \ 031 001 0125392 350 \ 031 001 351 \ 031 001 352 \ 031 001 353 \ 031 001 0125408 354 \ 031 001 355 \ 031 001 356 \ 031 001 357 \ 031 001 0125424 360 \ 031 001 361 \ 031 001 362 \ 031 001 363 \ 031 001 0125440 364 \ 031 001 365 \ 031 001 366 \ 031 001 367 \ 031 001 0125456 370 \ 031 001 371 \ 031 001 372 \ 031 001 373 \ 031 001 0125472 374 \ 031 001 375 \ 031 001 376 \ 031 001 377 \ 031 001 0125488 \0 ] 031 001 001 ] 031 001 002 ] 031 001 003 ] 031 001 0125504 004 ] 031 001 005 ] 031 001 006 ] 031 001 \a ] 031 001 0125520 \b ] 031 001 \t ] 031 001 \n ] 031 001 \v ] 031 001 0125536 \f ] 031 001 \r ] 031 001 016 ] 031 001 017 ] 031 001 0125552 020 ] 031 001 021 ] 031 001 022 ] 031 001 023 ] 031 001 0125568 024 ] 031 001 025 ] 031 001 026 ] 031 001 027 ] 031 001 0125584 030 ] 031 001 031 ] 031 001 032 ] 031 001 033 ] 031 001 0125600 034 ] 031 001 035 ] 031 001 036 ] 031 001 037 ] 031 001 0125616 ] 031 001 ! ] 031 001 " ] 031 001 # ] 031 001 0125632 $ ] 031 001 % ] 031 001 & ] 031 001 ' ] 031 001 0125648 ( ] 031 001 ) ] 031 001 * ] 031 001 + ] 031 001 0125664 , ] 031 001 - ] 031 001 . ] 031 001 / ] 031 001 0125680 0 ] 031 001 1 ] 031 001 2 ] 031 001 3 ] 031 001 0125696 4 ] 031 001 5 ] 031 001 6 ] 031 001 7 ] 031 001 0125712 8 ] 031 001 9 ] 031 001 : ] 031 001 ; ] 031 001 0125728 < ] 031 001 = ] 031 001 > ] 031 001 ? ] 031 001 0125744 @ ] 031 001 A ] 031 001 B ] 031 001 C ] 031 001 0125760 D ] 031 001 E ] 031 001 F ] 031 001 G ] 031 001 0125776 H ] 031 001 I ] 031 001 J ] 031 001 K ] 031 001 0125792 L ] 031 001 M ] 031 001 N ] 031 001 O ] 031 001 0125808 P ] 031 001 Q ] 031 001 R ] 031 001 S ] 031 001 0125824 T ] 031 001 U ] 031 001 V ] 031 001 W ] 031 001 0125840 X ] 031 001 Y ] 031 001 Z ] 031 001 [ ] 031 001 0125856 \ ] 031 001 ] ] 031 001 ^ ] 031 001 _ ] 031 001 0125872 ` ] 031 001 a ] 031 001 b ] 031 001 c ] 031 001 0125888 d ] 031 001 e ] 031 001 f ] 031 001 g ] 031 001 0125904 h ] 031 001 i ] 031 001 j ] 031 001 k ] 031 001 0125920 l ] 031 001 m ] 031 001 n ] 031 001 o ] 031 001 0125936 p ] 031 001 q ] 031 001 r ] 031 001 s ] 031 001 0125952 t ] 031 001 u ] 031 001 v ] 031 001 w ] 031 001 0125968 x ] 031 001 y ] 031 001 z ] 031 001 { ] 031 001 0125984 | ] 031 001 } ] 031 001 ~ ] 031 001 177 ] 031 001 0126000 200 ] 031 001 201 ] 031 001 202 ] 031 001 203 ] 031 001 0126016 204 ] 031 001 205 ] 031 001 206 ] 031 001 207 ] 031 001 0126032 210 ] 031 001 211 ] 031 001 212 ] 031 001 213 ] 031 001 0126048 214 ] 031 001 215 ] 031 001 216 ] 031 001 217 ] 031 001 0126064 220 ] 031 001 221 ] 031 001 222 ] 031 001 223 ] 031 001 0126080 224 ] 031 001 225 ] 031 001 226 ] 031 001 227 ] 031 001 0126096 230 ] 031 001 231 ] 031 001 232 ] 031 001 233 ] 031 001 0126112 234 ] 031 001 235 ] 031 001 236 ] 031 001 237 ] 031 001 0126128 240 ] 031 001 231 q D 002 232 q D 002 233 q D 002 0126144 234 q D 002 235 q D 002 236 q D 002 237 q D 002 0126160 240 q D 002 241 q D 002 242 q D 002 243 q D 002 0126176 244 q D 002 245 q D 002 247 q D 002 250 q D 002 0126192 251 q D 002 252 q D 002 253 q D 002 254 q D 002 0126208 255 q D 002 256 q D 002 257 q D 002 260 q D 002 0126224 261 q D 002 262 q D 002 263 q D 002 264 q D 002 0126240 265 q D 002 266 q D 002 267 q D 002 270 q D 002 0126256 271 q D 002 272 q D 002 273 q D 002 274 q D 002 0126272 275 q D 002 276 q D 002 277 q D 002 300 q D 002 0126288 301 q D 002 302 q D 002 303 q D 002 304 q D 002 0126304 305 q D 002 306 q D 002 307 q D 002 310 q D 002 0126320 311 q D 002 312 q D 002 313 q D 002 314 q D 002 0126336 315 q D 002 316 q D 002 317 q D 002 320 q D 002 0126352 321 q D 002 322 q D 002 323 q D 002 324 q D 002 0126368 325 q D 002 326 q D 002 327 q D 002 330 q D 002 0126384 331 q D 002 332 q D 002 333 q D 002 334 q D 002 0126400 335 q D 002 336 q D 002 337 q D 002 340 q D 002 0126416 341 q D 002 342 q D 002 343 q D 002 344 q D 002 0126432 345 q D 002 346 q D 002 347 q D 002 350 q D 002 0126448 351 q D 002 352 q D 002 353 q D 002 354 q D 002 0126464 t L \f \0 \t \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0126480 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0130560 u L \f \0 \b \0 \0 \0 376 \0 \0 \0 \0 \0 327 025 0130576 020 \0 \0 \0 } 021 327 025 5 / ~ \v A 256 j 025 0130592 i 025 327 025 k 031 327 025 & 230 345 016 \0 \0 \0 \0 0130608 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0134640 \0 \0 \0 \0 R e I s E r L B \0 \0 \0 \0 0134656 377 377 377 377 377 377 377 377 377 377 377 377 377 377 377 377 * 0135536 377 377 377 377 377 377 377 377 037 \0 \0 \0 \0 \0 \0 \0 0135552 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0138752 016 021 034 035 N 223 D \a 024 \0 c \0 022 \0 \0 \0 0138768 \0 \0 \0 \0 \0 \0 \0 \0 004 \0 \0 347 241 222 ( 0138784 204 003 \0 \0 036 \0 \0 \0 \0 \0 \0 \0 \0 020 314 003 0138800 334 002 002 \0 R e I s E r 2 F s \0 \0 \0 Quote Link to comment
Joe L. Posted June 11, 2013 Share Posted June 11, 2013 Here is the output from the command line entries... I dont see the reiserf2 statement anywhere.. Is my data still safe since my parity drive is in tact? I really can't answer that question, since if something overwrote the superblock AND parity was updated with it, then both will have the same contents. You can;t easily tell without un-assigning, or disconnecting disk3 so parity is used to re-construct the disk whose superblock contents apparently have been mangled. If you decide to try, do it this way so you can easily get back to the same status as now. Stop the array Copy the config/super.dat file to config/super.orig cp /boot/config/super.dat /boot/config/super.orig With the array stopped, un-plug disk3. (or un-assign it) Start the array If the disk mounts and the data on it is accessible, then parity is able to reconstruct it. You are in luck. If not, try the same "dd" commands, but this time on /dev/md3 The "Reiserfs" string should appear pretty close to the beginning of output. Odds are it will not if the disk could not be mounted. Now, you can stop the array once more and then re-connect the drive (r-reassign it) Before you re-start the array, copy the super.orig file back to super.dat cp /boot/config/super.orig /boot/config/super.dat DO NOT RE-START THE ARRAY, BUT INSTEAD type reboot The reboot is to let emhttp see the original super.dat file once more and be un-aware of your experiment in disconnecting/unassigning it. Since the snapshot copy was taken with the array cleanly stopped, it should have no issues when you reboot. (the disk will probably still not mount, but that is a different issue because of the corrupted superblock) Quote Link to comment
Critical Posted June 11, 2013 Author Share Posted June 11, 2013 ok.. so its not in parity because disk3 does not show up when I disconnect the drive and start the array back up again. What do I do next to get this drive back up and running? Update: Something real scary happened last night.. After I rebooted the system a couple of times the drive stopped showing up in the BiOS on system startup and it was not showing in unraid... I went to bed pissoed off but to my surprise it showed up again this morning in the bios.. I just bought this drive 2 weeks ago.. what do I need to do to save the data ... Its 1.5TB of collected data over many years.. HELP!! Quote Link to comment
Joe L. Posted June 11, 2013 Share Posted June 11, 2013 ok.. so its not in parity because disk3 does not show up when I disconnect the drive and start the array back up again. What do I do next to get this drive back up and running? Update: Something real scary happened last night.. After I rebooted the system a couple of times the drive stopped showing up in the BiOS on system startup and it was not showing in unraid... I went to bed pissoed off but to my surprise it showed up again this morning in the bios.. I just bought this drive 2 weeks ago.. what do I need to do to save the data ... Its 1.5TB of collected data over many years.. HELP!! First, if the data is really precious I'd copy the entire disk to a replacement and then perform the file-system recovery on the replacement. That way the original can be left as is. You'll need to rebuild the superblock, and then rebuild the file-tree. as far as 1.5TB of precious data... unRAID is NOT a backup for precious data, no RAID array is. A backup is another copy, preferably off-site. Do you have a spare disk of equal or larger size? I'd send a note to Tom @ Lime-technology. He might have some ideas. From what you described you replaced a smaller disk with a larger one and unRAID reconstructed the old disk onto the newer one and somehow did not rebuild a valid superblock. Point Tom at this thread.. Joe L. Quote Link to comment
Critical Posted June 11, 2013 Author Share Posted June 11, 2013 I have a new 3tb disk.. unused.. how I do the copy through the linux commandlines.. do I need to do something to prepare the 3tb disk before I copy? Quote Link to comment
Joe L. Posted June 11, 2013 Share Posted June 11, 2013 I have a new 3tb disk.. unused.. how I do the copy through the linux commandlines.. do I need to do something to prepare the 3tb disk before I copy? No, no need to do anything to it other than to know its correct device name. To copy the existing disk to the spare you would type (make sure you have the right "if=source" and more importantly, the correct "of=destination") dd bs=1M oflag=noerror if=/dev/sdh of=/dev/sdX It will take 6 or more hours to perform the copy. This is a blind copy... it will copy byte by byte to the 3TB disk. It will copy the smaller disk's partition table, so it will appear as if it is a 2TB partition even though the disk is bigger. Then, you can attempt to re-create the superblock and re-build the file-tree in the 3TB drive's first partition ( /dev/sdX1 ) and access the files there. Joe L. Quote Link to comment
Critical Posted June 13, 2013 Author Share Posted June 13, 2013 I have a new 3tb disk.. unused.. how I do the copy through the linux commandlines.. do I need to do something to prepare the 3tb disk before I copy? No, no need to do anything to it other than to know its correct device name. To copy the existing disk to the spare you would type (make sure you have the right "if=source" and more importantly, the correct "of=destination") dd bs=1M oflag=noerror if=/dev/sdh of=/dev/sdX It will take 6 or more hours to perform the copy. This is a blind copy... it will copy byte by byte to the 3TB disk. It will copy the smaller disk's partition table, so it will appear as if it is a 2TB partition even though the disk is bigger. Then, you can attempt to re-create the superblock and re-build the file-tree in the 3TB drive's first partition ( /dev/sdX1 ) and access the files there. Joe L. what commands do I use to re-create the superblock and re-build the file-tree on the 3tb drive? Quote Link to comment
Joe L. Posted June 13, 2013 Share Posted June 13, 2013 I have a new 3tb disk.. unused.. how I do the copy through the linux commandlines.. do I need to do something to prepare the 3tb disk before I copy? No, no need to do anything to it other than to know its correct device name. To copy the existing disk to the spare you would type (make sure you have the right "if=source" and more importantly, the correct "of=destination") dd bs=1M oflag=noerror if=/dev/sdh of=/dev/sdX It will take 6 or more hours to perform the copy. This is a blind copy... it will copy byte by byte to the 3TB disk. It will copy the smaller disk's partition table, so it will appear as if it is a 2TB partition even though the disk is bigger. Then, you can attempt to re-create the superblock and re-build the file-tree in the 3TB drive's first partition ( /dev/sdX1 ) and access the files there. Joe L. what commands do I use to re-create the superblock and re-build the file-tree on the 3tb drive? First, let's see if the copy made the 3TB drive look like the 2TB with a standard MBR. Type fdisk -lu /dev/sdX It should show a single partition has been defined. Then, you'll need to run reiserfsck on that first partition. reiserfsck --check /dev/sdX1 (note the trailing "1" on the device name, designating the first partition) It will complain about the missing superblock. Then, to rebuild the superblock (again, we are doing this on the first partition, the device name with the trailing "1") reiserfsck --rebuild-sb /dev/sdX1 It will ask a series of questions, they MUST be answered correctly as not all the defaults are correct. See this post for the responses: http://lime-technology.com/forum/index.php?topic=1483 Joe L. Quote Link to comment
Critical Posted June 13, 2013 Author Share Posted June 13, 2013 Rebuilt the drive.. it said it was successful .. rebooted and ran another check.. got this Tower login: root Linux 3.9.3-unRAID. root@Tower:~# eiserfsck --check /dev/sdi1 -bash: eiserfsck: command not found root@Tower:~# reiserfsck --check /dev/sdi1 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/sdi1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Thu Jun 13 09:42:39 2013 ########### Replaying journal: Done. Reiserfs journal '/dev/sdi1' in blocks [18..8211]: 0 transactions replayed Zero bit found in on-disk bitmap after the last valid bit. Killed root@Tower:~# Tower login: root Linux 3.9.3-unRAID.-bash: Tower: command not found root@Tower:~# Linux 3.9.3-unRAID. root@Tower:~# eiserfsck --check /dev/sdi1-bash: Linux: command not found root@Tower:~# root@Tower:~# eiserfsck --check /dev/sdi1 -bash: eiserfsck: command not found root@Tower:~# reiserfsck --check /dev/sdi1 -bash: root@Tower:~#: command not found root@Tower:~# -bash: eiserfsck: command not found reiserfsck 3.6.21 (2009 www.namesys.com) -bash: -bash:: command not found root@Tower:~# root@Tower:~# reiserfsck --check /dev/sdi1 ************************************************************* -bash: root@Tower:~#: command not found root@Tower:~# reiserfsck 3.6.21 (2009 www.namesys.com) -bash: syntax error near unexpected token `(' root@Tower:~# root@Tower:~# ************************************************************* This will rename super.dat to super.bak, effectively clearing array configuration. The array must be in the Stopped state and it is up to you to confirm this. Are you sure you want to proceed? (type Yes if you do):** If you are using the latest reiserfsprogs and it fails ** root@Tower:~# ** please email bug reports to [email protected], ** This will rename super.dat to super.bak, effectively clearing array configuration. The array must be in the Stopped state and it is up to you to confirm this. Are you sure you want to proceed? (type Yes if you do):** providing as much information as possible -- your ** root@Tower:~# ** hardware, kernel, patches, settings, all reiserfsck ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/sdi1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Thu Jun 13 09:42:39 2013 ########### Replaying journal: Done. Reiserfs journal '/dev/sdi1' in blocks [18..8211]: 0 transactions replayed This will rename super.dat to super.bak, effectively clearing array configuration. The array must be in the Stopped state and it is up to you to confirm this. Are you sure you want to proceed? (type Yes if you do):root@Tower:~# ** is available for $25 at www.namesys.com/support.html. ** This will rename super.dat to super.bak, effectively clearing array configuration. The array must be in the Stopped state and it is up to you to confirm this. Are you sure you want to proceed? (type Yes if you do):^C Did not proceed because I did not want to wipe my array configuration What next? Will I be able to also maintain my folder structure? Quote Link to comment
Joe L. Posted June 13, 2013 Share Posted June 13, 2013 Is /dev/sdi1 your original disk, or the 3TB you copied it to? I'm a bit confused, as your capture of the telnet session has many incorrectly typed commands and a few responses that are entirely unexpected. Let me try to interpret what you did: Youo logged in as "root" Tower login: root Linux 3.9.3-unRAID. You tried to type the reiserfsck command, but forgot the leading "r" so the "bash" shell said it did not recognize the command. root@Tower:~# eiserfsck --check /dev/sdi1 -bash: eiserfsck: command not found You then typed the command correctlyroot@Tower:~# reiserfsck --check /dev/sdi1 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/sdi1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Thu Jun 13 09:42:39 2013 ########### Replaying journal: Done. Reiserfs journal '/dev/sdi1' in blocks [18..8211]: 0 transactions replayed Zero bit found in on-disk bitmap after the last valid bit. Killed Apparently, it found some corruption, a killed itself (probably a memory fault) Here it gets interesting... You apparently pasted into the telnet session the text from above, so most of it is not meaningful to the "bash" shell. As an example, on this next line it is looking for the "Tower" command, which does not exist. root@Tower:~# Tower login: root Linux 3.9.3-unRAID.-bash: Tower: command not found Next, it is looking for the "Linux" command, again, this does not exist. root@Tower:~# Linux 3.9.3-unRAID. root@Tower:~# eiserfsck --check /dev/sdi1-bash: Linux: command not found And you pasted the reiserfsck command with the missing "r", and it still does not exist root@Tower:~# root@Tower:~# eiserfsck --check /dev/sdi1 -bash: eiserfsck: command not found root@Tower:~# reiserfsck --check /dev/sdi1 -bash: root@Tower:~#: command not found root@Tower:~# -bash: eiserfsck: command not found reiserfsck 3.6.21 (2009 www.namesys.com) -bash: -bash:: command not found root@Tower:~# root@Tower:~# reiserfsck --check /dev/sdi1 ************************************************************* -bash: root@Tower:~#: command not found root@Tower:~# reiserfsck 3.6.21 (2009 www.namesys.com) -bash: syntax error near unexpected token `(' root@Tower:~# root@Tower:~# ************************************************************* This will rename super.dat to super.bak, effectively clearing array configuration. The array must be in the Stopped state and it is up to you to confirm this. Are you sure you want to proceed? (type Yes if you do):** If you are using the latest reiserfsprogs and it fails ** root@Tower:~# ** please email bug reports to [email protected], ** This will rename super.dat to super.bak, effectively clearing array configuration. The array must be in the Stopped state and it is up to you to confirm this. Are you sure you want to proceed? (type Yes if you do):** providing as much information as possible -- your ** root@Tower:~# ** hardware, kernel, patches, settings, all reiserfsck ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/sdi1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Thu Jun 13 09:42:39 2013 ########### Replaying journal: Done. Reiserfs journal '/dev/sdi1' in blocks [18..8211]: 0 transactions replayed This will rename super.dat to super.bak, effectively clearing array configuration. The array must be in the Stopped state and it is up to you to confirm this. Are you sure you want to proceed? (type Yes if you do):root@Tower:~# ** is available for $25 at www.namesys.com/support.html. ** This will rename super.dat to super.bak, effectively clearing array configuration. The array must be in the Stopped state and it is up to you to confirm this. Are you sure you want to proceed? (type Yes if you do):^C I'm glad you stopped, because the string of "***************" you accidentally pasted to the command line was expanded by the shell to the set of files in the (current) root directory. In effect you typed (I used "echo" here to let you see what you typed by entering the string of "**********************************************"): root@Tower:~# echo ****** initconfig mdcmd mkmbr powerdown samba Basically, you asked it to set a new disk configuration by accidentally invoking the initconfig command. That is what was prompting you about renaming super.dat. You most definitely did not want to do this. Did not proceed because I did not want to wipe my array configuration What next? Will I be able to also maintain my folder structure? It should not affect the folder structure at all, but you do NOT want to set a new disk configuration... It should not ask you if you wanted to set a new disk configuration since you really did not want to change the configuration. You need to know that in "telnet" if you highlight a block of text it is AUTOMATICALLY copied to the clipboard, and if you click on the right-hand-mouse button, it is automatically PASTED to the command line to be executed. You apparently accidentally did that sequence of actions, by accident, pasting a whole series of lines, some of which were somewhat dangerous if they had been invoked correctly. Now, try, typing more carefully, the following commands (just make sure that /dev/sdi is the 3TB drive you copied the failing disk to): To confirm, type: hdparm -i /dev/sdi It should show the correct model/serial number of the 3TB drive you copied to. The device names can change when you reboot, so verify please. (there is no need to reboot at this time anyways) Then type: reiserfsck --check /dev/sdi1 followed by (if it does not complain of a missing superblock) reiserfsck --fix-fixable /dev/sdi1 If it does complain about the missing-superblck, then reiserfsck --rebuild-sb /dev/sdi1 Using the correct responses to its prompts as described earlier It might suggest rebuilding the file-tree, if it does, type reiserfsck --rebuild-tree /dev/sdi1 Joe L. Quote Link to comment
Critical Posted June 13, 2013 Author Share Posted June 13, 2013 You are correct in your assessment .. I did paste accidentally... I will try the commands you have listed.. Quote Link to comment
ridley Posted June 13, 2013 Share Posted June 13, 2013 When I had a similar problem recently I was successful in copying the data via "Diskinternals Linux Reader" (which is free) on the windows PC even though I could not read the disk in UNRAID, so I had a backup before I started trying to fix the drive. Quote Link to comment
Critical Posted June 21, 2013 Author Share Posted June 21, 2013 Im back to beating my head against the wall.. I think that the problem is the 2TB drive..I now have the 3TB set up successfully as parity... I went and bought another 2TB drive.. the same WD 2TB 20EARS drive and this one also shows up as unformatted and will not mount .. is there someting im missing with this particular type of drive? BTW.. I recovered my data Quote Link to comment
dgaschk Posted June 22, 2013 Share Posted June 22, 2013 Did you rebuild on to the new 2T disk? Quote Link to comment
Critical Posted June 22, 2013 Author Share Posted June 22, 2013 The rebuild happens but the disks won't format Quote Link to comment
dgaschk Posted June 22, 2013 Share Posted June 22, 2013 The errors are in the file-system. The rebuild happens at the partition level. Any errors in the file system have been recreated on the new disk. Joe. L provided reiserfsck commands to test and repair the file system. reiserfsck must be used to correct the file system. Quote Link to comment
Critical Posted June 22, 2013 Author Share Posted June 22, 2013 Both drives have thier superblocks rebuilt.. They both say they have no journal transactions.. I would have sent the putty screenshots but when I started the array it dumped my connection once again .. Im attaching my syslog and hopefully that will help.. I cant start the array now.. syslog.txt Quote Link to comment
dgaschk Posted June 22, 2013 Share Posted June 22, 2013 There are several things happening. Jun 9 19:38:01 Tower emhttp: unclean shutdown detected How do you restart the system? md: import disk0: [8,80] (sdf) WDC_WD20EARS-00MVWB0_WD-WMAZA0801924 size: 1953514552 Jun 9 19:37:21 Tower kernel: mdcmd (2): import 1 8,32 312571192 ST3320620AS_3QF0B7EW Jun 9 19:37:21 Tower kernel: md: import disk1: [8,32] (sdc) ST3320620AS_3QF0B7EW size: 312571192 Jun 9 19:37:21 Tower kernel: mdcmd (3): import 2 3,64 312571192 WDC_WD3200AAJB-00J3A0_WD-WCAV2CD09698 Jun 9 19:37:21 Tower kernel: md: import disk2: [3,64] (hdb) WDC_WD3200AAJB-00J3A0_WD-WCAV2CD09698 size: 312571192 Jun 9 19:37:22 Tower kernel: mdcmd (4): import 3 8,112 1953514552 WDC_WD20EARX-00PASB0_WD-WCAZAK100188 Jun 9 19:37:22 Tower kernel: md: import disk3: [8,112] (sdh) WDC_WD20EARX-00PASB0_WD-WCAZAK100188 size: 1953514552 Jun 9 19:37:22 Tower kernel: mdcmd (5): import 4 8,48 312571192 ST3320620AS_6QF0BNXX Jun 9 19:37:22 Tower kernel: md: import disk4: [8,48] (sdd) ST3320620AS_6QF0BNXX size: 312571192 Jun 9 19:37:22 Tower kernel: mdcmd (6): import 5 22,0 195360952 ST3200822A_3LJ2XNFH Jun 9 19:37:22 Tower kernel: md: import disk5: [22,0] (hdc) ST3200822A_3LJ2XNFH size: 195360952 Jun 9 19:37:22 Tower kernel: mdcmd (7): import 6 22,64 195360952 MDT_MD2000JB-00DUA3_MDT-PMACK1719406 Jun 9 19:37:22 Tower kernel: md: import disk6: [22,64] (hdd) MDT_MD2000JB-00DUA3_MDT-PMACK1719406 size: 195360952 Jun 9 19:37:22 Tower kernel: mdcmd (: import 7 34,0 244198552 WDC_WD2500JB-00REA0_WD-WMANK2219184 Jun 9 19:37:22 Tower kernel: md: import disk7: [34,0] (hdg) WDC_WD2500JB-00REA0_WD-WMANK2219184 size: 244198552 Jun 9 19:37:22 Tower kernel: mdcmd (9): import 8 3,0 78150712 WDC_WD800JB-00JJC0_WD-WCAM9R082982 Jun 9 19:37:22 Tower kernel: md: import disk8: [3,0] (hda) WDC_WD800JB-00JJC0_WD-WCAM9R082982 size: 78150712 Jun 9 19:37:22 Tower kernel: mdcmd (10): import 9 8,144 156290872 WDC_WD1600AAJS-00L7A0_WD-WMAV38778902 Jun 9 19:37:22 Tower kernel: md: import disk9: [8,144] (sdj) WDC_WD1600AAJS-00L7A0_WD-WMAV38778902 size: 156290872 Jun 9 19:37:22 Tower kernel: mdcmd (11): import 10 8,16 976762552 WDC_WD10EACS-22D6B0_WD-WCAU42571373 Jun 9 19:37:22 Tower kernel: md: import disk10: [8,16] (sdb) WDC_WD10EACS-22D6B0_WD-WCAU42571373 size: 976762552 Disk2-3, 5-8 and not configured as AHCI in BIOS. The device identifiers start with an h. They should start with a s. Correct the BIOS configuration. What does the following output? reiserfsck --check /dev/md3 Quote Link to comment
Critical Posted June 22, 2013 Author Share Posted June 22, 2013 There are several things happening. Jun 9 19:38:01 Tower emhttp: unclean shutdown detected How do you restart the system? md: import disk0: [8,80] (sdf) WDC_WD20EARS-00MVWB0_WD-WMAZA0801924 size: 1953514552 Jun 9 19:37:21 Tower kernel: mdcmd (2): import 1 8,32 312571192 ST3320620AS_3QF0B7EW Jun 9 19:37:21 Tower kernel: md: import disk1: [8,32] (sdc) ST3320620AS_3QF0B7EW size: 312571192 Jun 9 19:37:21 Tower kernel: mdcmd (3): import 2 3,64 312571192 WDC_WD3200AAJB-00J3A0_WD-WCAV2CD09698 Jun 9 19:37:21 Tower kernel: md: import disk2: [3,64] (hdb) WDC_WD3200AAJB-00J3A0_WD-WCAV2CD09698 size: 312571192 Jun 9 19:37:22 Tower kernel: mdcmd (4): import 3 8,112 1953514552 WDC_WD20EARX-00PASB0_WD-WCAZAK100188 Jun 9 19:37:22 Tower kernel: md: import disk3: [8,112] (sdh) WDC_WD20EARX-00PASB0_WD-WCAZAK100188 size: 1953514552 Jun 9 19:37:22 Tower kernel: mdcmd (5): import 4 8,48 312571192 ST3320620AS_6QF0BNXX Jun 9 19:37:22 Tower kernel: md: import disk4: [8,48] (sdd) ST3320620AS_6QF0BNXX size: 312571192 Jun 9 19:37:22 Tower kernel: mdcmd (6): import 5 22,0 195360952 ST3200822A_3LJ2XNFH Jun 9 19:37:22 Tower kernel: md: import disk5: [22,0] (hdc) ST3200822A_3LJ2XNFH size: 195360952 Jun 9 19:37:22 Tower kernel: mdcmd (7): import 6 22,64 195360952 MDT_MD2000JB-00DUA3_MDT-PMACK1719406 Jun 9 19:37:22 Tower kernel: md: import disk6: [22,64] (hdd) MDT_MD2000JB-00DUA3_MDT-PMACK1719406 size: 195360952 Jun 9 19:37:22 Tower kernel: mdcmd (: import 7 34,0 244198552 WDC_WD2500JB-00REA0_WD-WMANK2219184 Jun 9 19:37:22 Tower kernel: md: import disk7: [34,0] (hdg) WDC_WD2500JB-00REA0_WD-WMANK2219184 size: 244198552 Jun 9 19:37:22 Tower kernel: mdcmd (9): import 8 3,0 78150712 WDC_WD800JB-00JJC0_WD-WCAM9R082982 Jun 9 19:37:22 Tower kernel: md: import disk8: [3,0] (hda) WDC_WD800JB-00JJC0_WD-WCAM9R082982 size: 78150712 Jun 9 19:37:22 Tower kernel: mdcmd (10): import 9 8,144 156290872 WDC_WD1600AAJS-00L7A0_WD-WMAV38778902 Jun 9 19:37:22 Tower kernel: md: import disk9: [8,144] (sdj) WDC_WD1600AAJS-00L7A0_WD-WMAV38778902 size: 156290872 Jun 9 19:37:22 Tower kernel: mdcmd (11): import 10 8,16 976762552 WDC_WD10EACS-22D6B0_WD-WCAU42571373 Jun 9 19:37:22 Tower kernel: md: import disk10: [8,16] (sdb) WDC_WD10EACS-22D6B0_WD-WCAU42571373 size: 976762552 Disk2-3, 5-8 and not configured as AHCI in BIOS. The device identifiers start with an h. They should start with a s. Correct the BIOS configuration. What does the following output? reiserfsck --check /dev/md3 I have to physically shut the server down when I lose the connection... The drives that show up with an 'h' have always been my ide drives .. the 's' are the sata drives.. its been that way since i started using unraid in 2007.. root@Tower:~# reiserfsck --check /dev/md3 reiserfsck 3.6.21 (2009 www.namesys.com) ************************************************************* ** If you are using the latest reiserfsprogs and it fails ** ** please email bug reports to [email protected], ** ** providing as much information as possible -- your ** ** hardware, kernel, patches, settings, all reiserfsck ** ** messages (including version), the reiserfsck logfile, ** ** check the syslog file for any related information. ** ** If you would like advice on using this program, support ** ** is available for $25 at www.namesys.com/support.html. ** ************************************************************* Will read-only check consistency of the filesystem on /dev/md3 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Failed to open the device '/dev/md3': No such file or directory root@Tower:~# Quote Link to comment
dgaschk Posted June 23, 2013 Share Posted June 23, 2013 (sdh) WDC_WD20EARX is a SATA drive. This the problem drive. I suggest that you configure BIOS to AHCI for this drive and any other SATA drives. 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.