OsoSuerte Posted November 6, 2020 Share Posted November 6, 2020 (edited) I had a drive fail, replaced and rebuilt with out issues. Everything seemed to be fine except now my shares are empty. I only use unraid for media and I run a plex server. ON the GUI I click the shares tab and it shows my shares. User shares are Plex and Misc. Disk shares are disk1 - disk7. If I click on the folder icon to the right of plex it opens and says parent directory with 0 objects 0 Directories and 0 files. When I navigate to the disk shares all of the files are there and intact. I booted up in maintenance mode and ran a file system check on each drive with no issues. I tried to add a new share and replace the old one but that resulted in an immediate "Share has been deleted" message and all the shares disappeared tried to add shares multiple times with the same result. Not sure if this is related so I tried to reboot but the system got stuck on unmounting and retrying. I waited an hour with no change and had to manually power down. On reboot the same thing happened and if I try and shut down the array it gets stuck in the same loop. Any help would be appreciated. tower-diagnostics-20201106-1129.zip Edited November 6, 2020 by OsoSuerte Add log Quote Link to comment
JorgeB Posted November 6, 2020 Share Posted November 6, 2020 SSD dropped offline, then came back up again, replace cables and try again. Quote Link to comment
OsoSuerte Posted November 6, 2020 Author Share Posted November 6, 2020 Thanks I will work on that, Can you tell me what line in the log you got that from? I am trying to learn/understand Quote Link to comment
OsoSuerte Posted November 6, 2020 Author Share Posted November 6, 2020 Replaced the cable and powered on. I have not tried to start the Array yet because I dont want to get into the loopp preventing shut down. I will attach the new log. Do I need to start the array and post new log? tower-diagnostics-20201106-1206.zip Quote Link to comment
trurl Posted November 6, 2020 Share Posted November 6, 2020 Just now, OsoSuerte said: Do I need to start the array and post new log? Yes we can't tell if disks will mount until you start. Quote Link to comment
OsoSuerte Posted November 6, 2020 Author Share Posted November 6, 2020 (edited) Started array and added new log tower-diagnostics-20201106-1214.zip Edited November 6, 2020 by OsoSuerte Quote Link to comment
OsoSuerte Posted November 6, 2020 Author Share Posted November 6, 2020 that seems to have fixed the shares issue they now show up under user shares and can access the files on the hdds but I still can not stop the array. Still says "Unmounting disks...Retry unmounting disk share(s)...Unmounting disks...Retry unmounting disk share(s)" Quote Link to comment
trurl Posted November 6, 2020 Share Posted November 6, 2020 Post new diagnostics or at least syslog so we can see what is happening now. Quote Link to comment
OsoSuerte Posted November 6, 2020 Author Share Posted November 6, 2020 new log attached tower-diagnostics-20201106-1326.zip Quote Link to comment
trurl Posted November 6, 2020 Share Posted November 6, 2020 Nov 6 12:21:31 Tower kernel: ata6.00: ATA-8: ST2000DL003-9VT166, 5YD56M8Y, CC32, max UDMA/133 ... Nov 6 12:21:31 Tower kernel: ata2.00: ATA-9: ST5000DM000-1FK178, W4J0GWNW, CC47, max UDMA/133 ... Nov 6 12:32:22 Tower kernel: ata6.00: configured for UDMA/25 Nov 6 12:32:22 Tower kernel: ata6: EH complete Nov 6 12:32:54 Tower kernel: ata6: lost interrupt (Status 0x50) Nov 6 12:32:54 Tower kernel: ata6.00: limiting speed to PIO4 Nov 6 12:32:54 Tower kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Nov 6 12:32:54 Tower kernel: ata6.00: failed command: READ DMA EXT Nov 6 12:32:54 Tower kernel: ata6.00: cmd 25/00:00:68:1d:69/00:02:02:00:00/e0 tag 0 dma 262144 in Nov 6 12:32:54 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 6 12:32:54 Tower kernel: ata6.00: status: { DRDY } Nov 6 12:32:54 Tower kernel: ata6: soft resetting link Nov 6 12:32:54 Tower kernel: ata6.00: configured for PIO4 Nov 6 12:32:54 Tower kernel: ata6: EH complete Nov 6 12:42:32 Tower kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x400001 action 0x6 frozen Nov 6 12:42:32 Tower kernel: ata2.00: irq_stat 0x48000001, interface fatal error Nov 6 12:42:32 Tower kernel: ata2: SError: { RecovData Handshk } Nov 6 12:42:32 Tower kernel: ata2.00: failed command: WRITE DMA EXT Nov 6 12:42:32 Tower kernel: ata2.00: cmd 35/00:40:e0:04:00/00:05:1e:00:00/e0 tag 14 dma 688128 out Nov 6 12:42:32 Tower kernel: res 51/84:40:e0:05:00/00:04:1e:00:00/e0 Emask 0x10 (ATA bus error) Nov 6 12:42:32 Tower kernel: ata2.00: status: { DRDY ERR } Nov 6 12:42:32 Tower kernel: ata2.00: error: { ICRC ABRT } Nov 6 12:42:32 Tower kernel: ata2: hard resetting link Check connections Quote Link to comment
OsoSuerte Posted November 6, 2020 Author Share Posted November 6, 2020 (edited) I have replaced sata cable on disk two yesterday. That is the same drive that failed that I replaced. I also replaced the cable for the SSD as suggested earlier. If 2 and 6 also need to be replaced is that indicative of a bigger issue or a bad batch of cables? Or are these cables just at the end of their life cycle? Also, would that cause the array to not be able to shut down? Edited November 6, 2020 by OsoSuerte Quote Link to comment
trurl Posted November 6, 2020 Share Posted November 6, 2020 Did you also check power connections? Quote Link to comment
OsoSuerte Posted November 6, 2020 Author Share Posted November 6, 2020 yes I did they are all seated properly but I do not have spares to try replacing them. Quote Link to comment
OsoSuerte Posted November 6, 2020 Author Share Posted November 6, 2020 Do I need to order new power connectors? Quote Link to comment
trurl Posted November 7, 2020 Share Posted November 7, 2020 Why are you using such an (6.0.1 is over 5 years) old version of Unraid? But only joined the forum today? Very difficult to support versions we haven't seen in years. Lots of information we can't get from diagnostics on that old version. What controller(s) are these disks on? Quote Link to comment
OsoSuerte Posted November 7, 2020 Author Share Posted November 7, 2020 I did not have access to the server for the last couple of years. I only got it back two weeks ago and have been working on getting it going since then. I tried to update Unraid through the GUI but that failed also. I have not started to trouble shoot that part yet. I did not realize it was that out of date. MOBO F1A75 V Pro Quote Link to comment
trurl Posted November 7, 2020 Share Posted November 7, 2020 That old version won't GUI update to any current version. You will have to go from the Upgrade Wiki and do it manually: https://wiki.unraid.net/Upgrading_to_UnRAID_v6 Quote Link to comment
OsoSuerte Posted November 13, 2020 Author Share Posted November 13, 2020 On 11/6/2020 at 7:52 PM, trurl said: Why are you using such an (6.0.1 is over 5 years) old version of Unraid? But only joined the forum today? Very difficult to support versions we haven't seen in years. Lots of information we can't get from diagnostics on that old version. What controller(s) are these disks on? Updated but back where I started. I replaced the seta cable on the sdd and then my shares worked and I was able to run Plex. Then I updated to Unraid 6.8.3. Now the shares are empty again. When I navigate to the folder where the data is it says 0 files. Any help would be appreciated. tower-diagnostics-20201113-1450.zip Quote Link to comment
OsoSuerte Posted November 13, 2020 Author Share Posted November 13, 2020 (edited) I ran XFS repair in disk3. Did not seem to help here is a new log tower-diagnostics-20201113-1538.zip Edited November 13, 2020 by OsoSuerte Quote Link to comment
OsoSuerte Posted November 13, 2020 Author Share Posted November 13, 2020 So I replaced the sata cable on disk3 and tried again. Now it seems to be having issue s with disk 4 new log attached. Any ideas? tower-diagnostics-20201113-1551.zip Quote Link to comment
trurl Posted November 14, 2020 Share Posted November 14, 2020 1 hour ago, OsoSuerte said: issue s with disk 4 Nov 13 15:49:58 Tower kernel: ata4.00: ATA-9: ST5000DM000-1FK178, W4J0GWNW, CC47, max UDMA/133 ... Nov 13 15:50:20 Tower kernel: md: import disk0: (sde) ST5000DM000-1FK178_W4J0GWNW size: 4883770532 ... Nov 13 15:51:07 Tower kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x400000 action 0x6 frozen Nov 13 15:51:07 Tower kernel: ata4.00: irq_stat 0x08000000, interface fatal error Nov 13 15:51:07 Tower kernel: ata4: SError: { Handshk } Nov 13 15:51:07 Tower kernel: ata4.00: failed command: WRITE DMA EXT Nov 13 15:51:07 Tower kernel: ata4.00: cmd 35/00:08:80:00:00/00:01:00:01:00/e0 tag 26 dma 135168 out Nov 13 15:51:07 Tower kernel: res 50/00:00:87:01:00/00:00:00:01:00/e0 Emask 0x10 (ATA bus error) Nov 13 15:51:07 Tower kernel: ata4.00: status: { DRDY } Nov 13 15:51:07 Tower kernel: ata4: hard resetting link No, this is a connection issue with ST5000DM000-1FK178_W4J0GWNW parity (sde) Quote Link to comment
OsoSuerte Posted November 14, 2020 Author Share Posted November 14, 2020 So I changed sata ports for disk 4 now I am not seeing anything wrong in the long but I still can not see any thing in the Plex. If I navigate to : \\TOWER\disk7\Plex\DVD then there are files on the disk. if Navigate to : \\TOWER\Plex\DVD the file is empty. New log attached tower-diagnostics-20201113-1626.zip Quote Link to comment
OsoSuerte Posted November 14, 2020 Author Share Posted November 14, 2020 1 minute ago, trurl said: Nov 13 15:49:58 Tower kernel: ata4.00: ATA-9: ST5000DM000-1FK178, W4J0GWNW, CC47, max UDMA/133 ... Nov 13 15:50:20 Tower kernel: md: import disk0: (sde) ST5000DM000-1FK178_W4J0GWNW size: 4883770532 ... Nov 13 15:51:07 Tower kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x400000 action 0x6 frozen Nov 13 15:51:07 Tower kernel: ata4.00: irq_stat 0x08000000, interface fatal error Nov 13 15:51:07 Tower kernel: ata4: SError: { Handshk } Nov 13 15:51:07 Tower kernel: ata4.00: failed command: WRITE DMA EXT Nov 13 15:51:07 Tower kernel: ata4.00: cmd 35/00:08:80:00:00/00:01:00:01:00/e0 tag 26 dma 135168 out Nov 13 15:51:07 Tower kernel: res 50/00:00:87:01:00/00:00:00:01:00/e0 Emask 0x10 (ATA bus error) Nov 13 15:51:07 Tower kernel: ata4.00: status: { DRDY } Nov 13 15:51:07 Tower kernel: ata4: hard resetting link No, this is a connection issue with ST5000DM000-1FK178_W4J0GWNW parity (sde) Sorry saw this after my last post. So try changing the sata cable on the parity drive? Quote Link to comment
trurl Posted November 14, 2020 Share Posted November 14, 2020 9 minutes ago, OsoSuerte said: try changing the sata cable on the parity drive? yes or at least check connections. Still wondering about power connections too. Connectors must sit squarely and without tension on the connection. Cables must have enough slack to insure nothing is pulling on the connection. Don't bundle SATA cables together. Quote Link to comment
OsoSuerte Posted November 14, 2020 Author Share Posted November 14, 2020 (edited) 9 minutes ago, trurl said: Still wondering about power connections too. I am thinking I might need a bigger power supply, The current one was installed for 2 fewer drives. This all started when I replaced a drive that failed. The new drive is faster and uses more power. If the system does not have enough power in general could it cause these issues? Edited November 14, 2020 by OsoSuerte Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.