On 24/10/2019 12:43, Chris Elvidge wrote:
> On 22/10/2019 16:12, Mike Scott wrote:
>> Hi all, I'm stumped with this one.
.....
>> The system tries to start up off sda3, and gets as far as running
>> /sbin/init. But then it complains about various library files not
>> loading, starting with:
>>
>> ERROR: ld.so object
>> '/usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so' from
>> /etc/ld.so.preload cannot be preloaded (cannot open shared object
>> file): ignored
>>
>> (I had to video the console to get that :-)
>>
>> followed by a kernel panic.
>>
>> I know the libarmmem*.so files are there, as it still boots off the SD
>> card when I restore the original cmdline/fstab files.
>>
>> AFAICS what I've done reflects various how-to's off the web. But
>> something's amiss, clearly. Any help would be appreciated, thanks.
>>
>>
>>
>
> On mine (Raspbian Buster 9.11) /etc/ld.so.preload only contains the line:
>
> # cat /etc/ld.so.preload
> /usr/lib/arm-linux-gnueabihf/libarmmem.so

I think I may be getting closer to the issue. Sorry if this is longish;
work in progress.

The spare disk I mentioned is actually half-free, partitioned into two
500Gb chunks, one free. So I stuck it in in my desktop machine,
converted the spare partition to ext4, and used rsync -ax on it, and
tweaked the fstab and cmdline.txt to match. Stuck it in the PI, and
bingo, it boots happily.

But I don't like an all-in-one partition, so, I started over (on the
dekstop box), and repartitioned for a fresh root, var, usr, and so on. I
mounted the new root, and created mount points, and mounted those
partitions. Then again used rsync -ax  , edited
the fstab in the new etc (using device names), and updated the SD card's
cmdline.txt.

I stuck the SD card and disk onto the PI -- kernel panic.

Hmmm. Should have worked.

OK, back to the desktop box. This time, I rsync into place the entire SD
card into the new root partition (which was large enough). Restore my
fstab to mount the other partitions on top of the (unwanted)
directories. This really ought to behave the same as the last failed
effort, but no: this time it boots.

Conjecture (for now) - ld.so.preload moaned about missing files from
/usr/lib. But these aren't available until /usr is mounted, which I
presume must happen /after/ the preload stuff. Maybe I'll go back to the
original setup and put these files into the root partition, so they're
present before /usr is mounted. Bet it works then :-}

(Oh, and thanks again to all who've commented. It's useful to see
another POV and keeps the thoughts flowing.)

--
Mike Scott
Harlow, England

--- SoupGate-Win32 v1.05