larson Posted November 16, 2011 Share Posted November 16, 2011 Hi all. It seems I have screwed up a 2 TB drive by doing naughty things to it. I unmounted and mounted a couple of drives, a 2 TB and a 250 G, while Unraid was up and running. OS was apparently not very happy about that, and now when I try to access my 2 TB from a Ubuntu 10.10 it will not find any partitions at all on the disk. When I take a look at the 250, it looks all fine. I guess something has overwritten something. Do anyone have any idea of tools and procedures to try to recover from this? Disk should be full size Reiser partitions created in the unraid box When looking at the syslog I find a couple of events, see below. Happy for any advice, and happier if I can recover the data. (And you don't have to tell me to stop hotplugging the disks. This was the last time.) /Lars Olof Nov 12 00:28:26 Tower kernel: NTFS driver 2.1.30 [Flags: R/W MODULE]. Nov 12 00:29:05 Tower kernel: REISERFS (device sdf1): found reiserfs format "3.6" with standard journal Nov 12 00:29:05 Tower kernel: REISERFS (device sdf1): using ordered data mode Nov 12 00:29:05 Tower kernel: reiserfs: using flush barriers Nov 12 00:29:05 Tower kernel: REISERFS (device sdf1): journal params: device sdf1, size 8192, journal first block 18, max trans len 1024, max batc h 900, max commit age 30, max trans age 30 Nov 12 00:29:05 Tower kernel: REISERFS (device sdf1): checking transaction log (sdf1) Nov 12 00:29:05 Tower kernel: REISERFS (device sdf1): Using r5 hash to sort names Nov 12 00:32:14 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 12 00:32:14 Tower kernel: ata8.00: BMDMA stat 0x64 Nov 12 00:32:14 Tower kernel: ata8.00: failed command: READ DMA EXT Nov 12 00:32:14 Tower kernel: ata8.00: cmd 25/00:08:00:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in Nov 12 00:32:14 Tower kernel: res 51/04:08:00:88:e0/04:00:e8:00:00/e0 Emask 0x1 (device error) Nov 12 00:32:14 Tower kernel: ata8.00: status: { DRDY ERR } Nov 12 00:32:14 Tower kernel: ata8.00: error: { ABRT } Nov 12 00:32:14 Tower kernel: ata8.00: model number mismatch 'WDC WD20EARS-00MVWB0' != 'HDT722525DLA380' Nov 12 00:32:14 Tower kernel: ata8.00: revalidation failed (errno=-19) Nov 12 00:32:14 Tower kernel: ata8.00: limiting speed to UDMA/133:PIO3 Nov 12 00:32:14 Tower kernel: ata8: soft resetting link Nov 12 00:32:14 Tower kernel: ata8.00: model number mismatch 'WDC WD20EARS-00MVWB0' != 'HDT722525DLA380' Nov 12 00:32:14 Tower kernel: ata8.00: revalidation failed (errno=-19) Nov 12 00:32:14 Tower kernel: ata8.00: disabled Nov 12 00:32:19 Tower kernel: ata8: soft resetting link Nov 12 00:32:19 Tower kernel: ata8.00: ATA-7: HDT722525DLA380, V44OA99A, max UDMA/100 Nov 12 00:32:19 Tower kernel: ata8.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 0/32) Nov 12 00:32:19 Tower kernel: ata8.00: configured for UDMA/100 Nov 12 00:32:19 Tower kernel: sd 5:0:0:0: [sdf] Result: hostbyte=0x00 driverbyte=0x08 Nov 12 00:32:19 Tower kernel: sd 5:0:0:0: [sdf] Sense Key : 0xb [current] [descriptor] Nov 12 00:32:19 Tower kernel: Descriptor sense data with sense descriptors (in hex): Nov 12 00:32:19 Tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Nov 12 00:32:19 Tower kernel: e8 e0 88 00 Nov 12 00:32:19 Tower kernel: sd 5:0:0:0: [sdf] ASC=0x0 ASCQ=0x0 Nov 12 00:32:19 Tower kernel: sd 5:0:0:0: [sdf] CDB: cdb[0]=0x28: 28 00 e8 e0 88 00 00 00 08 00 Nov 12 00:32:19 Tower kernel: end_request: I/O error, dev sdf, sector 3907028992 Nov 12 00:32:19 Tower kernel: Buffer I/O error on device sdf, logical block 488378624 Nov 12 00:32:19 Tower kernel: ata8: EH complete Nov 12 00:32:19 Tower kernel: sd 5:0:0:0: rejecting I/O to offline device Nov 12 00:32:19 Tower kernel: ata8.00: detaching (SCSI 5:0:0:0) Nov 12 00:32:19 Tower kernel: sd 5:0:0:0: [sdf] Synchronizing SCSI cache Nov 12 00:32:19 Tower kernel: sd 5:0:0:0: [sdf] Stopping disk Nov 12 00:32:20 Tower kernel: scsi 5:0:0:0: Direct-Access ATA HDT722525DLA380 V44O PQ: 0 ANSI: 5 Nov 12 00:32:20 Tower kernel: sd 5:0:0:0: [sdf] 488397168 512-byte logical blocks: (250 GB/232 GiB) Nov 12 00:32:20 Tower kernel: sd 5:0:0:0: [sdf] Write Protect is off Nov 12 00:32:20 Tower kernel: sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00 Nov 12 00:32:20 Tower kernel: sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 12 00:32:22 Tower kernel: sdf: sdf1 Nov 12 00:32:22 Tower kernel: sd 5:0:0:0: [sdf] Attached SCSI disk Nov 12 00:33:13 Tower kernel: NTFS volume version 3.1. Nov 12 00:57:02 Tower kernel: REISERFS (device sdf1): found reiserfs format "3.6" with standard journal Nov 12 00:57:02 Tower kernel: REISERFS (device sdf1): using ordered data mode Nov 12 00:57:02 Tower kernel: reiserfs: using flush barriers Nov 12 00:57:02 Tower kernel: REISERFS (device sdf1): journal params: device sdf1, size 8192, journal first block 18, max trans len 1024, max batc h 900, max commit age 30, max trans age 30 Nov 12 00:57:02 Tower kernel: REISERFS (device sdf1): checking transaction log (sdf1) Nov 12 00:57:03 Tower kernel: REISERFS (device sdf1): Using r5 hash to sort names Nov 12 00:57:03 Tower kernel: REISERFS (device sdf1): Created .reiserfs_priv - reserved for xattr storage. Nov 13 09:44:25 Tower kernel: FAT-fs (sdf1): bogus number of reserved sectors Nov 13 09:44:25 Tower kernel: FAT-fs (sdf1): Can't find a valid FAT filesystem Nov 13 09:44:35 Tower kernel: FAT-fs (sdf1): bogus number of reserved sectors Nov 13 09:44:35 Tower kernel: FAT-fs (sdf1): Can't find a valid FAT filesystem Nov 13 09:46:46 Tower kernel: REISERFS (device sdf1): found reiserfs format "3.6" with standard journal Nov 13 09:46:46 Tower kernel: REISERFS (device sdf1): using ordered data mode Nov 13 09:46:46 Tower kernel: reiserfs: using flush barriers Nov 13 09:46:47 Tower kernel: REISERFS (device sdf1): journal params: device sdf1, size 8192, journal first block 18, max trans len 1024, max batc h 900, max commit age 30, max trans age 30 Nov 13 09:46:47 Tower kernel: REISERFS (device sdf1): checking transaction log (sdf1) Nov 13 09:46:47 Tower kernel: REISERFS (device sdf1): Using r5 hash to sort names Nov 13 09:46:47 Tower kernel: REISERFS (device sdf1): Created .reiserfs_priv - reserved for xattr storage. Link to comment
Joe L. Posted November 17, 2011 Share Posted November 17, 2011 Follow these steps to figure out if the partition starts on sector 63, or on sector 64. Then use the described unraid_partition_disk.sh script as instructed with (or without) the "-A" option. it will replace the partitioning in the MBR with what unRAID would have done originally. The drive should then be recognized and be able to be mounted as a reiserfs on its first partition. Link to comment
larson Posted November 17, 2011 Author Share Posted November 17, 2011 Follow these steps to figure out if the partition starts on sector 63, or on sector 64. Then use the described unraid_partition_disk.sh script as instructed with (or without) the "-A" option. it will replace the partitioning in the MBR with what unRAID would have done originally. The drive should then be recognized and be able to be mounted as a reiserfs on its first partition. Thanks Joe. I followed your instructions to the letter, but to no use :-) (Please provide link/instruction) /Lars Olof Link to comment
larson Posted November 17, 2011 Author Share Posted November 17, 2011 Btw, wouldn't the 2TB disk default to start on 64 if first formatted in a v5 Unraid installation? Will the script run OK on my Ubuntu laptop with the disk in a USB cradle, or should I run it on the Unraid box? /Lars Olof Link to comment
Joe L. Posted November 17, 2011 Share Posted November 17, 2011 Btw, wouldn't the 2TB disk default to start on 64 if first formatted in a v5 Unraid installation? Will the script run OK on my Ubuntu laptop with the disk in a USB cradle, or should I run it on the Unraid box? /Lars Olof 1. unknown. depends on so many factors. if there is a partition of any kind that is existing, even from pre-clearing, unRAID will use it. 2. unknown. probably will work... it has no dependency on unRAID itself. 3. Using the script before doing the analysis to determine where the file system might actually reside is pretty haphazard in my opinion. Where is the mbr pointing to now? Where is the file system start? (The commands in the thread I pointed you to will let you determine what is happening.) Otherwise, it is sort of like a doctor saying ... not sure what is wrong with you... try some of this high-blood-pressure medicine. If that does not work on your insomnia, we can put your arm in a cast, or start you on a pain killer, just in case the high blood-pressure medicine causes you pain, or causes you to loose consciousness, fall, and break your arm. If you are not going to proceed logically, you'll get pretty frustrated very quickly as you compound your problems. Link to comment
larson Posted November 17, 2011 Author Share Posted November 17, 2011 (The commands in the thread I pointed you to will let you determine what is happening.) That's all good, except you forgot to paste the link. I searched a bit but that script shows up in a lot of places... Link to comment
larson Posted November 17, 2011 Author Share Posted November 17, 2011 Digging a bit I have found reference to fdisk -lu /dev/sdX, and the output Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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/sdc1 64 3907029167 1953514552 0 Empty Partition 1 does not end on cylinder boundary. seems to suggest the partitions starts on sector 64. From another thread it is suggested to run some other commands: larson@larson-ubuntu:~$ sudo sfdisk -g /dev/sdc /dev/sdc: 243201 cylinders, 255 heads, 63 sectors/track larson@larson-ubuntu:~$ sudo blockdev --getsz /dev/sdc 3907029168 larson@larson-ubuntu:~$ sudo od -x -A d /dev/sdc | head 0000000 0000 0000 0000 0000 0000 0000 0000 0000 * 0000448 0000 0000 0000 0040 0000 8870 e8e0 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 * 0097792 88a0 03a3 6145 03a3 2013 0000 0012 0000 0097808 0000 0000 2000 0000 0400 0000 6edd 1693 This tells me nought, hope it can make someone happy. And here is the output from the script run without options: larson@larson-ubuntu:~$ sudo ./unraid_partition_disk.sh /dev/sdc ######################################################################## ./unraid_partition_disk.sh: line 163: smartctl: command not found Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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/sdc1 64 3907029167 1953514552 0 Empty Partition 1 does not end on cylinder boundary. ######################################################################## ============================================================================ == Disk /dev/sdc is NOT partitioned for unRAID properly == and file system type is not set properly: type=00000 == expected start = 63, actual start = 64 == expected size = 3907029105, actual size = 3907029104 ============================================================================ Are we better off now? I dug in my medicine cabinet and found some funny loking pills. I hope they will keep me going 'til the doctor is in :-) /Lars Olof Link to comment
Joe L. Posted November 17, 2011 Share Posted November 17, 2011 Sorry.... I thought I had posted the link: http://lime-technology.com/forum/index.php?topic=15385.msg144723#msg144723 Your partition data starts on the same address as mine, and mine is an older array with the partition starting on sector 63. 0097792 88a0 03a3 6145 03a3 2013 0000 0012 0000 Therefore, you need to set the MBR to point to sector 63, when it will then point to the correct start of your file system. As you've found with the fdisk command, you are currently pointing to sector 64, and the file-system does not start there, and therefore not being recognized. unraid_partition_disk.sh -p /dev/sdc should do it. Then, stop the array, re-start it, and the disk should mount. Link to comment
larson Posted November 18, 2011 Author Share Posted November 18, 2011 Ok, just for fun I ran the command from the other thread larson@larson-ubuntu:~$ sudo dd if=/dev/sda count=195 | od -c -A d | sed 30q [sudo] password for larson: 0000000 353 c 220 \0 004 \0 257 002 \0 \0 \0 \0 \0 \0 N P 0000016 372 3 300 274 \0 f 216 320 P \a P 037 373 374 276 \t 0000032 \0 211 024 277 \0 \b 276 \0 | 271 \0 001 363 245 P 277 0000048 4 \b W 313 273 \0 006 276 002 \b 017 266 \f 270 001 002 0000064 272 200 \0 315 023 272 005 \0 277 \0 006 271 \0 002 350 $ 0000080 001 271 005 \0 273 \0 022 276 \0 006 \0 200 001 \0 \0 \0 0000096 \0 \0 \0 \0 377 372 220 220 366 302 200 u 002 262 200 352 0000112 t | \0 \0 1 300 216 330 216 320 274 \0 373 240 d 0000128 | < 377 t 002 210 302 R 273 027 004 200 ' 003 t 006 0000144 276 210 } 350 034 001 276 005 | 366 302 200 t H 264 A 0000160 273 252 U 315 023 Z R r = 201 373 U 252 u 7 203 0000176 341 001 t 2 1 300 211 D 004 @ 210 D 377 211 D 002 0000192 307 004 020 \0 f 213 036 \ | f 211 \ \b f 213 036 0000208 ` | f 211 \ \f 307 D 006 \0 p 264 B 315 023 r 0000224 005 273 \0 p 353 v 264 \b 315 023 s \r 366 302 200 017 0000240 204 320 \0 276 223 } 351 202 \0 f 017 266 306 210 d 377 0000256 @ f 211 D 004 017 266 321 301 342 002 210 350 210 364 @ 0000272 211 D \b 017 266 302 300 350 002 f 211 004 f 241 ` | 0000288 f \t 300 u N f 241 \ | f 1 322 f 367 4 210 0000304 321 1 322 f 367 t 004 ; D \b } 7 376 301 210 305 0000320 0 300 301 350 002 \b 301 210 320 Z 210 306 273 \0 p 216 0000336 303 1 333 270 001 002 315 023 r 036 214 303 ` 036 271 \0 0000352 001 216 333 1 366 277 \0 200 216 306 374 363 245 037 a 377 0000368 & Z | 276 216 } 353 003 276 235 } 350 4 \0 276 242 0000384 } 350 . \0 315 030 353 376 G R U B \0 G e 0000400 o m \0 H a r d D i s k \0 R e a 0000416 d \0 E r r o r \r \n \0 273 001 \0 264 016 0000432 315 020 254 < \0 u 364 303 306 247 q / \0 \0 200 0000448 ! \0 \a 371 ! 230 \0 \b \0 \0 \0 x % \0 \0 371 0000464 " 230 \a 376 377 377 \0 200 % \0 \0 370 362 \a \0 376 larson@larson-ubuntu:~$ sudo dd if=/dev/sdc count=195 | od -c -A d | sed 30q 0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000448 \0 \0 \0 \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 * 0097792 240 210 243 003 E a 243 003 023 \0 \0 022 \0 \0 \0 0097808 \0 \0 \0 \0 \0 \0 \0 \0 004 \0 \0 335 n 223 026 0097824 204 003 \0 \0 036 \0 \0 \0 \0 \0 \0 \0 \0 020 314 003 0097840 002 \0 001 \0 R e I s E r 2 F s \0 \0 \0 0097856 003 \0 \0 \0 002 \0 H \a 002 \0 \0 \0 \0 \0 \0 \0 0097872 001 \0 \0 \0 355 y G 363 245 324 K 262 244 035 306 357 0097888 317 375 317 320 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0097904 \0 \0 \0 \0 002 \0 036 \0 205 203 277 N \0 N 355 \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 004 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0098016 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0099840 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 0.0105842 s, 9.4 MB/s And then the script Are you absolutely sure you want to write the MBR to partition this drive? (Answer 'Yes' to continue. Capital 'Y', lower case 'es'): Yes 48+0 records in 48+0 records out 48 bytes (48 B) copied, 0.00126531 s, 37.9 kB/s 1+0 records in 1+0 records out 446 bytes (446 B) copied, 0.00102087 s, 437 kB/s 1+0 records in 1+0 records out 1 byte (1 B) copied, 0.00124031 s, 0.8 kB/s 1+0 records in 1+0 records out 1 byte (1 B) copied, 0.000464584 s, 2.2 kB/s 1+0 records in 1+0 records out 1 byte (1 B) copied, 3.8413e-05 s, 26.0 kB/s 16+0 records in 16+0 records out 16 bytes (16 B) copied, 0.00116921 s, 13.7 kB/s ./unraid_partition_disk.sh: line 307: /etc/rc.d/rc.udev: No such file or directory ============================================================================ == Partitioning of /dev/sdc complete == ============================================================================ Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes 1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 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/sdc1 63 3907029167 1953514552+ 83 Linux Partition 1 does not end on cylinder boundary. Now it finds a 2 TB ReiserFS, but a quick read-only mount shows no files. I'll be digging the forum for hints on checking the FS now. That line "./unraid_partition_disk.sh: line 307: /etc/rc.d/rc.udev: No such file or directory" ought to come from me running it on Ubuntu 10.04 on my laptop. What did I miss there? /Lars Olof Link to comment
Joe L. Posted November 18, 2011 Share Posted November 18, 2011 Now it finds a 2 TB ReiserFS, but a quick read-only mount shows no files. I'll be digging the forum for hints on checking the FS now. If there were files on the disk, and you reformatted accidentally, you can usually get most back by running: reiserfsck -–scan-whole-partition -–rebuild-tree /dev/sdc1 If the disk is part of your array, and you have parity established, instead of /dev/sdc1, you will want to use the /dev/mdX device instead so parity is kept in sync. disk1 = /dev/md1 disk2 = /dev/md2 disk3 = /dev/md3 etc. as described in this thread: http://lime-technology.com/forum/index.php?topic=8771.msg85487#msg85487 Link to comment
larson Posted November 18, 2011 Author Share Posted November 18, 2011 This disk was never part of the array. I just ran "reiserfsck --check /dev/sdc1" ########### reiserfsck --check started at Fri Nov 18 02:33:07 2011 ########### Replaying journal: Done. Reiserfs journal '/dev/sdc1' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 1 Internal nodes 0 Directories 2 Other files 0 Data block pointers 0 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Fri Nov 18 02:33:25 2011 ########### There should be thousands of files on the disk in hundreds of directories. Shouldn't that be a lot of Leaves listed in the filesystem? I guess your suggested command will take a long time to run, so I ought to change my setup for that. I'll be looking to put the disk in a solid internal slot instead of the USB cradle on my laptop that I'm running now. When I mounted read-only earlier it showed no files but only 230 GB free. Sounds a bit strange to me, I thought it was a permission thing first, but looking on the disk as root didn't show any files either. Well, I'll dig more later, it's late here now. /Lars Olof Link to comment
larson Posted November 18, 2011 Author Share Posted November 18, 2011 Well, it looks like I just got myself 2 TB free space :-( reiserfsck --scan-whole-partition --rebuild-tree /dev/sdk1 . . . Will rebuild the filesystem (/dev/sdk1) tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Replaying journal: Done. Reiserfs journal '/dev/sdk1' in blocks [18..8211]: 0 transactions replayed ########### reiserfsck --rebuild-tree started at Fri Nov 18 09:04:57 2011 ########### Pass 0: ####### Pass 0 ####### The whole partition (61048992 blocks) is to be scanned Skipping 10074 blocks (super block, journal, bitmaps) 61038918 blocks will be read 0%....20%....40%....60%.. left 0, 30827 /secccseccccc 1 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 61038918 Leaves among those 2 - leaves all contents of which could not be saved and deleted 1 Objectids found 3 Pass 1 (will try to insert 1 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....100% left 0, 0 /sec Flushing..finished 1 leaves read 1 inserted ####### Pass 2 ####### Flushing..finished Pass 3 (semantic): ####### Pass 3 ######### Flushing..finished Files found: 0 Directories found: 3 Pass 3a (looking for lost dir/files): ####### Pass 3a (lost+found pass) ######### Looking for lost directories: Flushing..finishede 0, 0 /sec Pass 4 - finished done 0, 0 /sec Flushing..finished Syncing..finished ########### reiserfsck finished at Fri Nov 18 09:38:38 2011 ########### root@Tower:/mnt# mount -r /dev/sdk1 /mnt/2t root@Tower:/mnt# cd 2t root@Tower:/mnt/2t# ls lost+found root@Tower:/mnt/2t# cd lost+found/ root@Tower:/mnt/2t/lost+found# ls root@Tower:/mnt/2t/lost+found# Crap! I guess there is nothing more to do after this. And the run took less than one hour also. /Lars Olof Link to comment
Joe L. Posted November 18, 2011 Share Posted November 18, 2011 Well, it looks like I just got myself 2 TB free space :-( reiserfsck --scan-whole-partition --rebuild-tree /dev/sdk1 . . . Will rebuild the filesystem (/dev/sdk1) tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Replaying journal: Done. Reiserfs journal '/dev/sdk1' in blocks [18..8211]: 0 transactions replayed ########### reiserfsck --rebuild-tree started at Fri Nov 18 09:04:57 2011 ########### Pass 0: ####### Pass 0 ####### The whole partition (61048992 blocks) is to be scanned Skipping 10074 blocks (super block, journal, bitmaps) 61038918 blocks will be read 0%....20%....40%....60%.. left 0, 30827 /secccseccccc 1 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 61038918 Leaves among those 2 - leaves all contents of which could not be saved and deleted 1 Objectids found 3 Pass 1 (will try to insert 1 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....100% left 0, 0 /sec Flushing..finished 1 leaves read 1 inserted ####### Pass 2 ####### Flushing..finished Pass 3 (semantic): ####### Pass 3 ######### Flushing..finished Files found: 0 Directories found: 3 Pass 3a (looking for lost dir/files): ####### Pass 3a (lost+found pass) ######### Looking for lost directories: Flushing..finishede 0, 0 /sec Pass 4 - finished done 0, 0 /sec Flushing..finished Syncing..finished ########### reiserfsck finished at Fri Nov 18 09:38:38 2011 ########### root@Tower:/mnt# mount -r /dev/sdk1 /mnt/2t root@Tower:/mnt# cd 2t root@Tower:/mnt/2t# ls lost+found root@Tower:/mnt/2t# cd lost+found/ root@Tower:/mnt/2t/lost+found# ls root@Tower:/mnt/2t/lost+found# Crap! I guess there is nothing more to do after this. And the run took less than one hour also. /Lars Olof That seemed really fast. You did give it the --scan-whole-partition option? And.. did the device name change? before it was /dev/sdc Link to comment
larson Posted November 18, 2011 Author Share Posted November 18, 2011 That seemed really fast. You did give it the --scan-whole-partition option? And.. did the device name change? before it was /dev/sdc Yup, it was the full command. And device id changed because I installed it in the Unraid Box again, to have it on a solid connection. I had it in a usb cradle on my laptop when diagnosing it earlier. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.