我只想安装某些应用程序的旧版本。我对某些应用程序的旧版本更熟悉,在 Windows 中,你可以在 Ubuntu 中安装旧版 exe 文件,我不知道。
我对 Ubuntu 还很陌生,我对 Ubuntu 的工作原理并不是很了解,当我运行 sudo apt update 或当我想要安装应用程序或添加 repo 时,我收到超时错误或无法获取,我也尝试更改 dns。
例如 :
Err:8 http://in.archive.ubuntu.com/ubuntu bionic InRelease
Could not connect to in.archive.ubuntu.com:80 (103.97.84.254), connection timed out
有什么需要更改或重置吗?
安全摄像头中的 µSD 卡突然停止录制:
- 大部分数据都消失了(没问题)。
- 仍然存在的数据是正确且可读的。
- 该卡现在始终以只读方式安装(在 Chromebook、Windows 和 Ubuntu 上)。
我无法重新格式化它或用它做任何事情:
$ df
/dev/mmcblk0 vfat 117G 15G 102G 13% /media/ray/xxx
$ sudo fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 116.1 GiB, 124657860608 bytes, 243472384 sectors
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: dos
Disk identifier: 0x00000000
$ sudo fsck /dev/mmcblk0
fsck from util-linux 2.34
fsck.fat 4.1 (2017-01-24)
open: Read-only file system
$ sudo hdparm -r0 /dev/mmcblk0
/dev/mmcblk0:
setting readonly to 0 (off)
readonly = 1 (on)
$ sudo hdparm -r0 /dev/mmcblk0
/dev/mmcblk0:
setting readonly to 0 (off)
readonly = 1 (on)
$ sudo fsck /dev/mmcblk0
fsck from util-linux 2.34
fsck.fat 4.1 (2017-01-24)
open: Read-only file system
$ sudo umount /media/ray/xxx
$ sudo mount -o rw /dev/mmcblk0 /media/ray/xxx
mount: /media/ray/xxx: WARNING: device write-protected, mounted read-only.
请注意,这不是全尺寸的 SD 卡;没有物理写保护开关。
这张卡可以回收吗,还是垃圾?
我经常看到有人说最好等到 Ubuntu LTS 版本的第一个版本(例如 24.04.1)发布后再进行升级。这也适用于从临时版本(例如 23.10)升级吗?尤其是当达到的临时版本已过期(EOL)时?
我认为我的问题是双重的(除非不是),但它们来自我将一些 HDD 分区迁移到新的 SSD 驱动器。使用Boot-Repair,我现在可以启动 Ubuntu 22.04,但 Window 10 无法启动,我很确定 Grub 是其中的一部分。
我有两个驱动器,分别是 /dev/sda 和 /dev/nvme0n1。我从未使用过任何这些驱动器管理工具来写入 /dev/sda,所以应该不会发生任何事情。但如果我尝试从其中任何一个启动 Windows,它都不会起作用。
/dev/sda 包括:
- /dev/sda1:Linux 交换
- /dev/sda2:Linux启动
- /dev/sda3:另一个 ext4
- /dev/sda4:Windows 10
/dev/nvme0n1 包括:
- /dev/nvme0n1p1:/dev/sda2 的克隆(Linux 启动)
- /dev/nvme0n1p2:/dev/sda4 的克隆(Windows 10)
- /dev/nvme0n1p3:尚无文件系统,但标记为 ext4
我已经从 /dev/nvme0n1p1 运行os-prober
,grub-update
因此这些工具已经尽其所能。
从 /dev/nvme0n1 启动
Grub 现在可以访问任一驱动器上的每个分区,并且我可以启动 Ubuntu,但如果我尝试启动 /dev/nvme0n1p2或/dev/sda4,我会立即收到提示“发生磁盘读取错误 // 按 Ctrl-Alt-Del 重新启动”
引导修复摘要:
============================= Boot Repair Summary ==============================
Default settings: ______________________________________________________________
The default repair of the Boot-Repair utility would reinstall the grub2 of
nvme0n1p1 into the MBR of nvme0n1.
Grub-efi would not be selected by default because no ESP detected.
Additional repair would be performed: unhide-bootmenu-10s
Confirmation request before suggested repair: __________________________________
LegacyWindows detected. The boot of your PC is in EFI mode. You may want to retry after changing it to BIOS-compatibility/CSM/Legacy mode.
Are you sure you want to continue anyway?
Final advice in case of suggested repair: ______________________________________
Please do not forget to make your BIOS boot on nvme0n1 (TEAM TM8FP6512G) disk!
The boot files of [nvme0n1p1 (end>100GB)] are far from the start of the disk. Your BIOS may not detect them. You may want to retry after creating a /boot partition (EXT4, >200MB, start of the disk). This can be performed via tools such as gParted. Then select this partition via the [Separate /boot partition:] option of [Boot Repair]. (https://help.ubuntu.com/community/BootPartition)Please set your BIOS in Legacy mode in order to start your Ubuntu 22.04.4 LTS, then type command [sudo update-grub] in order to add the MacOS entry to your GRUB menu.
User settings: _________________________________________________________________
The settings chosen by the user will reinstall the grub2 of
nvme0n1p1 into the MBR of nvme0n1.
Grub-efi will not be selected by default because no ESP detected.
Additional repair will be performed: unhide-bootmenu-10s
Unhide GRUB boot menu in nvme0n1p1/etc/default/grub
==================== Reinstall the grub2 of /dev/nvme0n1p1 =====================
chroot /mnt/boot-sav/nvme0n1p1 grub-install --version
grub-install (GRUB) 2.06-2ubuntu7.2
==> Reinstall the GRUB of /dev/nvme0n1p1 into the MBR of /dev/nvme0n1
chroot /mnt/boot-sav/nvme0n1p1 grub-install /dev/nvme0n1
Installing for i386-pc platform.
Installation finished. No error reported.
chroot /mnt/boot-sav/nvme0n1p1 update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Found linux image: /boot/vmlinuz-5.15.0-116-generic
Found initrd image: /boot/initrd.img-5.15.0-116-generic
Found linux image: /boot/vmlinuz-5.15.0-113-generic
Found initrd image: /boot/initrd.img-5.15.0-113-generic
Found linux image: /boot/vmlinuz-5.15.0-76-generic
Found initrd image: /boot/initrd.img-5.15.0-76-generic
Found linux image: /boot/vmlinuz-5.4.0-104-generic
Found initrd image: /boot/initrd.img-5.4.0-104-generic
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
Found Ubuntu 22.04.4 LTS (22.04) on /dev/sda2
Unhide GRUB boot menu in nvme0n1p1/boot/grub/grub.cfg
Boot successfully repaired.
You can now reboot your computer.
Please do not forget to make your BIOS boot on nvme0n1 (TEAM TM8FP6512G) disk!
The boot files of [nvme0n1p1 (end>100GB)] are far from the start of the disk. Your BIOS may not detect them. You may want to retry after creating a /boot partition (EXT4, >200MB, start of the disk). This can be performed via tools such as gParted. Then select this partition via the [Separate /boot partition:] option of [Boot Repair]. (https://help.ubuntu.com/community/BootPartition)Please set your BIOS in Legacy mode in order to start your Ubuntu 22.04.4 LTS, then type command [sudo update-grub] in order to add the MacOS entry to your GRUB menu.
============================ Boot Info After Repair ============================
=> Grub2 (v2.00) is installed in the MBR of /dev/nvme0n1 and looks at sector
1 of the same hard drive for core.img. core.img is at this location and
looks for (,msdos1)/boot/grub. It also embeds following components:
modules
---------------------------------------------------------------------------
fshelp ext2 part_msdos biosdisk
---------------------------------------------------------------------------
=> Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for (,msdos2)/boot/grub. It also embeds following components:
modules
---------------------------------------------------------------------------
fshelp ext2 part_msdos biosdisk
---------------------------------------------------------------------------
nvme0n1p1: _____________________________________________________________________
File system: ext4
Boot sector type: Grub Legacy
Boot sector info: Grub Legacy (v) is installed in the boot sector of
nvme0n1p1 and looks at sector 17096832 of the same
hard drive for the stage2 file, but no stage2 files
can be found at this location.
Operating System: Ubuntu 22.04.4 LTS
Boot files: /boot/grub/grub.cfg /etc/fstab /etc/default/grub
/boot/grub/i386-pc/core.img
nvme0n1p2: _____________________________________________________________________
File system: ntfs
Boot sector type: NTFS
Boot sector info: According to the info in the boot sector, nvme0n1p2
starts at sector 1743808512. But according to the info
from fdisk, nvme0n1p2 starts at sector 204802048.
Operating System: Windows 8 or 10
Boot files: /bootmgr /Boot/BCD /Windows/System32/winload.exe
nvme0n1p3: _____________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
sda1: __________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
sda2: __________________________________________________________________________
File system: ext4
Boot sector type: Grub Legacy
Boot sector info: Grub Legacy (v) is installed in the boot sector of
sda2 and looks at sector 17096832 of the same hard
drive for the stage2 file, but no stage2 files can be
found at this location.
Operating System: Ubuntu 22.04.4 LTS
Boot files: /boot/grub/grub.cfg /etc/fstab /etc/default/grub
/boot/grub/i386-pc/core.img
sda3: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
sda4: __________________________________________________________________________
File system: ntfs
Boot sector type: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 8 or 10
Boot files: /bootmgr /Boot/BCD /Windows/System32/winload.exe
sdb: ___________________________________________________________________________
File system: iso9660
Boot sector type: Unknown
Boot sector info:
Mounting failed: mount: /mnt/BootInfo/FD/sdb: /dev/sdb already mounted or mount point busy.
================================ 4 OS detected =================================
OS#1: Ubuntu 22.04.4 LTS on nvme0n1p1
OS#2: Ubuntu 22.04.4 LTS on sda2
OS#3: Windows 8 or 10 on nvme0n1p2
OS#4: Windows 8 or 10 on sda4
================================ Host/Hardware =================================
CPU architecture: 64-bit
Video: GM107 [GeForce GTX 750 Ti] from NVIDIA Corporation
Live-session OS is Linuxmint 64-bit (Linux Mint 21.2, victoria, x86_64)
===================================== UEFI =====================================
BIOS/UEFI firmware: P2.20(5.17) from American Megatrends International, LLC.
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
SecureBoot disabled (confirmed by mokutil).
BootCurrent: 000D
Timeout: 1 seconds
BootOrder: 000D,0000,000C,000E,000A
Boot0000* Windows Boot Manager HD(4,MBR,0x1d8e78d7,0x67f06800,0xc7ff800)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot000A* Hard Drive BBS(HD,,0x0)..GO..NO........{.T.E.A.M. .T.M.8.F.P.6.5.1.2.G....................A..........................dy..... .....>..Gd-.;.A..MQ..L.T.P.B.F.2.3.1.2.1.2.0.0.3.0.2.0.2.9.9.2........BO..NO........u.S.T.3.1.0.0.0.5.2.4.A.S....................A.................................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .V.9.C.P.E.W.2.N........BO
Boot000C* CD/DVD Drive BBS(CDROM,,0x0)..GO..NO........u.H.L.-.D.T.-.S.T. .D.V.D.R.A.M. .G.H.2.4.N.S.7.0....................A.................................>..Gd-.;.A..MQ..L.4.K.B.U.J.5.0.6.5.3. .9. . . . . . . . ........BO
Boot000D* UEFI OS HD(2,MBR,0x14eb2669,0x23c,0x2130)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot000E* USB BBS(USB,,0x0)..GO..NO........a.J.M.i.c.r.o.n. .T.e.c.h. .0.5.0.8....................A................................Gd-.;.A..MQ..L.0.0.0.0.0.0.0.0.0.0.1.6........BO
ed45adef8b51b968450611d9d89804b4 sda4/Boot/bootx64.efi
13bbe79f47b4d57f791e51f5c01f7ac8 sda4/Microsoft/Boot/SecureBootRecovery.efi
ed45adef8b51b968450611d9d89804b4 sda4/Microsoft/Boot/bootmgfw.efi
0155f61ba8a2b8a43ff6c21012230205 sda4/Microsoft/Boot/bootmgr.efi
============================= Drive/Partition Info =============================
Disks info: ____________________________________________________________________
nvme0n1 : notGPT, no-BIOSboot, has-noESP, not-usb, not-mmc, has-os, has-win, 2048 sectors * 512 bytes
sda : notGPT, no-BIOSboot, has-noESP, not-usb, not-mmc, has-os, has-win, 2048 sectors * 512 bytes
Partitions info (1/3): _________________________________________________________
nvme0n1p1 : is-os, 64, apt-get, grub-pc , grub2, grub-install, grubenv-ok, update-grub, end-after-100GB
nvme0n1p2 : is-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
nvme0n1p3 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
sda2 : is-os, 64, apt-get, grub-pc , grub2, grub-install, grubenv-ok, update-grub, not-far
sda3 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
sda4 : is-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
Partitions info (2/3): _________________________________________________________
nvme0n1p1 : isnotESP, fstab-without-efi, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
nvme0n1p2 : isnotESP, part-has-no-fstab, no-nt, haswinload, no-recov-nor-hid, bootmgr, is-winboot
nvme0n1p3 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda2 : isnotESP, fstab-without-efi, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda3 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sda4 : isnotESP, part-has-no-fstab, no-nt, haswinload, no-recov-nor-hid, bootmgr, is-winboot
Partitions info (3/3): _________________________________________________________
nvme0n1p1 : not--sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, nvme0n1
nvme0n1p2 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme0n1
nvme0n1p3 : maybesepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme0n1
sda2 : not--sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, sda
sda3 : maybesepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sda
sda4 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, sda
fdisk -l (filtered): ___________________________________________________________
Disk nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk identifier: 0x000d06a8
Boot Start End Sectors Size Id Type
nvme0n1p1 2048 204802047 204800000 97.7G 83 Linux
nvme0n1p2 * 204802048 598018047 393216000 187.5G 7 HPFS/NTFS/exFAT
nvme0n1p3 598018048 1000214527 402196480 191.8G 83 Linux
Disk sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk identifier: 0x1d8e78d7
Boot Start End Sectors Size Id Type
sda1 2048 27097087 27095040 12.9G 82 Linux swap / Solaris
sda2 27097088 152436735 125339648 59.8G 83 Linux
sda3 152436736 1743808511 1591371776 758.8G 83 Linux
sda4 * 1743808512 1953521663 209713152 100G 7 HPFS/NTFS/exFAT
Disk sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk identifier: 0x14eb2669
Boot Start End Sectors Size Id Type
sdb1 * 0 5138431 5138432 2.5G 0 Empty
sdb2 572 9067 8496 4.1M ef EFI (FAT-12/16/32)
sdb3 5140480 1953525167 1948384688 929.1G 83 Linux
parted -lm (filtered): _________________________________________________________
sda:1000GB:scsi:512:512:msdos:ATA ST31000524AS:;
1:1049kB:13.9GB:13.9GB:linux-swap(v1)::;
2:13.9GB:78.0GB:64.2GB:ext4::;
3:78.0GB:893GB:815GB:ext4::;
4:893GB:1000GB:107GB:ntfs::boot;
sdb:1000GB:scsi:512:4096:msdos:JMicron Tech:;
2:293kB:4643kB:4350kB:::esp;
3:2632MB:1000GB:998GB:ext4::;
nvme0n1:512GB:nvme:512:512:msdos:TEAM TM8FP6512G:;
1:1049kB:105GB:105GB:ext4::;
2:105GB:306GB:201GB:ntfs::boot;
3:306GB:512GB:206GB:ext4::;
Free space >10MiB: ______________________________________________________________
sdb: 4.43MiB:2510MiB:2506MiB
blkid (filtered): ______________________________________________________________
NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda
├─sda1 swap 019e69d5-cbf4-4bf4-8f6f-1002f27bb8ad 1d8e78d7-01
├─sda2 ext4 f7c1939e-6939-417e-af42-7f9980294b87 1d8e78d7-02
├─sda3 ext4 e7dd6327-d1f8-40b8-9c74-5f1c9b088ebd 1d8e78d7-03
└─sda4 ntfs 08C80847C808358A 1d8e78d7-04
sdb iso9660 2023-12-23-05-05-55-00 Boot-Repair-Disk 64bit
├─sdb1 iso9660 2023-12-23-05-05-55-00 14eb2669-01 Boot-Repair-Disk 64bit
├─sdb2 vfat 8D6C-A9F8 14eb2669-02 ESP
└─sdb3 ext4 dbdf4531-251f-4191-a2c3-4e2904238123 14eb2669-03 writable
nvme0n1
├─nvme0n1p1 ext4 da5f7597-a235-4b9e-a118-16f157daf97d 000d06a8-01 UBUNTU_ROOT
├─nvme0n1p2 ntfs 08C80847C808358A 000d06a8-02
└─nvme0n1p3 ext4 87181479-e982-492f-9ba5-c36df1fe41bf 000d06a8-03
Mount points (filtered): _______________________________________________________
Avail Use% Mounted on
/dev/nvme0n1p1 55.1G 37% /mnt/boot-sav/nvme0n1p1
/dev/nvme0n1p2 99.1G 47% /mnt/boot-sav/nvme0n1p2
/dev/nvme0n1p3 179G 0% /mnt/boot-sav/nvme0n1p3
/dev/sda2 20G 61% /mnt/boot-sav/sda2
/dev/sda3 284G 62% /mnt/boot-sav/sda3
/dev/sda4 11.3G 89% /mnt/boot-sav/sda4
/dev/sdb1 0 100% /cdrom
Mount options (filtered): ______________________________________________________
/dev/nvme0n1p1 ext4 rw,relatime,stripe=32639
/dev/nvme0n1p2 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme0n1p3 ext4 rw,relatime
/dev/sda2 ext4 rw,relatime,stripe=32639
/dev/sda3 ext4 rw,relatime,stripe=32750
/dev/sda4 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/sdb1 iso9660 ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8
=================== nvme0n1p1/boot/grub/grub.cfg (filtered) ====================
Ubuntu da5f7597-a235-4b9e-a118-16f157daf97d
Ubuntu 22.04.4 LTS (22.04) (on sda2) f7c1939e-6939-417e-af42-7f9980294b87
### END /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_uefi-firmware ###
======================== nvme0n1p1/etc/fstab (filtered) ========================
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during installation
UUID=da5f7597-a235-4b9e-a118-16f157daf97d / ext4 errors=remount-ro 0 1
# /home was on /dev/sda3 during installation
UUID=e7dd6327-d1f8-40b8-9c74-5f1c9b088ebd /home ext4 defaults 0 2
# swap was on /dev/sda1 during installation
UUID=019e69d5-cbf4-4bf4-8f6f-1002f27bb8ad none swap sw 0 0
192.168.1.105:/mnt/mainhdd/dospace/ /mnt/pi/ nfs defaults,noauto,wsize=65536,retrans=5 0 0
==================== nvme0n1p1/etc/default/grub (filtered) =====================
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
GRUB_DISABLE_OS_PROBER=false
================= nvme0n1p1: Location of files loaded by Grub ==================
GiB - GB File Fragment(s)
?? = ?? boot/grub/grub.cfg 1
61.751464844 = 66.305130496 boot/grub/i386-pc/core.img 1
38.652488708 = 41.502793728 boot/vmlinuz 2
40.816543579 = 43.826429952 boot/vmlinuz-5.15.0-113-generic 2
38.652488708 = 41.502793728 boot/vmlinuz-5.15.0-116-generic 2
31.168018341 = 33.466404864 boot/vmlinuz-5.15.0-76-generic 1
7.794952393 = 8.369766400 boot/vmlinuz-5.4.0-104-generic 1
40.816543579 = 43.826429952 boot/vmlinuz.old 2
59.860347748 = 64.274558976 boot/initrd.img 5
29.602535248 = 31.785480192 boot/initrd.img-5.15.0-113-generic 8
59.860347748 = 64.274558976 boot/initrd.img-5.15.0-116-generic 5
57.750972748 = 62.009634816 boot/initrd.img-5.15.0-76-generic 8
49.625972748 = 53.285482496 boot/initrd.img-5.4.0-104-generic 4
29.602535248 = 31.785480192 boot/initrd.img.old 8
=================== nvme0n1p1: ls -l /etc/grub.d/ (filtered) ===================
-rwxr-xr-x 1 root root 18683 Apr 15 2022 10_linux
-rwxr-xr-x 1 root root 43031 Apr 15 2022 10_linux_zfs
-rwxr-xr-x 1 root root 14387 Dec 18 2022 20_linux_xen
-rwxr-xr-x 1 root root 13369 Apr 15 2022 30_os-prober
-rwxr-xr-x 1 root root 1372 Apr 15 2022 30_uefi-firmware
-rwxr-xr-x 1 root root 700 Feb 21 2022 35_fwupd
-rwxr-xr-x 1 root root 214 Apr 11 2014 40_custom
-rwxr-xr-x 1 root root 215 Apr 15 2022 41_custom
====================== sda2/boot/grub/grub.cfg (filtered) ======================
Ubuntu f7c1939e-6939-417e-af42-7f9980294b87
Windows 10 (on sda4) 08C80847C808358A
### END /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_uefi-firmware ###
========================== sda2/etc/fstab (filtered) ===========================
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during installation
UUID=f7c1939e-6939-417e-af42-7f9980294b87 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda3 during installation
UUID=e7dd6327-d1f8-40b8-9c74-5f1c9b088ebd /home ext4 defaults 0 2
# swap was on /dev/sda1 during installation
UUID=019e69d5-cbf4-4bf4-8f6f-1002f27bb8ad none swap sw 0 0
192.168.1.105:/mnt/mainhdd/dospace/ /mnt/pi/ nfs defaults,noauto,wsize=65536,retrans=5 0 0
======================= sda2/etc/default/grub (filtered) =======================
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
==================== sda2: Location of files loaded by Grub ====================
GiB - GB File Fragment(s)
19.049831390 = 20.454600704 boot/grub/grub.cfg 1
71.342910767 = 76.603867136 boot/grub/i386-pc/core.img 1
53.736465454 = 57.699090432 boot/vmlinuz 2
28.858394623 = 30.986465280 boot/vmlinuz-5.15.0-112-generic 2
53.736465454 = 57.699090432 boot/vmlinuz-5.15.0-113-generic 2
44.087940216 = 47.339065344 boot/vmlinuz-5.15.0-76-generic 1
20.714874268 = 22.242426880 boot/vmlinuz-5.4.0-104-generic 1
28.858394623 = 30.986465280 boot/vmlinuz.old 2
70.022457123 = 75.186040832 boot/initrd.img 3
71.408851624 = 76.674670592 boot/initrd.img-5.15.0-112-generic 5
70.022457123 = 75.186040832 boot/initrd.img-5.15.0-113-generic 3
66.545894623 = 71.453110272 boot/initrd.img-5.15.0-76-generic 4
46.304576874 = 49.719160832 boot/initrd.img-5.4.0-104-generic 5
71.408851624 = 76.674670592 boot/initrd.img.old 5
===================== sda2: ls -l /etc/grub.d/ (filtered) ======================
-rwxr-xr-x 1 root root 18683 Apr 15 2022 10_linux
-rwxr-xr-x 1 root root 43031 Apr 15 2022 10_linux_zfs
-rwxr-xr-x 1 root root 14387 Dec 18 2022 20_linux_xen
-rwxr-xr-x 1 root root 13369 Apr 15 2022 30_os-prober
-rwxr-xr-x 1 root root 1372 Apr 15 2022 30_uefi-firmware
-rwxr-xr-x 1 root root 700 Feb 21 2022 35_fwupd
-rwxr-xr-x 1 root root 214 Apr 11 2014 40_custom
-rwxr-xr-x 1 root root 215 Apr 15 2022 41_custom
======================== Unknown MBRs/Boot Sectors/etc =========================
Unknown BootLoader on sdb
sprunge.us ko ()
从 /dev/dsa 引导
就像我说的,我没有使用任何这些工具来写入 /dev/sda,但如果我尝试从安装在 /dev/sda 上的 grub 启动 /dev/dsa4,它会开始启动但随后停止,出现一般错误,然后重新启动。这就是我认为 /dev/nvme0n1 上的问题出在 grub 上的原因。
我希望我可以提供一些更具体的错误消息/代码,但我还没有看到。
所以我认为这个问题可以分解为两个:
- /dev/nvme0n1 上的 Grub 无法正确加载任何一个 Windows 分区。
- /dev/sda 上的 grub 可能有问题,也可能没问题,但显然有问题。我担心的是使用 MS 工具来纠正这个问题,因为它往往会破坏 Linux 安装。
我曾尝试使用 Google 搜索此类问题,但缺少特定的关键词,而且我发现的很多问题都是 10 年前的,可能不足以解决我的问题。
我正在尝试自定义PS1
,以便在我进入 git 存储库时显示我所在的分支。为此,我使用了该__git_ps1
函数,一切正常。
我的问题是,根据我在互联网上搜索到的解释,你必须将文件导入git-prompt.sh
到你的.bashrc
文件中。好吧,我还没有这样做,但它仍然有效。
事实上,我尝试过locate
这样find
的脚本,但它并不存在于我的文件系统中。所以我的问题是,这样的函数在哪里定义?
我最近在另一台笔记本电脑(22.04.4)上对 GNOME 进行了一些调整,打开多个窗口时没有这个预览。
系统如何运作:
当我点击多个打开的窗口(Dock 中的图标)时,活动窗口会旋转。因此,首先,它会激活第一个窗口,第二次点击,第二个,等等。
我期望系统的行为如下:
当我点击 Dock 中的图标时(当打开多个窗口时),我希望看到下面屏幕截图中显示的内容。这样我就可以轻松导航到相应的窗口。有时我有多个窗口,点击旋转效率不高。
起源:
我安装了 Evolution 电子邮件客户端,经过一些测试后,我将其删除了 ( sudo apt remove
)。最后我只能访问终端(重启后),所以我又安装了gnome
一次gnome-panel
。之后,它就不再像我想要的那样运行了。
我有另一台笔记本电脑,全新安装了 24.04,并且运行正常。
知道如何再次启用此功能吗?
pmount 可通过命令行安装 USB 驱动器(并使用 pumount 卸载)。pmount 需要知道要安装哪个设备和分区。如果我插入拇指驱动器并且我在 GUI 上,我可以使用 gnome-disks 来确定我想要安装的特定拇指驱动器是 /dev/sdb1、/dev/sdc1 还是 /dev/sde1。它甚至会确认卷标名称是什么 - 所有这些都无需使用 sudo。
如何在不使用 sudo 的情况下通过命令行获取类似信息?(设备/分区)
我的主机是 Ubuntu,我在 Virualbox 中有不同的客户机。直到昨天,它们(Windows 和 Ubuntu 客户机)都运行良好。今天,它们在启动时都会遇到此错误:
运行虚拟机时发生严重错误,机器执行已停止。
增加内存没有用。调整 CPU 选项也没有用。重启主机也没有用。
Virtualbox 版本:6.1.50_Ubuntu r161033
Ubuntu 主机版本:20.04 focus
日志文件太大。其结尾如下:
在单击“确定”之前结束记录:
--------------------------------------------------------------------------------
00:00:03.361140 !!
00:00:03.361140 !! {vmsvga}
00:00:03.361140 !!
00:00:03.361140 Extension enabled: false
00:00:03.361141 Configured: false
00:00:03.361141 Base I/O port: 0xd010
00:00:03.361142 FIFO address: 00000000f0000000
00:00:03.361142 FIFO size: 2097152 (0x200000)
00:00:03.361142 FIFO external cmd: 0x0
00:00:03.361143 FIFO extcmd wakeup: 0
00:00:03.361143 FIFO min/max: 0/0
00:00:03.361143 Busy: 0x0
00:00:03.361143 Traces: false (effective: true )
00:00:03.361144 Guest ID: 0x0 (0)
00:00:03.361144 IRQ status: 0x0
00:00:03.361144 IRQ mask: 0x0
00:00:03.361145 Pitch lock: 0x0 (FIFO:0x0)
00:00:03.361145 Current GMR ID: 0x0
00:00:03.361145 Capabilites reg: 0xf6c2a0
00:00:03.361145 Index reg: 0x0
00:00:03.361146 Action flags: 0x0
00:00:03.361146 Max display size: 5632x5632
00:00:03.361146 Display size: 4294967295x4294967295 4294967295bpp
00:00:03.361147 Scanline: 0 (0x0)
00:00:03.361147 Viewport position: 0x0
00:00:03.361147 Viewport size: 0x0
00:00:03.361147 Cursor active: false
00:00:03.361148 Cursor hotspot: 0x0
00:00:03.361148 Cursor size: 0x0
00:00:03.361149 Cursor byte size: 0 (0x0)
00:00:03.361149 3D enabled: false
00:00:03.361149 Driver mode: 720x400 32bpp
00:00:03.361150 Driver pitch: 2880 (0xb40)
00:00:03.361150 !!
00:00:03.361150 !! {vmsvga3dctx}
00:00:03.361151 !!
00:00:03.361152 !!
00:00:03.361152 !! {vmsvga3dsfc}
00:00:03.361152 !!
00:00:03.361152 !!
00:00:03.361152 !! {vmsvga3dsurf}
00:00:03.361153 !!
00:00:03.361153 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:03.361200 emR3Debug: rc=VERR_VMM_SET_JMP_ABORTED_RESUME
00:00:03.423841 GUI: Machine-window #0 deactivated
00:00:03.423874 GUI: Releasing mouse on focus out
00:00:03.423880 GUI: Releasing keyboard on focus out
00:00:03.425282 GUI: Machine-view #0 unfocused, reason=3
00:09:10.403673 GUI: User request to power VM off on Guru Meditation.
00:09:10.403700 GUI: Passing request to power VM off from machine-logic to UI session.
00:09:10.403706 GUI: Powering VM down on UI session power off request...
00:09:10.403866 Console: Machine state changed to 'Stopping'
00:09:10.404303 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
00:09:10.404559 Changing the VM state from 'GURU_MEDITATION' to 'POWERING_OFF'
00:09:10.404574 ****************** Guest state at power off for VCpu 1 ******************
单击“确定”后日志结束:
00:09:10.464817 E1000#0: Larger TX frames : 0
00:09:10.464823 E1000#0: Max TX Delay : 0
00:09:10.531519 GIM: KVM: Resetting MSRs
00:09:10.534960 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:09:10.534960 Console: Machine state changed to 'PoweredOff'
00:09:11.048662 GUI: Passing request to close Runtime UI from machine-logic to UI session.
我可以根据要求提供更多日志。