drjUnraid

Thanks everyone. I was able to replace the flash drive, get access to my shares via trial license, copy the backups from the share to my desktop using cloud commander. Then I restored my config folder, fixed my license key with tech support, and now I'm back in business.

Thanks Trurl. I will probably have to contact lime-tech as its been less than 12 months since I replaced my flash drive. I pre-emptively replaced it last year, but it didn't last very long....I learned those micro flash drives, while small, are not very robust.

I was still on 6.9.1 release, should I try and reinstall that version first? Were all the errors in my diagnostic related to the flash? Or is something else going on? Thanks in advance.

Hi Experts, Need help I noticed in my log I was seeing errors (Pasted below). So I downloaded a diagnostic log and rebooted. When my system came up, it launched right into a parity check which I thought was odd since I had just done one a few days ago. Then I noticed a bunch of read only errors showing up, so I stopped the parity check, downloaded a 2nd diagnostic file, then shut down the server. When I went for 2nd reboot my BIOS complained there was no boot disk. I pulled the flash drive out and tried it in Windows computer and its now is blank and can't be reformatted. Corrupt. So at a minimum I have to fix the flash and maybe other stuff. I use Community Apps to make weekly backups of my flash drive, but I store it an UInraid share (followin spaceinvader video). So I have a backup of my flash drive, but its on unraid. Whats my best course of action? I do have a recent copy of which disks are Parity/data etc. Get a trial license, start up unraid, get access to the share, download the flash backup, restore flash backup on different USB stick, reboot server from new restored stick? Thanks! Apr 8 07:54:05 NAS4x12 kernel: blk_update_request: critical target error, dev sda, sector 36456 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 0 Apr 8 07:54:05 NAS4x12 kernel: Buffer I/O error on dev sda1, logical block 34408, lost async page write Apr 8 07:54:05 NAS4x12 kernel: Buffer I/O error on dev sda1, logical block 34409, lost async page write Apr 8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Apr 8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x7 [current] Apr 8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x27 ASCQ=0x0 Apr 8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 1e 1c 28 00 00 f0 00 Apr 8 07:54:51 NAS4x12 kernel: blk_update_request: critical target error, dev sda, sector 1973288 op 0x1:(WRITE) flags 0x4800 phys_seg 30 prio class 0 Apr 8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Apr 8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x7 [current] Apr 8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x27 ASCQ=0x0 Apr 8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 1e 1d 18 00 00 f0 00 Apr 8 07:54:51 NAS4x12 kernel: blk_update_request: critical target error, dev sda, sector 1973528 op 0x1:(WRITE) flags 0x4800 phys_seg 30 prio class 0 Apr 8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Apr 8 07:54:51 NAS4x12 kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x7 [current] nas4x12-diagnostics-20210408-0754_Before1st_Reboot.zip nas4x12-diagnostics-20210408-1157_Before2ndReboot.zip

Thanks for the plugin, very cool. I just did a gather operation moving 714 folders and 7TB and ended up with 216 moves that resulted in "rmsrc button" appearing. I did have to do the docker safer permissions before I started. I show a log snippet below. Couple questions: Is it normal to get that many; anything I can do to minimize it? I basically moved all my data to disk 4. When I go and look for the data that genererated the "RSMC" I do not see it the original on Disk1, 2, or 3 anymore. Is there a chance it really did delete the source file already? Do I still need to click the RSMC button? Is there a faster way to click the RSMC button? Currently I go to the History tab of UnBalance, scroll down to find "RSMC", click it, then the webpage reloads. Navigate back to History tab, scroll down to find the next RSMC, click it. Rinse and repeat. Lost of clicking and scrolling. Here is a an example of an RSMC generated for Guardians of the Galaxy in the unbalance log. It processes the file then moves on to the next one: However about 1000 lines (and 4 hours) later in the log I get this entry: Edit: I see in the screen shots the 2nd failed operation is referencing Disk2, vs Disk1 in the first operation. Edit2: When I do click the RSMC button it seems to be confirming that the data was in fact deleted?

I do not have any spare ports. I have an PCIe card with 4 ports, but that is also marvel chip. Is there a PCI card with Intel, I will search. Maybe an LSI card? Also one other question, I'm currently doing a rebuild; can I pause the rebuild, power down, power up, and resume rebuild?

Hi All, I've had a couple issues with my array lately. In 3 weeks I've had Disk 4 go disabled and become not mountable (Replaced and rebuilt), Disk 1 XFS File corruption (repaired file system), and now yesterday Disk 1 is showing at Device Disabled. I could hear it spinning up, then spinning back down. I downloaded Diags, rebooted, and it sounds ok and passed a SMART test. Disk 1 is a pretty new disk. Seems like some gremlins? I'm buying new Sata Cables to try. Should I try a new Power Supply (curerntly a 700W from 2013). Is my motherboard taking a crap? These HW issues are driving me nuts lately Diag and Smart report attached To fix disk 1 I'm going to rebuild it onto a spare 12TB I have. Disable Array, replace disk 1 in array with spare 12TB, restart and repair array. I'll keep the original 12TB Disk 1 in case something bad happens during rebuild. nas4x12-smart-20200820-1953.zip nas4x12-diagnostics-20200819-2249.zip

