• Repair or Replace

    From Steve Matzura@21:1/5 to All on Wed May 21 01:10:01 2025
    After a year in storage, I'm trying to get a version 11 system back
    online. I connected it to power and network, then booted it.
    Interestingly, it appeared on my network not at the address it had when
    it went into storage, but one given it by my local DHCP server. The
    console scrolled, but not to completion, Speakup didn't start, and I
    cannot log in from the console. I have a couple applications on that
    system, including Asterisk version 20 with its configuration files, but
    the system is unusable as it stands. The questions are, repair Debian 11
    or or replace with Debian 12, and how do i reclaim those all-important configuration files from Asterisk and other applications? Can I try
    mounting the boot drive in WSL on another machine, or possibly inspect
    it with a running Debian system booted from the installation medium?


    Thanks in advance.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Smith@21:1/5 to Steve Matzura on Wed May 21 01:30:01 2025
    Hi,

    On Tue, May 20, 2025 at 06:20:33PM -0400, Steve Matzura wrote:
    After a year in storage, I'm trying to get a version 11 system back online.
    I connected it to power and network, then booted it. Interestingly, it appeared on my network not at the address it had when it went into storage, but one given it by my local DHCP server

    Are you saying that when it went into storage it was not using DHCP but
    static networking yet when you booted it later it had changed to DHCP?
    That would seem odd to me. If it was also DHCP before then it's not so
    odd.

    On the other hand if a machine with DHCP doesn't get a lease it often
    falls back to link-local IPv4 addresses.

    I cannot log in from the console.

    Reboot, select rescue mode from the Grub menu and log in that way. See
    "Rescue shell" from here:

    https://wiki.debian.org/InitramfsDebug

    If that seems too complex, boot with a Debian 11 or Debian 11 install
    media and select rescue mode instead. It will mount the existing
    filesystems and dump you toa shell prompt.

    repair Debian 11 or or replace with Debian 12

    If I was going to continue using the machine I'd probably get the data
    off and then reinstall with a Debian 13 pre-release. It went into
    hard freeze days ago and shouldn't see much change before the actual
    release of Debian 13. If that seems too bold to you then install Debian
    12.

    Leaving it as Debian 11 means it will be running oldoldstable in just a
    couple of months. Since you're making some effort now, it doesn't seem
    worth making work for yourself again so soon.

    how do i reclaim those all-important configuration files from Asterisk
    and other applications? Can I try mounting the boot drive in WSL on
    another machine, or possibly inspect it with a running Debian system
    booted from the installation medium?

    It doesn't sound so broken that booting to the rescue shell wouldn't
    allow you to fix it. If not then yeah, rescue mode from some Debian
    install media.

    Thanks,
    Andy

    --
    https://bitfolk.com/ -- No-nonsense VPS hosting

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alain D D Williams@21:1/5 to Steve Matzura on Wed May 21 01:40:01 2025
    On Tue, May 20, 2025 at 06:20:33PM -0400, Steve Matzura wrote:
    After a year in storage, I'm trying to get a version 11 system back online.
    I connected it to power and network, then booted it. Interestingly, it appeared on my network not at the address it had when it went into storage, but one given it by my local DHCP server. The console scrolled, but not to completion, Speakup didn't start, and I cannot log in from the console. I have a couple applications on that system, including Asterisk version 20
    with its configuration files, but the system is unusable as it stands. The questions are, repair Debian 11 or or replace with Debian 12, and how do i reclaim those all-important configuration files from Asterisk and other applications? Can I try mounting the boot drive in WSL on another machine,
    or possibly inspect it with a running Debian system booted from the installation medium?

    One easy thing to check: If it has been off for a year the battery that powers the BIOS clock might have gone flat and the close reset to 1980 or something.

    Switch it on, get into the BIOS setup and ensure that the clock is roughly correct. Then reboot.

    That will not fix the IP address, but that should not be a problem unless some firewall had rules special to the old IP address.

    Thanks in advance.


    --
    Alain Williams
    Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
    +44 (0) 787 668 0256 https://www.phcomp.co.uk/
    Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html
    #include <std_disclaimer.h>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dan Purgert@21:1/5 to Steve Matzura on Wed May 21 01:40:01 2025
    On May 20, 2025, Steve Matzura wrote:
    After a year in storage, I'm trying to get a version 11 system back online.
    I connected it to power and network, then booted it. Interestingly, it appeared on my network not at the address it had when it went into storage, but one given it by my local DHCP server. The console scrolled, but not to completion, Speakup didn't start, and I cannot log in from the console. I have a couple applications on that system, including Asterisk version 20
    with its configuration files, but the system is unusable as it stands. The questions are, repair Debian 11 or or replace with Debian 12, and how do i reclaim those all-important configuration files from Asterisk and other applications? Can I try mounting the boot drive in WSL on another machine,
    or possibly inspect it with a running Debian system booted from the installation medium?

    I don't know about WSL's capabilities. I'd just boot off any distro
    live image (Debian, Ubuntu, Mint, whatever) and pull off the important
    stuff.


    --
    |_|O|_|
    |_|_|O| Github: https://github.com/dpurgert
    |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEE3asj+xn6fYUcweBnbWVw5UznKGAFAmgtEXsACgkQbWVw5Uzn KGA0vxAAmEX4OlZlTaBgjgBlvq6kB0/oiyHCwQHj+JB1MTSuDQk5/+R6STlFAV75 zBfk7rT9GFfK91N72Fi+I7YikYq3KBl2UF+cQi3EAoB/LWPLUdi6XNwyAtNQinpT QP7aHdZAuBga5TWEQAq6uoDLG5LAC4JbV0S+S5bS+DCgkl/jzXBOigxt0QFtyS9h QVKIkQcr9DstRwF7DwoVD+4LvdoKwvSEIff05BttrzEqp1+jiDrCi35NSTJaU1xE vW11whh+IznV57q0YbU3ZZN4A6SP6Hushrg90NLYUjx+VAuF8J6HOhYtNd7nFQFd 7DzTxHv8umnC19P+wwk5+AnMN2P8irETTzhz7DTktkYHWi4rm0cACnAe9yM4C5kR gdZ7vC3XTeVA5M9FnwVIvhFsMB7s+QmFz6QWHtN4e/qfcgO9PdCwilzo8Lg5kEiV bVX9EbhOw23HUE3u2LuCUnak3gM2J3qYyhBFiEwpLuIjQww20Mr9kPq4NVxUtGRE gxx26ezC6qrnaXYR6WvpwJFBZyzYKitX+UgkUPhT5OYfh9eobpVZ0xE013OPlY9O jLguI/TdEYLGMP6TST3Vg4KQ7HoXnxh9Z3jPVA5IJME2+QH4T+UILhxsZiYZR1TQ bDU61/7LtQnE54wzhLP7P3oRpgcp/nIe+WLLL54wU3KkVK0plUU=
    =c0ch
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Us
  • From Felix Miata@21:1/5 to All on Wed May 21 02:10:01 2025
    Steve Matzura composed on 2025-05-20 18:20 (UTC-0400):

    After a year in storage, I'm trying to get a version 11 system back
    online. I connected it to power and network, then booted it.
    Interestingly, it appeared on my network not at the address it had when
    it went into storage, but one given it by my local DHCP server. The
    console scrolled, but not to completion,

    This is routine on all my Debian installations since long before Bullseye, continuing in Trixie. What seems to be the case is that tty1 is specially handled
    by Debian, and it appears the boot messages stop before boot completes. However,
    when boot has reached multi-user.target (complete short of running X), switching
    to any of tty2-6 provides working shell prompts.
    --
    Evolution as taught in public schools is, like religion,
    based on faith, not based on science.

    Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

    Felix Miata

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Smith@21:1/5 to Titus Newswanger on Wed May 21 04:10:02 2025
    Hi,

    On Tue, May 20, 2025 at 08:42:08PM -0500, Titus Newswanger wrote:
    I recall seeing something similar, where I thought boot didn't complete,
    then discovered if I tap the 'enter' key, the login prompt appeared. I
    wasn't sure what caused that behavior, my guess is there may have been some error messages printed to my terminal, scrolling the login text up off the screen.

    systemd runs an agetty process on each tty, but if there is no activity
    within a certain time it kills that process which clears the screen and
    leaves no visible login: prompt until a key is pressed.

    This behaviour can be disabled by overriding the [email protected] with:

    [Service]
    TTYVTDisallocate=no

    That will cause the agetty process per tty to stay around.

    Thanks,
    Andy

    --
    https://bitfolk.com/ -- No-nonsense VPS hosting

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Titus Newswanger@21:1/5 to All on Wed May 21 03:50:01 2025
    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------YtDdjpi1WeodAgJ3m0SEH9U2
    Content-Type: multipart/mixed; boundary="------------9rQ20D5Huw3Rkf19vVjQpw2A"

    --------------9rQ20D5Huw3Rkf19vVjQpw2A
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

    DQpPbiA1LzIwLzI1IDE5OjAyLCBGZWxpeCBNaWF0YSB3cm90ZToNCj4gVGhpcyBpcyByb3V0 aW5lIG9uIGFsbCBteSBEZWJpYW4gaW5zdGFsbGF0aW9ucyBzaW5jZSBsb25nIGJlZm9yZSBC dWxsc2V5ZSwNCj4gY29udGludWluZyBpbiBUcml4aWUuIFdoYXQgc2VlbXMgdG8gYmUgdGhl IGNhc2UgaXMgdGhhdCB0dHkxIGlzIHNwZWNpYWxseSBoYW5kbGVkDQo+IGJ5IERlYmlhbiwg YW5kIGl0IGFwcGVhcnMgdGhlIGJvb3QgbWVzc2FnZXMgc3RvcCBiZWZvcmUgYm9vdCBjb21w bGV0ZXMuIEhvd2V2ZXIsDQo+IHdoZW4gYm9vdCBoYXMgcmVhY2hlZCBtdWx0aS11c2VyLnRh cmdldCAoY29tcGxldGUgc2hvcnQgb2YgcnVubmluZyBYKSwgc3dpdGNoaW5nDQo+IHRvIGFu eSBvZiB0dHkyLTYgcHJvdmlkZXMgd29ya2luZyBzaGVsbCBwcm9tcHRzLg0KSSByZWNhbGwg c2VlaW5nIHNvbWV0aGluZyBzaW1pbGFyLCB3aGVyZSBJIHRob3VnaHQgYm9vdCBkaWRuJ3Qg Y29tcGxldGUsIA0KdGhlbiBkaXNjb3ZlcmVkIGlmIEkgdGFwIHRoZSAnZW50ZXInIGtleSwg dGhlIGxvZ2luIHByb21wdCBhcHBlYXJlZC4gSSANCndhc24ndCBzdXJlIHdoYXQgY2F1c2Vk IHRoYXQgYmVoYXZpb3IsIG15IGd1ZXNzIGlzIHRoZXJlIG1heSBoYXZlIGJlZW4gDQpzb21l IGVycm9yIG1lc3NhZ2VzIHByaW50ZWQgdG8gbXkgdGVybWluYWwsIHNjcm9sbGluZyB0aGUg bG9naW4gdGV4dCB1cCANCm9mZiB0aGUgc2NyZWVuLg0KDQotLSANCg0KVGl0dXMgTmV3c3dh bmdlcg0KQ3VydGlzcyBXSQ0KDQo=
    --------------9rQ20D5Huw3Rkf19vVjQpw2A
    Content-Type: application/pgp-keys; name="OpenPGP_0x17365CC7EC4FC3E6.asc" Content-Disposition: attachment; filename="OpenPGP_0x17365CC7EC4FC3E6.asc" Content-Description: OpenPGP public key
    Content-Transfer-Encoding: quoted-printable

    -----BEGIN PGP PUBLIC KEY BLOCK-----

    xsFNBGgMZLUBEACslFAcJI9+LvTdQM9ZceMVIxgmna9tl/zWzSprCjm3R+W6p5eb YfWWaJQRZnGQq5VYuiKK3AfvulKOqob6Jel7cbsAIwQVWog3Jv56nta72DXnHfI5 CsQoS4xXAluzYee50AWr5sv6ccR/vP5OXI3WeyGPnjn29zwthyTssUwqIRo24X2t SEQBYBrdelG014bXf99Ys25BGfOifmiBxRuD8Er4t99MiV8r0255uSRPU+AvvR34 lCB3+QD16iS16pfe+F4Zo//LL+RadoRpMpJYm070lbNvd7xFB/EkU/n7aIYA8OOE OrT9lrW/9G60SZsGR23EcQvrn+NOLOcF0DQNVPYTy3uG+bwQqivSD12su7AoM6pR 4OaBYrQyep3wVvb1z6aoTIMyi5LAHug3/SBDXPFjX0wBAfufNFNQ9BzGPND4lNzU PrKzhOlTZHBBMhXFn3qT9djo55E8fG98ecF392X6l6g797HV65u7tfujoiBWLtVE KIlgk+u7PjQm0fMlqV41qbCjhWk7WGVcZu8Cg6EGBGoZDBaN9vN4qS7YmW6y2DDe bWgoyJlOefso5dujSpzY7JXa5LEMz/RkDgbFP74eyGuXc+Al3OWR5OUOJuksKvtV Sn3f75hAwuv6Y+uXXp9qzFSconxY2sVQG3cRCXKyhHtfzX4b99XoNejUgwARAQAB zSVUaXR1cyBOZXdzd2FuZ2VyIDxud2VAYWJjbWFpbGJveC5uZXQ+wsGUBBMBCgA+ FiEEJ2LwHADW3dTgtISCFzZcx+xPw+YFAmgMZLUCGwMFCQPCZwAFCwkIBwIGFQoJ CAsCBBYCAwECHgECF4AACgkQFzZcx+xPw+Y1oxAAoIhr6XCK7GseJCAtYc7GqX/8 oEmCCfV7Xcf+STpG1GNUyyzuDWtfeyGbcBXYR5zJIMIhVusHgRVmgpJB/8KAj3q9 XBCrGYDAiChtn2gMcaOLmtGaKZYUTM8zkF5CUx4PJk6h5nAMQ/V8xgJlWeFfrNKg CTjS24lJgr2MTnVSD/H6NXTMxG2bY+dDPWJA586BLcUvcjr5uJumuHujRc3W5tUo XUkC8dUw+j8b96XETreygtpsER85sx1uuKkrqy0CpbcSacGYzmsxg5xb3qKmIcg7 6yAjIBc9EZWrZFWOG9Z/8UFaMFJUC0zwBYjDa4WIUQedEvk2kEBLJ5Jz/SACuPSB W124usYVpyb/YTfFwzomCGsN/Qsvcfl67Ta74BKRW9iZKAaH8WQU3zFO1TZmiaHi KK58MHL0SOKyhnIjZ/l7XMPYcBvJJDiQDDuqUj2uPg6myZt/Dp04gVYjKHXBQivH YwZYb9CgWI8Oo8uivrkF7Hz+EOcg6L+UGAYi+0lLU9fbOYP104RfMSm7r8zc8PbQ wKdP4X9yHqmE7V9LH7KryPLkKglTedlzbXOmWIguORbRPXDB17LiUbYMwQdDEhGm 5x7r8I7cRI2yVSkJPzb9t2Kje0HHmDTHSSsOyhDiaoLjqZv/sTFJdzqakGh9YS4P KWiOVgX84DmwXG2gUETOwU0EaAxktQEQAOs/00k1VB+n8iEZOY0VvN+MAtxtl037 uffm7YyznHwklGeBqrbbHgkQORMyFjHxB+eLq/0FtmGlAE1mfcDC4/cEMjqIR98n r5npZ2lNghSSlE2zwMBLwGk5czSPI91YAgpD54SDcSagoOhy4GfuDXtRWRIQAzWL ikZnrcoC0ERxdrdx5YNAOKt7XdYW4snLZCh/Lhs4JMcWyAyuERK6oktpdpHqD9AW 5qf8ZcvA9g8vR57WvFMgfGJaKcXuDj98DJ6ottPpmy+Zg6DRhffIk8dtixzxRaRJ 1ffy6oxj6zEu1BbUhdhoSYyB0OhwMI7xLUClG9b708Y5Hsn5PpEc9YJYcnKQq9fF 0Y6nzOWmhGY3rI+x7BziXSScIKm4z+kurwaEanLBg7vjRLsp/ShmIzaxlw2Cz+UC 1t9gsLQu62wU/gy+oNLP+l1YvozRRhbCcPy8c+31aJcXMVWzaqaYvxfZQtHhWoPx oRN34TXeDx+EuK3OlQQaP++mlWlp5ccb1hCq76vNIuJL9xw3VRCjqdoVJM+aAKx3 p26Xtjql0ZHorYTTXUS3VfwgR5k9TqoimMPnVTfyMmVqUczLJl8enx2U/NbX4KOF PZtwXwa/8ovEr5sf4TZwnMh4aF4lysaKlenRPXXX7umh7A6CsrwxwsunqwQrDCTb k7+EGobNxr4rABEBAAHCwXwEGAEKACYWIQQnYvAcANbd1OC0hIIXNlzH7E/D5gUC aAxktQIbDAUJA8JnAAAKCRAXNlzH7E/D5qP9D/9ivTiOAflRd3JeLW/jzHY3DzVi TmXzeYXQS0GQOMYX3TkHDS+QYDq3B/vHgbWmLKJ4qkMkXcwt65RCcWlmInUaiPkr 36LwMWH8QhO4pO/grjL6czKOMMtJ7jLOvtr4U9j3wzj8l8IsTItom4+kw/abptA0 r1QYM3hFMg4oJe45EtLS+5fUtZvtXRGhJ4Z/PSKkg7ijzG2iNpjzuB5qQlL0nP0b yJlau0nlUH6avCLlzMkdiSDGFMa2ChAYseDYizINFs63vorFw3JRVNYD4UdXdatO ccoHoI2e2E9K4JTjBa2ezBVfwbul00rPqtbi+xdb0OpFdjmBmdh7DQ7kNCfpX33j 7m/x2/rytg+Jvr4F1mTaPokO8iUfVMwZQY7IvV07Z5aYrnPyjasUqWlniXsHkS/Q +itkX3DNYIt/JCid9DUFWYPb90fl3QHemTJbrWK5AZ3dXN5PZLZ68FtnCYptloeK 3HjBSFlKRzLIjotm4TXs+UeuLKR5O455Cky/saR4XdpekMCjB8oFtOIbUwNl7NWc GXAEVVJMZjG5JyQAIKZQIoN9FhuqwMJrqsGb5nfqLXaCd56D84E2VJI1fn5Fw0Qt 2uLNNXxnNty9/Nw/ZhyfXsG+uRYYHpqhy2jqBIdxJV/BOtLgXgYNnIA0UyEIBVOC X9Y1PjUH70QkqLgthA==
    =MmQ0
    -----END PGP PUBLIC KEY BLOCK-----

    --------------9rQ20D5Huw3Rkf19vVjQpw2A--

    --------------YtDdjpi1WeodAgJ3m0SEH9U2--

    -----BEGIN PGP SIGNATURE-----

    wsF5BAABCAAjFiEEJ2LwHADW3dTgtISCFzZcx+xPw+YFAmgtL3EFAwAAAAAACgkQFzZcx+xPw+Yy NxAAoMIqzNTDXazJa6bAWo369W1dsmhQn84/jxtLMHjkISrLhY4gmgEQlmQ+0x9S3+0SVKWe5Z3/ N1QhTYaHJefe4cWz11Qs9VD3sExvkOVFNg+SCUowj5He0fQ854QrPII/8AkMGmmOL1P6LAoCgozi TAaZaa9KZWDBQCo1Ivfx1WUvHxW4B8XyBFb51s+SjRZx/3NxVoZRv/e4E1prZZADwUQY9L6y0Ju1 Mwa2ANlX/3OvXTd0tEclEQW5DMm6ut2b2SPss1VSML23Y6QoA4UEaT9BUXNJ1gm6EHc1W6NuPLUn FP9lY3x8BuA4KLZMoiGBVkm+NF+stMBBi7XqNVmdLoYTbLAfeTSix5I2YlYA7LAKAuaLQks7Zf4y fTcH2De0jYHQPtmgSbZbaAOumK8lWXmcagHrn75K+HOzHw5RXloDX6knAv3P5l3QxEmgdxLZjCM5 4LWMzp0s0JQSVH3lyAGH/cbRJBzZcdPBDDR3bagRY6FvVQrOhIPjNNlxq8So3NxqyO3KUxO4zRJb CSDBv1aJ2vCaJFpJWv05rCniclXILrXguO4XQoThwaMBU2tPPLkOvIG1wgvuntHs7S/BF302p4Yv ZohbngnpVopGkQQEumXXBoJlJoy/XLvnPDivRyqUXujtvT5jzg0B6R50zN6eIWuVYx1lxEs8uHcG 5GE=
    =qvqp
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From David Christensen@21:1/5 to Steve Matzura on Wed May 21 06:50:01 2025
    On 5/20/25 15:20, Steve Matzura wrote:
    After a year in storage, I'm trying to get a version 11 system back
    online. I connected it to power and network, then booted it.
    Interestingly, it appeared on my network not at the address it had when
    it went into storage, but one given it by my local DHCP server. The
    console scrolled, but not to completion, Speakup didn't start, and I
    cannot log in from the console. I have a couple applications on that
    system, including Asterisk version 20 with its configuration files, but
    the system is unusable as it stands. The questions are, repair Debian 11
    or or replace with Debian 12, and how do i reclaim those all-important configuration files from Asterisk and other applications? Can I try
    mounting the boot drive in WSL on another machine, or possibly inspect
    it with a running Debian system booted from the installation medium?


    Thanks in advance.


    I suggest:

    1, Remove the drive from the computer. Install drive into a working
    Debian computer. Take an image (e.g. dd(1) or Clonezilla). Mount
    filesystems read-only and backup. Shutdown. Remove old drive.

    2. Disconnect the power supply (PSU) from everything in the computer.
    Test the PSU with a hardware tester. If the PSU fails, replace it and
    repeat. Shutdown.

    3. Run the motherboard firmware Setup utility hardware diagnostic, if
    your motherboard has such. If your motherboard does not, boot and run memtest86+. If anything fails, fix or replace and repeat. Shutdown.

    4. Install a security erased SSD into the computer and connect it to
    the first HBA port. Do a fresh install of Debian *11* to minimize risk
    of configuration file version changes for OS and for software. Take an
    image. Backup all filesystems. Shutdown.

    5. Install the old drive into the computer. Mount the old drive
    filesystems read-only. Install desired software. Configure software by referring to contents of old filesystems. Shutdown. Remove old drive.
    Take an image. Backup all filesystems.


    David

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)