[opensuse] .mod files
In a related thread, I stated that I used the distribution media with the upgrade option to update my system. As part of that process it did run grub2 and update the boot configuration. I now find that I have 256 .mod files in my root directory. What are they and what should I do with them? A Google link says they are usually generated by grub2, but I do not understand why they were generated or what to do with them. Ideas or pointers would be appreciated. Thanks, Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
06.01.2016 21:02, don fisher пишет:
In a related thread, I stated that I used the distribution media with the upgrade option to update my system. As part of that process it did run grub2 and update the boot configuration. I now find that I have 256 .mod files in my root directory. What are they and what should I do with them? A Google link says they are usually generated by grub2, but I do not understand why they were generated or what to do with them.
Ideas or pointers would be appreciated.
Thanks, Don What exactly is root directory? "/"? "/root"? Something else?
In any case this is not supposed to happen and those files are likely useless in either of mentioned directories, but as you did not say from which to which version you updated, hard to say anything. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/06/2016 11:13 AM, Andrei Borzenkov wrote:
06.01.2016 21:02, don fisher пишет:
In a related thread, I stated that I used the distribution media with the upgrade option to update my system. As part of that process it did run grub2 and update the boot configuration. I now find that I have 256 .mod files in my root directory. What are they and what should I do with them? A Google link says they are usually generated by grub2, but I do not understand why they were generated or what to do with them.
Ideas or pointers would be appreciated.
Thanks, Don What exactly is root directory? "/"? "/root"? Something else?
In any case this is not supposed to happen and those files are likely useless in either of mentioned directories, but as you did not say from which to which version you updated, hard to say anything.
The root directory is /. They were all loaded with in two minutes of each other. I can attach a list if desired. All of the update to /boot were made at Jan 5 11:07. All of the 256 .mod files have time stamps between Jan 5 11:06 and Jan 5 11:07. Thanks don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/06/2016 11:24 AM, don fisher wrote:
On 01/06/2016 11:13 AM, Andrei Borzenkov wrote:
06.01.2016 21:02, don fisher пишет:
In a related thread, I stated that I used the distribution media with the upgrade option to update my system. As part of that process it did run grub2 and update the boot configuration. I now find that I have 256 .mod files in my root directory. What are they and what should I do with them? A Google link says they are usually generated by grub2, but I do not understand why they were generated or what to do with them.
Ideas or pointers would be appreciated.
Thanks, Don What exactly is root directory? "/"? "/root"? Something else?
In any case this is not supposed to happen and those files are likely useless in either of mentioned directories, but as you did not say from which to which version you updated, hard to say anything.
The root directory is /. They were all loaded with in two minutes of each other. I can attach a list if desired. All of the update to /boot were made at Jan 5 11:07. All of the 256 .mod files have time stamps between Jan 5 11:06 and Jan 5 11:07.
Thanks don Sorry for the incomplete response. I used a 13.2 DVD to update a 13.2 system. My hope was to get around the problems I was having using zypper up and the VLC files on packman that could not be accessed. I was also hoping that this might be a way to fix broken grub2 boot configurations.
Thanks Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/06/2016 11:37 AM, don fisher wrote:
On 01/06/2016 11:24 AM, don fisher wrote:
On 01/06/2016 11:13 AM, Andrei Borzenkov wrote:
06.01.2016 21:02, don fisher пишет:
In a related thread, I stated that I used the distribution media with the upgrade option to update my system. As part of that process it did run grub2 and update the boot configuration. I now find that I have 256 .mod files in my root directory. What are they and what should I do with them? A Google link says they are usually generated by grub2, but I do not understand why they were generated or what to do with them.
Ideas or pointers would be appreciated.
Thanks, Don What exactly is root directory? "/"? "/root"? Something else?
In any case this is not supposed to happen and those files are likely useless in either of mentioned directories, but as you did not say from which to which version you updated, hard to say anything.
The root directory is /. They were all loaded with in two minutes of each other. I can attach a list if desired. All of the update to /boot were made at Jan 5 11:07. All of the 256 .mod files have time stamps between Jan 5 11:06 and Jan 5 11:07.
Thanks don Sorry for the incomplete response. I used a 13.2 DVD to update a 13.2 system. My hope was to get around the problems I was having using zypper up and the VLC files on packman that could not be accessed. I was also hoping that this might be a way to fix broken grub2 boot configurations.
Thanks Don An update. This system is on a USB drive, so I have freedom to play with it. I did a mv /*.mod to a directory in my home. The system still boots. But I do not know how to determine if I have complete functionality.
Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/06/2016 01:58 PM, don fisher wrote:
This system is on a USB drive, so I have freedom to play with it. I did a mv /*.mod to a directory in my home. The system still boots. But I do not know how to determine if I have complete functionality.
Do you have .mod files under /boot/grub2/*. ?? Is there anything else in "/" that looks like it shouldn't belong there? Are you sure that you are booting in grub2? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/06/2016 12:14 PM, Anton Aylward wrote:
On 01/06/2016 01:58 PM, don fisher wrote:
This system is on a USB drive, so I have freedom to play with it. I did a mv /*.mod to a directory in my home. The system still boots. But I do not know how to determine if I have complete functionality.
Do you have .mod files under /boot/grub2/*. ??
Is there anything else in "/" that looks like it shouldn't belong there?
Are you sure that you are booting in grub2?
Sorry fir delay. Comcast, my ISP was having some problems. 1) there are 256 .mod files in the /boot/grub2/i386-pc directory. None any place else that I can see. 2) there are other file in / that should not be there. .readahead .so alternatives.log boot.img btmp command.1st efiemu32.o efiemu64.o faillog fs.1st last.log load.cfg moddep.1st parttool.1st pbl.log terminal.1st udateTestcase-2016-01-05-12-48-31/ video.1st wtmp y2yamldata-0B1B9E zypp/ 3. The system shows grub2 message at boot timne Thanks, Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/06/2016 03:46 PM, don fisher wrote:
2) there are other file in / that should not be there.
.readahead
That's OK to have there. The rest are anomalous. Something has gone seriously wrong, perhaps with your install, perhaps with unpacking some RPM. If this is a non-production//non-critical system, the experimentation on a USB as you say, they I would would not waste effort finding out why, just "nuke from orbit" and start over. If on subsequent attempts the same thing happens then its worth investigating.. HOWEVER ******* if this does reoccur ... it is worth paying a great deal more attention to what is going on in the install, logging EVERY DETAIL no matter how insignificant
.so alternatives.log boot.img btmp command.1st efiemu32.o efiemu64.o faillog fs.1st last.log load.cfg moddep.1st parttool.1st pbl.log terminal.1st udateTestcase-2016-01-05-12-48-31/ video.1st wtmp y2yamldata-0B1B9E zypp/
-- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-01-07 14:22, Anton Aylward wrote:
On 01/06/2016 03:46 PM, don fisher wrote:
2) there are other file in / that should not be there.
.readahead
That's OK to have there.
The rest are anomalous. Something has gone seriously wrong, perhaps with your install, perhaps with unpacking some RPM.
If this is a non-production//non-critical system, the experimentation on a USB as you say, they I would would not waste effort finding out why, just "nuke from orbit" and start over.
I don't think those files are that important to reinstall, Linux is usually more resilient than that :-) Often those files are user error when writing the destination for an operation. Or by a script. Dates can give clues. For instance, "udateTestcase" falls clearly in that case and can be deleted. rpm -f /filename will say if they belong to a package. Some 0 byte sized files can be flags for boot operations.
zypp/
This one is very strange. If the installation resides in a USB stick, there is the possibility that it has been used occasionally to write files to it, normal stick operation, from another installation. It could explain the most strange cases. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 01/06/2016 01:02 PM, don fisher wrote:
In a related thread, I stated that I used the distribution media with the upgrade option to update my system. As part of that process it did run grub2 and update the boot configuration. I now find that I have 256 .mod files in my root directory. What are they and what should I do with them? A Google link says they are usually generated by grub2, but I do not understand why they were generated or what to do with them.
Please clarify "root directory". Do you mean /*.mod /root/*.mod /boot/grub2/i386-pc/*.mod /boot/grub2/x86_64-efi/*.mod All those are *under* the "root directory" by various interpretations of the phrase. *IF AND ONLY IF* you mean one of the first two, then you have a problem, and I'm sure we'd be interested in how that came about. *HOWEVER* if its the last two, then that's correct and leave it alone. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/06/2016 01:02 PM, don fisher wrote:
A Google link says ...
+1 for making the effort to research this rather than just treating the forum like a crutch. BRAVO! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Andrei Borzenkov -
Anton Aylward -
Carlos E. R. -
don fisher