phenixdragon

Members
  • Posts

    171
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

phenixdragon's Achievements

Apprentice

Apprentice (3/14)

0

Reputation

  1. Connecting to the IPMI is simple. What I want to do is connect as in I am able to view the system as if I was standing there in front of a monitor. Such as beng able to view it booting through the BIOS and whatnot.
  2. I just installed a Supermicro MBD-X9SCM-F-O board into my unRAID server and I am trying to figure out how I would setup a KVM. Setting up a KVM is completely new so I really have no idea what to do here. Does anyone have any hows to anything to help me out? I really just really need to know what to be looking at and I am sure I could figure it out.
  3. Looks like I had to enable the 2nd LAN port to log into my unRAID web config. I would like to find out why this is and why LAN port 1 didn't just work as a LAN. It seems to just work as the IPMI port which I have nothing plugged into right now.
  4. I just installed this board into my unRAID server but am having an issue with it. It books up unRAID, but when I try to browse to the IP of the board, it always comes up to the IPMI login instead of my unRAID server. I have the LAN connect plugged into LAN1, IPMI is disabled, as far as I am aware, but I guess I am not really sure if it is disabled. Any thoughts on what I may need to look for?
  5. Figured it out. Even though my BIOS was set to boot USB only, the USB drive was 10th on the list instead of being #1. Moving it up corrected my boot issue.
  6. Looks like I was missing the syslinux.exe, which I have copied over but I am still just sitting at the Verifying DMI Pool Data.....
  7. I just noticed that the make bootable is failing. Make Bootable Volume in drive G is UNRAID Volume Serial Number is DA93-9947 G:\syslinux -ma G: 'G:\syslinux' is not recognized as an internal or external command, operable program or batch file. Press any key to continue . . .
  8. I needed to use my USB drive for something else for which I ended up having to format the drive. Before doing so, I did copy all the data off for unraid but now an issue I have is I can't get it to boot again. My system is sitting at Verifying DMI Pool Data..... I tried formatting, FAT32, and copying my data back over along with running the make bootable bat file. It has not helped. Any ideas on what I should do? I am running 5 rc 5.
  9. Took just over 47 hours but it finally finished. Thank you for the help.
  10. Cool, took me awhile but that is what I did, before reading this. I think years ago I tried using screen but had issues with it, but here I go again. I'll report back in like 30 hours or so on how the preclear goes.
  11. I am not finding a directory called that. I guess at this point I'd like to get screen to work.
  12. I don't have screen installed. With running UnRAID version 5, do I need to install UnMENU and than screen?
  13. It seemed like it worked but I am not sure. I last saw it at 98% on I think it was on step 2, but I am not sure now. I telneted it, ran the command, and all of a sudden, like 28 hours later, the telnet window disappeared. Is there a way to check if the preclear finished?
  14. Found the latest so I am at 1.13 now. Giving it a try.
  15. I would use a current version of the preclear script. It appears you are using a VERY OLD version. The older version worked fine on older versions of unRAID, but the "bash" shell changed, and the preclear script was subsequently changed to work with it. (There is nothing likely wrong with the physical disk) The error you saw is exactly what would have happened if you failed to use the most current preclear script. Oh yes, the older script would not have known how to write a proper preclear siginature for a 3TB drive regardless. (They did not exist when your version of the script was written.) Just for kicks, what does your version say when you type: preclear_disk.sh -v ? ? ? Joe L. I'll do some searching on here for the newer script, but I had not realized there was a newer one. preclear_disk.sh -v shows version .9.8