• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Quazz
    3. Posts
    Q
    • Profile
    • Following 3
    • Followers 2
    • Topics 27
    • Posts 1,977
    • Groups 3

    Posts

    Recent Best Controversial
    • RE: Can't deploy latest win10x64uefi with 1.5.5

      @kAs1m Interesting, I have seen a vast variety of BSOD but this is a first!

      Thankfully there is some info online about this which points to hardware/drivers (as the name of the BSOD would imply) (I’ve mostly seen complaints relating to GPUs)

      If an older version of Win 10 works on the same device we can only assume that there’s some new or updated driver in the latest Win 10 builds that are causing this to occur on your clients.

      What are the models of your clients? Perhaps this is a known problem for those devices.

      posted in Windows Problems
      Q
      Quazz
    • RE: Can't deploy latest win10x64uefi with 1.5.5

      @kAs1m Did you happen to catch the error code in the BSOD?

      Did you use the /generalize switch with sysprep? (I’m assuming you did based on the link you gave)

      Does the client reach the OOBE screen? (or do you use an unattend file?)

      Did you upgrade your image or did you start with a clean install?

      If you started with a clean install and used an unattend file, then there’s probably something going on with the latter. (maybe some options are no longer valid or some new mandatory options are missing)

      posted in Windows Problems
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      @Sebastian-Roth https://github.com/FOGProject/fos/pull/22

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      @Sebastian-Roth I was looking into a file based approach but ran into a major speed bump.

      It seems that on GPT builds of Windows 10 (at least on the latest official ISO release of Microsoft), the only folder (and there’s no files) on the first partition (which should be non-resizable) is ‘System Volume Information’ which is available on every NTFS partition…

      Not sure how to resolve this at this point.

      Got a working flag based approach available for now which should work fine for cases such as @maxcarpone has experienced.

      edit: Even better news, had an OEM disk come in so I checked it out and it turns out they also use the ‘hidden’ flag which means we can mark them as non-resizable as well with this approach.

      Of course as you pointed out, ideally they’d be ‘moveable’, but that’s a different issue I think, just fixing the partitions being resized that shouldn’t should do for now I think!

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      @Sebastian-Roth I’ll be glad to escape unicode hell, I do think focus on a language neutral solution is the way to go. I’m still unsure about the best direction to take.

      So far, it seems we have two possible paths to explore:

      File based detection:
      Will check the mounted partition for specific files/folders, if they exist then we know what kind of partition we can expect (eg resizable partition if Windows folder is found)

      However, I foresee some funky stuff being able to mess this up. Atypical installations might not be detected properly.

      Partition flag based detection:
      Will check the mounted partition for specific flags, if they exist then we know what kind of partition we can expect based on the set flags.

      However, partition flags seem to have been somewhat inconsistently set as well as have changed between MBR and GPT somewhat. And of course users/software could theoretically alter these (although this will typically lead to issues with the system in question so less likely than with labels and marginally less likely than with files)

      Our greatest advantage is that we only really need to think about NTFS partitions if we are simply replacing the old label system. This means we can work a lot more targetted regardless of the path taken.

      I created and tested out the partition flag system which seems to work well on the systems I use, but of course I have no idea how it will behave outside of that.

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      @Sebastian-Roth That’s usually true, but for some reason my changes weren’t being reflected, I was probably doing something wrong, but couldn’t figure it out.

      So far, the only thing I’ve been able to find is that everything should work, sigh.

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      Still no improvement, I did notice /usr/share/locale being empty, not sure if that’s expected on buildroot or not… (according to the buildroot code, locale support only works if the target file system has locales in /usr/share/locale)

      I have a week off next week, so this seems like it will be on hold for a while.

      posted in FOG Problems
      Q
      Quazz
    • RE: How do you create your image/s?

      Using sysprep you could create a ‘golden image’ (hardware neutral) that would install on any device. If you use an unattend file you can push it even further and configure the computer (create accounts, networks, etc).

      The software packages could be delivered through snapins instead post install. This will also make it easier to keep them all up to date anyway.

      Your option isn’t bad of course, it takes time to set up a more universal system.

      posted in General
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      @maxcarpone Basically, unicode support (required for letters such as é) is broken/missing in current builds, causing the check to fail.

      I think we’re on the right track, but each build takes time to compile, so for each idea it takes hours before I can test.

      Currently looking into busybox locale support.

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      Haven’t forgotten about this, just been setting up a build environment so I can try out some of the locale options and see if anything helps.

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      @Tom-Elliott BR2_ENABLE_LOCALE_WHITELIST="en_US"

      to

      BR2_ENABLE_LOCALE_WHITELIST="en_US.UTF-8" ?

      edit: is it possible the difference is down the glibc vs uClibc???

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      @Tom-Elliott Unfortunately not, it turns out it was working because the variable was empty.

      Back to square one.

      Would [Rr]*[Ss][Ee][Rr][Vv]* be dangerous to use in production? I don’t expect many false positives, but arguably not resizing certain partitions that should is less harmful than the reverse.

      edit: Even stuff like grep fails, the accents are blocking everything so far

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      @Sebastian-Roth Yes, I have tested in FOS, every other variation we tried worked on regular systems already 🙂

      edit: I may have messed up the test case, I’ll try again in a bit though

      I dun goofed, I’m pretty embarassed. I messed up my sed which made the variable empty and of course it matches then…

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      @Tom-Elliott [Rr][Ee|É|é][Ss][Ee][Rr][Vv][Ee|É|é][Dd|]

      This one is confirmed to work in my test case.

      Feel free to update github as I can’t create a PR atm

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      @Tom-Elliott

      I like that idea, I will test it in a minute, but I did edit it a little bit (correcting accents and changing the last character possibilities given the label format that gets checked + added support for Dutch)

      [Rr][Ee|É|é][Ss][Ee][Rr][Vv][Ee|É|é][Dd|_|Ee]

      Well edit with results

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      @Tom-Elliott We had case originally I believe, but it has more limited pattern matching, it wouldn’t work at all at the time.

      I think it’s ultimately just going to be struggling with accented letters no matter what we do. Even cheeky capture methods like [D-Fd-f] don’t work to capture é in the inits (but does on something like Centos 7 or even online shell sandboxes.

      I’m not sure WHY that is, though.

      Basically, ? in the if statement regex = Wildcard for one or more characters. You were, I presume, using [Dd] as an “if d exists or not, let’s be true” kind of scenario?

      I don’t think it has to do with the e or accented e’s, just plain it doesn’t know what to match and what not.

      Yes, that was the original idea, which works in certain environments I suppose, but should definitely be replaced with a wild card instead. (along with [Dd])

      However, even when removing that bit, it still fails to match. It so far has only worked with

      [Rr]*[Ss][Ee][Rr][Vv]* as the pattern.

      [Rr][EeÉé][Ss][Ee][Rr][Vv][EeÉé]* does not work.

      I’m thinking that perhaps using grep to do the matching might be more consistent and predictable in its behavior.

      Something like:

      echo $label | grep -iq "R[ée]serv[ée]"

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      @Sebastian-Roth Soooo, this is bizarre, but both the [EeÉé] and [Dd]? seem to fail now.

      I am at a loss as to explain why though since it definitely worked 😕

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      After further investigation, using the ‘English’ label ‘System Reserved’ works fine.

      I double checked my french images and one dating 25 october capture the label was picked up correctly, but one dating 16 november was not.

      I believe the one around 25 october was the one I was using when I originally tested the new label regex and confirmed it working.

      Not sure how/why it wouldn’t work now, though.

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      @maxcarpone Looks normal to me, should just work, very strange!

      Will likely look into an entirely different system for this later tonight if I don’t forget.

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG resizes all partitions even System Reserved!

      @maxcarpone Could you provide a screenshot of the disk layout in Windows Disk Management?

      :1:3 is odd to say the least, thinking that disk layout is something like “System Reserved” “Main Windows partition” “Recovery”. Either that or it’s GPT and somehow the second partition wasn’t picked up… Not sure.

      But anyway, let’s focus on the images you have available to you in front of you first. I currently don’t really have an idea as to why it would fail in your situation, though.

      posted in FOG Problems
      Q
      Quazz
    • 1
    • 2
    • 19
    • 20
    • 21
    • 22
    • 23
    • 98
    • 99
    • 21 / 99