You are not logged in.
Doing my ordinary daily apt update just now and - although no updates available - got the first-time-ever message:
N: Repository 'http://deb.devuan.org/merged chimaera-security InRelease' changed its 'Suite' value from 'stable-security' to 'oldstable-security'
Devuan.org Home page still says:
Devuan Releases
Chimaera 4.0 is the current stable release.
Beowulf 3.1 point release has moved to oldstable status.
Hopefully this will get you a little closer; I'm running Chimaera myself:
$ apt search udhcpc
Sorting... Done
Full Text Search... Done
busybox/stable,now 1:1.30.1-6+b3 amd64 [installed,automatic]
Tiny utilities for small and embedded systems
udhcpc/stable 1:1.30.1-6+b3 amd64
Provides the busybox DHCP client implementation
$ apt-cache policy udhcpc
udhcpc:
Installed: (none)
Candidate: 1:1.30.1-6+b3
Version table:
1:1.30.1-6+b3 500
500 http://deb.devuan.org/merged chimaera/main amd64 PackagesAs soon as I can find out how to discover it, I'll tell you a location for the .deb.
HTH
I'm waiting for the "official" Daedalus release. Thanks for the info.
From memory, that is the error message that I received shortly before posting this msg.
Steps to get to that point:
Click an internal bookmark for the Forum Index
(internal to my own browser-setup, which is to say not directly connected with Dev1)
I refreshed the page & after a short delay got re-directed to the normal index listing (and forgot to copy the error before doing so).
Extra: Clicking any forum section- or post-link seems to have a delay before completion for the past day or so.
xfce4 has it's own 'startx': /usr/bin/startxfce4. Here is the head (options at bottom):
$ head -50 /usr/bin/startxfce4
#!/bin/sh
#
# xfce4
#
# Copyright (C) 1996-2003 Olivier Fourdan (fourdan@xfce.org)
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
#
if test "x$*" != "x"
then
OPTS=""
for OPT in $*
do
if test "x$OPT" = "x--help"
then
# print help and exit
echo "Usage:"
echo " startxfce4 [OPTIONS...]"
echo
echo "Options:"
echo " --help Show help options"
echo " --with-ck-launch Start xfce4-session inside a"
echo " ConsoleKit session"
echo
exit 0
elif test "x$OPT" = "x--with-ck-launch"
then
# try to launch xfce4-session with ck-launch-session in xinitrc
XFCE4_SESSION_WITH_CK="1"
export XFCE4_SESSION_WITH_CK
else
# append
OPTS="$OPTS $OPT"
fi
donePerhaps try that?
Lord, but these threads are full of noise. Please stop it.
Most applications people would want/need in WINE are 32-bit.
Agree. Which is why WINE is (IMO) deprecated for modern Linux, which almost entirely is powered by 64-bit cpus.
This thread is about Daedalus, not Chimaera.
I'm actually reasonably capable of reading the thread title. However, if I can pass over that & like an idiot try to implement it in Chimaera (for the second time), so can others. Hence my post to try to help others not do that.
This has been written about a number of times. Do not attempt to mix the architectures for WINE. Cannot work (been there, done that).
Hello. Check your source list. It should look like this
deb http://deb.devuan.org/merged daedalus main non-free-firmware contrib non-free
Adding 'non-free-firmware' gives continuous errors in Chimaera:
All packages are up to date.
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://deb.devuan.org/merged chimaera InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en_GB' as repository 'http://deb.devuan.org/merged chimaera InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://deb.devuan.org/merged chimaera InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://deb.devuan.org/merged chimaera-security InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en_GB' as repository 'http://deb.devuan.org/merged chimaera-security InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://deb.devuan.org/merged chimaera-security InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://deb.devuan.org/merged chimaera-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://deb.devuan.org/merged chimaera-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en_GB' as repository 'http://deb.devuan.org/merged chimaera-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://deb.devuan.org/merged chimaera-proposed-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en_GB' as repository 'http://deb.devuan.org/merged chimaera-proposed-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://deb.devuan.org/merged chimaera-proposed-updates InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/binary-amd64/Packages' as repository 'http://deb.devuan.org/merged chimaera-backports InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en_GB' as repository 'http://deb.devuan.org/merged chimaera-backports InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'non-free-firmware/i18n/Translation-en' as repository 'http://deb.devuan.org/merged chimaera-backports InRelease' doesn't have the component 'non-free-firmware' (component misspelt in sources.list?)$
$ cat /etc/apt/sources.list
# 2023-02-01 added non-free-firmware; see https://dev1galaxy.org/viewtopic.php?pid=40751
# 2023-02-01 above removed as not active in Chimaera
deb http://deb.devuan.org/merged/ chimaera main contrib non-free
deb http://deb.devuan.org/merged/ chimaera-security main contrib non-free
deb http://deb.devuan.org/merged/ chimaera-updates main contrib non-free
# changed next line following https://dev1galaxy.org/viewtopic.php?pid=38033#p38033
# deb http://deb.devuan.org/devuan/ chimaera-proposed-updates contrib non-free main
deb http://deb.devuan.org/merged/ chimaera-proposed-updates main contrib non-free
deb http://deb.devuan.org/merged/ chimaera-backports main contrib non-freeGah!
I blame forgetfulness (aka old age):
$ ps aux | grep cron
root 1516 0.0 0.0 8684 3460 ? Ss Jul01 0:01 /usr/sbin/cron
alexk 8432 0.0 0.0 6372 712 pts/0 S+ 14:52 0:00 grep --color=auto cronit's look like that we see the grep process ! not the crond !? Am I right?
Correct (I got the exact same result). Cron is NOT running in your system (you have grepped for 'crond', and therefore in the ps listing it shows the full command-line, which includes 'crond'). If Cron *was* running there would be at least 2 ps lines containing 'crond', one for the daemon & one for grep.
Synaptic 0.90.2
Tried just now, no problems (no update neither, because I update daily using a self-written script).
$ uname -a
Linux ng3 6.1.0-0.deb11.7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-2~bpo11+1 (2023-04-23) x86_64 GNU/Linux
$ cat /etc/os-release
PRETTY_NAME="Devuan GNU/Linux 4 (chimaera)"
NAME="Devuan GNU/Linux"
VERSION_ID="4"
VERSION="4 (chimaera)"
VERSION_CODENAME="chimaera"
ID=devuan
ID_LIKE=debian
HOME_URL="https://www.devuan.org/"
SUPPORT_URL="https://devuan.org/os/community"
BUG_REPORT_URL="https://bugs.devuan.org/"$ apt search gtk | fgrep -i installed
# …
gir1.2-ayatanaappindicator3-0.1/stable,now 0.5.5-2+deb11u2 amd64 [installed,automatic]
gir1.2-gtk-3.0/stable,now 3.24.24-4+deb11u3 amd64 [installed,automatic]
gir1.2-gtksource-3.0/stable,now 3.24.11-2 amd64 [installed,automatic]
gir1.2-gtksource-4/stable,now 4.8.0-1 amd64 [installed,automatic]
gir1.2-javascriptcoregtk-4.0/stable-security,stable-proposed-updates,now 2.40.2-1~deb11u1 amd64 [installed]
gir1.2-keybinder-3.0/stable,now 0.3.2-1.1 amd64 [installed,automatic]
gir1.2-pango-1.0/stable,now 1.46.2-3 amd64 [installed,automatic]
gir1.2-soup-2.4/stable,now 2.72.0-2 amd64 [installed,automatic]
gir1.2-webkit2-4.0/stable-security,stable-proposed-updates,now 2.40.2-1~deb11u1 amd64 [installed]
gksu/now 2.0.2-9+b1 amd64 [installed,local]
gpick/stable,now 0.2.6-1 amd64 [installed]
spell-checking library for GTK+ applications - installed tests
gstreamer1.0-gtk3/stable-security,stable-proposed-updates,now 1.18.4-2+deb11u2 amd64 [installed,automatic]
gtk-update-icon-cache/stable,now 3.24.24-4+deb11u3 amd64 [installed,automatic]
gtk2-engines/stable,now 1:2.20.2-5 amd64 [installed,automatic]
gtk3-engines-xfce/now 3.2.0-4 amd64 [installed,local]
gtk3-nooverlayscrollbar/stable,now 7.0.1-5 all [installed,automatic]
# …I got a bunch of Bind updates today:
$ tail /var/log/apt/history.log
Commandline: apt upgrade
Requested-By: alexk (1000)
Upgrade: josm-latest:amd64 (1.5.svn18763, 1.5.svn18765), libx11-xcb1:amd64 (2:1.7.2-1, 2:1.7.2-1+deb11u1), libx11-data:amd64 (2:1.7.2-1, 2:1.7.2-1+deb11u1), libx11-dev:amd64 (2:1.7.2-1, 2:1.7.2-1+deb11u1), libx11-doc:amd64 (2:1.7.2-1, 2:1.7.2-1+deb11u1), libx11-6:amd64 (2:1.7.2-1, 2:1.7.2-1+deb11u1)
End-Date: 2023-06-21 10:57:12
Start-Date: 2023-06-26 15:49:36
Commandline: apt upgrade
Requested-By: alexk (1000)
Upgrade: josm-latest:amd64 (1.5.svn18765, 1.5.svn18770), bind9-host:amd64 (1:9.16.37-1~deb11u1, 1:9.16.42-1~deb11u1), bind9-dnsutils:amd64 (1:9.16.37-1~deb11u1, 1:9.16.42-1~deb11u1), bind9-libs:amd64 (1:9.16.37-1~deb11u1, 1:9.16.42-1~deb11u1), dnsutils:amd64 (1:9.16.37-1~deb11u1, 1:9.16.42-1~deb11u1)
End-Date: 2023-06-26 15:50:44Thanks for the use of 'neofetch' - works nicely on my Chimaera system, yet I never knew it existed:
$ apt search neofetch
Sorting... Done
Full Text Search... Done
neofetch/stable,now 7.1.0-2 all [installed]
Shows Linux System Information with Distribution Logoalexk@ng3:~$ neofetch
..,,;;;::;,.. alexk@ng3
`':ddd;:,. ---------
`'dPPd:,. OS: Devuan GNU/Linux 4 (chimaera) x86_64
`:b$$b`. Model: 90BJ008CUK Lenovo H30-05
'P$$$d` Kernel: 6.1.0-0.deb11.7-amd64
.$$$$$` Uptime: 1 day, 11 hours, 58 mins
;$$$$$P Packages: 2724 (dpkg)
.:P$$$$$$` Shell: bash 5.1.4
.,:b$$$$$$$;' Resolution: 1366x768
.,:dP$$$$$$$$b:' DE: Xfce 4.16
.,:;db$$$$$$$$$$Pd'` WM: Xfwm4
,db$$$$$$$$$$$$$$b:'` WM Theme: Default
:$$$$$$$$$$$$b:'` Theme: Clearlooks-Phenix-Deepsea [GTK2], Adw
`$$$$$bd:''` Icons: oxygen [GTK2], Adwaita [GTK3]
`'''` Terminal: xfce4-terminal
Terminal Font: Monospace 12
CPU: AMD A8-7410 APU with AMD Radeon R5 Grap
GPU: AMD ATI Radeon R4/R5 Graphics
Memory: 1770MiB / 7356MiBPS
I see the colours in the terminal, but cannot display them as background in BBCode. Here they are as text (does not work within code tags):
>EEE8D5DC322F859900B58900268BD2D336822AA198073642<
>FDF6E3CB4B1693A1A1839496657B836C71C4586E75002B36<
Devuan only forks a few hundered packages.
Love the "only"; yikes!
OK, dd has finally finished & I can get a first look at both images.
(Life with this desktop is not as easy at this moment as it should be: the 1TB hdd is 97% full, which means that there is some serious clear-out to be done, and as I work HandBreak is ripping an ancient Blu-ray to disc which means 100% on the CPU, 6 hours to rip it, 2% swap, and as soon as swap initiates I notice that the performance of the whole system falls through the floor.)
part1.img seems to be composed entirely of null-bytes:
:~/TMP$ hexdump -C part1.img | head
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
01000000part2.img is NOT an exFAT fs:
$ mdir -i part2.img -a
Unknown media type f5
$ hexdump -C part2.img | head
00000000 98 56 46 c4 a3 02 69 13 da 93 4f 6a fc 9b 87 72 |.VF...i...Oj...r|
00000010 0e 17 d8 67 56 d6 1f 53 1b 0f f4 b7 cd 4d c4 c1 |...gV..S.....M..|
00000020 75 27 9c a0 10 c7 43 3a a5 be 2a 08 63 5d 51 48 |u'....C:..*.c]QH|
00000030 24 37 00 54 38 66 ca 64 4f 9a 61 e7 e3 8c 63 9c |$7.T8f.dO.a...c.|
00000040 9b ca 08 17 86 78 f4 61 07 ae 54 9f ce da 2e 66 |.....x.a..T....f|
00000050 89 fe dd 59 27 fb c8 ad d4 11 1f 8d 31 3c 17 a7 |...Y'.......1<..|
00000060 1b bb 51 b8 74 8a b8 21 9f ec cc f4 32 74 2b 9a |..Q.t..!....2t+.|
00000070 c8 e1 e4 4d 16 e3 dd 88 6e e0 63 c7 3e 48 7c f9 |...M....n.c.>H|.|
00000080 db ce 24 6f 97 5a b9 62 8b 2e e4 e3 2a dd 95 c2 |..$o.Z.b....*...|
00000090 24 1d 8e a0 a2 15 f7 51 d9 4e 38 2f 92 a4 5c 17 |$......Q.N8/..\.|A little extra:
Checking the disk-image ‘sdc64gb.img’ that I took using dd at 02:59 this morning shows the reason that testdisk reports it as an EFI partition (look at 00000200):–
$ la
total 62367844
-rw-r--r-- 1 alexk alexk 63864569856 Jun 11 02:59 sdc64gb.img
alexk@ng3:~/TMP$ hexdump -C sdc64gb.img | less
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001c0 02 00 ee ff ff ff 01 00 00 00 ff 4f 6f 07 00 00 |...........Oo...|
000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200 45 46 49 20 50 41 52 54 00 00 01 00 5c 00 00 00 |EFI PART....\...|
00000210 cb cc 43 cd 00 00 00 00 01 00 00 00 00 00 00 00 |..C.............|
00000220 ff 4f 6f 07 00 00 00 00 22 00 00 00 00 00 00 00 |.Oo.....".......|
00000230 de 4f 6f 07 00 00 00 00 82 13 4b 1d 39 c6 3d 44 |.Oo.......K.9.=D|
00000240 9d 04 e4 c1 d8 ad b9 0b 02 00 00 00 00 00 00 00 |................|
00000250 80 00 00 00 80 00 00 00 98 a4 38 f4 00 00 00 00 |..........8.....|
00000260 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000400 a2 10 a7 19 ca b3 e4 11 b0 26 10 60 4b 88 9d cf |.........&.`K...|
00000410 fb c6 93 19 db 24 c6 4f 94 52 35 21 39 17 8b d0 |.....$.O.R5!9...|
00000420 00 08 00 00 00 00 00 00 ff 87 00 00 00 00 00 00 |................|
00000430 00 00 00 00 00 00 00 00 61 00 6e 00 64 00 72 00 |........a.n.d.r.|
00000440 6f 00 69 00 64 00 5f 00 6d 00 65 00 74 00 61 00 |o.i.d._.m.e.t.a.|
00000450 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000480 a4 1e 3d 19 ca b3 e4 11 b0 75 10 60 4b 88 9d cf |..=......u.`K...|
00000490 6a 46 de cf 74 a0 c9 7a 0a 48 a7 66 19 2a d9 4a |jF..t..z.H.f.*.J|
000004a0 00 88 00 00 00 00 00 00 de 4f 6f 07 00 00 00 00 |.........Oo.....|
000004b0 00 00 00 00 00 00 00 00 61 00 6e 00 64 00 72 00 |........a.n.d.r.|
000004c0 6f 00 69 00 64 00 5f 00 65 00 78 00 70 00 61 00 |o.i.d._.e.x.p.a.|
000004d0 6e 00 64 00 00 00 00 00 00 00 00 00 00 00 00 00 |n.d.............|
000004e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|It's a damn shame that it could not detect the fstype.
Now tried selecting FAT32 for both partitions, leading to this screen:
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
Disk /dev/sdc - 63 GB / 59 GiB - CHS 60906 64 32
Partition Start End Size in sectors
P EFI System 2048 34815 32768
>P EFI System 34816 124735454 124700639
Structure: Ok. Use Up/Down Arrow keys to select partition.
Use Left/Right Arrow keys to CHANGE partition characteristics:
P=Primary D=Deleted
Keys A: add partition, L: load backup, T: change type, P: list files,
Enter: to continue
63 GB / 59 GiB… but no joy. Choosing P to list files gave the following screen:–
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
P EFI System 2048 34815 32768
Directory /
No file found, filesystem may be damaged.
Use Right to change directory, h to hide deleted files
q to quit, : to select the current file, a to select all files
C to copy the selected files, c to copy the current fileI'm going to leave this now. testdisk cannot find the fstype, and there are too many options to try to guess.
This post is about using testdisk
When launched all by itself, testdisk launches into it’s own text-window with highlit-options to choose from. We select Create:–
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
TestDisk is free data recovery software designed to help recover lost
partitions and/or make non-booting disks bootable again when these symptoms
are caused by faulty software, certain types of viruses or human error.
It can also be used to repair some filesystem errors.
Information gathered during TestDisk use can be recorded for later
review. If you choose to create the text file, testdisk.log , it
will contain TestDisk options, technical information and various
outputs; including any folder/file names TestDisk was used to find and
list onscreen.
Use arrow keys to select, then press Enter key:
>[ Create ] Create a new log file
[ Append ] Append information to log file
[ No Log ] Don't record anythingNow /dev/sdc is chosen …
!!! REMEMBER !!! This is running as root. This is the perfect opportunity to shaft a working system. Be very careful!
:–
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
TestDisk is free software, and
comes with ABSOLUTELY NO WARRANTY.
Select a media (use Arrow keys, then press Enter):
Disk /dev/sda - 1000 GB / 931 GiB - WDC WD10EZEX-08Y20A0
>Disk /dev/sdc - 63 GB / 59 GiB - Generic- SD/MMC
>[Proceed ] [ Quit ]
Note: Disk capacity must be correctly detected for a successful recovery.
If a disk listed above has an incorrect size, check HD jumper settings and BIOS
detection, and install the latest OS patches and disk drivers.Now to select the partition (fingers crossed):–
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
Disk /dev/sdc - 63 GB / 59 GiB - Generic- SD/MMC
Please select the partition table type, press Enter when done.
[Intel ] Intel/PC partition
>[EFI GPT] EFI GPT partition map (Mac i386, some x86_64...)
[Humax ] Humax partition table
[Mac ] Apple partition map (legacy)
[None ] Non partitioned media
[Sun ] Sun Solaris partition
[XBox ] XBox partition
[Return ] Return to disk selection
Hint: EFI GPT partition table type has been detected.
Note: Do NOT select 'None' for media with only a single partition. It's very
rare for a disk to be 'Non-partitioned'.Now Analyse to try to check stuff
([ Advanced ] Filesystem Utils is used to undelete files, and is *very* effective) (no use here since files cannot be detected):–
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
Disk /dev/sdc - 63 GB / 59 GiB - Generic- SD/MMC
CHS 60906 64 32 - sector size=512
>[ Analyse ] Analyse current partition structure and search for lost partitions
[ Advanced ] Filesystem Utils
[ Geometry ] Change disk geometry
[ Options ] Modify options
[ Quit ] Return to disk selection
Note: Correct disk geometry is required for a successful recovery. 'Analyse'
process may give some warnings if it thinks the logical geometry is mismatched.Choose default option (this takes a heck of a long while as it ploughs through every cylinder) (~1hr for 64G disk):–
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
Disk /dev/sdc - 63 GB / 59 GiB - CHS 60906 64 32
Current partition structure:
Partition Start End Size in sectors
1 P Unknown 2048 34815 32768 [android_meta]
2 P Unknown 34816 124735454 124700639 [android_expand]
P=Primary D=Deleted
>[Quick Search] [ Backup ]
Try to locate partitionAfter ~1 hour the next screen is shown:–
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
Disk /dev/sdc - 63 GB / 59 GiB - CHS 60906 64 32
Partition Start End Size in sectors
Keys A: add partition, L: load backup, Enter: to continuePressing 'A' then gives this next screen (this is NOT what a successful fix looks like):–
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
Disk /dev/sdc - 63 GB / 59 GiB - CHS 60906 64 32
Unknown 1 124735487 124735487
>[Sector] [Sector] [ Type ] [ Done ]
Change starting sectorI entered two partitions using the former values, each with a fstype of EFI/ext2, but then trying to view files gave a "must be damaged" result. Entering a fstype EFI/unknown gave the following (no files can be viewed):–
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
Disk /dev/sdc - 63 GB / 59 GiB - CHS 60906 64 32
Partition Start End Size in sectors
P EFI System 2048 34815 32768
>P EFI System 34816 124735454 124700639
Structure: Ok. Use Up/Down Arrow keys to select partition.
Use Left/Right Arrow keys to CHANGE partition characteristics:
P=Primary D=Deleted
Keys A: add partition, L: load backup, T: change type,
Enter: to continue
63 GB / 59 GiBPressing Enter now gave:
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
Disk /dev/sdc - 63 GB / 59 GiB - CHS 60906 64 32
Partition Start End Size in sectors
1 P EFI System 2048 34815 32768
2 P EFI System 34816 124735454 124700639
[ Quit ] >[ Return ] [ Write ]
Return to partition selectionChoosing Write gave:
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
Write partition table, confirm ? (Y/N)Ah well, the disk is toast anyway, so I said 'Y':
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
You will have to reboot for the change to take effect.
>[Ok]Chose Quit
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
Disk /dev/sdc - 63 GB / 59 GiB - Generic- SD/MMC
CHS 60906 64 32 - sector size=512
[ Analyse ] Analyse current partition structure and search for lost partitions
[ Advanced ] Filesystem Utils
[ Geometry ] Change disk geometry
[ Options ] Modify options
>[ Quit ] Return to disk selection
Note: Correct disk geometry is required for a successful recovery. 'Analyse'
process may give some warnings if it thinks the logical geometry is mismatched.and Quit:
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
TestDisk is free software, and
comes with ABSOLUTELY NO WARRANTY.
Select a media (use Arrow keys, then press Enter):
Disk /dev/sda - 1000 GB / 931 GiB - WDC WD10EZEX-08Y20A0
>Disk /dev/sdc - 63 GB / 59 GiB - Generic- SD/MMC
[Proceed ] >[ Quit ]
Quit program
Note: Disk capacity must be correctly detected for a successful recovery.
If a disk listed above has an incorrect size, check HD jumper settings and BIOS
detection, and install the latest OS patches and disk drivers.Hi Ralph.
Yup, did that before starting! It is a 59.5 GiB file called "sdc64gb.img". It is also worth pointing out that testdisk can also save an image of the partition(s) to disk before trying to rewrite.
partitions might be FAT32 (or vfat?) with an ext2 (or perhaps ext4) within
I'm spending yet another hour analysing the wretched cylinders to try that one. I previously set the fstype to 'ext2' & tried to view files & it said "none … damaged".
I'm pretty sure that I'm going to have to let the A52 reformat it & forget any existing files. I've got a very old backup on disk, but that is all.
This is a report on my attempts to recover info from a sd-card before I re-format it. Here is how the story begins:
A 64GB SD-Card was used within a SmartPrime7 (VFD-600) Android-6 mobile phone
June 08: The (non-replaceable) battery in that SmartPrime7 died
June 09: A Blackview A52 Android-12 mobile phone was obtained as a replacement
June 10: Vodaphone transferred both SIMM + SD-Card to the A52 for me
The A52 Contact list was easily populated from the SIMM during setup
The A52 wanted to re-format the SD-Card; could any data be extracted first?
The Card was plugged into a SD/MMC cardreader and then into a USB socket in my Desktop computer running Chimaera 4
The reader LED lit-up, but it did not auto-mount. I now entered into a blizzard of DDG-searches to discover how-to mount these partitions (and why they did not auto-mount).
Consulting man mount, the process at it’s simplest is the command “sudo mount device mountpoint”, where:–
‘sudo’ == in most cases this admin command must be performed as root
‘mount’ == the Devuan command to mount the device
‘device’ == the name given by Devuan to the physical device that contains a filesystem (fs)
‘mountpoint’ == a directory that pre-exists within the existing Devuan fs
There are 3 wrinkles to this command in this case:–
It usually is able to auto-detect the fs type (but not here), so a `-t fstype` will be required
‘device’ can often change on restart, meaning that a `-L Label` or `-U UUID` would be required if repetitively loaded
Any existing files within ‘mountpoint’ will no longer be accessible when a device is mounted there.
dmesg is normally the first port of call if it has just been inserted/attached, and fdisk is next, with two levels of detail available (both below). Neither helps, and an attempt at mount simply underlines the error. The fs can be found using fsck -N (no-action, and it simply reports the fs). That is fsck.ext2 which means that the fs is ‘ext2’. We try a mount with that & it fails. So, try to find alternate superblocks with mke2fs -n /dev/sdc1, and try to use an alternate superblock to fix the fs, but nothing works (the disk is in the toilet).
We need to try more desperate measures, and turn to testdisk (available from the standard distribution) (see next post).
$ sudo dmesg | tail
[ 832.195604] scsi host3: usb-storage 1-1.3:1.0
[ 833.219061] scsi 3:0:0:0: Direct-Access Generic- SD/MMC 1.00 PQ: 0 ANSI: 0 CCS
[ 833.219877] sd 3:0:0:0: Attached scsi generic sg3 type 0
[ 834.000163] sd 3:0:0:0: [sdc] 124735488 512-byte logical blocks: (63.9 GB/59.5 GiB)
[ 834.001152] sd 3:0:0:0: [sdc] Write Protect is off
[ 834.001164] sd 3:0:0:0: [sdc] Mode Sense: 03 00 00 00
[ 834.002150] sd 3:0:0:0: [sdc] No Caching mode page found
[ 834.002160] sd 3:0:0:0: [sdc] Assuming drive cache: write through
[ 834.020198] sdc: sdc1 sdc2
[ 834.020700] sd 3:0:0:0: [sdc] Attached SCSI removable disk$ sudo fdisk -l
[sudo] password for alexk:
…
Disk /dev/sdc: 59.48 GiB, 63864569856 bytes, 124735488 sectors
Disk model: SD/MMC
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 1D4B1382-C639-443D-9D04-E4C1D8ADB90B
Device Start End Sectors Size Type
/dev/sdc1 2048 34815 32768 16M unknown
/dev/sdc2 34816 124735454 124700639 59.5G unknown$ sudo fdisk -x
…
Disk /dev/sdc: 59.48 GiB, 63864569856 bytes, 124735488 sectors
Disk model: SD/MMC
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 1D4B1382-C639-443D-9D04-E4C1D8ADB90B
First LBA: 34
Last LBA: 124735454
Alternative LBA: 124735487
Partition entries LBA: 2
Allocated partition entries: 128
Device Start End Sectors Type-UUID UUID Name Attrs
/dev/sdc1 2048 34815 32768 19A710A2-B3CA-11E4-B026-10604B889DCF 1993C6FB-24DB-4FC6-9452-352139178BD0 android_meta
/dev/sdc2 34816 124735454 124700639 193D1EA4-B3CA-11E4-B075-10604B889DCF CFDE466A-A074-7AC9-0A48-A766192AD94A android_expand$ sudo fsck -N /dev/sdc1
fsck from util-linux 2.36.1
[/sbin/fsck.ext2 (1) -- /dev/sdc1] fsck.ext2 /dev/sdc1
$ sudo fsck -N /dev/sdc2
fsck from util-linux 2.36.1
[/sbin/fsck.ext2 (1) -- /dev/sdc2] fsck.ext2 /dev/sdc2$ mkdir -p ~/TMP/SDC1
$ mkdir -p ~/TMP/SDC2
$ sudo mount /dev/sdc1 ~/TMP/SDC1
[sudo] password for alexk:
mount: /home/alexk/TMP/SDC1: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.
$ sudo mount -t ext2 /dev/sdc1 ~/TMP/SDC1
mount: /home/alexk/TMP/SDC1: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.$ sudo fsck.ext2 /dev/sdc1 -v
e2fsck 1.46.2 (28-Feb-2021)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdc1
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>$ sudo mke2fs -n /dev/sdc1
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 16384 1k blocks and 4096 inodes
Filesystem UUID: 4fce5c0e-d330-4406-b7bf-3935e5161dac
Superblock backups stored on blocks:
8193
$ sudo e2fsck -b 8193 /dev/sdc1
e2fsck 1.46.2 (28-Feb-2021)
e2fsck: Invalid argument while trying to open /dev/sdc1
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>$ sudo e2fsck -b 32768 /dev/sdc1
e2fsck 1.46.2 (28-Feb-2021)
e2fsck: Invalid argument while trying to open /dev/sdc1
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>cd ~/TMP
$ sudo testdisk /list
[sudo] password for alexk:
TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
Please wait...
Disk /dev/sda - 1000 GB / 931 GiB - CHS 121601 255 63
Sector size:512
Model: WDC WD10EZEX-08Y20A0, S/N:WD-WCC3F1TLE7XN, FW:02.01A02
Disk /dev/sdc - 63 GB / 59 GiB - CHS 60906 64 32
Sector size:512
Model: Generic- SD/MMC, FW:1.00
Disk /dev/sda - 1000 GB / 931 GiB - CHS 121601 255 63
Partition Start End Size in sectors
1 P EFI System 2048 1050623 1048576
2 P Linux filesys. data 1050624 1937960959 1936910336
3 P Linux Swap 1937960960 1953523711 15562752
Disk /dev/sdc - 63 GB / 59 GiB - CHS 60906 64 32
Partition Start End Size in sectors
1 P Unknown 2048 34815 32768 [android_meta]
2 P Unknown 34816 124735454 124700639 [android_expand]The next post will run through how-to use testdisk (and I hope that it works).
There is now a chromium-l10n update & this one is SOLVED.
/.local/sbin/update
Hit:1 http://deb.devuan.org/merged chimaera InRelease
Hit:2 http://deb.devuan.org/merged chimaera-security InRelease
Hit:3 http://deb.devuan.org/merged chimaera-updates InRelease
Hit:4 http://deb.devuan.org/merged chimaera-proposed-updates InRelease
Hit:5 http://deb.devuan.org/merged chimaera-backports InRelease
Hit:6 https://josm.openstreetmap.de/apt alldist InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
5 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
chromium chromium-common chromium-l10n chromium-sandbox josm-latest
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 95.5 MB of archives.
After this operation, 2,050 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://deb.devuan.org/merged chimaera-security/main amd64 chromium-l10n all 114.0.5735.90-2~deb11u1 [6,184 kB]
Get:5 https://josm.openstreetmap.de/apt alldist/universe amd64 josm-latest all 1.5.svn18746 [15.7 MB]
Get:2 http://deb.devuan.org/merged chimaera-security/main amd64 chromium amd64 114.0.5735.90-2~deb11u1 [68.5 MB]
Get:3 http://deb.devuan.org/merged chimaera-security/main amd64 chromium-common amd64 114.0.5735.90-2~deb11u1 [4,970 kB]
Get:4 http://deb.devuan.org/merged chimaera-security/main amd64 chromium-sandbox amd64 114.0.5735.90-2~deb11u1 [134 kB]
Fetched 95.5 MB in 9s (10.1 MB/s)
Reading changelogs... Done
(Reading database ... 201190 files and directories currently installed.)
Preparing to unpack .../chromium-l10n_114.0.5735.90-2~deb11u1_all.deb ...
Unpacking chromium-l10n (114.0.5735.90-2~deb11u1) over (113.0.5672.126-1~deb11u1) ...
Preparing to unpack .../chromium_114.0.5735.90-2~deb11u1_amd64.deb ...
Unpacking chromium (114.0.5735.90-2~deb11u1) over (113.0.5672.126-1~deb11u1) ...
Preparing to unpack .../chromium-common_114.0.5735.90-2~deb11u1_amd64.deb ...
Unpacking chromium-common (114.0.5735.90-2~deb11u1) over (113.0.5672.126-1~deb11u1) ...
Preparing to unpack .../chromium-sandbox_114.0.5735.90-2~deb11u1_amd64.deb ...
Unpacking chromium-sandbox (114.0.5735.90-2~deb11u1) over (113.0.5672.126-1~deb11u1) ...
Preparing to unpack .../josm-latest_1.5.svn18746_all.deb ...
Unpacking josm-latest (1.5.svn18746) over (1.5.svn18744) ...
Setting up chromium-sandbox (114.0.5735.90-2~deb11u1) ...
Setting up chromium-common (114.0.5735.90-2~deb11u1) ...
Setting up chromium (114.0.5735.90-2~deb11u1) ...
Setting up josm-latest (1.5.svn18746) ...
Setting up chromium-l10n (114.0.5735.90-2~deb11u1) ...
Processing triggers for mailcap (3.69) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for shared-mime-info (2.0-1) ...
Processing triggers for menu (2.1.48) ...Hi,
Just use the command as so without packages
Nope (but thanks for trying).
$ sudo apt --fix-broken install
[sudo] password for alexk:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.The page also mentions a bug in the chromium-l10n package, which is about this issue:
https://bugs.debian.org/cgi-bin/bugrepo … ug=1037087
Clearly that is the issue; it is the precise error previously reported by me above. The bug report was made today (I was searching for such a report yesterday but of course, could find nothing
Have you tried the following command?
sudo apt --fix-broken install
Essentially, I got the same as the previous attempts:
$ sudo apt --fix-broken install chromium-l10n chromium-shell chromium-driver chromium chromium-common chromium-sandbox josm-latest
[sudo] password for alexk:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
chromium-l10n is already the newest version (113.0.5672.126-1~deb11u1).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
chromium-l10n : Depends: chromium (< 113.0.5672.126-1~deb11u1.1~) but 114.0.5735.90-2~deb11u1 is to be installed
E: Unable to correct problems, you have held broken packages.im on unstable and its still only at 113?
The latest version (albeit Windows) is 116.0.5812.0 (Sunday, June 4, 2023 Revision: 1152969).