fonts4eva Posted September 3 Share Posted September 3 Hi All, i had a faulty disk and i replaced it with a brand new drive and unraid can not see the disk in the webui if i remove the disk and re-insert it back dmesg shows when i remove and re-insert the disk so i dont know why its not working. its the same size as the previous one, i have also moved the disk to a new slot to rule that out. the drives are connected via a raid card that is flashed to IT-Mode so i am unable to see if the bios can see the disks i have to rely on the os to check disks. does anyone have any ideas ? diagnostics-20240903-2039.zip Quote Link to comment
JorgeB Posted September 3 Share Posted September 3 18 minutes ago, fonts4eva said: if i remove the disk and re-insert it back dmesg shows when i remove and re-insert the disk Did you do that in the diags posted? If yes, what was the timecode? Quote Link to comment
fonts4eva Posted September 4 Author Share Posted September 4 (edited) 20 hours ago, JorgeB said: Did you do that in the diags posted? If yes, what was the timecode? nah i didnt, ill do that and upload the logs again Edited September 4 by fonts4eva Quote Link to comment
fonts4eva Posted September 4 Author Share Posted September 4 (edited) here is the messages from dmesg when i remove and re-insert the disk. also included the diagnostics zip for good measure. the disk is a Western Digital Ultrastar 8TB DC HC320 Quote [ 220.267517] mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221105000000) [ 220.267524] mpt2sas_cm0: removing handle(0x000b), sas_addr(0x4433221105000000) [ 220.267527] mpt2sas_cm0: enclosure logical id(0x5b8ca3a0ebecae00), slot(6) [ 280.518779] mpt2sas_cm0: handle(0xb) sas_address(0x4433221105000000) port_type(0x1) [ 281.860807] mpt2sas_cm0: log_info(0x31111000): originator(PL), code(0x11), sub_code(0x1000) [ 283.360850] mpt2sas_cm0: log_info(0x31111000): originator(PL), code(0x11), sub_code(0x1000) [ 284.860886] mpt2sas_cm0: log_info(0x31111000): originator(PL), code(0x11), sub_code(0x1000) [ 286.361003] mpt2sas_cm0: log_info(0x31111000): originator(PL), code(0x11), sub_code(0x1000) [ 286.361110] end_device-1:8: add: handle(0x000b), sas_addr(0x4433221105000000) [ 286.361563] mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221105000000) [ 286.361572] mpt2sas_cm0: removing handle(0x000b), sas_addr(0x4433221105000000) [ 286.361577] mpt2sas_cm0: enclosure logical id(0x5b8ca3a0ebecae00), slot(6) diagnostics-20240904-1813.zip Edited September 4 by fonts4eva Quote Link to comment
Solution JorgeB Posted September 4 Solution Share Posted September 4 See if that disk works in another PC, or a different disk with the server. Quote Link to comment
fonts4eva Posted September 4 Author Share Posted September 4 29 minutes ago, JorgeB said: See if that disk works in another PC, or a different disk with the server. looks my brand new drive is dead. i can see it on another machine, in bios and in the os but i cant write to the disk. what's most annoying is i brought this drive a while ago and its no longer under warranty. thanks for your help. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.