prostuff1 Posted November 26, 2011 Posted November 26, 2011 So last night as some point my cache drive (sdh) got kicked from the array, but was picked back up as sdr. This screwed up a couple of my apps that were running there but nothing to big. I stopped the array, looked around, and then started it again. On restart everything came up fine with the exception being that the cache drive being shown as unformatted. I have searched around the forum and came up with some threads but wanted to get the opinion of some of the members here. Below is the output of the commands from the other threads as I was not quite sure how to interpret them before moving forward. fdisk -lu /dev/sdr root@Andromeda:/boot/custom/bin# fdisk -lu /dev/sdr Disk /dev/sdr: 500.1 GB, 500107862016 bytes 1 heads, 63 sectors/track, 15504336 cylinders, total 976773168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdr1 63 976773167 488386552+ 83 Linux Partition 1 does not end on cylinder boundary. dd if=/dev/sdr count=195 | od -c -A d | sed 30q root@Andromeda:~# dd if=/dev/sdr count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 83.4881 s, 1.2 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 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 241 X 262 \0 \ 003 \n 005 022 \0 \0 \0 0097808 \0 \0 \0 \0 \0 \0 \0 \0 004 \0 \0 261 3 201 " 0097824 204 003 \0 \0 036 \0 \0 \0 \0 \0 \0 \0 \0 020 314 003 0097840 314 001 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 x 324 026 \0 0097872 001 \0 \0 \0 F e u 340 " 232 O 3 237 205 211 \0 0097888 \0 \ 307 021 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0097904 \0 \0 \0 \0 = \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0097920 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0097984 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 001 \0 \0 \0 0098000 \ # 002 \0 ] # 002 \0 e # 002 \0 p # 002 \0 0098016 q # 002 \0 s # 002 \0 t # 002 \0 205 # 002 \0 0098032 240 # 002 \0 245 # 002 \0 246 # 002 \0 264 # 002 \0 0098048 276 # 002 \0 277 # 002 \0 301 # 002 \0 314 # 002 \0 0098064 316 # 002 \0 317 # 002 \0 354 # 002 \0 357 # 002 \0 0098080 360 # 002 \0 005 $ 002 \0 0 $ 002 \0 1 $ 002 \0 0098096 ? $ 002 \0 D $ 002 \0 F $ 002 \0 X $ 002 \0 0098112 Y $ 002 \0 Z $ 002 \0 ` $ 002 \0 d $ 002 \0 0098128 f $ 002 \0 g $ 002 \0 h $ 002 \0 x $ 002 \0 0098144 y $ 002 \0 213 $ 002 \0 214 $ 002 \0 221 $ 002 \0 0098160 227 $ 002 \0 233 $ 002 \0 234 $ 002 \0 237 $ 002 \0 Reiser FS shows up from the above command but I don't quite know how to interpret it. This is an older 500GB drive that has not failed me until now and was originally set up before the unRAID 4.7 days. I was actually going to be replacing it soon... tomorrow with a newer 1TB drive and moving the server to its final home in my utility room. Since I will be replacing the drive with a 1TB drive I don't care for how long this one comes back online, just long enough to copy some stuff across really. A smartctl on the drive shows that there are now 740(ish) sectors pending allocation, so the drive is probably on its way out. I might try to preclear it just for grins and giggles but I have not decided yet. Anyway, please take a look and let me know the next steps please! I know it probably involves unraid_partiton_disk.sh syslog-2011-11-26.txt.zip
dgaschk Posted November 26, 2011 Posted November 26, 2011 The drive appears to be dying. Run a few passes of pre-clear and see how it does.
Johnm Posted November 26, 2011 Posted November 26, 2011 fdick -lu /dev/sdr It looks like you F'd the drive.. that is about what happened to my cache drive.. It copied a bunch of corrupt files to my array before it died. the drive ended up being a lost cause..
prostuff1 Posted November 26, 2011 Author Posted November 26, 2011 The drive appears to be dying. Run a few passes of pre-clear and see how it does. Oh, I have no doubt it is dying... finally. It has been a great drive and until this latest instance has never given me a problem. I would like to get it back up and running long enough to copy the few files that are on it to another drive.
prostuff1 Posted November 26, 2011 Author Posted November 26, 2011 fdick -lu /dev/sdr It looks like you F'd the drive.. that is about what happened to my cache drive.. It copied a bunch of corrupt files to my array before it died. the drive ended up being a lost cause.. I don't think there were any files on it that needed copied over so not to concerned about that. I only had a few apps running from the cache drive, so nothing of a huge lose, but would like to get it back up long enough to copy stuff from it. I think I can fix the unformatted issue, mount the drive, and then send the drive to the scrap pile. Hoping Joe L. sees this and can give some guidance.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.