[opensuse] Installing 13.1 with NET iso, hangs at "Loading Installation System x/6, arbitrary percentage
This weekend I was working on upgrading an old system to 13.1. It has no PXE support, so I had to use the NET iso. The process kept stalling at "Loading Installation System 1/6" at some percentage. The machine would appear locked, sometimes Ctrl-Alt-SysRq-B would work, some times not. I thought this was probably due to the machine being _very_ old, but I tried swapping the NIC, no change. Then this morning I decided to try with a newer box. Same result .... Anything wonky with the network installation process? I'll try to use our local mirror and see how that goes. -- Per Jessen, Zürich (0.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
This weekend I was working on upgrading an old system to 13.1. It has no PXE support, so I had to use the NET iso. The process kept stalling at "Loading Installation System 1/6" at some percentage. The machine would appear locked, sometimes Ctrl-Alt-SysRq-B would work, some times not. I thought this was probably due to the machine being _very_ old, but I tried swapping the NIC, no change. Then this morning I decided to try with a newer box. Same result .... Anything wonky with the network installation process?
I'll try to use our local mirror and see how that goes.
Using a local mirror didn't work either. Now I'll try to use PXE booted from CD, which is more like our regular process. -- Per Jessen, Zürich (0.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Per Jessen wrote:
This weekend I was working on upgrading an old system to 13.1. It has no PXE support, so I had to use the NET iso. The process kept stalling at "Loading Installation System 1/6" at some percentage. The machine would appear locked, sometimes Ctrl-Alt-SysRq-B would work, some times not. I thought this was probably due to the machine being _very_ old, but I tried swapping the NIC, no change. Then this morning I decided to try with a newer box. Same result .... Anything wonky with the network installation process?
I'll try to use our local mirror and see how that goes.
Using a local mirror didn't work either. Now I'll try to use PXE booted from CD, which is more like our regular process.
Okay, problem found - out-of-memory. 256M is apparently no longer sufficient to run the installer :-( /Per -- Per Jessen, Zürich (0.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Jan 20, 2014 at 01:17:32PM +0100, Per Jessen wrote: [ 8< ]
Okay, problem found - out-of-memory. 256M is apparently no longer sufficient to run the installer :-(
You have time and some disk space to swap? Then you might get it working. By default the install system is this smart to notice that there is a partition with a valid swap signature and even uses it. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Lars Müller wrote:
On Mon, Jan 20, 2014 at 01:17:32PM +0100, Per Jessen wrote: [ 8< ]
Okay, problem found - out-of-memory. 256M is apparently no longer sufficient to run the installer :-(
You have time and some disk space to swap?
Then you might get it working. By default the install system is this smart to notice that there is a partition with a valid swap signature and even uses it.
Yeah, I thought so too, but it doesn't seem to be recognizing my swap partition. I wonder if I can add it manually. Anyway, I'm doing the install on a machine with 512M, then I'll copy it to the smaller box later on. Once the system is running, it uses very little memory, 80-90M. /Per -- Per Jessen, Zürich (0.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-01-20 14:40 (GMT+0100) Per Jessen composed:
Lars Müller wrote:
On Mon, Jan 20, 2014 at 01:17:32PM +0100, Per Jessen wrote:
Okay, problem found - out-of-memory. 256M is apparently no longer sufficient to run the installer :-(
Fedora claims 1G is needed to run its installer. :-p
You have time and some disk space to swap?
Then you might get it working. By default the install system is this smart to notice that there is a partition with a valid swap signature and even uses it.
Yeah, I thought so too, but it doesn't seem to be recognizing my swap partition. I wonder if I can add it manually.
In my experience it only automatically "uses" swap by making an entry in fstab for the newly installed system. I've always needed to goto tty2 as soon as possible and execute swapon for the installer to use swap. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (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
Felix Miata wrote:
On 2014-01-20 14:40 (GMT+0100) Per Jessen composed:
Lars Müller wrote:
On Mon, Jan 20, 2014 at 01:17:32PM +0100, Per Jessen wrote:
Okay, problem found - out-of-memory. 256M is apparently no longer sufficient to run the installer :-(
Fedora claims 1G is needed to run its installer. :-p
You have time and some disk space to swap?
Then you might get it working. By default the install system is this smart to notice that there is a partition with a valid swap signature and even uses it.
Yeah, I thought so too, but it doesn't seem to be recognizing my swap partition. I wonder if I can add it manually.
In my experience it only automatically "uses" swap by making an entry in fstab for the newly installed system. I've always needed to goto tty2 as soon as possible and execute swapon for the installer to use swap.
Like Lars said, in the past the installer has added swap space automatically. I have not played with such tiny systems for quite some time though. -- Per Jessen, Zürich (0.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-01-20 19:46 (GMT+0100) Per Jessen composed:
Felix Miata wrote:
In my experience it only automatically "uses" swap by making an entry in fstab for the newly installed system. I've always needed to goto tty2 as soon as possible and execute swapon for the installer to use swap.
Like Lars said, in the past the installer has added swap space automatically. I have not played with such tiny systems for quite some time though.
Maybe the automatic use only occurred if more RAM was required than available? It's been a very long time since I tried installing with less than 384M. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (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
Felix Miata wrote:
On 2014-01-20 19:46 (GMT+0100) Per Jessen composed:
Felix Miata wrote:
In my experience it only automatically "uses" swap by making an entry in fstab for the newly installed system. I've always needed to goto tty2 as soon as possible and execute swapon for the installer to use swap.
Like Lars said, in the past the installer has added swap space automatically. I have not played with such tiny systems for quite some time though.
Maybe the automatic use only occurred if more RAM was required than available?
Yes, quite possibly, using the swap-space makes it difficult/impossible to alter the disk-layout. If you prepare the disk before-hand, it's quite a useful feature though. -- Per Jessen, Zürich (0.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-01-21 07:50 (GMT+0100) Per Jessen composed:
Felix Miata wrote:
Maybe the automatic use only occurred if more RAM was required than available?
Yes, quite possibly, using the swap-space makes it difficult/impossible to alter the disk-layout. If you prepare the disk before-hand, it's quite a useful feature though.
Never an if here. No installation ever gets done here without all partitioning done in advance, so swap is always available to any installer I'm running. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (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 2014-01-21 07:50, Per Jessen wrote:
Yes, quite possibly, using the swap-space makes it difficult/impossible to alter the disk-layout. If you prepare the disk before-hand, it's quite a useful feature though.
AFAIK, that's the reason it is not used automatically. It is the admin who knows if he can allow swap to be used and from what disk. Otherwise, you'd get complains from people getting errors when trying to repartition the entire disk (yes, many of us don't do as Felix ;-) ) -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
On 2014-01-21 15:28 (GMT+0100) Carlos E. R. composed:
Per Jessen wrote:
Yes, quite possibly, using the swap-space makes it difficult/impossible to alter the disk-layout. If you prepare the disk before-hand, it's quite a useful feature though.
AFAIK, that's the reason it is not used automatically. It is the admin who knows if he can allow swap to be used and from what disk. Otherwise, you'd get complains from people getting errors when trying to repartition the entire disk (yes, many of us don't do as Felix ;-) )
One important reason for partitioning in advance is the value of multiboot. It can be so very much handier if some kind of repair to an installation becomes necessary, even just to troubleshoot if some repair is necessary, if it can be done via a menu that brings up an older, known working installation with similar configuration, compared to using some random live media to attempt same. Saturday I had an alien Windows 2008 Server here for diagnosis running on my LAN for about 6 hours. Sunday I found that my openSUSE 11.4 LAN/web server could see no shares except its own, while other systems on the LAN, both eComStation and Linux, could see most or all shares on the LAN, except those from the server. Neither rebooting everything nor shutting down everything except this and one other system helped. Eventually I tried booting the server to 11.2 instead of 11.4, and shares became visible both ways again. I rebooted back to 11.4, and shares remained visible both ways, just as if 11.4 had never had a problem seeing or being seen in the first place. I explained what happened after the fact to kukks on irc://freenode/#samba-os2 and he suggested 'smbcontrol nmbd force-election' might have been a solution. He also suggested configuring the server's smb.conf with higher priority, setting preferred master = as high as 255. Before that suggestion I had it set to 40. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (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 1/21/2014 7:05 AM, Felix Miata wrote:
I rebooted back to 11.4, and shares remained visible both ways, just as if 11.4 had never had a problem seeing or being seen in the first place.
I often run into the exact same problem, and simple take down and bring up nmbd. I've always liked the ability to do that separate from smbd, because it doesn't disrupt existing user connections. However it seems in later releases, smbd and nmbd are managed in parallel and are harder to manage separately. Forcing an election doesn't always work. (That happens every time a new station comes on line anyway). -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi, On Tue, Jan 21, 2014 at 12:12:10PM -0800, John Andersen wrote:
On 1/21/2014 7:05 AM, Felix Miata wrote:
I rebooted back to 11.4, and shares remained visible both ways, just as if 11.4 had never had a problem seeing or being seen in the first place.
I often run into the exact same problem, and simple take down and bring up nmbd. I've always liked the ability to do that separate from smbd, because it doesn't disrupt existing user connections. However it seems in later releases, smbd and nmbd are managed in parallel and are harder to manage separately.
That's more or less still the same. Independent if we use native systemd service files or not. hip:~ # systemctl status nmb.service nmb.service - Samba NMB Daemon Loaded: loaded (/usr/lib/systemd/system/nmb.service; disabled) Active: inactive (dead) Jan 18 18:25:13 hip systemd[1]: Stopped Samba NMB Daemon. Jan 18 18:27:18 hip systemd[1]: Stopped Samba NMB Daemon. Here you see nmbd is inactive. hip:~ # systemctl status smb.service smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; disabled) Active: active (running) since Mo 2014-01-20 15:20:13 CET; 1 day 18h ago Main PID: 24854 (smbd) CGroup: /system.slice/smb.service ├─24854 /usr/sbin/smbd -D └─24855 /usr/sbin/smbd -D Jan 20 15:20:13 hip systemd[1]: Started Samba SMB Daemon. Instead of the status command you're ale tu use start, stop, enable, disable, is-enabled, and so on. See the systemctl man page for all the details.
Forcing an election doesn't always work. (That happens every time a new station comes on line anyway).
Is AppArmor active? Are you able to pin it down to a particular Samba or SUSE version when it still worked and when it got broken? Please consider to file a bug report and include the ID in your reply to this thread. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Hi, On Wed, Jan 22, 2014 at 10:20:20AM +0100, Lars Mueller wrote:
On Tue, Jan 21, 2014 at 12:12:10PM -0800, John Andersen wrote:
On 1/21/2014 7:05 AM, Felix Miata wrote:
I rebooted back to 11.4, and shares remained visible both ways, just as if 11.4 had never had a problem seeing or being seen in the first place.
I often run into the exact same problem, and simple take down and bring up nmbd. I've always liked the ability to do that separate from smbd, because it doesn't disrupt existing user connections. However it seems in later releases, smbd and nmbd are managed in parallel and are harder to manage separately.
That's more or less still the same. Independent if we use native systemd service files or not.
But we didn't had tmpfiles for samba from the beginning while using the systemd service files. This was covered by bug 856759. You need to have the following line in the package change log: - Create /var/run/samba with systemd-tmpfiles on post-12.2 systems; (bnc#856759). Till we published updated samba packages including this change you're able to grab fixed packages from the network:samba:STABLE repository at http://download.opensuse.org/repositories/network:/samba:/STABLE/ Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On 2014-01-22 11:27 (GMT+0100) Lars Mueller composed:
On Wed, Jan 22, 2014 at 10:20:20AM +0100, Lars Mueller wrote:
On Tue, Jan 21, 2014 at 12:12:10PM -0800, John Andersen wrote:
On 1/21/2014 7:05 AM, Felix Miata wrote:
I rebooted back to 11.4, and shares remained visible both ways, just as if 11.4 had never had a problem seeing or being seen in the first place. I often run into the exact same problem, and simple take down and bring up nmbd. I've always liked the ability to do that separate from smbd, because it doesn't disrupt existing user connections. However it seems in later releases, smbd and nmbd are managed in parallel and are harder to manage separately.
That's more or less still the same. Independent if we use native systemd service files or not.
But we didn't had tmpfiles for samba from the beginning while using the systemd service files. This was covered by bug 856759.
You need to have the following line in the package change log:
- Create /var/run/samba with systemd-tmpfiles on post-12.2 systems; (bnc#856759).
Till we published updated samba packages including this change you're able to grab fixed packages from the network:samba:STABLE repository at http://download.opensuse.org/repositories/network:/samba:/STABLE/
FWIW, my comment forking the thread above quoted is about samba-3.6.3-122.1.i586 on 11.4 aka Evergreen, which predates systemd and /run by a very long time. Last changelog entry for samba is Wed May 08 2013. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (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 Wed, Jan 22, 2014 at 05:58:15AM -0500, Felix Miata wrote: [ <8 ]
FWIW, my comment forking the thread above quoted is about samba-3.6.3-122.1.i586 on 11.4 aka Evergreen, which predates systemd and /run by a very long time. Last changelog entry for samba is Wed May 08 2013.
Thanks Felix. I've missread John's mail. I've read the complete thread once again from the archive. I bit to fast reflex-reply. ;) Nevertheless both services are manageable the same way as in the past. It shouldn't be harder than five years back. John might provide us some more details. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On Wed, 2014-01-22 at 11:27 +0100, Lars Mueller wrote:
Hi,
On Wed, Jan 22, 2014 at 10:20:20AM +0100, Lars Mueller wrote:
On Tue, Jan 21, 2014 at 12:12:10PM -0800, John Andersen wrote:
On 1/21/2014 7:05 AM, Felix Miata wrote:
I rebooted back to 11.4, and shares remained visible both ways, just as if 11.4 had never had a problem seeing or being seen in the first place.
I often run into the exact same problem, and simple take down and bring up nmbd. I've always liked the ability to do that separate from smbd, because it doesn't disrupt existing user connections. However it seems in later releases, smbd and nmbd are managed in parallel and are harder to manage separately.
That's more or less still the same. Independent if we use native systemd service files or not.
But we didn't had tmpfiles for samba from the beginning while using the systemd service files. This was covered by bug 856759.
You need to have the following line in the package change log:
- Create /var/run/samba with systemd-tmpfiles on post-12.2 systems; (bnc#856759).
Till we published updated samba packages including this change you're able to grab fixed packages from the network:samba:STABLE repository at http://download.opensuse.org/repositories/network:/samba:/STABLE/
Cheers,
Lars
Lars, please We are discussing a released version of openSUSE. Samba has been a mess here for too long. We should not have to refer to endless bug reports, stop/start binaries to get it to work, insert lines here and there or install from an additional repository. There was a golden opportunity to get smbd and nmbd into proper systemd service files like the other maintainers have with the transition from 12.3. What a pity. . . Thanks. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 2014-01-21 07:50, Per Jessen wrote:
Yes, quite possibly, using the swap-space makes it difficult/impossible to alter the disk-layout. If you prepare the disk before-hand, it's quite a useful feature though.
AFAIK, that's the reason it is not used automatically. It is the admin who knows if he can allow swap to be used and from what disk.
Yes, that makes sense. I wonder if the installer would ask me if I want to add swap, but it's been years since I have had to work with such tiny systems. However, I did manage to install this system, 13.1 is now running on a PII 333MHz with 256Mb RAM. It's perfectly useable too, using up about 95Mb memory. In case you're wondering, I need this box because it has a couple of ISA slots, and I needed to upgrade it because I needed the comedi drivers for an I/O card. As it turns out, the comedi drivers weren't enabled in the opensuse kernel anyway, so the exercise was somewhat pointless, but nonetheless good fun. Wrt the disk-drive, well, they just don't make them like that anymore. It's a 1999 10Gb Western Digital Caviar, showing no problems and passing the short smart selftest every day. -- Per Jessen, Zürich (3.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-01-22 08:43 (GMT+0100) Per Jessen composed:
Wrt the disk-drive, well, they just don't make them like that anymore.
Good riddance.
It's a 1999 10Gb Western Digital Caviar, showing no problems and passing the short smart selftest every day.
Lucky you. They were my last choice, used only if free, nothing else available, and going into something that matters little if lost: https://web.archive.org/web/20070504095735/http://archives.mandrivalinux.com... I only ever started buying any WD after WD & Seagate bought up everyone else making 3.5" drives. With only two choices left, picking only one results in all eggs in same basket risk. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (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
Felix Miata wrote:
On 2014-01-22 08:43 (GMT+0100) Per Jessen composed:
Wrt the disk-drive, well, they just don't make them like that anymore.
Good riddance.
Dunno about that - the life expectancy of drives today is just about = warranty period. Enterprise drives do last longer, but not 15 years. When this drive eventually breaks too, I guess I'll need to find a separate SATA PCI controller, but the replacement SATA drive will likely break in 4-5 years.
It's a 1999 10Gb Western Digital Caviar, showing no problems and passing the short smart selftest every day.
Lucky you. They were my last choice, used only if free, nothing else available,
The latter is exactly why it's still in use. -- Per Jessen, Zürich (0.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Lars Müller wrote:
On Mon, Jan 20, 2014 at 01:17:32PM +0100, Per Jessen wrote: [ 8< ]
Okay, problem found - out-of-memory. 256M is apparently no longer sufficient to run the installer :-(
You have time and some disk space to swap?
Then you might get it working. By default the install system is this smart to notice that there is a partition with a valid swap signature and even uses it.
Yeah, I thought so too, but it doesn't seem to be recognizing my swap partition. I wonder if I can add it manually.
Adding swap space manually works, but the installer seems to have lost the ability to add it automagically. -- Per Jessen, Zürich (0.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dne Po 20. ledna 2014 13:17:32, Per Jessen napsal(a):
Per Jessen wrote:
Per Jessen wrote: Okay, problem found - out-of-memory. 256M is apparently no longer sufficient to run the installer :-(
Cover of promo DVD says, that minimal amount of RAM is 512 MB...
/Per
Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/
В Mon, 20 Jan 2014 13:17:32 +0100
Per Jessen
Okay, problem found - out-of-memory. 256M is apparently no longer sufficient to run the installer :-(
I think it is possible to force installer in text mode. It may work. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
Andrey Borzenkov -
Carlos E. R. -
Felix Miata -
John Andersen -
Lars Mueller -
Lars Müller
-
lynn -
Per Jessen -
Vojtěch Zeisek