Code: Select all
fsck /dev/sda2 -y
Also paste output of terminal commands rather than post pictures. It's more readable.
To use testdisk see https://linuxconfig.org/how-to-recover- ... e-in-linux
Code: Select all
fsck /dev/sda2 -y
I'm not certain whether you wanted me to run fsck on the whole 02TB NVME SSD ... or on partition #1 ... or on the large (1.7TB) partition #5 that containsdeepakdeshp wrote: ⤴Sun May 28, 2023 1:23 pm Run fsck on the 2tb unbootable 2 tb drive.replace sda2 in the command with the nvme 2tb partition.Code: Select all
fsck /dev/sda2 -y
Also paste output of terminal commands rather than post pictures. It's more readable.
To use testdisk see https://linuxconfig.org/how-to-recover- ... e-in-linux[/color]
/
and /home
and everything except swap
and other partitions reserved for recovery and such. So I will run and display the output from all 3 potential candidates below to hopefully assure you have what you need.testdisk
application. I will read that later today. The more information I have the better! It was the testdisk
application that mostly fixed the 02TB_0001 SSD drive --- until the latest disaster.disks
and gparted
applications displayed for this 02TB_0001 SSD drive in my previous message on 20230528 at 01:22am
... just in case those displays provide more clues that might be helpful to you. The previous two of my message that contain images were from after the 02TB_0001 SSD became unmountable and unreadable after executing sudo update-grub
while displayed the error dialog that said "no object for D-Bus interface" ... whatever that means.sudo fsck /dev/nvme0n1p1
display. But everything I tried was difficult to read. For example, the text inside the "code" and "/code" markers was not dark enough (against the white background) to read easily, or alternately not large enough text to read easily.rimg
tags.That is your extended partition, you had more than four partitions on the drive so when testdisk restored a legacy partition table it had to create an extended partition.There is another peculiarity that maybe someone understands and can comment upon. On the disks image of the recovered 02TB SSD drive there is a second longer/larger bar overlaying in parallel with the main OS/user/data partition and the final /recovery partition.
What the hell is that about?
No, it is you that is at fault not linux and like kato181 I do not like being shouted at, that coupled with your attitude means that I not not be contributing to this topic any further.I'm getting the feeling that the entire boot aspect of Linux is A TOTAL MESS.
Of course, it may be slightly more likely that it is my brain that is A TOTAL MESS ... but that seems less likely as time passes.
Code: Select all
ls -ls
Code: Select all
sync
. They don't get trashed at all. Also whats the use case of your machine. You use it for what purpose?. why do MBR, partition tables and partitions get trashed so often
I just built the computer about 2 months ago (meaning I purchased a CPU, case, fans, motherboard, DDR5 DRAM, CPU-cooler, GPU card, 02TB M.2 NVME SSD, 2 new 16TB SATA drives, 43" display screen, downloaded the latest Linux Mint Cinnamon ... plus a few other components and assembled them). So I don't have any "instructions" for my computer, if that's your reason for asking.deepakdeshp wrote: ⤴Mon May 29, 2023 2:23 pm. They don't get trashed at all. Also whats the use case of your machine. You use it for what purpose?. why do MBR, partition tables and partitions get trashed so often
swap
partition, and also not creating any partitions for recovery purposes./
and /home
... to make updates of the OS without updating the development applications that support my own projects, plus my own projects (and huge quantities of data they need to access).transmission
client ... and I did forget to stop and close the transmission client when I shutdown once. That is when I had the original disaster --- the 02TB NVME SSD boot-drive on the motherboard would no longer boot and apparently its partition table got wiped. The testdisk
app seemed to most fix that, except that drive would not appear as a boot-up drive any more in BIOS. Where we are now is ... the update-grub
process you asked me to run rendered that 02TB drive unable to mount.update-grub
execution that you asked me to perform made the 02TB device "unmountable" and "unreadable" ... which has prevented me from continuing with his requests. I hope (and assume) he understands why I haven't answered his latest query yet.disks
application before I ran the update-grub
command. So if you want, I can try the reverse process with the disks
app to restore the 02TB drive. Just let me know what to do next ... restore with disks
or repair with testdisk
--- or something else?Code: Select all
inxi -Fxxxrz
Well, sorry to see you abandon me and my problem. I can assure you, I had no intention to annoy you or anyone else. In fact, just the opposite, which I explain in my previous message if you care to learn why and how. I won't repeat here.AndyMH wrote: ⤴Mon May 29, 2023 9:11 am First - none of your screenshots display, you are not using the preview button to check that what you want is what you get. I am not going to wade through a wall of text with missing information to try and second-guess what you have.
For the future, this may help:
viewtopic.php?p=2333339#p2333339
You are limited to three screenshots per post and the max file size is 200KB, for larger files you need to use a remote hosting site like imgur and therimg
tags.
You clearly do not understand how partition tables work with your many references to the MBR - that is irrelevant. Lack of understanding is acceptable, your attitude is not. There are two types of partition table:
- legacy (or msdos or mbr), usually associated with legacy boot, and
Suggest you have a look at the foxclone user guide, I wrote a couple of sections on partition tables and the use of disks and gparted.
- GPT usually associated with UEFI boot.
https://foxclone.org/
I thought that you originally had a GPT partition table on the drive, testdisk restored a legacy partition table.
That is your extended partition, you had more than four partitions on the drive so when testdisk restored a legacy partition table it had to create an extended partition.There is another peculiarity that maybe someone understands and can comment upon. On the disks image of the recovered 02TB SSD drive there is a second longer/larger bar overlaying in parallel with the main OS/user/data partition and the final /recovery partition.
What the hell is that about?
I did ask you to check the contents of your EFI partition and if the esp & boot flags were set. If the flags were not set or the boot files were not present, no boot. No answer, you went off at a tangent.
We don't know if you are booting UEFI or legacy, if legacy the EFI partition is irrelevent and I would not expect testdisk to restore grub (with legacy boot, boot.img lives in the first 446 bytes of sector 1 and core.img lives in the gap between the end of the partition table and start of the first partition). That is why having recovered your files I suggested you did a fresh install with a sensible partition layout. That recommendation remains unchanged. Having done a fresh install you can copy all your config files back and keep all the changes you have made to the desktop, etc.
No, it is you that is at fault not linux and like kato181 I do not like being shouted at, that coupled with your attitude means that I not not be contributing to this topic any further.I'm getting the feeling that the entire boot aspect of Linux is A TOTAL MESS.
Of course, it may be slightly more likely that it is my brain that is A TOTAL MESS ... but that seems less likely as time passes.
update-grub
command as requested by your fellow expert helper, which rendered the 02TB SSD "unmountable" and thus "unreadable". And for that reason, I could not answer your request. You see, I get blamed for everything ... even stuff that is not my fault. I did display an image that shows what gparted
displays for that nvme0n1 drive, but I guess you didn't see that. That display said that /dev/nvme0n1p1 was "ext4" filesystem and had only "boot" under the "flags" column (no "esp").transmission
was still running. You could say "I asked for it" and maybe you're right ... though in the past 4~5 years I never had a problem with vuze
on my old LM19 computer. Maybe just my bad luck, maybe transmission
is less forgiving than vuze
, or maybe LM21 is less forgiving than LM19. Who knows. I will definitely try to remember to pause, stop, close, shutdown transmission
before LM21 in the future.inxi -Fxxxrz
or similar. But it looks like a very excellent set of summary information, so here that is in a "code" block (even though it is vastly easier for me to read in an image, due to ... some unknown reason). Plus I include the efibootmgr
output at the beginning.Code: Select all
max@mintoid:~$ efibootmgr
BootCurrent: 0007
Timeout: 1 seconds
BootOrder: 0007,000A
Boot0007* ubuntu
Boot000A* ubuntu
max@mintoid:~$ inxi -Fxxxrz
System:
Kernel: 5.15.0-72-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
Desktop: Cinnamon 5.6.8 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG CROSSHAIR X670E EXTREME v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 1101
date: 04/10/2023
CPU:
Info: 16-core model: AMD Ryzen 9 7950X bits: 64 type: MT MCP smt: enabled
arch: Zen 3 rev: 2 cache: L1: 1024 KiB L2: 16 MiB L3: 64 MiB
Speed (MHz): avg: 2970 high: 3591 min/max: 3000/5880 boost: enabled
cores: 1: 2760 2: 2928 3: 2997 4: 2993 5: 2992 6: 2990 7: 2992 8: 2992
9: 2993 10: 2996 11: 2871 12: 3589 13: 2858 14: 2859 15: 2874 16: 2790
17: 2988 18: 2993 19: 2993 20: 2994 21: 2994 22: 2994 23: 2994 24: 2994
25: 2872 26: 3591 27: 2874 28: 2795 29: 2873 30: 2872 31: 2876 32: 2874
bogomips: 287460
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD vendor: Micro-Star MSI driver: amdgpu v: kernel pcie:
speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3
bus-ID: 03:00.0 chip-ID: 1002:73ef class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu display-ID: :0
screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.0x22.5")
s-diag: 1165mm (45.9")
Monitor-1: HDMI-A-0 mapped: HDMI-A-1 model: Samsung res: 3840x2160 hz: 60
dpi: 52 size: 1872x1053mm (73.7x41.5") diag: 1093mm (43") modes:
max: 3840x2160 min: 640x480
OpenGL: renderer: AMD Radeon RX 6650 XT (navi23 LLVM 15.0.6 DRM 3.42
5.15.0-72-generic)
v: 4.6 Mesa 22.2.5 direct render: Yes
Audio:
Device-1: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT]
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 03:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-2: ASUSTek USB Audio type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-6:3 chip-ID: 0b05:1a53
class-ID: 0300
Device-3: Logitech 960 Headset type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 9-1:2 chip-ID: 046d:0a45
class-ID: 0300 serial: <filter>
Sound Server-1: ALSA v: k5.15.0-72-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel
pcie: speed: 5 GT/s lanes: 1 bus-ID: 09:00.0 chip-ID: 8086:2725
class-ID: 0280
IF: wlp9s0 state: up mac: <filter>
Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
pcie: speed: 5 GT/s lanes: 1 port: N/A bus-ID: 0a:00.0 chip-ID: 8086:15f3
class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-3: Aquantia vendor: ASUSTeK driver: atlantic v: kernel pcie:
speed: 16 GT/s lanes: 1 port: N/A bus-ID: 0b:00.0 chip-ID: 1d6a:94c0
class-ID: 0200
IF: eno2 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Bluetooth:
Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 3-6:4 chip-ID: 8087:0032 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 45.48 TiB used: 20 TiB (44.0%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 2TB size: 1.82 TiB
speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: 5B2QGXA7
temp: 30.9 C scheme: MBR
ID-2: /dev/sda vendor: Western Digital model: WD161KFGX-68AFPN0
size: 14.55 TiB speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: 0A83 scheme: GPT
ID-3: /dev/sdb vendor: Western Digital model: WD161KFGX-68AFPN0
size: 14.55 TiB speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: 0A83 scheme: GPT
ID-4: /dev/sdc vendor: Seagate model: ST8000VN0022-2EL112 size: 7.28 TiB
speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: SC61 scheme: GPT
ID-5: /dev/sdd vendor: Seagate model: ST8000VN0022-2EL112 size: 7.28 TiB
speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: SC61 scheme: GPT
Partition:
ID-1: / size: 13.95 TiB used: 8.76 TiB (62.8%) fs: ext4 dev: /dev/sda4
ID-2: /boot/efi size: 61.02 GiB used: 6.4 MiB (0.0%) fs: vfat
dev: /dev/sda1
Swap:
ID-1: swap-1 type: partition size: 61.04 GiB used: 318.3 MiB (0.5%)
priority: -2 dev: /dev/sda3
Sensors:
System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 36.0 C
mem: 34.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Repos:
Packages: 2853 apt: 2846 flatpak: 7
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list
1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http://packages.linuxmint.com vera main upstream import backport
2: deb http://archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
3: deb http://archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
4: deb http://archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
1: deb [arch=amd64] https://repo.skype.com/deb stable main
Info:
Processes: 614 Uptime: 2d 12h 20m wakeups: 0 Memory: 62.53 GiB
used: 9.52 GiB (15.2%) Init: systemd v: 249 runlevel: 5 Compilers:
gcc: 11.3.0 alt: 11/12 Shell: Bash v: 5.1.16 running-in: gnome-terminal
inxi: 3.3.13
max@mintoid:~$
sudo dd if=/dev/nvme0n1 bs=512 count=1 | hexdump -C
the output of the first 512 bytes == first sector of the device/drive shows a bunch of bytes (that I assume is the lowest-level boot-loader code), then some bytes of 0x00, then a 4-byte drive ID field of some kind, followed by a 4-element partition table.testdisk
... it no longer had GPT on that drive.testdisk
on that 02TB NVME SSD drive multiple times, it was only when I selected "Intel/PC" instead of one of the other options, that the number of partitions and their sizes looked correct. As you (I think it was you) mentioned, the "swap" partition looked completely absurd when I selected the UEFI or GPT option (forget what it was called now) in testdisk
... like only 16 sectors or something. And so, because only "Intel/PC" displayed correct-size partitions (as far as we could tell), that was the selection the recovery process was performed in.initramfs
prompt during the boot-up process when I tried to boot from that drive. But otherwise, until I ran update-grub
as I was requested to do (which has made that drive unmountable), I was able to read and write to that drive with no problems.boot.img
plus 4-element partition table is not one of those partitions (which I assume is true)? Maybe I should ask that as a separate new question/thread to omit all the side-issues in this thread, huh?deepakdeshp wrote: ⤴Mon May 29, 2023 7:23 pm You come across as a very detailed oriented and a technical person.Building open source projects which are being used for NASA. Using controllers as well as software . That makes you a complete systems man. I am honoured to know you. deepakdeshp@gmail.com is my mail id. Do drop me an email.
As for your problems I feels they aren't because you opted for multi boot. I have been operating Windows 10/Mint multi boot on a single HDD for more than 10 years without a problem. I do t have a separate home partition. You can have one . That's your choice. What you can do is as follows:
Instead of multi boot disks have a single bootable disk. Have the other ssd as data disks. Clone the system disk with Clonezilla, a very versatile program but not so user friendly or with Foxzilla, developed by AndyMH himself.
Always backup on external drives, ssd or HDD. Avoid too many writes on the ssds as ssds have a lifetime of fixed writes on them.
https://easylinuxtipsproject.blogspot.c ... d.html?m=1
Also read the related topics of the site . A site developed by pjotr of the Mint forum.
https://easylinuxtipsproject.blogspot.com/p/1.html?m=1
This way in case of corruption of your system you are covered. My advise is to test your hardware for reliability. Especially memory, test it with memtest86 . ssd with https://ubuntuhandbook.org/index.php/20 ... buntu/amp/. It may be worth changing power supply, test for loose connections. Always backup. Backup the backup too. The backup interval determines the data you may loose in case of disaster which is the data that's not backed up.
Unrelated but I would like to know about your build. For that please post output of commandin code tags.Code: Select all
inxi -Fxxxrz
You are so much technically oriented that getting to know and using terminal commands will be very easy for you.
One such resource for it https://www.google.com/url?sa=t&source= ... 62_tv5_F1b
As you know more, deep dive in it. Learns shell scripting, using scripting with Python for system tasks...
https://www.google.com/url?sa=t&source= ... AtZU9ICwpf.
May be because you built the system, there is some glitch and there is some hardware problem like bad cable,power supply etc which corrupts your disks and ssds. I want to assure you that multibooot isn't the cause of your problems. It lies somewhere else. I have posted some of the possible causes in my posts.
/
and /home
partitions is --- the claim that I can update to say LM22 when it comes out, without anything in /home
being changed ... including all my own configuration settings for all system applications and personal applications that I installed and configured (or wrote myself and configured). However, without really knowing how Linux organizes all the different classes of applications and configurations, I am a bit skeptical that this really works as well as I see people claim. But if that really works --- wow! If LM22 or LM23 can be installed over the /
directory in a LM21 system without altering anything in the /home
directory, and all the OS and user configuration systems still work as before --- I mean that is really awesome. I think I'll probably post a question long these lines in the forum (separate from this thread) to ask what experiences people have had when doing/trying this. transmission
was still running and in the process of downloading about 15 huge files from the internet. While I try to shutdown things correctly, I was in a big hurry that day and just totally forgot to pause then close transmission
before shutting down LM21. I don't want to falsely accuse or even imply anything ... but over the past few years I've forgotten to shut down vuse
before shutdown on my old LM19 computer many times and that never caused any problems (or data corruption). But I could not immediately find vuze
for LM21 after I finished building this new computer, so I just adopted the default transmission
application that comes already installed on LM21 Cinnamon. In fact, I only mention this factoid in case someone else runs into partition-table or file corruption when they shutdown LM21 while transmission
is still running.Code: Select all
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-72-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: Samsung SSD 980 PRO 2TB
Serial Number: S6B0NL0W224966T
Firmware Version: 5B2QGXA7
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 2,000,398,934,016 [2.00 TB]
Unallocated NVM Capacity: 0
Controller ID: 6
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 2,000,398,934,016 [2.00 TB]
Namespace 1 Utilization: 811,155,243,008 [811 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 b231a491a0
Local Time is: Mon May 29 19:41:42 2023 PDT
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0057): Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f): S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size: 128 Pages
Warning Comp. Temp. Threshold: 82 Celsius
Critical Comp. Temp. Threshold: 85 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 8.49W - - 0 0 0 0 0 0
1 + 4.48W - - 1 1 1 1 0 200
2 + 3.18W - - 2 2 2 2 0 1000
3 - 0.0400W - - 3 3 3 3 2000 1200
4 - 0.0050W - - 4 4 4 4 500 9500
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Code: Select all
max@mintoid:~$ inxi -Fxxxrz
System:
Kernel: 5.15.0-72-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
Desktop: Cinnamon 5.6.8 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG CROSSHAIR X670E EXTREME v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 1101
date: 04/10/2023
CPU:
Info: 16-core model: AMD Ryzen 9 7950X bits: 64 type: MT MCP smt: enabled
arch: Zen 3 rev: 2 cache: L1: 1024 KiB L2: 16 MiB L3: 64 MiB
Speed (MHz): avg: 3007 high: 4088 min/max: 3000/5880 boost: enabled
cores: 1: 2992 2: 2993 3: 2992 4: 2987 5: 2993 6: 2993 7: 2990 8: 2994
9: 2872 10: 3571 11: 2852 12: 2778 13: 2875 14: 2835 15: 2870 16: 3590
17: 2993 18: 2992 19: 2991 20: 2996 21: 2993 22: 2991 23: 2994 24: 2993
25: 2837 26: 2873 27: 2873 28: 2870 29: 2859 30: 2871 31: 2849 32: 4088
bogomips: 287460
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD vendor: Micro-Star MSI driver: amdgpu v: kernel pcie:
speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3
bus-ID: 03:00.0 chip-ID: 1002:73ef class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu display-ID: :0
screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.0x22.5")
s-diag: 1165mm (45.9")
Monitor-1: HDMI-A-0 mapped: HDMI-A-1 model: Samsung res: 3840x2160 hz: 60
dpi: 52 size: 1872x1053mm (73.7x41.5") diag: 1093mm (43") modes:
max: 3840x2160 min: 640x480
OpenGL: renderer: AMD Radeon RX 6650 XT (navi23 LLVM 15.0.6 DRM 3.42
5.15.0-72-generic)
v: 4.6 Mesa 22.2.5 direct render: Yes
Audio:
Device-1: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT]
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 03:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-2: ASUSTek USB Audio type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-6:3 chip-ID: 0b05:1a53
class-ID: 0300
Device-3: Logitech 960 Headset type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 9-1:2 chip-ID: 046d:0a45
class-ID: 0300 serial: <filter>
Sound Server-1: ALSA v: k5.15.0-72-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel
pcie: speed: 5 GT/s lanes: 1 bus-ID: 09:00.0 chip-ID: 8086:2725
class-ID: 0280
IF: wlp9s0 state: up mac: <filter>
Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
pcie: speed: 5 GT/s lanes: 1 port: N/A bus-ID: 0a:00.0 chip-ID: 8086:15f3
class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-3: Aquantia vendor: ASUSTeK driver: atlantic v: kernel pcie:
speed: 16 GT/s lanes: 1 port: N/A bus-ID: 0b:00.0 chip-ID: 1d6a:94c0
class-ID: 0200
IF: eno2 state: down mac: <filter>
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Bluetooth:
Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 3-6:4 chip-ID: 8087:0032 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 45.48 TiB used: 20 TiB (44.0%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 2TB size: 1.82 TiB
speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: 5B2QGXA7
temp: 28.9 C scheme: MBR
ID-2: /dev/sda vendor: Western Digital model: WD161KFGX-68AFPN0
size: 14.55 TiB speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: 0A83 scheme: GPT
ID-3: /dev/sdb vendor: Western Digital model: WD161KFGX-68AFPN0
size: 14.55 TiB speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
rev: 0A83 scheme: GPT
ID-4: /dev/sdc vendor: Seagate model: ST8000VN0022-2EL112 size: 7.28 TiB
speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: SC61 scheme: GPT
ID-5: /dev/sdd vendor: Seagate model: ST8000VN0022-2EL112 size: 7.28 TiB
speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: SC61 scheme: GPT
Partition:
ID-1: / size: 13.95 TiB used: 8.76 TiB (62.8%) fs: ext4 dev: /dev/sda4
ID-2: /boot/efi size: 61.02 GiB used: 6.4 MiB (0.0%) fs: vfat
dev: /dev/sda1
Swap:
ID-1: swap-1 type: partition size: 61.04 GiB used: 323.8 MiB (0.5%)
priority: -2 dev: /dev/sda3
Sensors:
System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 36.0 C
mem: 36.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Repos:
Packages: 2853 apt: 2846 flatpak: 7
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list
1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http://packages.linuxmint.com vera main upstream import backport
2: deb http://archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
3: deb http://archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
4: deb http://archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
1: deb [arch=amd64] https://repo.skype.com/deb stable main
Info:
Processes: 621 Uptime: 2d 16h 44m wakeups: 0 Memory: 62.53 GiB
used: 10.31 GiB (16.5%) Init: systemd v: 249 runlevel: 5 Compilers:
gcc: 11.3.0 alt: 11/12 Shell: Bash v: 5.1.16 running-in: gnome-terminal
inxi: 3.3.13
max@mintoid:~$