thefly

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?

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

Next? Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (2): (Input/output error). Aborted

Trying to mount a failed drive that used to be in my array in an attempt to copy out data. Is this completely dead or is there a potential to get it going? Mar 24 10:56:31 Tower kernel: sd 1:0:1:0: [sdi] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)Mar 24 10:56:31 Tower kernel: sd 1:0:1:0: [sdi] Write Protect is offMar 24 10:56:31 Tower kernel: sd 1:0:1:0: [sdi] Mode Sense: 00 3a 00 00Mar 24 10:56:31 Tower kernel: sd 1:0:1:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUAMar 24 10:56:31 Tower kernel: sdi: sdi1Mar 24 10:56:31 Tower kernel: sd 1:0:1:0: [sdi] Attached SCSI diskMar 24 10:56:37 Tower emhttp: ST31500341AS_9VS1GLK5 (sdi) 1465138584Mar 24 10:56:39 Tower emhttp: ST31500341AS_9VS1GLK5 (sdi) 1465138584Mar 24 10:59:43 Tower emhttp: ST31500341AS_9VS1GLK5 (sdi) 1465138584Mar 24 10:59:59 Tower unassigned.devices: Adding disk '/dev/sdi1'...Mar 24 10:59:59 Tower unassigned.devices: Mount drive command: /sbin/mount -t reiserfs -o auto,async,noatime,nodiratime '/dev/sdi1' '/mnt/disks/ST31500341AS_9VS1GLK5'Mar 24 10:59:59 Tower kernel: REISERFS (device sdi1): found reiserfs format "3.6" with standard journalMar 24 10:59:59 Tower kernel: REISERFS (device sdi1): using ordered data modeMar 24 10:59:59 Tower kernel: REISERFS (device sdi1): journal params: device sdi1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30Mar 24 10:59:59 Tower kernel: REISERFS (device sdi1): checking transaction log (sdi1)Mar 24 11:00:42 Tower kernel: sd 1:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00Mar 24 11:00:42 Tower kernel: sd 1:0:1:0: [sdi] tag#0 CDB: opcode=0x28 28 00 ad f2 a0 a8 00 00 08 00Mar 24 11:00:42 Tower kernel: blk_update_request: I/O error, dev sdi, sector 2918359208Mar 24 11:00:42 Tower kernel: REISERFS error (device sdi1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1 2 0x0 SD]Mar 24 11:00:42 Tower kernel: REISERFS (device sdi1): Remounting filesystem read-onlyMar 24 11:00:42 Tower kernel: REISERFS (device sdi1): Using r5 hash to sort namesMar 24 11:00:42 Tower kernel: sd 1:0:1:0: [sdi] Read Capacity(16) failed: Result: hostbyte=0x04 driverbyte=0x00Mar 24 11:00:42 Tower kernel: sd 1:0:1:0: [sdi] Sense not available.Mar 24 11:00:42 Tower kernel: sd 1:0:1:0: [sdi] Read Capacity(10) failed: Result: hostbyte=0x04 driverbyte=0x00Mar 24 11:00:42 Tower kernel: sd 1:0:1:0: [sdi] Sense not available.Mar 24 11:00:42 Tower kernel: sdi: detected capacity change from 1500301910016 to 0Mar 24 11:00:42 Tower unassigned.devices: Mount of '/dev/sdi1' failed. Error message: mount: /dev/sdi1: can't read superblockMar 24 11:02:35 Tower emhttp: device /dev/sdi zero-sizeMar 24 11:02:38 Tower emhttp: device /dev/sdi zero-sizeMar 24 11:02:52 Tower emhttp: device /dev/sdi zero-sizeMar 24 11:04:21 Tower emhttp: device /dev/sdi zero-sizeMar 24 11:04:57 Tower emhttp: device /dev/sdi zero-sizeMar 24 11:04:58 Tower emhttp: device /dev/sdi zero-sizeMar 24 11:04:59 Tower emhttp: device /dev/sdi zero-sizeMar 24 11:05:29 Tower emhttp: device /dev/sdi zero-size

