mikedpitt420

Members
  • Posts

    387
  • Joined

  • Last visited

Everything posted by mikedpitt420

  1. I have tried stopping the array, unassigned cache drives, starting the array again, and I can still not see my old cache drive other than to format it.
  2. I removed a cache drive from my system and installed a new one. I am trying to use UD to access the data on this drive. It is formatted BTRFS. UD sees the drive, but my only option is to format it. Is there another way to get at this data?
  3. I have tried recreating this VM with the old vdisk1.img and it either will not start at all, or it does with oddly missing data. Is there a setting in the creation that I am missing? tower-diagnostics-20211008-0036.zip
  4. This was not entirely accurate. Let me try to start again. I think I started my VM service again, thus creating a new libvrt file. I have backups of my vdisk1.img file. When I try to create a new VM with my vdisk1.img file, it does load, but seems to be missing a bunch of data. Is this expected behavior?
  5. Changed cache drive, and no VMs exist any longer. All my ISOs and vdisk.img are located on the array. My libvrt ISO and windows installation ISO are located at /mnt/user/isos. My vdisk is located at /mnt/user/domains/Windows 7/vdisk1.img. I have tried to change these settings in the VM manager and the VM service will not start. Any help is appreciated. tower-diagnostics-20211007-2306.zip
  6. I replaced my cache drive, and forgot about a VM that was on there. I can still mount it and access the disk image, but where do I find the XML? Or what is the best way to restore the VM ? I still have the same flash drive, and access to anything that was stored on the cache drive including the disk image.
  7. I was hoping that wouldn't be the case. I'll have no idea if the solder was bad or if it was the parity drive
  8. So I lost 8 drives due to a completely moronic move and I have been repairing them one by one. I do not know which drives were which. I have been de soldering the BIOS chips of my old drives onto new PCBs and so far so good. I have managed to resurrect 3 of 8 dead drives so far. What I am curious about is this: when I finally get to my old parity drive and I plug it in and mount it, what will I see? I just was hoping to have some idea so when I do get to that one I know to just skip it.
  9. @trurl I don't believe I have any saved but if there are some that still exist on the forum here they're the same disks so should still apply. Wow that's an impressive find man thanks!
  10. I will do what squid said and just try to mount them as I can and the one I can't must be parity. Is just a shame I will probably have to burn a PCB on a drive without knowing before hand
  11. Yes, all I have is a backup of my config folder and it was previous to this file apparently. Is there a way to get this info from the super.dat file? I mean it's not the end of the world if I order another PCB I can't use but it'd be great if I could skip it obviously
  12. I don't seem to have this file in my config folder.
  13. I burned out 8 HDDs on an old setup. Is there anywhere in my old flash drive that I can find the serial #s to tell which disk was parity and which ones were data? I have started the process of ordering new PCBs for the old dead drives and successfully replaced a new BIOS with the old, and the drive now works again. Since these PCBs are shipped from China and aren't cheap I would like to avoid ordering one for my parity drive as I have gotten new data drives and only wish to reconstruct those.
  14. Hello. I recently lost almost all of my data drives, but my cache drive with all of my dockers on it seems fine. Is there a way to extract a list of my DB from this drive to know all of the TV I'm missing? (Plex DB extraction would be even better as that would have everything that I've lost) Thanks in advance!
  15. They do detect some disks. But with both 9211s when the bios loads it identifies one properly and the other unsuccessfully. I will report back when I get my SAS expander. Which I have verified works with the 9211 in it mode.
  16. SuperMicro CSE-836A-R1200B> I really hope this isn't incompatible as several people from the forums told me that there are "great deals on supermicro 836 cases on ebay".... I wouldn't think it's entirely incompatible as it does see some drives. I think it's just that the BIOS for both cards is not loading correctly.
  17. During boot the 9211 BIOS screen goes by and says something about configuration changes but when I enter it, I don't seem to have many options to change anything. I think this is definitely the problem. Should I get an SAS expander instead of 2 9211 8is? If so, which one would anyone recommend with this card? I've never really used one before.
  18. So I just purchased a Supermicro 836, new Supermicro X10SRL-F, installed 16GB of recommended Supermicro RAM, flashed 2 9211-8i's to IT mode successfully. Plugged everything in, and unRAID just says "too many incorrect disks". It looks from the main page that it sees 3 random disks. Can anyone tell me what I've done incorrectly? tower-diagnostics-20190204-0313.zip
  19. Mini sas has a higher signaling voltage than sata. I suspect that's what happened....should have known not to do that
  20. Yes where the mini SAS to a SATA cables smoked for a second at the board. Now it wont boot and there is visible char marks around those ports on the board
  21. Oh it did. Small wisp of smoke and now the board won't boot. Smoke came directly from where the sata cables were plugged in
  22. Yes. But I am thinking the issue may be that I shouldn't have plugged a mini SAS cable from the backplane to 4 sata slots on the motherboard. I think I may have burned out the board. I just ordered another motherboard and another lsi 8 drive card so everything is mini sas to mini sas.
  23. I'm sorry. I don't know what that is. Can you elaborate a bit?