LFletcher

I've been having a look. In reality it shouldn't be too difficult to work out what goes where as its either a movie or a tv series/episode. I suppose I didn't expect everything to be in a lost+found directory, but as I've never done this before - you live and learn. I'll wait for the scan of corrupt files to finish, but what is my next step? Is it to unassign Disk 5 (physically remove it from the server), and then assign this cloned disk in its place? If I do that will unRaid recreate the old folder structure and I'll just have to manually move things into the correct place or will I have to do something else? Also what are the next steps to sorting out the issues with both Disk 3 (which we unassigned earlier) and the Parity 2 drive which also has issues still? Thanks

ddrescue has now finished. I then ran the xfs_repair against the cloned drive; I've now run the following commands from the ddrescue faq; printf "unRAID " >~/fill.txt ddrescue -f --fill=- ~/fill.txt /dev/sdd /boot/ddrescue.log find /mnt/disks/Z2GBNVET -type f -exec grep -l "unRAID" '{}' ';' which is still in the process of running. When looking at the data on the mounted cloned drive everything appears to now be in a lost+found directory Shouldn't the cloned drive have a directory structure that mirrored the original disk? I assumed after the check I would have been able to unassign the old bad drive (Disk 5) and assign the cloned drive in it's place, restart the array and this part of the issue would be resolved. I guess with just the lost+folder that is not going to be the case or am I missing something?

Is there any way to speed up the ddrescue process? It's been running for about 30 hours and it less than 70% done of pass 1 (ignore the run time on the screen shot, I had to restart it after 24 hours, so this is the second run)

I have copied the important stuff onto another (external) drive. Ran the -v command and got this; So then ran the -vL and got this; And also these notifications;

It's not my machine (I'm trying to sort it out for a friend), but it's safe to assume there won't be any backups. I know there are photos on the array, but I don't know where they are, or whether they are likely to be on any of the impacted drives. Obviously in an ideal world we'll be able to restore all of the drives without losing any data, but in an ideal world he would have paid more attention when the box started having issues (and given it to me sooner). What options do we have, assuming we have no backups to rely on and I need to try and save as much of the data as possible? All of the assistance I have been given so far is very much appreciated.

OK, so I restarted the array in maintenance mode and ran the check with -nv and this was the output I assume I now need to run; -v /dev/md5

Yes, the disk was unassigned when I started the server, so I reassigned it, but I hadn't started the array up until now. I have unassigned disk 3 and started the array. Disk 3 now resides in the unassigned devices section Disk 5 isn't happy though and states its unmountable I've attached the updated diagnostics file. tower-diagnostics-20221123-1623.zip

Parity 2 passes a SMART test, but unRAID isn't happy with the results Disk 3 was unassigned when I booted the server up. When I allocated the drive thats when the udma crc message popup box came up. The drives are on a miniSAS backplane so it's unlikely to be a cable issue causing the crc errors. To the best of my knowledge I don't believe anything has been written to the emulated disk 3. Thanks

Hi, Helping a friend who has some issues with his unRAID server. My understanding is that the parity drive had issues first of all and went offline (Parity 2). Then there was issues with a data drive (disk 3 - sdd) - this appears to have udma crc errors. I did SMART checks on the other drives and it appears Disk 5 (sdh) has issues as well, although it hasn't failed the drive (yet). I've got 3 14TB drives, which I had originally planned to replace both the parity drives with and also disk 3. Now that disk 5 also has potential issues I can get another 14TB drive to replace that. My question is, can the data from disk 3 be recovered or is it lost? If it can be recovered whats the correct order to do things in? Do I need to copy the data from disk 5 before that has any more issues? I've attached the diagnostics file as well. Thanks in advance. tower-diagnostics-20221123-1310.zip

Thanks for the response - very much appreciated. New hard drive arriving tomorrow. Fingers crossed I don't have another one die on me with this rebuild.

I had a drive failure a few days ago (Disk 5). Replaced it with a new drive, precleared and then started the data rebuild. That finished a few hours ago, but it appears that I have had another drive failure (Disk 8 this time). I am mostly concerned that the data rebuild wasn't successful for disk 5 - although the message on screen was green and said that there were 0 errors. I have checked some random files on Disk 5 and they appear to play back fine. I've attached the diagnostics file, would someone be able to confirm that the rebuild of disk 5 did complete successfully? I'm paranoid that it wasn't successful and that I have lost data on that drive. Is it common for other drives to fail during a rebuild - I thought the data was reconstructed from information on the parity drives (or is it stored across other drives on the array as well)? Once thats done, 'll have to start the process all over again with disk 8. Thanks in advance unraid-diagnostics-20210224-1852.zip

