Início / user-487383

Lexx Luxx's questions

Martin Hope
Lexx Luxx
Asked: 2022-05-11 02:47:05 +0800 CST
  • 0

na reinicialização, o Debian 11 sempre abre a /run/systemdpasta, enquanto antes, o Debian não abria nenhuma pasta específica após a reinicialização. Isso não causa problemas, mas mesmo assim.

Editar: pesquisa grep

~$ grep -r /run/systemd $HOME/.??*
/home/lunar/.bash_history:/run/systemd/resolve/stub-resolv.conf
/home/lunar/.bash_history:cd /run/systemd/resolve/stub-resolv.conf
/home/lunar/.bash_history:/run/systemd/resolve/stub-resolv.conf
/home/lunar/.cache/sessions/Thunar-24a92edbf-804a-4cab-b0ec-cc7b5d660023:URI=file:///run/systemd
grep: /home/lunar/.mozilla/firefox/3allhj9p.Default-User/places.sqlite-wal: binary file matches
grep: /home/lunar/.mozilla/firefox/3allhj9p.Default-User/places.sqlite: binary file matches

~/.cache/sessions$ cat Thunar-24a92edbf-804a-4cab-b0ec-cc7b5d660023
[Thunar-1651872231-2573164324]
PAGE=0
URI=file:///run/systemd
debian systemd
Martin Hope
Lexx Luxx
Asked: 2021-12-09 05:33:30 +0800 CST
  • 0

Debian 11 nova instalação no novo disco rígido, modo UEFI e disco particionado GPT. O problema é que, ao inicializar o sistema, o erro é mostrado:

"Unidade de disco rígido interna não encontrada. Para resolver esse problema, tente redefinir a unidade. Nenhum dispositivo inicializável - pressione F1 para tentar novamente, F2 para entrar no menu de configuração, F5 para entrar no PSA."

A instalação foi do Live USB, antes disso, criei partições usando o GParted Live. Acho que possivelmente o problema foi quando criei a primeira partição (inicialização), primeiro defini o nome do rótulo 'efi' e tentei renomeá-lo para '/boot/efi': e o GParted imediatamente desligou e parou de responder, então eu tinha manualmente power-Off para forçar o desligamento do PC. Possivelmente, duas barras '/' no nome do rótulo podem causar um problema, mas não tenho certeza.

