509 - RAID!

部署运行你感兴趣的模型镜像

解题思路:1.每一竖排上,如果有奇数个1,则为奇校验,否则为偶校验.

                    2.每一竖排最多可以损坏一个数据。 

                    3.题目中“校验错”的含义:例如,若为E(偶校验),则每一竖排的1都必须是偶数个。是每一排啊

#include
   
    
#include
    
     
#include
     
      
#include
      
#include
       
         using namespace std; int n,k,m,maxnn=1; char buf[10]; string a[20],b[20]; map
        
          p; void mapp(){ p["0000"]="0"; p["0001"]="1";p["0010"]="2";p["0011"]="3"; p["0100"]="4";p["0101"]="5";p["0110"]="6"; p["0111"]="7";p["1000"]="8";p["1001"]="9"; p["1010"]="A";p["1011"]="B";p["1100"]="C"; p["1101"]="D";p["1110"]="E";p["1111"]="F"; } bool solve(){ for(int i=0;i
         
          =2) return false; else if(kase==0&&buf[0]=='E'&&ans%2==1) return false; else if(kase==0&&buf[0]=='O'&&ans%2==0) return false; else if(kase==1&&buf[0]=='E'&&ans%2==0) a[bbs][i]='0'; else if(kase==1&&buf[0]=='E'&&ans%2==1) a[bbs][i]='1'; else if(kase==1&&buf[0]=='O'&&ans%2==0) a[bbs][i]='1'; else if(kase==1&&buf[0]=='O'&&ans%2==1) a[bbs][i]='0'; } return true; } void print(){ cout<<"Disk set "<
          
           <<" is valid, contents are: "; int kase=0;string s; for(int i=0;i
           
            >n&&n){ cin>>k>>m; cin>>buf; for(int i=0;i
            
             >a[i]; string s1,s2; int kase=0; for(int i=0;i
             
            
           
          
         
        
       
     
    
   

您可能感兴趣的与本文相关的镜像

Stable-Diffusion-3.5

Stable-Diffusion-3.5

图片生成
Stable-Diffusion

Stable Diffusion 3.5 (SD 3.5) 是由 Stability AI 推出的新一代文本到图像生成模型,相比 3.0 版本,它提升了图像质量、运行速度和硬件效率

ipxc时sol的打印 [ 26.737004] usb 10-1: Manufacturer: VIA Labs, Inc. [ 26.737005] usb 10-1: SerialNumber: 000000000 [ 26.742166] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.9.auto: option mask 0x0 [ 26.767746] hub 10-1:1.0: USB hub found [ 26.770917] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.9.auto: Registered PMU @ 0x0000006800020000 using 8 counters with Individual filter settings [ 26.774780] hub 10-1:1.0: 4 ports detected [ 26.787188] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.10.auto: option mask 0x0 [ 26.797751] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.10.auto: Registered PMU @ 0x0000007002c20000 using 8 counters with Individual filter settings [ 26.810302] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.11.auto: option mask 0x0 [ 26.816853] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.11.auto: Registered PMU @ 0x0000007200020000 using 8 counters with Individual filter settings [ 26.829963] drop_monitor: Initializing network drop monitor service [ 26.836278] Initializing XFRM netlink socket [ 26.840856] NET: Registered protocol family 10 [ 26.845937] Segment Routing with IPv6 [ 26.849606] NET: Registered protocol family 17 [ 26.854051] Bridge firewalling registered [ 26.858093] 8021q: 802.1Q VLAN Support v1.8 [ 26.862288] Key type dns_resolver registered [ 26.866646] registered taskstats version 1 [ 26.870733] Loading compiled-in X.509 certificates [ 26.875769] zswap: loaded using pool lzo/zbud [ 26.880572] Key type ._fscrypt registered [ 26.884572] Key type .fscrypt registered [ 26.888838] Key type encrypted registered [ 26.892842] ima: No TPM chip found, activating TPM-bypass! [ 26.898317] ima: Allocated hash algorithm: sha1 [ 26.902838] ima: No architecture policies found [ 26.910425] rtc-efi rtc-efi: setting system clock to 2025-11-07T06:45:42 UTC (1762497942) [ 26.930603] md: Waiting for all devices to be available before autodetect [ 26.937379] md: If you don't use raid, use raid=noautodetect [ 26.943403] md: Autodetecting RAID arrays. [ 26.947491] md: autorun ... [ 26.950272] md: ... autorun DONE. [ 26.953597] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 [ 26.961070] Please append a correct "root=" boot option; here are the available partitions: [ 26.969411] 103:00000 7501465944 nvme0n1 [ 26.969412] (driver?) [ 26.975757] 103:00001 614400 nvme0n1p1 81e3b7e6-8a78-4372-9f3a-885e6bf08ab7 [ 26.975757] [ 26.984705] 103:00002 1048576 nvme0n1p2 0c8ca6e5-8738-4244-a4da-c29fc4b35a5a [ 26.984705] [ 26.993652] 103:00003 7499801600 nvme0n1p3 88e13abd-3ac4-4360-bbee-dc2cd42d3cbf [ 26.993653] [ 27.002603] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 27.010853] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.4.241-30.0017.17 #1 [ 27.017799] Hardware name: To be filled by O.E.M. HuaKun TG225 B3/BC85AMDATE, BIOS 10.60 11/05/2025 [ 27.026830] Call trace: [ 27.029265] dump_backtrace+0x0/0x1c0 [ 27.032914] show_stack+0x1c/0x28 [ 27.036217] dump_stack+0xd4/0x10c [ 27.039606] panic+0x16c/0x358 [ 27.042649] mount_block_root+0x2c8/0x368 [ 27.046645] mount_root+0x50/0x5c [ 27.049947] prepare_namespace+0x134/0x178 [ 27.054030] kernel_init_freeable+0x300/0x33c [ 27.058373] kernel_init+0x18/0x110 [ 27.061848] ret_from_fork+0x10/0x18 [ 27.065558] SMP: stopping secondary CPUs [ 27.069513] Kernel Offset: disabled [ 27.072989] CPU features: 0x0000,002d0017,3a408a28 [ 27.077766] Memory Limit: none [ 27.080852] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---
11-08
[ 26.522703] input: Keyboard/Mouse KVM 2.0 as /devices/pci0000:20/0000:20:04.0/0000:22:00.1/usb1/1-1/1-1:1.0/0003:12D1:0001.0001/input/input1 [ 26.565599] usb 9-1: New USB device found, idVendor=2109, idProduct=2817, bcdDevice= 7.c3 [ 26.573764] usb 9-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 26.580886] usb 9-1: Product: USB2.0 Hub [ 26.585924] usb 9-1: Manufacturer: VIA Labs, Inc. [ 26.591397] usb 9-1: SerialNumber: 000000000 [ 26.594600] hid-generic 0003:12D1:0001.0001: input,hidraw0: USB HID v2.00 Keyboard [Keyboard/Mouse KVM 2.0] on usb-0000:22:00.1-1/input0 [ 26.608110] hub 9-1:1.0: USB hub found [ 26.608555] input: Keyboard/Mouse KVM 2.0 as /devices/pci0000:20/0000:20:04.0/0000:22:00.1/usb1/1-1/1-1:1.1/0003:12D1:0001.0002/input/input2 [ 26.612044] hub 9-1:1.0: 4 ports detected [ 26.624483] hid-generic 0003:12D1:0001.0002: input,hidraw1: USB HID v2.00 Mouse [Keyboard/Mouse KVM 2.0] on usb-0000:22:00.1-1/input1 [ 26.640430] usbcore: registered new interface driver usbhid [ 26.645991] usbhid: USB HID core driver [ 26.649894] ashmem: initialized [ 26.653093] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.0.auto: option mask 0x0 [ 26.659567] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.0.auto: Registered PMU @ 0x0000002c08020000 using 8 counters with Individual filter settings [ 26.672023] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.1.auto: option mask 0x0 [ 26.678491] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.1.auto: Registered PMU @ 0x0000002d08020000 using 8 counters with Individual filter settings [ 26.690941] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.2.auto: option mask 0x0 [ 26.697404] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.2.auto: Registered PMU @ 0x0000002000020000 using 8 counters with Individual filter settings [ 26.709858] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.3.auto: option mask 0x0 [ 26.716323] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.3.auto: Registered PMU @ 0x0000002800020000 using 8 counters with Individual filter settings [ 26.717400] usb 10-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 26.728791] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.4.auto: option mask 0x0 [ 26.742328] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.4.auto: Registered PMU @ 0x0000003002c20000 using 8 counters with Individual filter settings [ 26.754782] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.5.auto: option mask 0x0 [ 26.761246] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.5.auto: Registered PMU @ 0x0000003200020000 using 8 counters with Individual filter settings [ 26.773727] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.6.auto: option mask 0x0 [ 26.780196] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.6.auto: Registered PMU @ 0x0000006c08020000 using 8 counters with Individual filter settings [ 26.792651] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.7.auto: option mask 0x0 [ 26.799116] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.7.auto: Registered PMU @ 0x0000006d08020000 using 8 counters with Individual filter settings [ 26.807101] usb 10-1: New USB device found, idVendor=2109, idProduct=0817, bcdDevice= 7.c3 [ 26.811572] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.8.auto: option mask 0x0 [ 26.819783] usb 10-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 26.819784] usb 10-1: Product: USB3.0 Hub [ 26.826248] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.8.auto: Registered PMU @ 0x0000006000020000 using 8 counters with Individual filter settings [ 26.833418] usb 10-1: Manufacturer: VIA Labs, Inc. [ 26.833419] usb 10-1: SerialNumber: 000000000 [ 26.847995] hub 10-1:1.0: USB hub found [ 26.851001] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.9.auto: option mask 0x0 [ 26.856794] hub 10-1:1.0: 4 ports detected [ 26.860904] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.9.auto: Registered PMU @ 0x0000006800020000 using 8 counters with Individual filter settings [ 26.887666] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.10.auto: option mask 0x0 [ 26.894215] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.10.auto: Registered PMU @ 0x0000007002c20000 using 8 counters with Individual filter settings [ 26.906765] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.11.auto: option mask 0x0 [ 26.913316] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.11.auto: Registered PMU @ 0x0000007200020000 using 8 counters with Individual filter settings [ 26.926432] drop_monitor: Initializing network drop monitor service [ 26.932753] Initializing XFRM netlink socket [ 26.937336] NET: Registered protocol family 10 [ 26.942391] Segment Routing with IPv6 [ 26.946056] NET: Registered protocol family 17 [ 26.950504] Bridge firewalling registered [ 26.954545] 8021q: 802.1Q VLAN Support v1.8 [ 26.958744] Key type dns_resolver registered [ 26.963116] registered taskstats version 1 [ 26.967203] Loading compiled-in X.509 certificates [ 26.972205] zswap: loaded using pool lzo/zbud [ 26.976949] Key type ._fscrypt registered [ 26.980950] Key type .fscrypt registered [ 26.985230] Key type encrypted registered [ 26.989236] ima: No TPM chip found, activating TPM-bypass! [ 26.994713] ima: Allocated hash algorithm: sha1 [ 26.999236] ima: No architecture policies found [ 27.007048] rtc-efi rtc-efi: setting system clock to 2025-11-07T07:28:48 UTC (1762500528) [ 27.027449] md: Waiting for all devices to be available before autodetect [ 27.034229] md: If you don't use raid, use raid=noautodetect [ 27.040273] md: Autodetecting RAID arrays. [ 27.044365] md: autorun ... [ 27.047150] md: ... autorun DONE. [ 27.050473] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 [ 27.057945] Please append a correct "root=" boot option; here are the available partitions: [ 27.066286] 103:00000 7501465944 nvme0n1 [ 27.066287] (driver?) [ 27.072637] 103:00001 614400 nvme0n1p1 81e3b7e6-8a78-4372-9f3a-885e6bf08ab7 [ 27.072637] [ 27.081587] 103:00002 1048576 nvme0n1p2 0c8ca6e5-8738-4244-a4da-c29fc4b35a5a [ 27.081587] [ 27.090537] 103:00003 7499801600 nvme0n1p3 88e13abd-3ac4-4360-bbee-dc2cd42d3cbf [ 27.090537] [ 27.099493] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 27.107743] CPU: 10 PID: 1 Comm: swapper/0 Not tainted 5.4.241-30.0017.17 #1 [ 27.114777] Hardware name: To be filled by O.E.M. HuaKun TG225 B3/BC85AMDATE, BIOS 10.60 11/05/2025 [ 27.123807] Call trace: [ 27.126242] dump_backtrace+0x0/0x1c0 [ 27.129891] show_stack+0x1c/0x28 [ 27.133194] dump_stack+0xd4/0x10c [ 27.136582] panic+0x16c/0x358 [ 27.139625] mount_block_root+0x2c8/0x368 [ 27.143621] mount_root+0x50/0x5c [ 27.146923] prepare_namespace+0x134/0x178 [ 27.151006] kernel_init_freeable+0x300/0x33c [ 27.155349] kernel_init+0x18/0x110 [ 27.158825] ret_from_fork+0x10/0x18 [ 27.162534] SMP: stopping secondary CPUs [ 27.166490] Kernel Offset: disabled [ 27.169965] CPU features: 0x0000,002d0017,3a408a28 [ 27.174742] Memory Limit: none [ 27.177829] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---
最新发布
11-08
<think>好的,我现在需要帮助用户在CentOS 9上安装RAID卡驱动。首先,我得理解用户的问题是什么。他们可能在安装CentOS 9时遇到了找不到硬盘的问题,这可能是因为系统没有预装对应的RAID卡驱动。根据提供的引用资料,特别是引用[1]和[2],说明在某些情况下,CentOS安装时需要手动加载RAID驱动,否则无法识别硬盘。用户现在用的是CentOS 9,可能需要类似的步骤。 接下来,我需要参考已有的解决方案。引用[3]中提到了在CentOS 9 Stream安装LSI RAID卡驱动的具体步骤,包括解压驱动包、编译、复制到内核目录等。虽然用户的问题是关于CentOS 9,但CentOS 9 Stream的步骤可能类似,可以作为参考。 首先,需要确认用户的RAID卡型号。不同厂商(如LSI、Adaptec等)的驱动安装方法可能不同。用户需要从官方网站或硬件供应商处获取正确的驱动,并确保其支持CentOS 9。例如,如果用户使用的是LSI MegaRAID卡,可以按照引用[3]中的步骤操作。 然后,安装必要的编译工具和内核头文件,这是编译驱动的前提。CentOS通常使用yum或dnf包管理器,所以需要运行sudo dnf install gcc make kernel-devel kernel-headers来安装这些工具。 接下来,解压驱动包,进入源码目录,执行编译脚本。这里需要注意驱动包是否包含适用于当前内核版本的编译脚本,可能需要根据实际情况调整。编译成功后,将生成的驱动模块(.ko文件)复制到内核的模块目录,并更新模块依赖关系。最后,重启系统并检查驱动是否加载。 另外,引用[2]提到,除了编译驱动,还可以在安装系统时手动加载驱动。如果用户在安装过程中遇到找不到硬盘的问题,可能需要使用安装介质的“inst.drv”参数指定驱动,或者制作包含驱动的自定义ISO。不过,用户已经进入系统安装后的阶段,所以可能更关注如何在已安装的系统上添加驱动。 需要提醒用户注意内核版本的一致性,驱动必须与当前运行的内核版本匹配,否则编译可能会失败。如果用户更新了内核,可能需要重新编译驱动。 此外,驱动安装完成后,使用lspci和dmesg命令检查驱动是否成功加载,以及RAID卡是否被正确识别。如果遇到问题,查看系统日志(如journalctl或/var/log/messages)可能会有帮助。 总结步骤应该是:确认RAID型号→安装依赖→下载驱动→编译安装→更新模块→重启验证。同时需要注意事项,比如内核版本匹配、安全启动可能的影响等。</think>### 如何在 CentOS 9 上安装 RAID 卡驱动? #### 1. **确认 RAID 卡型号与驱动兼容性** - 通过命令 `lspci | grep -i raid` 查看 RAID 卡型号(如 LSI MegaRAID、Adaptec 等)[^3]。 - 从厂商官网下载对应的 Linux 驱动(确保支持 CentOS 9 及当前内核版本)。 #### 2. **安装编译工具与内核头文件** ```bash sudo dnf install gcc make kernel-devel kernel-headers ``` *需保证内核头文件版本与当前运行的内核一致(通过 `uname -r` 查看)*。 #### 3. **编译并安装驱动** - **解压驱动包**: ```bash tar -zxvf megaraid_sas-<版本号>-src.tar.gz cd megaraid_sas-<版本号>/ ``` - **编译驱动**: ```bash ./compile.sh # 或根据驱动包内的说明执行 make 命令 ``` - **复制驱动到内核目录**: ```bash sudo cp megaraid_sas.ko /lib/modules/$(uname -r)/kernel/drivers/scsi/megaraid/ ``` - **更新模块依赖**: ```bash sudo depmod -a ``` #### 4. **加载驱动并验证** - **手动加载驱动**: ```bash sudo modprobe megaraid_sas ``` - **检查驱动状态**: ```bash lspci -nnv | grep -i raid # 确认 RAID 卡信息 dmesg | grep -i megaraid # 查看驱动加载日志 modinfo megaraid_sas # 显示驱动详细信息 ``` #### 5. **持久化配置(重启后生效)** ```bash echo "megaraid_sas" | sudo tee /etc/modules-load.d/megaraid.conf sudo systemctl restart systemd-modules-load ``` #### 6. **安装后验证** - 检查硬盘是否被识别:`lsblk` 或 `fdisk -l`。 - 确认 RAID 状态:通过厂商工具(如 `storcli64` 或 `MegaCLI`)。 --- ### §§ 1. **内核版本一致性**:驱动必须与当前内核版本匹配,否则编译失败。若升级内核,需重新编译驱动。 2. **安全启动**:若系统启用了 Secure Boot,需先禁用或手动签名驱动模块。 3. **驱动签名**:部分场景需对驱动进行签名,参考命令: ```bash sudo /usr/src/kernels/$(uname -r)/scripts/sign-file sha512 /path/to/signing_key.priv /path/to/signing_key.x509 megaraid_sas.ko ``` --- ###
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值