Hi, I've been running on 6.5.3 since it was released. Finally upgraded this box to 6.6.7 and I can no longer access the SMB shares via the server name. Thought it might have been an issue with that specific release so upgraded to the Next Branch release of 6.7.0-rc5, but that has the same issue. Before upgrading I could access \\UNRAID\media from both my Windows 8.1 and 10 machines without issue. Since the upgrade the only way I can now access the box (from the Windows clients) is via the ip address, so \\192.168.1.235\media. If I try to access via the server name I get a Network Error message and Windows Cannot access \\UNRAID - specifically The network path was not found. None of the dockers or anything else appears to be having any issues accessing the shares on the box. Having searched the forums the most resolutions seem to point back to issues on the client machines, but I do not believe the issue is with the Windows clients in this instance. I have another unraid server on 6.7.0-rc5 (which was previously running 6.6.7 and 6.5.3 before that) and they can both access all the smb shares as expected. I have checked settings -> SMB settings and both servers appear to have the same values. Another thread mentioned removing an extras folder from the flash drive, but I don't have one of those. I checked the Fix Problems plugin and that only mentions a few deprecated plugins. Does anyone have any idea what might be causing the issue? It seems odd that one server running this release is fine and the other isn't. Thanks for your help. unraid-diagnostics-20190323-1521.zip

I have tried putting the drive back into its original bay (it's in a 16 bay server case using HBA's and SFF8087 connectors) and it won't show up. I've moved it to two other bays and it also doesn't show up. I tried a different hard drive in the original bay of this disk and that is recognised without any issues. I can't leave the drive attached to the SATA connector on the motherboard, so are there any other options as to why Unraid won't recognise it now unless it's connected to the SATA connector on the motherboard? It worked fine for months before this. I note these messages are still in the log; Feb 6 22:16:02 Media kernel: sd 9:0:3:0: rejecting I/O to offline device Feb 6 22:16:02 Media kernel: sdd: unable to read partition table Feb 6 22:16:02 Media kernel: sd 9:0:3:0: [sdd] Attached SCSI disk Feb 6 22:16:03 Media emhttpd: device /dev/sdd problem getting id Any ideas as to whether reformatting the drive on a different system would help? media-diagnostics-20190206-2216.zip

Right, I have connected it to an onboard SATA port and the disk shows up. It's sdd rather than sdl this time. It won't let me run a SMART test against it (either short or long) - when I click on start, it flashes stop and then shows the start button again. Any thoughts on what I need to do next? Thanks media-diagnostics-20190204-2219.zip

Hi, Turned on a box I am building for someone else (after it has been off for a few weeks) and one of the 2 parity drives has disappeared. The GUI tells me it is missing. When looking at the logs it appears (if I am reading them correctly) that the partition table on the parity drive cannot be read. Feb 1 11:55:50 Media kernel: sd 10:0:6:0: [sdl] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 Feb 1 11:55:50 Media kernel: sd 10:0:6:0: [sdl] tag#4 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Feb 1 11:55:50 Media kernel: print_req_error: I/O error, dev sdl, sector 0 Feb 1 11:55:50 Media kernel: Buffer I/O error on dev sdl, logical block 0, async page read Feb 1 11:55:50 Media kernel: sd 10:0:6:0: rejecting I/O to offline device Feb 1 11:55:50 Media kernel: ldm_validate_partition_table(): Disk read failed. Feb 1 11:55:50 Media kernel: sd 10:0:6:0: rejecting I/O to offline device Feb 1 11:55:50 Media kernel: sdl: unable to read partition table The drive doesn't appear in unassigned drives and I cannot get to any smart information. I have tried the drive in a different slot (just in case) and that also didn't resolve the issue. Any idea how I can resolve the issue? I assume I should just be able to format the drive, put it back in the box and rebuild parity from scratch - but as I can't get to the drive how would I go about this? I've attached the diagnostics file as well. Thanks for your help media-diagnostics-20190201-1157.zip