March 7, 201214 yr Hi, I changed my hdd´s to a new case and after connecting everything again I cannot make it work as before. I get the following error on 3 disks: "DISK_NP_MISSING" i attach 2 screen shots: http://i236.photobucket.com/albums/ff75/razzta01/missingdisks.jpg http://i236.photobucket.com/albums/ff75/razzta01/missingdisks2.jpg Can anyone tell me what options do I have to solve it? Let me know if you more info from my system. Rgds.
March 7, 201214 yr Hi, I changed my hdd´s to a new case and after connecting everything again I cannot make it work as before. I get the following error on 3 disks: "DISK_NP_MISSING" i attach 2 screen shots: http://i236.photobucket.com/albums/ff75/razzta01/missingdisks.jpg http://i236.photobucket.com/albums/ff75/razzta01/missingdisks2.jpg Can anyone tell me what options do I have to solve it? Let me know if you more info from my system. Rgds. Do the disks show up in the BIOS? I see two of them in the unMENU screen shot,as not part of the array (they matched serial numbers from those missing) so perhaps all you need to do is stop the array and assign them to their respective slots in the array. The third might just not have the cable seated properly.
March 7, 201214 yr Author Do the disks show up in the BIOS? I see two of them in the unMENU screen shot,as not part of the array (they matched serial numbers from those missing) so perhaps all you need to do is stop the array and assign them to their respective slots in the array. Hi, thx for replay, but how can I "assign them to their respective slots in the array"...you mean connecting the sata cables? or doing it using unmenu? Rgds.
March 8, 201214 yr Do the disks show up in the BIOS? I see two of them in the unMENU screen shot,as not part of the array (they matched serial numbers from those missing) so perhaps all you need to do is stop the array and assign them to their respective slots in the array. Hi, thx for replay, but how can I "assign them to their respective slots in the array"...you mean connecting the sata cables? or doing it using unmenu? Rgds. That would depend on the version of unRAID you are running. On older arrays you use the "devices" page. On new beta's you stop the array and do it on the main web-management page. I'm guessing you are on 4.7 or earlier, since the new beta versions would figure it out on its own.
March 9, 201214 yr Author Hi, i followed your instructions and assigned the recognized disks. After that I did a parity check. I attach the resulting unmenu screen: http://i236.photobucket.com/albums/ff75/razzta01/missingdisks3.jpg ... as you can see disk /mnt/disk3 is not mounted in the array..it does not have any recognized format. Pls, what option do I have now? Let me know if you need the syslog too. Rgds.
March 9, 201214 yr Hi, i followed your instructions and assigned the recognized disks. After that I did a parity check. I hope you performed a non-correcting check. If you did not, then you may have lost the ability to recover what was on the disabled disk. I attach the resulting unmenu screen: http://i236.photobucket.com/albums/ff75/razzta01/missingdisks3.jpg ... as you can see disk /mnt/disk3 is not mounted in the array..it does not have any recognized format. Pls, what option do I have now? Let me know if you need the syslog too. Rgds. Are you sure disk3 was not the old parity disk? Yes... a system log is critical... you're wasting everybody's time unless you supply one. we need to know why disk3 did not mount. You can also help by running the following commands fdisk -lu /dev/sdg and dd if=/dev/sdg count=195 | od -c -A d | sed 30q The output should look a lot like this... Note where the string "R e I s E r 2 F s" appears.... Let's see if yours is at the same address, or one sector further. Output on one of my drives looks like this (it has a file-system starting on sector 63): 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 0.00169403 s, 58.9 MB/s 0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000448 \0 \0 203 \0 \0 \0 ? \0 \0 \0 361 _ 8 : \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000496 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0000512 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0097792 376 \v G \a e \a - \0 \a 212 267 001 022 \0 \0 \0 0097808 \0 \0 \0 \0 \0 \0 \0 \0 004 \0 \0 % 254 227 \ 0097824 204 003 \0 \0 036 \0 \0 \0 \0 \0 \0 \0 \0 020 314 003 0097840 220 \0 002 \0 R e I s E r 2 F s \0 \0 \0 0097856 003 \0 \0 \0 005 \0 217 016 002 \0 \0 \0 204 ] \0 \0 0097872 001 \0 \0 \0 353 300 256 263 242 347 N 347 264 362 315 364 0097888 345 V 253 366 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0097904 \0 \0 \0 \0 \a \0 036 \0 255 262 303 M \0 N 355 \0 0097920 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 Do NOT format the disk, do NOT run any more parity checks (wiping out parity is the LAST thing you want to do when you have a disk failure. You should NEVER calculate parity with a disk invalid... unfortunately, with the number of "writes" to the parity drive evident in your screen shot, odds are it is already been overwritten.)
March 9, 201214 yr Author Hi Joe, here is my last syslog. I am sure disk3 was not the old parity disk! I did a normal parity check, because I thought I can recover the info on disk3 since I have all other disks+the parity one. I hope I did not make a mistake. I will try the commands you mentioned. syslog-2012-03-09.txt
March 9, 201214 yr Author root@Tower:~# fdisk -lu /dev/sdg dd if= Disk /dev/sdg: 2000.3 GB, 2000397852160 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907027055 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0xb2aa4e90 Device Boot Start End Blocks Id System /dev/sdg1 2048 3907026943 1953512448 7 HPFS/NTFS root@Tower:~# dd if=/dev/sdg count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 9.5263 s, 10.5 kB/s 0000000 3 300 216 320 274 \0 | 216 300 216 330 276 \0 | 277 \0 0000016 006 271 \0 002 374 363 244 P h 034 006 313 373 271 004 \0 0000032 275 276 \a 200 ~ \0 \0 | \v 017 205 016 001 203 305 020 0000048 342 361 315 030 210 V \0 U 306 F 021 005 306 F 020 \0 0000064 264 A 273 252 U 315 023 ] r 017 201 373 U 252 u \t 0000080 367 301 001 \0 t 003 376 F 020 f ` 200 ~ 020 \0 t 0000096 & f h \0 \0 \0 \0 f 377 v \b h \0 \0 h \0 0000112 | h 001 \0 h 020 \0 264 B 212 V \0 213 364 315 023 0000128 237 203 304 020 236 353 024 270 001 002 273 \0 | 212 V \0 0000144 212 v 001 212 N 002 212 n 003 315 023 f a s 034 376 0000160 N 021 u \f 200 ~ \0 200 017 204 212 \0 262 200 353 204 0000176 U 2 344 212 V \0 315 023 ] 353 236 201 > 376 } U 0000192 252 u n 377 v \0 350 215 \0 u 027 372 260 321 346 d 0000208 350 203 \0 260 337 346 ` 350 | \0 260 377 346 d 350 u 0000224 \0 373 270 \0 273 315 032 f # 300 u ; f 201 373 T 0000240 C P A u 2 201 371 002 001 r , f h \a 273 \0 0000256 \0 f h \0 002 \0 \0 f h \b \0 \0 \0 f S f 0000272 S f U f h \0 \0 \0 \0 f h \0 | \0 \0 f 0000288 a h \0 \0 \a 315 032 Z 2 366 352 \0 | \0 \0 315 0000304 030 240 267 \a 353 \b 240 266 \a 353 003 240 265 \a 2 344 0000320 005 \0 \a 213 360 254 < \0 t \t 273 \a \0 264 016 315 0000336 020 353 362 364 353 375 + 311 344 d 353 \0 $ 002 340 370 0000352 $ 002 303 I n v a l i d p a r t i 0000368 t i o n t a b l e \0 E r r o r 0000384 l o a d i n g o p e r a t i 0000400 n g s y s t e m \0 M i s s i n 0000416 g o p e r a t i n g s y s t 0000432 e m \0 \0 \0 c { 232 220 N 252 262 \0 \0 \0 0000448 ! \0 \a 376 377 377 \0 \b \0 \0 \0 x 340 350 \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 I guess it is missing.
March 9, 201214 yr root@Tower:~# fdisk -lu /dev/sdg dd if= Disk /dev/sdg: 2000.3 GB, 2000397852160 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907027055 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0xb2aa4e90 Device Boot Start End Blocks Id System /dev/sdg1 2048 3907026943 1953512448 7 HPFS/NTFS root@Tower:~# dd if=/dev/sdg count=195 | od -c -A d | sed 30q 195+0 records in 195+0 records out 99840 bytes (100 kB) copied, 9.5263 s, 10.5 kB/s 0000000 3 300 216 320 274 \0 | 216 300 216 330 276 \0 | 277 \0 0000016 006 271 \0 002 374 363 244 P h 034 006 313 373 271 004 \0 0000032 275 276 \a 200 ~ \0 \0 | \v 017 205 016 001 203 305 020 0000048 342 361 315 030 210 V \0 U 306 F 021 005 306 F 020 \0 0000064 264 A 273 252 U 315 023 ] r 017 201 373 U 252 u \t 0000080 367 301 001 \0 t 003 376 F 020 f ` 200 ~ 020 \0 t 0000096 & f h \0 \0 \0 \0 f 377 v \b h \0 \0 h \0 0000112 | h 001 \0 h 020 \0 264 B 212 V \0 213 364 315 023 0000128 237 203 304 020 236 353 024 270 001 002 273 \0 | 212 V \0 0000144 212 v 001 212 N 002 212 n 003 315 023 f a s 034 376 0000160 N 021 u \f 200 ~ \0 200 017 204 212 \0 262 200 353 204 0000176 U 2 344 212 V \0 315 023 ] 353 236 201 > 376 } U 0000192 252 u n 377 v \0 350 215 \0 u 027 372 260 321 346 d 0000208 350 203 \0 260 337 346 ` 350 | \0 260 377 346 d 350 u 0000224 \0 373 270 \0 273 315 032 f # 300 u ; f 201 373 T 0000240 C P A u 2 201 371 002 001 r , f h \a 273 \0 0000256 \0 f h \0 002 \0 \0 f h \b \0 \0 \0 f S f 0000272 S f U f h \0 \0 \0 \0 f h \0 | \0 \0 f 0000288 a h \0 \0 \a 315 032 Z 2 366 352 \0 | \0 \0 315 0000304 030 240 267 \a 353 \b 240 266 \a 353 003 240 265 \a 2 344 0000320 005 \0 \a 213 360 254 < \0 t \t 273 \a \0 264 016 315 0000336 020 353 362 364 353 375 + 311 344 d 353 \0 $ 002 340 370 0000352 $ 002 303 I n v a l i d p a r t i 0000368 t i o n t a b l e \0 E r r o r 0000384 l o a d i n g o p e r a t i 0000400 n g s y s t e m \0 M i s s i n 0000416 g o p e r a t i n g s y s t 0000432 e m \0 \0 \0 c { 232 220 N 252 262 \0 \0 \0 0000448 ! \0 \a 376 377 377 \0 \b \0 \0 \0 x 340 350 \0 \0 0000464 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 I guess it is missing. disk3 is not a disk that was ever in unRAID. It is apparently an NTFS disk. it is not partitioned as a disk in unRAID would be. Are you perhaps copying data from other disks... in which case, it is one of the other disks. It is most certainly not a reiserfs file-system, and not partitioned as unRAID would require... Sorry... Which "check" button did you use to check parity? The un-correcting one in unMENU, or the one in the stock unRAID interface? Joe L.
March 11, 201214 yr Author Hi Joe, "It is most certainly not a reiserfs file-system, and not partitioned as unRAID would require..." .. i am surprised too, i guess it is one of my spare disks. i checked the" unraid main" shares set up and it only shows: disk1,disk2,disk3,disk5,disk6. disk4 was in the array but not assigned to any share and in fact it was empty, now I took it out. If I sum up all the disks in total i have 5disks. I guess the parity one is not here, so in total 6disks. I think this makes senseto me. "Which "check" button did you use to check parity? The un-correcting one in unMENU, or the one in the stock unRAID interface?" I used "unraid main" in unMENU. I already did a format to this disk. I still get in unMenu the following error in red: DISK_DSBL..any ideas? i attach screenshots: http://i236.photobucket.com/albums/ff75/razzta01/missingdisk5.jpg http://i236.photobucket.com/albums/ff75/razzta01/missingdisks3.jpg
March 12, 201214 yr Author Hi, can anyone help regarding error message "DISK_DSBL" as mentioned in my previous post. Rgds.
March 13, 201214 yr Author "Which "check" button did you use to check parity? The un-correcting one in unMENU, or the one in the stock unRAID interface?" I used "unraid main" in unMENU. Pls, can you tell me the difference?
March 13, 201214 yr "Which "check" button did you use to check parity? The un-correcting one in unMENU, or the one in the stock unRAID interface?" I used "unraid main" in unMENU. Pls, can you tell me the difference? unRAID Main in unMENU is the stock unRAID interface, but accessed through unMENU top menu.. Therefore, you used the correcting parity check, exactly as if you had used the unRAID web-interface directly.
March 13, 201214 yr Author Hi Joe, I am getting crazy. I thought disconnecting sata cables and connecting them back -exactly the same way as before- should bring my array to the same status. But it is not the case. I attach 2 screeshots: 1) BEFORE: it was the status of my array after running the "correcting parity check". As you can see everything was fine, except I got one error: "DISK_DSBL" on disk3 ... I would appreciate if you explain to me what it means. http://i236.photobucket.com/albums/ff75/razzta01/missingdisk5.jpg 2) NOW: actual status. As you can see all disks are in the same position as before, but: -on disks5,6 I get error "DISK_NP_MISSING"..but if I go to unRAID Main_Devices, and from theer you go to disk5 and disk6 ... there are no disks available to be assigned to this 2 slots. -on disk3 I get "NEW DISK", but although you see on the screenshot "/dev/sdb ST32000542AS_9XW070JL" if you go to unRAID Main_Devices, this one is only shown "SAMSUNG_HD103SJ_S246JDWZ101892". I don´t understand it. Pls, let me know what command I should run to solve this. I tried a non-correcting parity check (I mean: reiserfsck --check), but it is not possible. Rgds http://i236.photobucket.com/albums/ff75/razzta01/cc.png syslog-2012-03-13.txt
March 14, 201214 yr Hi Joe, I am getting crazy. I thought disconnecting sata cables and connecting them back -exactly the same way as before- should bring my array to the same status. But it is not the case. I attach 2 screeshots: 1) BEFORE: it was the status of my array after running the "correcting parity check". As you can see everything was fine, except I got one error: "DISK_DSBL" on disk3 ... I would appreciate if you explain to me what it means. Disk 3 has been disabled because a "write" to it failed. It is now being simulated by parity in combination with all the other data drives. http://i236.photobucket.com/albums/ff75/razzta01/missingdisk5.jpg 2) NOW: actual status. As you can see all disks are in the same position as before, but: -on disks5,6 I get error "DISK_NP_MISSING"..but if I go to unRAID Main_Devices, and from theer you go to disk5 and disk6 ... there are no disks available to be assigned to this 2 slots. -on disk3 I get "NEW DISK", but although you see on the screenshot "/dev/sdb ST32000542AS_9XW070JL" if you go to unRAID Main_Devices, this one is only shown "SAMSUNG_HD103SJ_S246JDWZ101892". I don´t understand it. Pls, let me know what command I should run to solve this. I tried a non-correcting parity check (I mean: reiserfsck --check), but it is not possible. Rgds http://i236.photobucket.com/albums/ff75/razzta01/cc.png DISK_NP_MISSING indicates the disks are Not-Present (do they show in the BIOS when you boot? ) perhaps the cabling to those two drives is not plugged in all the way? Do they share a cable? or power connector? or splitter? or disk controller board? disk3 shows as new because you started the array with it un-assigned, so unRAID forgot its model/serial number. It is probably OK at this point, but you have two disks that are not working (they have no power, or their cables are loose, etc) That is why they do not show in the drop-down list, it is because they are not being detected. Power down, re-seat the power and data connections to those two disks. Power up, enter the BIOS. Do the disks show up there. If the BIOS does not see them, unRAID will not. Once the BIOS sees them, they should not show as NP_MISSING and will show up in the drop-down lists for assignment. one last thing. reiserfsck is a file system check. It has absolutely nothing to do with parity. you can have perfect parity, and a corrupted file system. You can have a perfect file-system, and bad parity. Joe L.
March 14, 201214 yr Author Hi Joe, thx for being patient with me. Funny, but the last 2 disks did appear on the BIOS of my Adaptec card, but not in Unraid. I did change power cables and now both appear in Unraid too. So this point is SOLVED. Hi Joe, I am getting crazy. I thought disconnecting sata cables and connecting them back -exactly the same way as before- should bring my array to the same status. But it is not the case. I attach 2 screeshots: 1) BEFORE: it was the status of my array after running the "correcting parity check". As you can see everything was fine, except I got one error: "DISK_DSBL" on disk3 ... I would appreciate if you explain to me what it means. Disk 3 has been disabled because a "write" to it failed. It is now being simulated by parity in combination with all the other data drives. I still get the "DISK_DSBL" on disk3. What should I do now? Is there any way to tell Unraid to solve it? I don´t want to start my array since I finally can solve this. Rgds.
March 15, 201214 yr Author Hi! Here is the SMART STATUS REPORT FOR DISK3: Rgds. Statistics for /dev/sdg ST32000542AS_9XW070JL smartctl -a -d ata /dev/sdg smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST32000542AS Serial Number: 9XW070JL Firmware Version: CC34 User Capacity: 2,000,397,852,160 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Thu Mar 15 18:22:39 2012 UTC SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 623) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail Always - 74092716 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 313 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 067 060 030 Pre-fail Always - 6130347 9 Power_On_Hours 0x0032 091 091 000 Old_age Always - 8510 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 303 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 12885098499 189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2 190 Airflow_Temperature_Cel 0x0022 073 058 045 Old_age Always - 27 (Lifetime Min/Max 20/27) 194 Temperature_Celsius 0x0022 027 042 000 Old_age Always - 27 (0 19 0 0) 195 Hardware_ECC_Recovered 0x001a 040 026 000 Old_age Always - 74092716 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 194 000 Old_age Always - 3976 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 225958229451709 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3684650875 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3149980963 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Interrupted (host reset) 90% 8508 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. 2) SHORT SMART TEST
March 17, 201214 yr Author Hi, just wondering, i think i have no single green hdd. Let me know why you think so, pls. Rgds.
March 18, 201214 yr Author Sorry mate, I thought you meant green drives=a hard disk that uses AF, lower rpm, less power consumption, etc... but you meant the green dot next to each disk in the unraid interface. Yes, all other disks have a green dot. I need to solve this, since I need to start using my array again as storage for my media. I haven´t used it yet till I solve this issue. Let me know what can I do. Rgds.
March 18, 201214 yr Author Sorry mate, I thought you meant green drives=a hard disk that uses AF, lower rpm, less power consumption, etc... but you meant the green dot next to each disk in the unraid interface. Yes, all other disks have a green dot. I need to solve this, since I need to start using my array again as storage for my media. I haven´t used it yet till I solve this issue. Let me know what can I do. Rgds. Also, what is the next step I should do: -run a parity check? -change disk3 and use a new spare hdd? -any other option?
March 19, 201214 yr Rebuild disk3 using the same drive. Start the array with disk 3 unassigned. Then assign disk 3 and restart the array. disk 3 will rebuild. Do a parity check after the rebuild.
March 20, 201214 yr Author Thx dgaschk! I finally solved this point . Now, before I close this post, just one more question.I have the following mapping of my actual physical sata ports in my MB/raid card vs the disks in actual array: array mb port disk device in array disk ID 1 parity 5yd4178p (only last part of p/n) 2 disk1 5yd3qesa 3 disk2 5yd40jnv 4 disk39xw070jl 5xw0r0sz 5 disk49xw07wdc 9xw070jl 6 raidcard disk55xw0r0sz 01892 7 raidcard disk601892 9xw07wdc 8 raidcard disk7 5yd534w4 As you can see I marked some disks in red. For example, the disk3 shown in array is 9xw070jl, but in mb´s sata port4 i have connected 5xw0r0sz. And 5xw0r0sz is assigned in my array to disk5. My question is if this is ok or do i need to take any corrective action? Or: is there a way to unassign the mentioned disks, and then reassign them back with the correct mapping to the mb ports? Rgds, and thx again for the help provided to me in the previous days!
Archived
This topic is now archived and is closed to further replies.