telegram_138149119
@telegram_138149119:nichi.co
94 messages · Page 1 of 1
telegram_138149119
* 就比如你的照片,手机里一份,电脑里一份,还有一份(加密)存在网盘。
telegram_138149119
就比如你的照片,手机里一份,电脑里一份,还有一份(加密)存在网盘
telegram_138149119
* 重要文件,有3个副本,存在2个不同介质上,1份为异地备份
telegram_138149119
重要文件,3份拷贝,存在2个不同介质上,1份为异地备份
telegram_138149119
3-2-1文件备份原则你知道吗?
telegram_138149119
* 自己买个rk3588再配一个机械盘就行了(ot了
telegram_138149119
自己买个rk3588再配一个机械盘就行了(ot
telegram_138149119
推迟也好(
telegram_138149119
跑PT有啥要求?
telegram_138149119
[m.image] (跑
telegram_138149119
(有时间的话,让他跑完
telegram_138149119
连进去之后把btrfs check的输出重定向到文件,然后发出来
telegram_138149119
win10自带OpenSSH
telegram_138149119
然后你会用ssh连进archiso么
telegram_138149119
你进archiso
telegram_138149119
没问题
telegram_138149119
或者这个链已经死了
telegram_138149119
就是运气
telegram_138149119
先看一下这个 @zerodegress2023
telegram_138149119
先停了吧
telegram_138149119
内存是DDR4?
telegram_138149119
看下内存有无问题
telegram_138149119
先跑memtest(泛指)吧
telegram_138149119
* 那就memtest64+(
telegram_138149119
memtest64+(
telegram_138149119
我建议先跑memtest,你这么多error,btrfs check估计没多大意义了,数据大概率已经无了
telegram_138149119
或者先在这台机器上跑memtest
telegram_138149119
你有另外一台机器么
telegram_138149119
你先这样
telegram_138149119
草
telegram_138149119
现在到哪一步了?
telegram_138149119
以及有条件的话,跑memtest
telegram_138149119
* kernel版本?有无kernel panic或者强制关机?
telegram_138149119
kernel版本?有无kernel panic或者强制关基?
telegram_138149119
* 你这个fi usage太奇葩了
telegram_138149119
我第一次见
telegram_138149119
你这个df太奇葩了
telegram_138149119
你是两个盘组成一个文件系统?
telegram_138149119
ssd型号?
telegram_138149119
check之前确保没挂载
telegram_138149119
* 草
telegram_138149119
艹
telegram_138149119
😭这下真要换了
telegram_138149119
坏消息,一启动就死了
telegram_138149119
😭下次回家的时候换掉吧
telegram_138149119
是的
telegram_138149119
似乎要等drm(?)开始之后才能正常看到画面
telegram_138149119
nope
telegram_138149119
我知道,我的意思是不太方便看结果(
telegram_138149119
😭这不是机器不在身边吗,在老家
telegram_138149119
* 嗯,但是其他的都是正常进系统了,然后大概15分钟左右就突然没响应
telegram_138149119
嗯,但是其他的都是正常进系统了
telegram_138149119
难道真的是内存坏了吗
telegram_138149119
这个只是一次启动过程里出的(
telegram_138149119
😡已经被折腾得吐血了
telegram_138149119
是
telegram_138149119
* 这个看不到的问题大致是因为VGA转HDMI芯片和nanokvm兼容性问题(
telegram_138149119
这个看不到的问题大致是因为VGA转HDMI芯片和nanokvm兼容性问题
telegram_138149119
* 目前做不到,BIOS阶段的画面远程看不到(我也不知道为啥)
telegram_138149119
目前做不到,BIOS阶段的画面远程看不到
telegram_138149119
我有一次 machine-id 出问题就是它
telegram_138149119
之前长期运行正常
telegram_138149119
* 一个2个月不用的设备,春节回家的时候给他点亮了
telegram_138149119
* 屏幕没有东西
telegram_138149119
* 一个长期不用的设备,春节回家的时候给他点亮了
telegram_138149119
一个长期不用的设备,春节回家的时候给他弄伤了
telegram_138149119
没有东西
telegram_138149119
* 硬件看门狗看了,应该是关掉的;温度也正常
telegram_138149119
硬件看门狗看了,应该是关掉的
telegram_138149119
但是我没在dmesg里面看到任何东西
telegram_138149119
我的NAS大概15分钟左右会自动重启
telegram_138149119
我现在碰到一个问题
telegram_138149119
emmm
telegram_138149119
* https://pastebin.com/bvu5bTGZ
telegram_138149119
https://pastebin.com/bvu5bTGZ
telegram_138149119
艹,太长了
telegram_138149119
115.722969] ? __pfx_napi_threaded_poll+0x10/0x10 [ 115.723770] napi_threaded_poll+0x71/0xa0 [ 115.724574] kthread+0xfc/0x240 [ 115.725380] ? __pfx_kthread+0x10/0x10 [ 115.726192] ret_from_fork+0x1c2/0x1f0 [ 115.726993] ? __pfx_kthread+0x10/0x10 [ 115.727782] ret_from_fork_asm+0x1a/0x30 [ 115.728575] </TASK> [ 115.729350] Modules linked in: dm_crypt encrypted_keys trusted asn1_encoder tee wireguard overlay libcurve25519 ip6_udp_tunnel udp_tunnel cfg80211 rfkill ip6t_REJECT nf_reject_ipv6 xt_tcpudp ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 nct6775 nct6775_core xt_conntrack hwmon_vid nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter ip_tables x_tables intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel jc42 kvm at24 irqbypass polyval_clmulni ghash_clmulni_intel aesni_intel i2c_i801 rapl intel_cstate nls_iso8859_1 i2c_smbus vfat intel_uncore i2c_mux fat iTCO_wdt pcspkr e1000e intel_pmc_bxt ptp ipmi_ssif iTCO_vendor_support pps_core acpi_ipmi ipmi_si ipmi_devintf video intel_oc_wdt joydev ipmi_msghandler wmi ie31200_edac dm_mod mousedev mac_hid sch_fq tcp_bbr tcp_lp nfnetlink mpt3sas mgag200 raid_class i2c_algo_bit lpc_ich scsi_transport_sas [ 115.736074] CR2: ffffffff8945d289 [ 115.736844] ---[ end trace 0000000000000000 ]--- [ 115.855561] RIP: 0010:refill_obj_stock+0x8f/0x240 [ 115.856198] Code: f8 0f 84 a4 00 00 00 48 89 ef 44 89 4c 24 04 e8 a7 f2 ff ff e8 e2 21 d2 ff 49 8b 04 24 44 8b 4c 24 04 a8 03 0f 85 8a 01 00 00 <65> 48 ff 00 44 89 4c 24 04 e8 f3 a3 d2 ff 41 8b 44 24 18 44 8b 4c [ 115.857483] RSP: 0018:ffffcd1cc4077ab8 EFLAGS: 00010246 [ 115.858139] RAX: 0000000000000000 RBX: 00000000000000c8 RCX: ffffed1cbfa00000 [ 115.858795] RDX: ffff895ddf149b00 RSI: 0000000000000001 RDI: ffff895ddf149b00 [ 115.859447] RBP: ffff89648fc33a80 R08: 0000000000000006 R09: 0000000000000006 [ 115.860093] R10: 0000000000000240 R11: 0000000000000000 R12: ffff895de4b800c0 [ 115.860736] R13: ffff8964affb9280 R14: 00000000ffffff38 R15: ffffcd1cc4077b50 [ 115.861386] FS: 0000000000000000(0000) GS:ffff8964d232f000(0000) knlGS:0000000000000000 [ 115.862036] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 115.862679] CR2: ffffffff8945d289 CR3: 000000068f624003 CR4: 00000000001726f0 [ 115.863335] Kernel panic - not syncing: Fatal exception in interrupt [ 115.863390] Kernel Offset: 0x39800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
telegram_138149119
Panic Report
Arch: x86_64
Version: 6.18.9-arch1-2
[ 114.731780] ? __wake_up_klogd+0x4e/0x80 [ 114.731796] ? vprintk_emit+0x2d4/0x340 [ 114.731824] ? _printk+0x6b/0x90 [ 114.731834] do_task_dead+0x4b/0xb0 [ 114.731868] make_task_dead.cold+0x10a/0x116 [ 114.731899] rewind_stack_and_make_dead+0x16/0x20 [ 114.731909] RIP: 0033:0x7fc3bc852000 [ 114.732065] Code: Unable to access opcode bytes at 0x7fc3bc851fd6. [ 114.732068] RSP: 002b:00007ffea9dbbc48 EFLAGS: 00010206 [ 114.732078] RAX: 00007fc3bc852000 RBX: 00007fc3bd895000 RCX: 00007ffea9dbbd28 [ 114.732101] RDX: 00007ffea9dbbd28 RSI: 00007ffea9dbbce8 RDI: 0000000000000007 [ 114.732112] RBP: 00007ffea9dbbc80 R08: 00007ffea9dbce28 R09: 00007ffea9dbb900 [ 114.732122] R10: 00007ffea9dbb900 R11: 0000000000000203 R12: 0000000000000007 [ 114.732125] R13: 00007ffea9dbbce8 R14: 00007ffea9dbbd28 R15: 00007fc3bda392e0 [ 114.732144] </TASK> [ 114.986849] ehci-pci 0000:00:1d.0: fatal error [ 114.987560] ehci-pci 0000:00:1d.0: HC died; cleaning up [ 114.998502] usb 2-1: USB disconnect, device number 2 [ 114.999509] usb 2-1.1: USB disconnect, device number 3 [ 115.005758] hid-generic 0003:051D:0002.0006: usb_submit_urb(ctrl) failed: -19 [ 115.026238] hid-generic 0003:051D:0002.0006: usb_submit_urb(ctrl) failed: -19 [ 115.046405] hid-generic 0003:051D:0002.0006: usb_submit_urb(ctrl) failed: -19 [ 115.087553] hid-generic 0003:051D:0002.0006: usb_submit_urb(ctrl) failed: -19 [ 115.127761] hid-generic 0003:051D:0002.0006: usb_submit_urb(ctrl) failed: -19 [ 115.687094] BUG: unable to handle page fault for address: ffffffff8945d289 [ 115.688020] #PF: supervisor write access in kernel mode [ 115.688896] #PF: error_code(0x0002) - not-present page [ 115.689773] PGD 68f629067 P4D 68f629067 PUD 68f62a063 PMD 0 [ 115.690658] Oops: Oops: 0002 [#4] SMP PTI [ 115.691538] CPU: 1 UID: 0 PID: 901 Comm: napi/wg0-0 Tainted: G D W 6.18.9-arch1-2 #1 PREEMPT(full) acc0345693780c55f83aaf9a0c9efd10d8da358f [ 115.693289] Tainted: [D]=DIE, [W]=WARN [ 115.694131] Hardware name: Supermicro X9SCL/X9SCM/X9SCL/X9SCM, BIOS 2.3a 01/06/2021 [ 115.694971] RIP: 0010:tcp_ack+0x8f1/0x1660 [ 115.695794] Code: 83 b0 06 00 00 44 8b 5c 24 44 4c 89 c2 48 29 c2 b8 00 00 00 00 48 0f 48 d0 4c 2b 44 24 20 b8 00 00 00 00 4c 0f 48 c0 45 85 db <0f> 94 c0 89 d2 45 89 c0 44 84 d0 74 0b 83 7c 24 0c 01 0f 84 28 07 [ 115.697466] RSP: 0018:ffffcd1cc2dc38b0 EFLAGS: 00010246 [ 115.698287] RAX: 0000000000000000 RBX: ffff895de49c5580 RCX: 00000000fca23ab1 [ 115.699094] RDX: 000000000001a959 RSI: ffff895ddc781e00 RDI: ffff895de49c5580 [ 115.699882] RBP: ffff895ddc781e00 R08: 0000000000008a46 R09: ffffcd1cc2dc3940 [ 115.700698] R10: 0000000000000001 R11: 0000000000000000 R12: 00000000fca23af9 [ 115.701492] R13: 00000000fca23ab1 R14: 0000000000000204 R15: ffff895d86045600 [ 115.702279] FS: 0000000000000000(0000) GS:ffff8964d232f000(0000) knlGS:0000000000000000 [ 115.703086] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 115.703898] CR2: ffffffff8945d289 CR3: 000000068f624003 CR4: 00000000001726f0 [ 115.704737] Call Trace: [ 115.705558] <TASK> [ 115.706384] ? nf_conntrack_tcp_packet+0x9ec/0x17b0 [nf_conntrack ae3ae3f014ce84e5ce96e4960e8682ba63b74bf5] [ 115.707305] tcp_rcv_established+0x557/0xc20 [ 115.708178] tcp_v4_do_rcv+0x1e7/0x380 [ 115.709048] tcp_v4_rcv+0xe45/0x1560 [ 115.709943] ? raw_local_deliver+0xd0/0x2b0 [ 115.710814] ? ip_route_use_hint+0x133/0x1b0 [ 115.711664] ip_protocol_deliver_rcu+0x2c/0x170 [ 115.712466] ip_local_deliver_finish+0x85/0x100 [ 115.713262] ip_sublist_rcv+0x2c9/0x370 [ 115.714053] ? __pfx_ip_rcv_finish+0x10/0x10 [ 115.714835] ip_list_rcv+0x138/0x170 [ 115.715615] __netif_receive_skb_list_core+0x2a3/0x2d0 [ 115.716511] netif_receive_skb_list_internal+0x1d5/0x310 [ 115.717297] ? __mod_timer+0x123/0x340 [ 115.718080] napi_complete_done+0x80/0x1b0 [ 115.718858] wg_packet_rx_poll+0x3f9/0x8b0 [wireguard 03c220bfeb91096c8bfc46785cada4ce1ffb1fd8] [ 115.719799] ? psi_task_switch+0x113/0x2a0 [ 115.720598] __napi_poll+0x31/0x1e0 [ 115.721390] ? __schedule+0x420/0x1320 [ 115.722179] napi_threaded_poll_loop+0x16b/0x1c0 [
telegram_138149119
(扫了之后发现太长了
telegram_138149119
kernel panic
telegram_138149119
kp的二维码怎么发比较好
telegram_138149119
懂了
telegram_138149119
CPU渲染?
telegram_138149119
* initramfs是为了让你能挂 / 从而访问 /etc/fstab 的
telegram_138149119
initramfs是为了让你能挂/从而访问 /etc/fstab的
telegram_138149119
fallback到vesa是吧
telegram_138149119
懂了
telegram_138149119
艹
telegram_138149119
这个是为啥能解决问题
telegram_138149119
你是不是写错fstab了?
telegram_138149119
efi怎么会挂不上
telegram_138149119
原来这个可以skip掉root密码啊
telegram_138149119
学会了(
telegram_138149119
第一次见
Page 1 / 1