• Posts

  • Joined

  • Last visited

Everything posted by abhi.ko

  1. Hello - installed this plugin and it is working fine - Thanks for the work. I am not super knowledgeable regarding networking - but I am using the remote access to LAN as shown below, followed the steps laid out in the very detailed write up, and I can connect to Unraid and docker containers (e.g. Plex, Emby etc.) well from outside my home network, so ports are forwarded correctly and everything seems to be working well. However I cannot access anything else connected to my LAN (e.g. Pi-Hole running on an R-Pi) or my router admin page. I was using openVPN before this and could access all devices on the network easily. Any advice for me to try and get to everything connected to the LAN? Thanks in advance.
  2. No I did not, and that was exactly what was happening with my upgrade too. So I downgraded and went back to 6.8.3 stable and everything is fine, no issues what so ever, nothing changed other than the version of unRaid. I had this happen twice - once with 6.9beta and RC1 - so I am pretty sure it is something related to the code changes, I have no idea what. I did post my diagnostics but did not get any feedback on it. Another thing, which I believe is related, is what happened with my NVME cache drive, 6.9 RC showed errors related to the NVME drive (Samsung 980 Pro 1TB on an M.2 slot) and after that it became unavailable and all my cache content with it. So I switched to another SSD on hand and rebuilt everything again, was planning to remove the m.2 drive and RMA it but strangely enough on the next reboot it came back as unassigned with no data loss - with all the appdata and VM's intact. I was running it on 6.8.3 until recently, moved it to my windows machine last week. So something is up, doesn't seem like 6.9.3RC doesn't like my hardware/setup. @touz do you have any nvme drives in your build - what hardware are you using?
  3. I understand the reasons why for an unclean shutdown. Just trying to figure out why this wasn't a problem before the upgrade on 6.8.3, I had even rebooted the server yesterday morning and it had gracefully shutdown and came back up without any issues. I did not change the location of the flash drive or anything else between that reboot and the upgrade reboot. Hence the thought that this might be an issue with the upgrade. In fact I had tried to upgrade previously (beta 35 I believe) and had the same issue while stopping and starting the array, it always comes back as unclean and starts parity check. So decided to go back to the stable version, now the rc came out and decided to try again and wanted to report it. Seems like there is at least another user with the same issue, @ClunkClunk. Was there anything in the logs and what is with the error related to my nvme drive, that is also new after the upgrade.
  4. So I upgraded just now, and after the reboot via the WebGUI (did not shutdown the server physically) unRaid came back up and said it detected an unclean shutdown and started a parity check. There are errors related to my nvme cache disk on the log, none of this was there prior to the upgrade, I believe. Any idea what is going on? tower-syslog-20201211-0230.zip
  5. Oh I see now. Never used this New Config option before and I don't think it was even there when I built the server in 2011. Here is what I did. Stop the array. So Tools -->New Config -->Keep All Assignments -->Apply : This is done. Added Disk 15 back to the array and used the same disk as before. Started the array. Everything looks good as of now. Parity rebuild is in process. Will report back how it goes. Thanks a ton for your help. Will try and trouble shoot the disks not being detected issue soon after. Hopefully I won't mess anything more up in that process. Any guidance you can provide there would be helpful. BTW, I did check the BIOS Boot settings and 'option ROM' and 'UEFI and Legacy OPROM' is selected under boot devices control and CSM is enabled, still no luck getting the LSI BIOS to show up.
  6. Thanks! Did that and it looks good after un-assigning from array and mounting in UD. Dec 7 11:31:09 Tower kernel: sd 10:0:2:0: [sdq] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) Dec 7 11:31:09 Tower kernel: sd 10:0:2:0: [sdq] 4096-byte physical blocks Dec 7 11:31:09 Tower kernel: sd 10:0:2:0: [sdq] Write Protect is off Dec 7 11:31:09 Tower kernel: sd 10:0:2:0: [sdq] Mode Sense: 9b 00 10 08 Dec 7 11:31:09 Tower kernel: sd 10:0:2:0: [sdq] Write cache: enabled, read cache: enabled, supports DPO and FUA Dec 7 11:31:09 Tower kernel: sdq: sdq1 Dec 7 11:31:09 Tower kernel: sd 10:0:2:0: [sdq] Attached SCSI disk Dec 7 11:31:32 Tower emhttpd: ST8000VN004-2M2101_WKD08RSZ (sdq) 512 15628053168 Dec 7 11:31:33 Tower kernel: mdcmd (16): import 15 sdq 64 7814026532 0 ST8000VN004-2M2101_WKD08RSZ Dec 7 11:31:33 Tower kernel: md: import disk15: (sdq) ST8000VN004-2M2101_WKD08RSZ size: 7814026532 Dec 7 11:31:38 Tower emhttpd: shcmd (53): /usr/local/sbin/set_ncq sdq 1 Dec 7 11:31:38 Tower root: set_ncq: setting sdq queue_depth to 1 Dec 7 11:31:38 Tower emhttpd: shcmd (54): echo 128 > /sys/block/sdq/queue/nr_requests Dec 7 12:57:25 Tower emhttpd: ST8000VN004-2M2101_WKD08RSZ (sdq) 512 15628053168 Dec 7 12:58:22 Tower unassigned.devices: Issue spin down timer for device '/dev/sdq'. Dec 7 12:59:38 Tower unassigned.devices: Adding disk '/dev/sdq1'... Dec 7 12:59:38 Tower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdq1' '/mnt/disks/ST8000VN004-2M2101_WKD08RSZ' Dec 7 12:59:38 Tower kernel: XFS (sdq1): Mounting V5 Filesystem Dec 7 12:59:38 Tower kernel: XFS (sdq1): Starting recovery (logdev: internal) Dec 7 12:59:38 Tower kernel: XFS (sdq1): Ending recovery (logdev: internal) Dec 7 12:59:38 Tower unassigned.devices: Successfully mounted '/dev/sdq1' on '/mnt/disks/ST8000VN004-2M2101_WKD08RSZ'. Dec 7 12:59:38 Tower unassigned.devices: Issue spin down timer for device '/dev/sdq'. The content looks okay as well, screenshot below. I have no ways of verifying whether this is what was in Disk 15 before the FS corruption, but it looks good to me from a cursory look. Diagnostics attached as well What should I do next? tower-diagnostics-20201207-1305.zip
  7. So ignore the lost and found and do the following, just for clarity: 1. Stop the array 2. Unassign disk 15 3. Start the array 4. Stop it again 5. Assign this disk to disk 15 again 6. Start the array 7. Resync parity Are these the right steps @JorgeB?
  8. So I did an xfs repair on disk 15 and had to use the -L option because the drive was un-mountable. It was completed and now the disk is mounted but still shows as disabled and there is a bunch of data in Lost+Found - I'm unclear on the next steps. No SMART errors on the disk. What are the steps to get the drive to function normally and move the files from Lost+Found to the right folders/shares? tower-diagnostics-20201205-0902.zip Edit - Can I not worry about the Lost+Found directory as mentioned here and just reconstruct the disk from parity? Or is the parity for this disk messed up (somehow) as well because of the fs corruption? Disk 15 was emulated when the array was started last, I have switched the server off for now.
  9. @JorgeB I missed this response till now, will try this. But have a different problem I am trying to solve for. Something is definitely up with my setup, not sure if the hard drive power connectors are to blame, or if something more problematic is at play. Priority #1: I have an xfs disk in error now that happened when I was trying to insert another unassigned HDD on the hot swap bay to test while the array was running. Have done it many times before, this is the reason why I bought a case with hot swap-able bays to begin with, not sure what went wrong this time. Any how I have the array running with this disk showing as unmountable. How do I recover this and clear this? Priortiy #2: Will come back to the other issue of drives not being detected soon, but I took those drives out (a WD Gold 8TB and a ST Ironwolf 8TB) and tested them on a windows system (through an external SATA hot swap bay attachment from SABRENT) and the ST did get recognized, but the WD did not, so I am RMA-ing that one (that is the one that was already precleared in Unraid before all this started). So I plugged in the external SATA device with the ST drive on to Unraid by USB and the drive did get detected, which leads me to believe that the issue is with the NORCO drive bays/SAS Backplanes/power connectors etc? The unassigned SSD is part of the same SAS Backplane (HDD row) and it works fine. So I'm not sure what the issue is. The one I was trying to plug in today was different 5TB drive, which was being detected by windows as well but not detected now, by unraid . Anyhow that was just to test this hypothesis. Priority is to recover the disk in error. All help appreciated please. tower-diagnostics-20201204-1216.zip
  10. So this did not work and I am not able to get in to LSI BIOS. Soon after POST the MB logo splash screen appears on my MB with the "Press F2/Del to Enter BIOS", Don't see a way to disable the boot logo splash screen in the BIOS either. Will have to dig through it. Found this and disabled it, tried hitting Ctrl+C while booting up but still no luck on getting to the LSI BIOS. Any ideas?
  11. Thanks @JorgeB again. So the HBA card is flashed and I had to do it twice for both chipsets with -c 0 and -c 1, for FW and BIOS, now everything looks good. root@Tower:/lsi# sas3flash -listall Avago Technologies SAS3 Flash Utility Version (2018.04.02) Copyright 2008-2018 Avago Technologies. All rights reserved. Adapter Selected is a Avago SAS: SAS3008(C0) Num Ctlr FW Ver NVDATA x86-BIOS PCI Addr ---------------------------------------------------------------------------- 0 SAS3008(C0) 0e.01.00.03 00:19:00:00 1 SAS3008(C0) 0e.01.00.03 00:1b:00:00 Finished Processing Commands Successfully. Exiting SAS3Flash. Update: So the array is now back to normal, did not even have to reboot. The disks all got assigned properly immediately after the HBA was flashed. The only problem is that the 2TB SSD that was showing up prior as unassigned is no longer showing up, neither are the other 2 hard drives. Should I just reboot the system and hit Ctrl+C as soon as it posts to bring up the LSI BIOS?
  12. Appreciate the guidance @JorgeB, so following your instructions I did a -listall and was surprised to see 2 devices come up, even though I only have one HBA card. But I think that it is because of the 2 chipsets on the card. Quote from some product documentation below, so I will have flash the FW twice with -c 0 and -c 1 , right? root@Tower:/lsi# sas3flash -listall Avago Technologies SAS3 Flash Utility Version (2018.04.02) Copyright 2008-2018 Avago Technologies. All rights reserved. Adapter Selected is a Avago SAS: SAS3008(C0) Num Ctlr FW Ver NVDATA x86-BIOS PCI Addr ---------------------------------------------------------------------------- 0 SAS3008(C0) 00:19:00:00 1 SAS3008(C0) 00:1b:00:00 Finished Processing Commands Successfully. Exiting SAS3Flash. root@Tower:/lsi# sas3flash -c 0 -list Avago Technologies SAS3 Flash Utility Version (2018.04.02) Copyright 2008-2018 Avago Technologies. All rights reserved. Adapter Selected is a Avago SAS: SAS3008(C0) Controller Number : 0 Controller : SAS3008(C0) PCI Address : 00:19:00:00 SAS Address : 500062b-2-0168-0580 NVDATA Version (Default) : NVDATA Version (Persistent) : Firmware Product ID : 0x2221 (IT) Firmware Version : NVDATA Vendor : LSI NVDATA Product ID : SAS9300-16i BIOS Version : UEFI BSD Version : FCODE Version : N/A Board Name : SAS9300-16i Board Assembly : 03-25600-01B Board Tracer Number : SP63315150 Finished Processing Commands Successfully. Exiting SAS3Flash. root@Tower:/lsi# sas3flash -c 1 -list Avago Technologies SAS3 Flash Utility Version (2018.04.02) Copyright 2008-2018 Avago Technologies. All rights reserved. Adapter Selected is a Avago SAS: SAS3008(C0) Controller Number : 1 Controller : SAS3008(C0) PCI Address : 00:1b:00:00 SAS Address : 500062b-2-0168-8c80 NVDATA Version (Default) : NVDATA Version (Persistent) : Firmware Product ID : 0x2221 (IT) Firmware Version : NVDATA Vendor : LSI NVDATA Product ID : SAS9300-16i BIOS Version : UEFI BSD Version : FCODE Version : N/A Board Name : SAS9300-16i Board Assembly : 03-25600-01B Board Tracer Number : SP63315150 Finished Processing Commands Successfully. Exiting SAS3Flash. Also the current FW version is v5, that doesn't sound right because the current version seems to be v16 (readme file text below) - is this just a really an old product that I got from ebay, it was in a sealed box? I will wait for your response to flash this, just being gun shy. Hopefully once this is done the other 2 unassigned disks will show up, otherwise I will have to troubleshoot that after this. *********************************************************************************************************************** Package for SAS3 Phase 16 Firmware BIOS Upgrade on MSDOS & Windows ************************************************************************************************************************ LSI Host Bus Adapter(HBA) - LSI SAS9300_16i Package Contents- Readme first note : README_9300_16i_Package_P16_IT_FW_BIOS_for_MSDOS_Windows.txt Component : Path Version Release Date ============================================================================================================================= Firmware : \firmware\SAS9300_16i_IT\SAS9300_16i_IT.bin 01-Aug-19 BIOS : \sasbios_rel\mptsas3.rom 05-Apr-18
  13. I will read through and try updating the FW, biggest problem I see is that there is no 9300-16i product on the Broadcom site. So should I use the 9305-16i as the product. Do you know? Found it, not sure why I couldn't yesterday while filtering for the HBA. Also I tried to boot into the LSI Bios yesterday but it did not come up when I tried to start the system without unraid usb plugged in, tried charging the boot order and looking through the Bios management page but had no luck getting into it. Edit: For getting into the LSI BIOS should I be hitting Ctrl+C as soon as the system posts and start booting up? Obviously the HBA is installed and found by the system.
  14. Thank you. So I plugged everything in and started the system. Unfortunately, I do not see the unassigned disks still, all the assigned disks still do get recognized. So the HBA card did not solve the issue, those 2 disks are connected to the HBA card. Also bigger problem is that I have a ton of missing disks now. I guess the way the card identifies the disk and how it was identified earlier with the SATA multiplier cards are different, please see the screenshot below. Unraid says they are wrong disks but they are the same. How do I fix this without loosing any data please? Thanks.
  15. Hi @JorgeB - I ended up getting the 9300-16i. Had some questions before connecting and turning the system on. Does this card need a power connection from the PSU? Do I need to flash the FW or BIOS to put it in IT mode, or would it work out of the box? Anything else I need to keep in mind before installing and booting up Unraid? I plugged it into a free PCIe slot on the MB and connected all the SAS cables to the disks, but have not switched anything on yet, a little worried I might make a stupid mistake and fry something, because I know nothing about HBA cards. Thanks in advance. PS: Is this discontinued? Asking because I cannot find the 9300-16i on the Broadcom site, I do see a 9300-8i and a 9305-16i, was trying to find any drivers or FW upgrades needed, just in case.
  16. Hello - As the topic suggests trying to see why the shfs task is taking up a lot of processing power, even without active writes happening on the system. below is a screenshot from glances and terminal showing the usage. I found this topic from 2017 (with 6.2.x), I don't have freeze-up issues currently as I upgraded to a much beefier processor and doubled the memory, but used to have those issues with my old 4 core xeon, but still this is a concern. Also what is that %CPU out of because my server load is not greater than 10-15% when this task shows up as 200% of CPU. I do have a mix of rfs and xfs disks in the array. Not sure if that is causing this? Thanks.
  17. Thanks a ton. Dang these are not cheap! Hopefully there is something on sale this week or next. I would need 4 SAS to SAS connectors as well I am assuming. Also is there a preference where parity and cache are connected to between the MB ports and the card?
  18. Thanks again @JorgeB and @dlandon I have 24 drive slots on the case and 8 SATA ports on the mother board, the Case has Six internal SFF-8087 Mini SAS connectors that support up to twenty-four 3.5″ or 2.5″ SATA (II or III) or SAS hard drives. Currently I am using SAS to 4xSATA reverse breakout cables to connect these drives. That said, any guidance on a better and more stable way to achieve this with an LSI HBA controller is welcome and appreciated, not sure as to which one I should get?
  19. Thanks - but that is what I was trying to explain. Let us say the other HDD, the one that is not found, was on sds. This unassigned drive (SSD) is on sdl and is found. I tried switching the drive slots of the HDD and SSD (or any other drive on the array) and it gets found again and shows up as sds (for e.g.), and the other one which is now on sdl is still invisible. So I am not sure how one drive is not working on the same drive slot but another one is. How could that be a hardware problem?
  20. I have a very weird issue with my server now - I cannot see either of my two unassigned HDD's, there is an unassigned SSD - which shows up fine. I did recently update my hardware, everything except for the disks pretty much was changed. So naturally I though it is a hardware related issue, but since then I have been able to pretty much rule out my SATA port multiplier cards or my NORCO 4224 SAS connectors and other hardware. I think the problem started after I updated the Unassigned Devices plugin yesterday at some point. I am thinking something changed after that. What I have tried so far in an effort to narrow down on the problem: SATA/SAS connectors and Hardware: I switched drive slots, cards and cables on those two and tried swapping with a device that Unraid does find, and those devices do show up without an issue, with a different device letter (sdX), but the unassigned devices, now connected via previously working hardware (SATA ports and cables) are still not found and does not show up. So in effect the assigned devices work on the same drive slots and other hardware without an issue. Unassigned does not seem to work on any. So doesn't look like it is a hardware issue to me, I might be wrong. I even tried switching the SATA port multiplier card to a different one and that also did not work. HDD's: One of the unassigned devices were present and detected before yesterday and was pre-cleared. So I am pretty sure that drive is a working drive. so not a drive issue either. The other one is a brand new disk I just added, will be checking that drive on a different computer soon to see if it is an issue with the drive. Tried switching to 6.9-beta35 but no luck there either. Has anyone encountered this before. Diagnostics is attached. All help appreciated. tower-diagnostics-20201126-1012.zip
  21. So an update on this: Thanks @JorgeB - I did what you suggested and everything seems to be working from a docker perspective. But my VM's are not starting up now, not a big deal for me because I have a snapshot of my hassos VM saved up. What I did: Run CA Backup & Restore to backup appdata and and other files. Copy over systems and domain shares (they were set to Cache Prefer) manually to location on the array. Did not copy over the data since there was nothing valuable to me in cache at the time. Just some media files. Stop the array. For formatting the cache SSD - Changed the filesystem for the Cache Drive to xfs from btrfs, and clicked apply & done. I am not planning to use a Cache pool anytime soon, not sure if that corruption was any fault of the btrfs. (my knowledge on linux filesystems is very limited, so this is just google/unraid wiki based. Cache Drive showed up to be formatted - clicked checkbox and format. Once done, restarted the array. Restored appdata using the CA backup/restore Restarted the server as suggested by the plugin. Copied everything over other than the docker image. Re-enabled docker in settings and set the image size to 20G - thanks @trurl Rebuilt docker image from existing templates in my templates. All containers are now back up and running fine! Re-enabled VM service, with the copied over image and the VM's showed up. But they are not starting, so not sure what is wrong there, unsure if the filesystem change caused that? That's it now. Dockers are all back and shares are intact, so I'm happy. Will have to try fixing VM again later, any suggestions here would be appreciated.
  22. That is interesting since I have it mapped to the system share which is set cache prefer, and there is plenty of space left on the cache drive. So not sure why there is another image on Disk15.
  23. No - never filled. Docker is not currently running - so I couldn't tell you what the status is currently. I think it was a stupid mistake some years back when I changed the default size of the file to 100G, not understanding what I was doing. But never had it filled up.