• Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About abhi.ko

  • Rank
  • Birthday 11/13/1978


  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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 slo
  2. 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 u
  3. 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
  4. 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 m
  5. 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:
  6. 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?
  7. 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
  8. @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
  9. 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?
  10. 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
  11. 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 N
  12. 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 sys
  13. 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 d
  14. 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.