no disk passed

[Tom Elliott]

@Scott-B how is that possible?

[Tom Elliott]

@Scott-B I think you made a mistake for searching for the file.

The mbr files aren’t located in /usr/share/fog/mbr/fog/, they’re located in /usr/share/fog/mbr/

[Scott B]

@Tom-Elliott said:

@Scott-B I think you made a mistake for searching for the file.

The mbr files aren’t located in /usr/share/fog/mbr/fog/, they’re located in /usr/share/fog/mbr/

Weird right!

[Tom Elliott]

@Scott-B What do you mean?

[Scott B]

@Tom-Elliott said:

@Scott-B What do you mean?

About the location of where the mbr files should be and were the install think they are located.

[Tom Elliott]

@Scott-B Where do you think the install thinks that’s where it’s foudn?

[Scott B]

@Tom-Elliott said:

@Scott-B Where do you think the install thinks that’s where it’s foudn?

When I ran a debug task it said it was looking for “/usr/share/fog/mbr/fog/win7.mb” which isn’t correct. Correct?

[Tom Elliott]

@Scott-B Where did it say that?

[ITSolutions]

I am getting the same issue. This started at 6094 that I went to to fix an issue with the client. I upgraded this morning to 6122 and still have the issue. Below is from the Debug output. Everything seems good the MBR is there, the hard drive is there and this machine has been deployed to before. I tried on 3 separate machines, they are Dell Optiplex 3020 micros. I tried to do a disk wipe on one thinking a corrupt part table, but that didn’t help either. Let me know what else can help in troubleshooting this.

[Scott B]

@ITSolutions said:

I tried on 3 separate machines, they are Dell Optiplex 3020 micros. I tried to do a disk wipe on one thinking a corrupt part table, but that didn’t help either.

I tried the same thing, tested on HP dc5800, HP 4000 SFF, and Daktech Discovery 81.

[ITSolutions]

@Tom-Elliott The output for my lsblk on the client does show the hdd and list it as:

sda              8:0      465.8G
: --sda1         8:1       39.2M
: --sda2         8:2       13.8G
: --sda3         8:3       452G

[Tom Elliott]

@Scott-B Thanks for reporting this issue.

For future reference to all who post.

If it’s dealing with imaging, please please please, provide information of the image.

Image issues are vast and confusing to track sometimes.

The issue you guys were seeing with “No disk passed” was because your images were in the type of: Multi-Part Single Disk.

Please clarify this on the forum posting for this. While I understand pictures help, when I’m seeing a particular issue, I’m not reading the entirety of the text in the picture, I’m most typically looking at the source.

In either case, all having the issue, the init’s have been updated, and the scripts have been updated. Please update your FOG Server and you should be, once again, operational.

[Scott B]

@Tom-Elliott said:

We are up and rolling after the latest SVN. Thank you Tom!