sed, grep, tr and all the rest are very nice but we don’t really need them here, do we?
[CODE]… cat /sys/class/net/[^l][^o]*/address …[/CODE]
And still wondering about if ‘IFS’ is needed here. Sorry goto go now.
[quote=“Tom Elliott, post: 43626, member: 7271”]We have to know the exact path name, so it’s simpler to just use the tools that get that for us I think.[/quote]
I don’t think so…
[CODE]# Get All Active MAC Addresses
# Create a pipe-separated MAC List
for macline in $(cat /sys/class/net/*/address); do
# Add a pipe before adding more MACs
if [ -n “$mac” ]; then
No ip, no awk, no grep…
Would it be possible to dump your whole FOG database and upload that dump file to this forum?? I’d love to push this data into my database to see if it looks me out as well… I hope there is no sensitive data in it. Please look through the file an delete password hashes before posting the file here!
[CODE]$ mysqldump --databases fog --user <your-db-user> -p > fog_dump.sql[/CODE]
[quote=“michieru, post: 43559, member: 3086”]Which version of FOG you are using? I am on 1.2.0 and I don’t see these options under image management.[/quote]
Hmmm that’s interesting. As you didn’t mentoin the FOG version in your first post I just searched the source of 1.2.0 and SVN version. FOG 1.2.0 doesn’t have any “Skipping partition” messages in the code as far as I could find. That’s why I suggested the setting.
Are you absolutely sure you use 1.2.0 on that server?? Maybe you updated kernel and initrd at some point??? Maybe check md5sums to see if you still use kernel/initrd coming with FOG 1.2.0
[CODE]$ md5sum fog_1.2.0/packages/web/service/ipxe/init*
[quote=“Clifford Raymond, post: 43552, member: 28730”]You are correct, I do see the same message. What does it mean when the file is corrupt? Do we have to reconfigure the whole server?[/quote]
What do you mean by “same message”??? Does the kernel image have the same md5sum??
I am sorry to say this but this forum is about FOG and things related to FOG. Don’t think a crashed hard drive should be discussed here.
That said I still try to give you a few hints that may be of help. [B]Be as carefully with this drive as possible![/B] Try connecting it to other computers (especially with different operating systems) to see if it comes up again. If not you might be able to disassemble it from its external case and try a different USB connector device or connect it straight to the normal ATA/SATA interface of a PC.
Depending on the outcome of all this you might end up having to recover data. ‘testdisk’ is definitely a great tool to look at… And lots of others. But this is a whole new (and way too complex) story. All the best with this!