On 12/5/2015 2:13 PM, Patrick J. Timlick wrote: > On Sat, Dec 5, 2015 at 10:24 AM, Richard Owlett <[email protected]> wrote: > >> On 12/5/2015 9:20 AM, Patrick J. Timlick wrote: >>> I think you should add more detail. Show your partition tables, show the >>> commands you used to install, show the messages that indicate the wrong >>> thing happened. >> >> I think you have me moving in a productive {possibly not "*THE* >> right"} direction. >> > You don't want to go in the productive direction?
Maybe I should have said "optimal" instead of "right". > >> "Show your partition tables" lead to reading up on fdisk. >> > put the output of sudo fdisk -l in your query. I'd seen "fdisk", but never used it. > >> I don't know to "show the commands you used to install" as was >> responding to prompts from the installer. > > Write down what the installer ask and what you answered. ????? I had said " ... accepting all defaults except configuring network [none present] and setting clock to UTC." > >> I was hoping that log >> files would give useful info. >> > Look through /var/logs for potential clues, and put them in your query. I did a normal person's install of Squeeze to hard drive. I then looked at /var/log/installer/syslog. It was educational. I also noted it was ~5k lines. Suspect that is one reason installing to flash is very slow. "6.3.8.1. Saving the installation logs" of https://www.debian.org/releases/squeeze/i386/ch06s03.html.en states: "Choosing Save debug logs from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report." I used gparted to to create a 1GB ext2 formatted logical partition (sda6) for it. When I'm in the installer's Ash shell I can't seem to be able to mount in. Tried mkdir /owl mount -t ext2 /dev/sda6 /owl failed. Suspect I'm missing something, but what? > >> >> In answer to my second question of my debian-user post, I >> discovered existence of >> "/var/log/installer/". I had read "Debian GNU/Linux Installation >> Guide" several times in the last couple of years. That's why I >> knew log files existed. Just didn't remember where. >> >> As to "show the messages that indicate the wrong thing happened", >> there were none - i.e. a "silent" failure. The only system was >> inability to boot the newly installed system. >> > put the commands you used to try to unsucessfully boot and the response > from the system. > >> >> I'm now setting out to do a series of installs to *CLEAN* media. >> > > >> That explicitly means use of "dd" with "if=/dev/zero". > > I wouldn't bother with that, but I'm always encouraged to see the > scientific method in use. I could give you decades of experience (hardware and software) of things that should not have mattered, but did. > >> Yess I do >> have hardware dedicated to 'educational' experiments <GRIN> { > >> 50 yrs of component level trouble shooting has taught me to start >> from a known state ;} >> >>> >>> On Sat, Dec 5, 2015 at 6:11 AM, Richard Owlett <[email protected]> >> wrote: >>> >>>> [snip] _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
