dlandon

Community Developer
  • Content Count

    6125
  • Joined

  • Last visited

  • Days Won

    10

dlandon last won the day on January 9

dlandon had the most liked content!

Community Reputation

563 Guru

About dlandon

  • Rank
    Advanced Member
  • Birthday 07/31/1946

Converted

  • Gender
    Male
  • Location
    Cincinnati, Ohio

Recent Profile Visitors

5825 profile views
  1. UD will use the same mount point for the disk when it is reformatted. You can change the mount point. The issue is the UUID. Go to the UD settings and change the UUID.
  2. sdam is currently showing a duplicate UUID. You'll need to go to D settings and change the UUID so it will mount.
  3. Post your diagnostics. Where are you getting the /dev/sdam designation? Are you using a port expander or drive bay?
  4. When the "Mount Disks with 'discard' option?" is set to yes an encrypted disk will be mounted with the discard option. The --allow-discards is used with the luksOpen command. Some of the confusion is that the use of discard on encrypted disks has changed and the posts reflect the discussion of those changes. I will review the first post write up and adjust as necessary to clear up any confusion. The UUID issue is because the disk is encrypted and UD is not determining that the disk is formatted XFS when creating a list of disks where the UUID can be changed. I will have to look
  5. What it means is that UD needs to not mount the the disk because it is being passed through. This is the normal way a UD disk is handled when UD is not to mount it. I think it makes sense. You seem to imply that if UD marks it as passed through, that UD manages passing it through to a VM automatically. UD doesn't do that, it only makes it available because UD won't mount it.
  6. UD will not try to mount a passed through disk. You still have to do the steps to pass it to the VM.
  7. As per above. UD is checking to see if the disk is spinning. The command is timing out because there are issues with your disk system, which is where you need to spend your time.
  8. It could be something like a power supply problem, cabling, or a failing controller. I don't think it is a disk issue. It's something common to several disks. UD checks a spinning disk for disk temperatures. Preclear checks disks in the background. You'd need to post on the preclear forum for more information.
  9. Get the new template from CA and read the instructions on how to set shared memory. It has changed.
  10. Your disks are having problems: Dec 13 01:13:14 Juno kernel: sd 8:0:1:0: [sdw] tag#6846 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Dec 13 01:13:14 Juno kernel: sd 8:0:1:0: [sdw] tag#6846 CDB: opcode=0x88 88 00 00 00 00 05 74 ff ff 80 00 00 00 08 00 00 Dec 13 01:13:14 Juno kernel: print_req_error: I/O error, dev sdw, sector 23437770624 Dec 13 01:13:14 Juno rc.diskinfo[9245]: SIGHUP received, forcing refresh of disks info. Dec 13 01:13:14 Juno kernel: sd 7:0:10:0: [sdp] tag#1601 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Dec 13 01:13:14 Juno kernel: sd 7:0:10:0: [sdp] t
  11. Yes, on top of the configuration change regarding shared memory, the new ES presented a lot of issues. Once we get started with a new 'all in one' Docker, we can sort through the ES issues. There is actually a 6.1.7 release now.