INTL 3:770/1 3:770/3   
   REPLYADDR tnp@invalid.invalid   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  a69b0473   
   REPLY:  b08db69f   
   PID: SoupGate-Win32 v1.05   
   On 01/02/2024 19:38, The Natural Philosopher wrote:   
   > On 01/02/2024 19:21, LucLan wrote:   
   >> On 01.02.2024 21:17, The Natural Philosopher wrote:   
   >>> Bookworm. Pi 4B   
   >>> .....   
   >>> Setting up mesa-vulkan-drivers:arm64 (23.2.1-1~bpo12+rpt3) ...   
   >>> Setting up mesa-vdpau-drivers:arm64 (23.2.1-1~bpo12+rpt3) ...   
   >>> Setting up firmware-atheros (1:20230210-5+rpt3) ...   
   >>> Setting up firmware-misc-nonfree (1:20230210-5+rpt3) ...   
   >>> Setting up linux-libc-dev:arm64 (1:6.1.73-1+rpt1) ...   
   >>> Setting up libkms++0:arm64 (0~git20231115~065257+9ae90ce-1) ...   
   >>> Setting up firmware-brcm80211 (1:20230210-5+rpt3) ...   
   >>> Setting up firmware-realtek (1:20230210-5+rpt3) ...   
   >>> Setting up raspi-firmware (1:1.20231024+ds-1+rpt5) ...   
   >>> Installing new version of config file /etc/default/raspi-firmware ...   
   >>> Installing new version of config file   
   >>> /etc/initramfs/post-update.d/z50-raspi-firmware ...   
   >>> Installing new version of config file   
   >>> /etc/kernel/postinst.d/z50-raspi-firmware ...   
   >>>   
   >>>   
   >>> and here it sits. I cant ssh into it. It's bricked itself AGAIN   
   >>>   
   >>> Last time I power cycled it, when this happened it wouldn't boot at all.   
   >>>   
   >>>   
   >>> I've plugged an HDMI screen and key board into it and it shows the   
   >>> boot sequence and something about a disk drive aborted   
   >>> journal...detected by systemd and apt-get   
   >>>   
   >>> Is there any hope or do I reinstall all over AGAIN.   
   >>>   
   >>> And how to stop it happening again.   
   >>>   
   >>>   
   >>>   
   >> You boot from card or USB?   
   >> I never faced that error. Maybe a hw problem with the card ...   
   >   
   > USB booting.  Two SSDs - one to boot, one for data. Data one is never   
   > used normally - its a test setup for a new NAS and its not in any sort   
   > of use.   
   >   
   > But errors on both  drives are showing up   
   >   
   More errors   
      
   dpkg: error processing package raspi-firmware (--configure):   
     installed raspi-firmware package post-installation script subprocess   
   returned error exit status 1   
   Setting up libglapi-mesa:arm64 (23.2.1-1~bpo12+rpt3) ...   
   dpkg: unrecoverable fatal error, aborting:   
     unable to truncate for updated status of 'libglapi-mesa:arm64':   
   Read-only file system   
   E: Sub-process /usr/bin/dpkg returned an error code (2)   
   W: Operation was interrupted before it could finish   
   W: Problem unlinking the file /var/cache/apt/pkgcache.bin -   
   pkgDPkgPM::Go (30: Read-only file system)   
      
      
   --   
   Socialism is the philosophy of failure, the creed of ignorance and the   
   gospel of envy.   
      
   Its inherent virtue is the equal sharing of misery.   
      
   Winston Churchill   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 128/260 129/305 135/225   
   SEEN-BY: 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1 6 226/17   
   SEEN-BY: 226/30 100 227/114 229/110 112 113 200 206 307 317 400 426   
   SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038   
   SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364   
   SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100   
   SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35   
   PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426