• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. mutant
    3. Posts
    M
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 8
    • Best 2
    • Controversial 0
    • Groups 0

    Posts made by mutant

    • Use Windows share to store fog image with cifs on Ubuntu

      Reason:

      For the people that do not want to setup NFS server on windows but want to use windows share to store fog images.

      Windows share that use CIFS/SMB mount will only work with user space NFS server such as unfsd3 or NFS-Ganesha

      The regular kernel mode nfs_kernel_server does not compiled to support NFS re-export.

      Assume you have a windows server with a share folder call fogshare and the share user is fog with the password fog. The FOG sever is on Ubuntu server.

      sudo -i
      #install CIFS support
      apt-get install cifs-utils

      #Backup images folder so you can copy .mntcheck file later
      mv /images /images.old
      mkdir images
      chmod -R 777

      #edit /etc/fstab to add the following line so windows share folder will mount to /images
      //windows server IP or name/fogshare /images cifs username=fog, password=fog,noserverinfo,iocharset=utf8,file_mode=0777,dir_mode=0777,sec=ntlmssp 0 0

      #backup /etc/exports
      cp exports exports_nfs_kernal_server

      #remove nfs_kernal_server
      apt-get remove nfs-kernal-server

      #add the unfsd3 server source to /etc/apt/sources.list
      #add archive lucid apt source for unfsd3
      #Lucid
      deb http://old-releases.ubuntu.com/ubuntu/ lucid main restricted universe
      deb-src http://old-releases.ubuntu.com/ubuntu/ lucid main restricted universe

      #install unfs3
      apt-get update
      apt-get install unfs3

      #unfs3 does not like a * in the /etc/exports
      replace the * with internal network x.x.x.x/24

      /images x.x.x.x/24(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
      /images/dev x.x.x.x/24(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

      #backup exports for future use
      cp /etc/exports /etc/exports_ufs3

      #copy /image.old files to the new /images

      #restart unfs3
      /etc/init.d/unfs3 restart

      This works on Ubuntu 14.04 and should work with other version as well.

      posted in Tutorials
      M
      mutant
    • RE: Intel RAID

      When setting the “Host Primary Disk” to /dev/md126 because there is no /dev/md0.

      The following error message show up when restore a resizable windows 7 sysprep image.

      Problem opening /dev/md126p for reading! Error is 2.
      The specified file does not exist!
      Problem opening /dev/md126p for reading! Error is 2.
      The specified file does not exist!

      • Processing Partition: /dev/md126p1 (p1)
      • Partition File Missing: /images/W7/d1pp1.im*
        Problem opening /dev/md126p for reading! Error is 2.
        The specified file does not exist!
        Problem opening /dev/md126p for reading! Error is 2.
        The specified file does not exist!
        Problem opening /dev/md126p for reading! Error is 2.
        The specified file does not exist!

      It looks some kind of fog bugs when processing fakeraid Raid0 partition.

      It has problem to properly read the raid0 partition and it tries to read d1pp1.im* file instead of d1p1.im* file.

      posted in Hardware Compatibility
      M
      mutant
    • RE: Intel RAID

      Set the “Host Primary Disk” to /dev/md0 and test again and still no go.

      Went into debug mode to check the raid status

      mdadm -D /dev/md0
      shows the status of md0 is “inactive”

      cat /proc/mdstat
      shows only md126 is “active” and md127 is inactive

      The problem seems that FOG does not assemble /dev/md0 properly

      Re-run the task after setting the “Host Primary Disk” to /dev/md126
      still not go , it shows “Problem opening /dev/md126p1 for reading! Error is 2. The specified file does not exist!”

      The problem seems that FOG try to read from /dev/md126p1 instead of /dev/md126

      posted in Hardware Compatibility
      M
      mutant
    • RE: Intel RAID

      Upgrade the official published kernel from 4.2.0(Sept 17 2015) to 4.2.1 TomElliott (Sept 22 2015) and test again

      Optiplex 9020 with two 500GB physical hard drive.
      The system can network boot.
      Both of Raid0 and Raid1 test with deploy successfully to boot OS but only deploy to one disk.

      Raid1 (Mirror) 465.8GB
      Deploy a sysprep windows7 image result in degraded raid as it only deploy to one disk.
      Raid0 (Stripe) 931.5GB
      Deploy a sysprep windows7 image result in failed raid as it only deploy to one disk.
      Raid0 Image
      2015-09-24_101613.gif
      2015-09-24_101510.gif
      Raid1 Image
      2015-09-24_104638.gif
      2015-09-24_104609.gif

      posted in Hardware Compatibility
      M
      mutant
    • RE: Intel RAID

      Kernel was updated last week when upgrade using git to trunk version 4702.
      The git source “S99fog” file does have the $mdraid change.

      posted in Hardware Compatibility
      M
      mutant
    • RE: Intel RAID

      2015-09-23_152422.gif
      putting Host Kernel Arguments “mdraid=true” still result in the same issue that when deploy image it will break the raid and only image one disk.

      posted in Hardware Compatibility
      M
      mutant
    • RE: Fedora + Mounting NFS3 windows share.

      Windows share that use CIFS/SMB mount will only work with user space NFS server such as unfsd3 or NFS-Ganesha
      The regular kernel mode nfs_kernel_server does not compiled to support NFS re-export.

      posted in Linux Problems
      M
      mutant
    • RE: Intel RAID

      The issue is still there
      Test on trunk version: 4702 with Optiplex 9020 Raid 0.

      posted in Hardware Compatibility
      M
      mutant
    • 1 / 1