Got it. So don't I add a disk using UD plug in and just clone to it?

Both Disk 2 and 10 are mostly videos. I have no source back-up files. I have chosen ddrescue and have installed the plug in. As I understand it, if I place a new drive in free slot 19 and wish to clone disable device Disk 10, I would enter the following terminal command to attempt a clone??: ddrescue -f /dev/sd19 /dev/sd10 /boot/ddrescue.log

I'm stuck with Disk 2 showing missing, contents emulated and Disk 10 disabled, contents emulated. Obviously I can not start the array. I am resigned to losing these disks but would like some direction on the order of new drive replacements. Is there any way to get a directory of what was on the drives? Do I replace Disk 2 or 10 first? Depressing...

Restarted. See pre and post diagnostics. Disk 5, Disk 10 now gone tower-diagnostics-current.zip tower-diagnostics-restart.zip

After suffering numerous disk issues I have completed an uncorrected parity-check and I am left with (what I believe are) numerous disk irregularities. Can someone provide a next step(s) to deal with them. Attached is a screenshot of main. Thanks.

Here is my overview: 1. Yesterday I replaced disk 8 and followed johnnie.black's instruction (using terminal mdcmd set invalidslot 2. Drive 8 and 10 were unmountable during the parity-sync 3. I cancelled the sync at about 13% and shut down the server 4. Today I started the server to find Disk 2 unavailable for assignment BUT Disk 10, which was a problem yesterday, now is assignable 5. I shut down and I have checked all cables 6. With new drive in slot 8, disk 2 does not appear for assignment at all 7. On start up with dead drive in slot 8 back installed, disk 2 appears available for assignment but once assigned disappears after a few minutes I am attaching diagnostics based on my current state with the new drive in slot 8. Your help during this freak out is very much appreciated. tower-diagnostics-20180315-1249.zip

I will investigate those possible issues, reboot and update this thread. Thank you.

Attached tower-diagnostics-20180315-1034.zip

The drive is not available for assignment anymore.

Disk 2 was not a problem previously. It is now gone for assignment. Is there a terminal command to try and re-mount it?

Bigger issues now. Created a new config: 1. disk 2 has now disappeared from the selection list; 2. disk 8 is showing the new disk that I previously entered 3. disk 10 is unassigned

Based on some differing posts, I stopped the process last night and performed a clean shut down. I restarted this morning and before bringing the array online could I please get direction of the steps I should take this time: 1. Repeat johnnie.blacks attempt to re-enable disk 10 or 2. do not check the "parity is already valid" box and start the array or 3. another option In notice my option to bring the array online only allows: Start will bring the array on-line and start Parity-Sync. Thanks.

I have completed the prior instructions. Is this the process I should be achieving to repair?

It has archived notifications in the tools section

Please bear with my ignorance. I have not ssh'd in over 3 years. I have a monitor connected to the box. Login is root and takes me to root@Tower:~#. I then enter mdcmd set invalidslvot 8 [single space between entries, then return]. Good?

Here are the diagnostics tower-diagnostics-20180314-1243.zip

Hey team. Just returned form a vacation to an extended power outage. Upon restarting I was presented with a disk outage (Disk 8 - see image). I shut down and inserted an new drive. When restarting and preparing to initialize, Disk 10 is now showing and error (Disk 10 - see image). Am I in major trouble?

Server came back online. Here are diagnostics. It will revert back to the Supermicro log in sporadically. Thanks someone.... tower-diagnostics-20170629-1833.zip

j.b I have no idea what that means? I get a mount and then it defaults to the log in.

Hi Guys. I've had a great experience with UnRaid. So good (a few years of no issues) in fact that I've completely forgotten what to do in case of an issue. Well I have one and I'm lost. My server suddenly dropped today, reappeared and dropped again. I am getting a SuperMicro Log in screen. I'm freaking! Experts?