$ efibootmgr -v
BootCurrent: 000C
Timeout: 1 seconds
BootOrder: 0000,0004,0003,0009,000A,000C
Boot0000* Debian    HD(1,GPT,c906677e-c2c2-42b5-b818-f0b19c046e95,0x800,0xfa000)/File(\EFI\Debian\shimx64.efi)
Boot0003* UEFI OS   HD(2,MBR,0xfcba9dae,0x14000,0x1388000)/File(\EFI\BOOT\BOOTX64.EFI)
Boot0004* UEFI OS   HD(2,MBR,0xb45e11b8,0xaf800,0x600000)/File(\EFI\BOOT\BOOTX64.EFI)
Boot0009* Onboard NIC(IPV4) PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(20474749bc75,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot000A* Onboard NIC(IPV6) PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(20474749bc75,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot000C* UEFI:  USB DISK 2.0 PMAP  PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(3,0)/HD(1,MBR,0xcd9a6b9,0x5d4,0x146a)..BO

EDIT: saída blkid e fdisk

$ sudo blkid
/dev/sdb1: BLOCK_SIZE="2048" UUID="2021-10-09-12-36-57-00" LABEL="d-live nf 11.1.0 xf amd64" TYPE="iso9660" PTUUID="0cd9a6b9" PTTYPE="dos" PARTUUID="0cd9a6b9-01"
/dev/loop0: TYPE="squashfs"
/dev/sda1: LABEL="BOOT" UUID="2F1D-01E6" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="c906677e-c2c2-42b5-b818-f0b19c046e95"
/dev/sda2: LABEL="swap" UUID="1274a782-676a-41b0-8509-92f73bd675c3" TYPE="swap" PARTUUID="4a555697-e713-400d-ae9e-613d028c7893"
/dev/sda3: LABEL="root" UUID="13503165-9c5f-498d-ab5f-0c13f11cbaa6" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="5484dedd-6adf-45af-b7b0-ba105d14528b"
/dev/sda4: LABEL="home" UUID="93c98828-5fb8-4c0e-b6bf-de8d13a9d22e" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="ae15bbdb-4e29-4dfa-aa99-b39e5377a098"
/dev/sdb2: SEC_TYPE="msdos" UUID="DEB0-0001" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="0cd9a6b9-02"

$ sudo fdisk -l
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: TOSHIBA HDWK105 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 0C3CF112-75DD-4197-9A0C-7C92036731C6

Device        Start       End   Sectors   Size Type
/dev/sda1      2048   1026047   1024000   500M EFI System
/dev/sda2   1026048   9414655   8388608     4G Linux swap
/dev/sda3   9414656  61843455  52428800    25G Linux filesystem
/dev/sda4  61843456 976773119 914929664 436.3G Linux filesystem


Disk /dev/sdb: 7.22 GiB, 7747928064 bytes, 15132672 sectors
Disk model: USB DISK 2.0    
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: 0x0cd9a6b9

Device     Boot Start     End Sectors  Size Id Type
/dev/sdb1  *        0 6240351 6240352    3G  0 Empty
/dev/sdb2        1492    6717    5226  2.6M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 2.6 GiB, 2789027840 bytes, 5447320 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

No menu BIOS: [Debian (Drive not present)]

smartctlferramenta mostra que o disco está OK:

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

/etc/fstab conteúdo:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=2F1D-01E6                            /boot/efi      vfat    defaults,noatime 0 2
UUID=13503165-9c5f-498d-ab5f-0c13f11cbaa6 /              ext4    defaults,noatime 0 1
UUID=93c98828-5fb8-4c0e-b6bf-de8d13a9d22e /home          ext4    defaults,noatime 0 2

EDIT: erro parted

root@debian:/# parted /dev/sda1
GNU Parted 3.4
Using /dev/sda1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p                                                                
Model: Unknown (unknown)
Disk /dev/sda1: 524MB
Sector size (logical/physical): 512B/4096B
Partition Table: loop
Disk Flags: 

Number  Start  End    Size   File system  Flags
 1      0.00B  524MB  524MB  fat32

(parted) help toggle                                                      
  toggle [NUMBER [FLAG]]                   toggle the state of FLAG on partition
        NUMBER

    NUMBER is the partition number used by Linux.  On MS-DOS disk labels,
        the primary partitions number from 1 to 4, logical partitions from 5
        onwards.
        FLAG is one of: boot, root, swap, hidden, raid, lvm, lba, hp-service,
        palo, prep, msftres, bios_grub, atvrecv, diag, legacy_boot, msftdata,
        irst, esp, chromeos_kernel, bls_boot
(parted) toggle 1 esp                                                     
Error: No flags supported
(parted) toggle 1 bios_grub                                               
Error: No flags supported
(parted) quit
debian boot
Martin Hope
Lexx Luxx
Asked: 2017-11-27 06:41:16 +0800 CST
  • 1

Sistema embarcado Linux versão 2.6.26.5 integrado. O dispositivo usa o Kernel da imagem completo. Sistema de arquivos armazenado em memória Flash NAND, Hynix NAND 32MiB 3,3V 8 bits.

# printenv
baudrate=115200
ethaddr=FF:FF:FF:FF:FF:FF
netmask=255.255.255.0
ipaddr=192.168.1.1
serverip=192.168.1.100
bootfile=firetux.kernel
bootcmd1=setenv bootargs ${bootargs} && nboot 0x20200000 0 ${image_addr} && bootm 0x20200000
bootcmd2=setenv bootargs ${bootargs} && tftpboot 20200000 firetux.kernel && bootm 20200000
phymode=auto
mtdids=nand0=gen_nand
unlock=yes
verify=y
update.uboot=echo Update u-boot && tftpboot 0x20000000 nandboot.flash && nand erase 0x0 0x03ffff && nand write.jffs2 0x20000000 0x0 ${filesize}
update.kernel=echo Update kernel && tftpboot 0x20000000 uImage && nand erase 0x80000 0x180000 && nand write.jffs2 20000000 0x80000 0x180000
update.romimg=echo Update RomImage && tftpboot 0x20000000 romimage.img && nand erase 0x80000 0x13e0000&& nand write.jffs2 20000000 0x80000 ${filesize}
update.halfimg=echo Update HalfImage && tftpboot 0x20000000 recovery.img && nand erase 0x1460000 0x700000&& nand write.jffs2 20000000 0x1460000 ${filesize}
eraseenv=echo Erase Environment && nand erase 0x60000 0x20000
HwModel=Hw_Model=NXPi02
bootcmd=run bootcmd1
halfImage=half_image=0
cy_boot_code_ver=1.0.1 (Oct  6 2011 - 20:04:00)
RouterMode=Router_Mode=0
stdin=serial
stdout=serial
stderr=serial
bootcmd=run bootcmd1
image_addr=0x80000
bootargs=console=ttyS1,115200n8 rootfstype=squashfs noalign half_image=0 verify=y Hw_Model=NXPi02 Router_Mode=0
ethact=ETN1
bootdelay=3

Precisa fazer backup de algumas áreas da memória NAND (NVRAM) do U-boot, conexão com a placa via interface serial (UART), conexão de rede não está disponível. O U-boot tem certas opções para gerenciar a memória nand:

# help nand
nand info - show available NAND devices
nand device [dev] - show or set current device
nand read - addr off|partition size
nand write - addr off|partition size
    read/write 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
nand erase [clean] [off size] - erase 'size' bytes from
    offset 'off' (entire device if not specified)
nand bad - show bad blocks
nand dump[.oob] off - dump page
nand scrub - really clean NAND erasing bad blocks (UNSAFE)
nand markbad off - mark bad block at offset (UNSAFE)
nand biterr off - make a bit error at offset (UNSAFE)

Em particular,nand dump[.oob] off - dump page

Qual é o endereço nand offset para isso? Não foi especificado o tamanho da partição para despejar. Preciso despejar toda a NVRAM.

Depois que o dispositivo carrega a imagem do Kernel, ele cria 11 partições MTD:

Creating 11 MTD partitions on "gen_nand":
0x00000000-0x00060000 : "u-boot"
0x00060000-0x00080000 : "u-bootenv"
0x00080000-0x01460000 : "ROMIMAGE"
0x01460000-0x01b60000 : "HALFIMAGE"
0x00200000-0x01460000 : "LINUX_ROOTFS"
0x01b60000-0x01d60000 : "HS_FW"
0x01d60000-0x01e60000 : "FPAR"
0x01e60000-0x01ee0000 : "SNOM"
0x01ee0000-0x01f00000 : "EEPROM"
0x01f00000-0x01f80000 : "NVRAM"
0x01f80000-0x02000000 : "CA_DATA"

O 0x01f00000endereço nvram é offset? Qual é o tamanho do nvram? É 0x80000? U-boot também tem comando md - memory display.

=> help md
md - memory display
Usage:
md [.b, .w, .l] address [# of objects]
=>

Eu tentei o comando md.b 0x01f00000 0x80000para exibir nvram no terminal, mas não produz nada, o terminal desliga.

EDIT: [uma adição]

# nand info

Device 0: NAND 32MiB 3,3V 8-bit, sector size 16 KiB
# nand device nand0
Device 0: NAND 32MiB 3,3V 8-bit... is now current device
# nand read 0x20000000 NVRAM

NAND read: mtdparts variable not set, see 'help mtdparts'
incorrect device type in NVRAM
'NVRAM' is not a number
# nand read 0x20000000 0x01f00000 0x00080000

NAND read: device 0 offset 0x1f00000, size 0x80000
 524288 bytes read: OK

BusyBox v1.10.2 (2015-09-06 10:58:05 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
# help

Built-in commands:
-------------------
    . : [ [[ alias bg break cd chdir continue echo eval exec exit
    export false fg hash help jobs let local pwd read readonly return
    set shift source test times trap true type ulimit umask unalias
    unset wait

# ext4write LINUX_ROOTFS /NVRAM.img 0x20000000 0x00080000
/bin/sh: ext4write: not found
partition terminal
Martin Hope
Lexx Luxx
Asked: 2017-11-24 13:07:31 +0800 CST
  • 0

Qual é a sintaxe adequada para o comando setenv bootargs ao usar a sintaxe abreviada para o método? Por exemplo, as variáveis ​​de ambiente do kernel completas são

U-Boot> setenv bootargs console=ttyS1,115200n8 rootfstype=squashfs noalign half_image=0 verify=y Hw_Model=pnx8181 Router_Mode=0

Eu quero adicionar 2 bootargs ao código mencionado singlee init=/bin/sh.

O seguinte comando com sintaxe abreviada está correto?

setenv bootargs ${bootargs} single init=/bin/sh

Nenhuma aspa simples é necessária em qualquer lugar?

linux quoting
Martin Hope
Lexx Luxx
Asked: 2017-11-23 06:52:55 +0800 CST
  • 1

Dispositivo integrado, Linux versão 2.6.26.5, U-Boot 2009.03 bootloader. ARM Linux Kernel Image em flash NAND, carregando de NAND.

Como acessar o sistema de arquivos como usuário root e redefinir a senha root? É possível obter isso fornecendo singleo argumento de inicialização (modo de usuário único) ao kernel do Linux por meio dos parâmetros U-boot? Ou adicionando init=/bin/bashum argumento ao final dos parâmetros de inicialização. A saída bootargse bootcmdas variáveis ​​de ambiente:

Kernel command line: console=ttyS1,115200n8 rootfstype=squashfs noalign half_image=0 verify=y Hw_Model=RZU017 Router_Mode=0
kernel embedded