Hello List os-prober seems to have taken control of my system !! it has created a huge directory under : /var/lib/os-prober/mount - the mode is 0555 : it seems impossible to change mode and impossible to delete .......... what to do please?? thanks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/02/2014 02:02 PM, ellanios82 wrote:
Hello List
os-prober seems to have taken control of my system !!
it has created a huge directory under :
/var/lib/os-prober/mount
- the mode is 0555 : it seems impossible to change mode and impossible to delete
..........
what to do please??
thanks
Wait for more os-prober specific answers, but worst-case, boot from the install cd/dvd and boot the rescue console, then you can take care of the file/directory permission my simply mounting the partition and manually chmod to whatever you need. If needed you can also chroot your entire install under /mnt and fix it that way as well. If you get to that point, report back and we'll help you thought it. I've never messed with os-prober, so for now wait on some specific advise. There may be a magic fix that will work without doing it the old-fashioned way. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2/2/2014 2:07 PM, David C. Rankin wrote:
On 02/02/2014 02:02 PM, ellanios82 wrote:
Hello List
os-prober seems to have taken control of my system !!
it has created a huge directory under :
/var/lib/os-prober/mount
- the mode is 0555 : it seems impossible to change mode and impossible to delete
..........
what to do please??
thanks
Wait for more os-prober specific answers, but worst-case, boot from the install cd/dvd and boot the rescue console, then you can take care of the file/directory permission my simply mounting the partition and manually chmod to whatever you need.
If needed you can also chroot your entire install under /mnt and fix it that way as well. If you get to that point, report back and we'll help you thought it.
I've never messed with os-prober, so for now wait on some specific advise. There may be a magic fix that will work without doing it the old-fashioned way.
It is not a file. It is just another partition on the hard disk mounted there. It is not taking up any actual room from this linux machine. os-prober is used by Grub2. It came from the Ubuntu world. It attempts to figure out all the other bootable partitions on the system and determine what OS is installed there. If you don't dual boot you will never see it. It simply mounts other partitions in that directory, (read only) and then it goes rooting around in there to find out what OS is there. It should Unmount it when it is done. Its been known to fail and leave it mounted. It can be unmounted by root. If you boot via a rescue CD it won't be there, because OS-Prober won't have mounted it. Its not taking up room. Worst case is it causes a system backup to balloon in size. What ever you do, don't start trying to make it write-able. You will hoze one of your other dual boot OSs if you succeed. (But you probably won't succeed). Treat it like a scabbed genital. (Don't F__K with it). -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/03/2014 12:20 AM, John Andersen wrote:
On 2/2/2014 2:07 PM, David C. Rankin wrote:
On 02/02/2014 02:02 PM, ellanios82 wrote:
Hello List
os-prober seems to have taken control of my system !!
it has created a huge directory under :
/var/lib/os-prober/mount
- the mode is 0555 : it seems impossible to change mode and impossible to delete
..........
what to do please??
thanks
Wait for more os-prober specific answers, but worst-case, boot from the install cd/dvd and boot the rescue console, then you can take care of the file/directory permission my simply mounting the partition and manually chmod to whatever you need.
If needed you can also chroot your entire install under /mnt and fix it that way as well. If you get to that point, report back and we'll help you thought it.
I've never messed with os-prober, so for now wait on some specific advise. There may be a magic fix that will work without doing it the old-fashioned way.
It is not a file.
It is just another partition on the hard disk mounted there. It is not taking up any actual room from this linux machine.
os-prober is used by Grub2. It came from the Ubuntu world.
It attempts to figure out all the other bootable partitions on the system and determine what OS is installed there.
If you don't dual boot you will never see it.
It simply mounts other partitions in that directory, (read only) and then it goes rooting around in there to find out what OS is there.
It should Unmount it when it is done. Its been known to fail and leave it mounted. It can be unmounted by root.
If you boot via a rescue CD it won't be there, because OS-Prober won't have mounted it.
Its not taking up room. Worst case is it causes a system backup to balloon in size.
What ever you do, don't start trying to make it write-able. You will hoze one of your other dual boot OSs if you succeed. (But you probably won't succeed).
Treat it like a scabbed genital. (Don't F__K with it).
- many thanks all ! - i do not dual boot thus do not understand what triggered this crisis - grub2 had mounted something ............. eventually used oS 13.1 Live on usb stick to mount root partition and also mount a backup of that partition : then used tar to restore : tar clf - . | ( umask 0; cd /; tar xvf - ) ............... - i have no idea what caused grub2 to mount something consequently causing os-prober crisis : again - do not dual boot. thank goodness . . . system seems ok now many thanks regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/02/2014 02:20 PM, John Andersen wrote:
On 2/2/2014 2:07 PM, David C. Rankin wrote:
On 02/02/2014 02:02 PM, ellanios82 wrote:
Hello List
os-prober seems to have taken control of my system !!
it has created a huge directory under :
/var/lib/os-prober/mount
- the mode is 0555 : it seems impossible to change mode and impossible to delete
..........
what to do please??
thanks
Wait for more os-prober specific answers, but worst-case, boot from the install cd/dvd and boot the rescue console, then you can take care of the file/directory permission my simply mounting the partition and manually chmod to whatever you need.
If needed you can also chroot your entire install under /mnt and fix it that way as well. If you get to that point, report back and we'll help you thought it.
I've never messed with os-prober, so for now wait on some specific advise. There may be a magic fix that will work without doing it the old-fashioned way.
It is not a file.
It is just another partition on the hard disk mounted there. It is not taking up any actual room from this linux machine.
os-prober is used by Grub2. It came from the Ubuntu world.
It attempts to figure out all the other bootable partitions on the system and determine what OS is installed there.
If you don't dual boot you will never see it.
It simply mounts other partitions in that directory, (read only) and then it goes rooting around in there to find out what OS is there.
It should Unmount it when it is done. Its been known to fail and leave it mounted. It can be unmounted by root.
If you boot via a rescue CD it won't be there, because OS-Prober won't have mounted it.
Its not taking up room. Worst case is it causes a system backup to balloon in size.
What ever you do, don't start trying to make it write-able. You will hoze one of your other dual boot OSs if you succeed. (But you probably won't succeed).
Treat it like a scabbed genital. (Don't F__K with it).
More on os-prober: I installed 13.1 64-bit on a Supermicro server yesterday without any apparent problems. The first thing I did was to edit /etc/default/grub to enable verbose logging. But the subsequent 'grub2-mkconfig -o /boot/grub2/grub.cfg' hung for as long as I was willing to wait. A cntl-C killed the process and /boot/grub2/grub.cnf wasn't updated. I then performed a "zypper dup" with the stock repositories and had a script-hang error on one of the packages. Again, cntl-C freed it up, only to encounter it again. Another cntl-C allowed the upgrade to complete. I then found a running os-prober process and errors in /var/log/messages showing I/O errors on /dev/fd0! There is no floppy drive in the system, but there could very well be a floppy controller (I'll check next week). At any rate, the system boots, but I don't have confidence in it and will scrub/reinstall next week since I have very little time invested at this point. I won't enable verbose booting until a successful zypper dup next time. Also, booting off the install DVD leads to a black-screen of death unless a "nomodeset" is added to the first kernel command-line. The VGA graphics adapter is embedded on the motherboard and I tried two different monitors without success. It seems that there's always something... Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/07/2014 09:35 PM, Lew Wolfgang wrote:
I then found a running os-prober process and errors in /var/log/messages showing I/O errors on /dev/fd0! There is no floppy drive in the system, but there could very well be a floppy controller (I'll check next week).
on Dec 07 2013,
i note that on my system, yast's bootloader takes a very long time "Reading Partitions".
"Shot in the dark - try disabling floppy controller in BIOS." .............. in my case, disabling floppy controller in BIOS fixed the probs ........... thank you Andrey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
David C. Rankin -
ellanios82 -
John Andersen -
Lew Wolfgang