[opensuse] the gost of a removed hard-disk gives me a problem
From where is the boot-loader getting its information so that I can remove
One of my hard-disk stopped functioning properly so I removed it from my main computer. The HDD had two partitions, the first a 2 GB swap and the second partition an ext 4 159 GB single work-space. After removal of the disk I found that the reboot took me much longer. Looking at the cause I found that the machine is still looking for the local swap. I have given all my swap spaces a volume label, in this case label swapc. this old and unjust information. -- opensuse:tumbleweed:20171108 Qt: 5.9.2 KDE Frameworks: 5.39.0 kf5-config: 1.0 KDE Plasma: 5.11.2 plasmashell 5.11.2 Kernel: 4.13.11-1-default Linux User 183145 working on a Pentium IV . -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
C. Brouerius van Nidek wrote:
One of my hard-disk stopped functioning properly so I removed it from my main computer. The HDD had two partitions, the first a 2 GB swap and the second partition an ext 4 159 GB single work-space. After removal of the disk I found that the reboot took me much longer. Looking at the cause I found that the machine is still looking for the local swap. I have given all my swap spaces a volume label, in this case label swapc. From where is the boot-loader getting its information so that I can remove this old and unjust information.
Your initrd perhaps. -- Per Jessen, Zürich (6.5°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/10/2017 03:20 PM, C. Brouerius van Nidek wrote:
One of my hard-disk stopped functioning properly so I removed it from my main computer. The HDD had two partitions, the first a 2 GB swap and the second partition an ext 4 159 GB single work-space. After removal of the disk I found that the reboot took me much longer. Looking at the cause I found that the machine is still looking for the local swap. I have given all my swap spaces a volume label, in this case label swapc. From where is the boot-loader getting its information so that I can remove this old and unjust information.
I don't think it's the bootloader who would care about the swap partition but rather the booted GNU/Linux system. AFAIK the correct place to specify swap is still good old '/etc/fstab'. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday, November 10, 2017 9:20:23 PM EST C. Brouerius van Nidek wrote:
One of my hard-disk stopped functioning properly so I removed it from my main computer. The HDD had two partitions, the first a 2 GB swap and the second partition an ext 4 159 GB single work-space. After removal of the disk I found that the reboot took me much longer. Looking at the cause I found that the machine is still looking for the local swap. I have given all my swap spaces a volume label, in this case label swapc. From where is the boot-loader getting its information so that I can remove this old and unjust information.
Check your grub kernel boot line, the "resume" clause. It may be pointing to what was the swap partition. --dg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dennis Gallien composed on 2017-11-10 11:12 (UTC-0500):
C. Brouerius van Nidek wrote:
One of my hard-disk stopped functioning properly so I removed it from my main computer. The HDD had two partitions, the first a 2 GB swap and the second partition an ext 4 159 GB single work-space. After removal of the disk I found that the reboot took me much longer. Looking at the cause I found that the machine is still looking for the local swap. I have given all my swap spaces a volume label, in this case label swapc. From where is the boot-loader getting its information so that I can remove this old and unjust information.
Check your grub kernel boot line, the "resume" clause. It may be pointing to what was the swap partition.
It almost certainly does, as would the initrd, and fstab. Replacing the Grub kernel line's resume=foobarbaz with noresume will avoid the initrd call pending regeneration or new kernel installation, but fstab needs an update to exclude the swapc partition as well. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday, November 10, 2017 11:45:53 PM WIB Felix Miata wrote:
Dennis Gallien composed on 2017-11-10 11:12 (UTC-0500):
C. Brouerius van Nidek wrote:
One of my hard-disk stopped functioning properly so I removed it from my main computer. The HDD had two partitions, the first a 2 GB swap and the second partition an ext 4 159 GB single work-space. After removal of the disk I found that the reboot took me much longer. Looking at the cause I found that the machine is still looking for the local swap. I have given all my swap spaces a volume label, in this case label swapc. From where is the boot-loader getting its information so that I can remove this old and unjust information.
Check your grub kernel boot line, the "resume" clause. It may be pointing to what was the swap partition.
It almost certainly does, as would the initrd, and fstab. Replacing the Grub kernel line's resume=foobarbaz with noresume will avoid the initrd call pending regeneration or new kernel installation, but fstab needs an update to exclude the swapc partition as well.
Thanks everybody for their input. The main problem in my case was the fstab which still contained the line with the swapc partition. I had overlooked the line because my fstab has now all the directories included from "home". I also stood under the impression that the fstab is renewed with every main update. My mistake. -- opensuse:tumbleweed:20171108 Qt: 5.9.2 KDE Frameworks: 5.39.0 kf5-config: 1.0 KDE Plasma: 5.11.2 plasmashell 5.11.2 Kernel: 4.13.11-1-default Linux User 183145 working on a Pentium IV . -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* C. Brouerius van Nidek
On Friday, November 10, 2017 11:45:53 PM WIB Felix Miata wrote:
Dennis Gallien composed on 2017-11-10 11:12 (UTC-0500):
C. Brouerius van Nidek wrote:
One of my hard-disk stopped functioning properly so I removed it from my main computer. The HDD had two partitions, the first a 2 GB swap and the second partition an ext 4 159 GB single work-space. After removal of the disk I found that the reboot took me much longer. Looking at the cause I found that the machine is still looking for the local swap. I have given all my swap spaces a volume label, in this case label swapc. From where is the boot-loader getting its information so that I can remove this old and unjust information.
Check your grub kernel boot line, the "resume" clause. It may be pointing to what was the swap partition.
It almost certainly does, as would the initrd, and fstab. Replacing the Grub kernel line's resume=foobarbaz with noresume will avoid the initrd call pending regeneration or new kernel installation, but fstab needs an update to exclude the swapc partition as well.
Thanks everybody for their input. The main problem in my case was the fstab which still contained the line with the swapc partition. I had overlooked the line because my fstab has now all the directories included from "home". I also stood under the impression that the fstab is renewed with every main update. My mistake.
*if* you had used yast to configure your swap, all the changes would have been made for you -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Bernhard Voelker -
C. Brouerius van Nidek -
Dennis Gallien -
Felix Miata -
Patrick Shanahan -
Per Jessen