Thanks. I tried the plug-in using v6.7.3 and I ran into the same issue that @Keexrean had where two ports were being passed, but two were remaining in Unraid. Unraid was also randomly reassigning the eth0 interface to the HW address of the wrong Ethernet port after reboots. I then uninstalled the plugin, installed v6.9.0 Beta 25. I used the now built in tool to select the 4 ethernet ports off the NIC. That was the solution as it is now working again. I'm back to just having append initrd=/bzroot in my syslinux config.

I was able to solve this. 1st we repaired the XFS file system. Use Space Invaders XFS guide. Had to use -L while repairing. Then I tried to mount Disk 4, but it did not want to mount. So I added a new disk and rebuilt disk 4 using the parity and new disk.

I had a working setup with a 4 port intel network card and pfsense running in a VM (following Spaceinvader guide mostly). Then I had a disk fail and some issues, that i've fixed. Now my last issue is I can't get my pfsense working again. It seems that unRaid keeps detecting and initializing my 4 port NIC even thought I have used the "append vfio-pci.ids=8086:150e initrd=/bzroot" in my syslinux config. This used to work fine, but now unRaid just keeps detecting the card and I can't pass it thru to the VM. Any suggestion? I've tried deleting the vfio-pci.ids=8086:150e line and rebooting, but adding it back it still doesn't work. nas4x12-diagnostics-20200809-1723.zip

@trurl et all I redid all the screen shots here. Disk1 FileSystem Check is shown attached. (Screenshot_2020-08-03 NAS4x12 Device.png) The main and Dashboard screens are also captured. Before this boot I swapped the power cords and data cords for Disk 1 with another disk. I think I still heard the spindown/reset. It didn't change the file structure error status. Included latest diagnostic dump. I have additional 12TB HD's I can swap in if needed when it comes to recovery. nas4x12-diagnostics-20200803-1303Stop_Restart_MovedDisk1PowerAndDataCable.zip

@trurl and Unraiders: I got the a new SATA card installed. I can see Disk4 in the unassigned devices now, its the Toshiba 2TB drive. (I also figured out how to save screen shots in the console GUI to the unRaid flash drive). That made me realize that the log file I "thought" I saved was not correct as you suspected. I uploaded a new one to the OP and repeated it here as well. I booted, stoped array, did some check disk, started array in maintence mode, checked Disk1 XFS File System Repair "-nv" then I restarted the array and took the diagnostic. Not sure which problem to tackle first, Disk 4 or Disk 1. I notice that I can hear Disk1 clicking, like its resetting or spinning down abruptly. I changed the SATA data cable and switched to a different Sata Port on the Motherboard, but it didn't change the clicking/resetting sound. Thanks! nas4x12-diagnostics-20200802-2320_Stop_RestartArray.zip

Sorry for photos. I lost the net login and had to plug in a monitor and keyboard to the server. Then take photos with my camera to post to forum. I'll do screen shots whenever possible. Thanks for the reply. The array size is much smaller now that it says Disk 1 is unmountable. Any advice on the order to try and recover my systems disks 4 and disk 1.

Hi All, I have an issue with my Unraid 6.8.2. I think its two issues that happened back to back. I hope I'm not screwed. Apologies for photos, lost my net connection and had to go log into unraid local GUI. After a server reboot my Disk 4 disappeared and came up as "Not Installed". I have a 4 port Sata 3 PCIE Card that uses a Marvell controller and it has issues occasionally being detected by Unraid. In the past I added "iommu=pt" in my syslinux and it fixed it mostly, but occasionally after a reboot it does still disappear and show as Not Installed. I decided to clean shut down my server again to see if Disk 4 will come back. Power back up After the reboot it takes forever to boot when I'm able to log in using the GUI Console I see a new Issue: Disk 1 says it's "Unmountable: No File System". It's giving me an option to Format it, which I don't believe I want to do. I stopped the array and clicked on Disk 1 and did a Files System Check "-nv", but not a repair. At this point I am stuck with my knowledge and need Google/Help. So thats the background, I've attached my diagnostic file, after all the reboots (sorry for that). I'd like to recover my data and array if possible. I've ordered a different SATA3 PCI card that uses a ASMEDIA chip, so hopefully that resolves the Disk 4 issue. How about disk 1 loss of file system? Can I get Disk 1 back? Is there a certain order I should try and recover my system? I'm about to embark on my own searching exercise. Thanks in advance. Edit1_20200802: I got a new Sata PCIe card and now Disk 4 is detected in Unassigned Devices. I uploaded a new Diagnostic as I realized my other one was not current. nas4x12-diagnostics-20200802-2320_Stop_RestartArray.zip

I also have this problem. Came upon this googling. I was thinking to maybe try and just assign them myself and hope i get it right. If I go for edges of the card I should get eth0 and eth3 then can guess from there haha. Or downgrade to 2.3.4 like you.