March 27, 20188 yr I thought I had just finished cleaning up my array with a major overhaul. Per previous posts, I lost 3 drives (2 of which were completely unrecoverable. 1 which I successfully repaired outside the array). I set up a new array with the remaining good drives. The new parity sync was running fine until about 50% when I saw a drive drop (temp went to "*"). Parity Sync completed successfully. Upon bringing the array on, the drive shows disabled, disk emulated. I am attaching a smart report and my diagnostics. Amazingly, all 4 of these drives are Seagate. Can I get a step by step to try and bring the drive back up? Do I need to runreiserfsck --check /dev/sdn on this drive again? This is exhausting... ST2000DL003-9VT166_5YD5NWP1-20180327-0119.txt tower-diagnostics-20180327-1008.zip
March 27, 20188 yr If the disk dropped before the parity sync completed parity won't be valid and the emulated disk is corrupt, you can replace and rebuild that disk, run reiserfsck on it and then try to copy everything you can from the old disk replacing the existing files.
March 27, 20188 yr Author reiserfsck output: If the partition table has not been changed, and the partition is valid and it really contains a reiserfs partition, then the superblock is corrupted and you need to run this utility with --rebuild-sb. Do I do this?
March 27, 20188 yr if you run on the device you need to use the partition, /dev/sdn1, but that only if the disk doen't mount e.g. using the UD plugin, it won't change anything for the emulated disk.
March 27, 20188 yr Author I ran reiserfsck on sdn1 which is still in the array with the following results below. I don't understand what to do now. Do I now have to: 1. add an unassigned device and clone it over, 2. remove the device, 3. create yet another new config and run parity, 4. format a new drive, 5. copy the clone to the new reformatted drive? reiserfsck --check started at Tue Mar 27 10:47:03 2018 ########### Replaying journal: Trans replayed: mountid 50, transid 21863, desc 2407, len 1, commit 2409, next trans offset 2392 Trans replayed: mountid 50, transid 21864, desc 2410, len 1, commit 2412, next trans offset 2395 Trans replayed: mountid 50, transid 21865, desc 2413, len 1, commit 2415, next trans offset 2398 Trans replayed: mountid 50, transid 21866, desc 2416, len 1, commit 2418, next trans offset 2401 Trans replayed: mountid 50, transid 21867, desc 2419, len 1, commit 2421, next trans offset 2404 Trans replayed: mountid 50, transid 21868, desc 2422, len 1, commit 2424, next trans offset 2407 Trans replayed: mountid 50, transid 21869, desc 2425, len 6, commit 2432, next trans offset 2415 Trans replayed: mountid 50, transid 21870, desc 2433, len 6, commit 2440, next trans offset 2423 Trans replayed: mountid 50, transid 21871, desc 2441, len 6, commit 2448, next trans offset 2431 Trans replayed: mountid 50, transid 21872, desc 2449, len 6, commit 2456, next trans offset 2439 Trans replayed: mountid 50, transid 21873, desc 2457, len 12, commit 2470, next trans offset 2453 Trans replayed: mountid 50, transid 21874, desc 2471, len 9, commit 2481, next trans offset 2464 Trans replayed: mountid 50, transid 21875, desc 2482, len 8, commit 2491, next trans offset 2474 Trans replayed: mountid 50, transid 21876, desc 2492, len 6, commit 2499, next trans offset 2482 Trans replayed: mountid 50, transid 21877, desc 2500, len 6, commit 2507, next trans offset 2490 Trans replayed: mountid 50, transid 21878, desc 2508, len 6, commit 2515, next trans offset 2498 Trans replayed: mountid 50, transid 21879, desc 2516, len 6, commit 2523, next trans offset 2506 Trans replayed: mountid 50, transid 21880, desc 2524, len 6, commit 2531, next trans offset 2514 Trans replayed: mountid 50, transid 21881, desc 2532, len 13, commit 2546, next trans offset 2529 Trans replayed: mountid 50, transid 21882, desc 2547, len 12, commit 2560, next trans offset 2543 Trans replayed: mountid 50, transid 21883, desc 2561, len 8, commit 2570, next trans offset 2553 Trans replayed: mountid 50, transid 21884, desc 2571, len 6, commit 2578, next trans offset 2561 Replaying journal: Done. Reiserfs journal '/dev/sdn1' in blocks [18..8211]: 22 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 486398 Internal nodes 2980 Directories 11505 Other files 121175 Data block pointers 486724854 (0 of them are zero) Safe links 1 ########### reiserfsck finished at Tue Mar 27 11:42:02 2018
March 27, 20188 yr Like I mentioned you're seeing the emulated disk on the array, and a corrupt one since the disk dropped offline during the parity sync, you can run reiserfsck on /dev/md18 (after starting in maintenance mode), since there should still be some good data, then rebuild disk18 to a new disk, then mount the old disk with UD and copy everything you can overwriting the data on new disk18, everything you can copy should be OK, what you can't copy check the files on the new disk to see if they are OK. Another option would be to clone the old disk to a new disk, then do a new config and re-sync parity with the new disk in place.
March 27, 20188 yr Author Ok. So cloning the disk would be as follows: 1. Add a new UD to the server; 2. Start the array (or not???); 3. dd if=/dev/sdn of=/dev/sdY bs=32M (X=source Y=destination) 4. replace new UD cloned drive with original sdn 5. reassign drives 6. create new parity?
March 27, 20188 yr 2 minutes ago, thefly said: Start the array (or not???); Doesn't really matter for the clone, but better not since there's filesystem corruption on the emulated disk. 3 minutes ago, thefly said: create new parity? Yes, after new config sync parity
March 27, 20188 yr 6 minutes ago, thefly said: dd if=/dev/sdn of=/dev/sdY bs=32M (X=source Y=destination) Sorry, didn't noticed this, because the source disk is failing use ddrescue for the clone instead.
March 27, 20188 yr Author root@Tower:~# ddrescue -f /dev/sdo /dev/sdh /boot/ddrescue.log -bash: ddrescue: command not found
March 27, 20188 yr I believe I already linked that for you before, that's why I assumed you were already using ddrescue, or am I confusing your with someone else?
March 27, 20188 yr 2 minutes ago, thefly said: I installed Nerd Pack already. Why command not found? Nerdpack doesn't install any of its packages by default. It allows you to choose which to install.
March 27, 20188 yr Author Dashboard Main Shares Users Settings Plugins Apps Tools off-line Feedback Help Info Log Nerd Pack Name Status Size Downloaded Installed Plugins unInstall Select All by statusuninstalled by downloadno by installno apr-1.5.0-x86_64-1.txz uninstalled 226.3 KB no no -- Off apr-util-1.5.3-x86_64-1.txz uninstalled 121.7 KB no no -- Off bc-1.06.95-x86_64-2.txz uninstalled 99.7 KB no no -- Off bind-9.9.8P4-x86_64-1_slack14.1.txz uninstalled 2.1 MB no no -- Off bwm-ng-0.6-x86_64-1_SBo.txz uninstalled 40.7 KB no no -- Off cksfv-1.3.14-x86_64-1_slack.txz uninstalled 22.4 KB no no -- Off cpio-2.11-x86_64-2.txz uninstalled 178.2 KB no no -- Off fdupes-1.51-x86_64-3_slack.txz uninstalled 17.1 KB no no -- Off git-2.3.5-x86_64-1.txz uninstalled 4.1 MB no no -- Off iftop-1.0pre2-x86_64-1.txz uninstalled 37.7 KB no no -- Off inotify-tools-3.14-x86_64-1.txz uninstalled 42.9 KB no no -- Off iotop-0.6-x86_64-1_fs.tgz uninstalled 49.1 KB no no -- Off iperf-3.0.11-x86_64-1_SBo.txz uninstalled 72.4 KB no no -- Off jhead-3.00-x86_64-1_slack.txz uninstalled 47.7 KB no no -- Off joe-3.7-x86_64-1.txz uninstalled 310.6 KB no no -- Off kbd-1.15.3-x86_64-2.txz uninstalled 1.1 MB no no -- Off lftp-4.7.3-x86_64-2.txz uninstalled 788.8 KB no no -- Off lshw-B.02.17-x86_64-1_SBo_LT.txz uninstalled 1.3 MB no no -- Off mcelog-128-x86_64-1.txz uninstalled 308.6 KB no no -- Off nc-1.10-x86_64-1.txz uninstalled 52.3 KB no no -- Off neon-0.29.6-x86_64-2.txz uninstalled 202.5 KB no no -- Off nload-0.7.4-x86_64-1_slack.txz uninstalled 58.6 KB no no -- Off nodejs-4.2.4-x86_64-1_slack.txz uninstalled 5.8 MB no no -- Off p7zip-9.38.1-x86_64-1tom.txz uninstalled 1.1 MB no no -- Off perl-5.22.0-x86_64-1.txz uninstalled 14.0 MB no no -- Off python3-3.5.1-x86_64-1.txz uninstalled 18.1 MB no no -- Off python-2.7.9-x86_64-1.txz uninstalled 13.6 MB no no -- Off readline-6.3-x86_64-1.txz uninstalled 335.8 KB no no -- Off screen-4.2.1-x86_64-1.txz uninstalled 521.9 KB no no -- Off sshfs-fuse-2.5-x86_64-1sl.txz uninstalled 52.9 KB no no -- Off strace-4.10-x86_64-1.txz uninstalled 160.6 KB no no -- Off stunnel-5.35-x86_64-2.txz uninstalled 161.9 KB no no -- Off subversion-1.7.16-x86_64-1.txz uninstalled 3.2 MB no no -- Off sysstat-9.0.6.1-x86_64-1.txz uninstalled 181.0 KB no no -- Off unrar-5.2.5-x86_64-1_SBo.txz uninstalled 317.3 KB no no -- Off utempter-1.1.5-x86_64-1.txz uninstalled 13.6 KB no no -- Off vim-7.4.898-x86_64-1.txz uninstalled 5.9 MB no no -- Off virtualenv-13.1.2-x86_64-1_slack.txz uninstalled 1.5 MB no no -- Off
March 27, 20188 yr 2 minutes ago, thefly said: No updates when checked. Just installed last week. No idea then, post in the plugin thread.
March 27, 20188 yr Now that I think about possibly because you're on a very old unRAID release, some utils might require a more recent one.
Archived
This topic is now archived and is closed to further replies.