Everything posted by mew0717
-
Strange Drive Problem Recognition problem
OK.. So I've read a lot about what could be wrong and tried reconnecting my cables (#1 issue found here) but I'm not sure thats the solution, so I thought I'd explain the problem and see if anyone has any suggestions or ideas. I'm running unraid on a SuperMicro 6047R-E1R24N. Its the SCE-846 (24 Bay) Chassis on a X9DR3-LN4F+ Motherboard. I currently have 18 Drives (1 Partiy, 1 SSD and 16 Data drives ) in the actual 24 bay chassis. (There are also some nvme SSDs on an m.2 card as well that i use a cache pools). With the array stopped, If i remove a drive (and it lists as missing in the UI), when i put it back in I only can recognize it again by restarting the server. If i add a brand new drive (with or without the array running), it doesn't show up in the UI. I've checked the LSI in the BIOS and that new disk isn't being recognized it at all, even when I restart the server. I've tried moving it to different spots as well. The fact that the server is able to recognize existing drives and they are in various locations leads me (though i am quite inexperienced) to think its not a connection issue but maybe something else. This is where my current drives are located in the array: Bay 23 = Parity, Bay 24 = Cache SSD Does anyone have any ideas on what to do? happy to upload any logs that you think would be helpful.
-
[Plugin] Nvidia-Driver
Well new card seems to be working just fine... so problem is solved
-
[Plugin] Nvidia-Driver
still nothing, so i'm getting a new card tomorrow to try again. Will let you know if that works.
-
[Plugin] Nvidia-Driver
I wonder if it got fried. It showed up fine at first, then it ended up getting to around 96c and thats when i first saw the error. Does / can that happen?
-
[Plugin] Nvidia-Driver
Hi everyone. I'm having a similar issue with the error: I've got a Tesla P4... and Oddly enough it was working fine.. But it was getting really hot and I saw this error...... So i took it out, got a fan adapter for it that i'm powering w/a different power supply, and I still have this SMI issue. I've attached diagnostics, but I hope it doesn't suggest there is an issue with the actual card. I've reinsalled the driver, I'm moved the card to a different PCIE and still not able to get passed this error. Any thoughts or suggestions would be greatly appreciated. odyssey-diagnostics-20240425-1029.zip
-
Cant Assign 14TB Drives to my array
The Solution to this is above, but it will require a little digging. For those who want the digging done for them, here's the TL'DR. - This thread is what I used to find the answer (it's a link to another thread which you can get to in the thread posted above) - This page with the actual solution. Ultimately once I confirmed there was protection, this was the only thing i needed to do... sg_format --format --fmtpinfo=0 /dev/sda where /sda is the name of the disk you want to format. There was a lot of talk about sg3 tools etc, but i didnt need those in the end. One tip ... Formatting these drives takes a long, long time. Im not familiar enough to know how to see the status of the format if you start it in an Unraid terminal from the web interface and then close that terminal, so i'd recommend doing the format on the actual bare metal linux terminal when you start the machine.
-
Cant Assign 14TB Drives to my array
I was trying this once more and checking logs as it happened. This section seems to be the error: Nov 26 19:26:42 odyssey kernel: protection error, dev sdf, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0 Nov 26 19:26:42 odyssey kernel: mpt3sas_cm0: log_info(0x3112043b): originator(PL), code(0x12), sub_code(0x043b) Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 UNKNOWN(0x2003) Result: hostbyte=0x05 driverbyte=DRIVER_OK cmd_age=0s Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 Sense Key : 0x5 [current] Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 ASC=0x10 ASCQ=0x3 Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 CDB: opcode=0x7f, sa=0x9 Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 CDB[00]: 7f 00 00 00 00 00 00 18 00 09 20 00 00 00 00 00 Nov 26 19:26:42 odyssey kernel: sd 1:0:4:0: [sdf] tag#2758 CDB[10]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 Nov 26 19:26:42 odyssey kernel: protection error, dev sdf, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 26 19:26:42 odyssey kernel: Buffer I/O error on dev sdf, logical block 0, async page read Nov 26 19:26:42 odyssey emhttpd: error: ckmbr, 2291: Input/output error (5): read: /dev/sdf Nov 26 19:26:42 odyssey emhttpd: ckmbr error: -1
-
Cant Assign 14TB Drives to my array
Hi everyone. I'm brand new to Unraid (seriously, I just got a supermicro CSE-846 and got it running unraid 20 minutes ago). I also have 3 14TB Seagate Exos drives, 4-4TB drives and an SSD I want to use for cache. The strange thing is, when i try to mount any of the 14TB drives as a parity drive or as drives in the array, the page refreshes like it was successful, but then the drive disappears. If i reboot the system it shows back up. I did some searching in this forum and it seems like i'm having the same problem as this post, only I (am ashamed to admit) i dont really how to hook these up to onboard stata ports when I want to put them in the hot-swappable bays. Is there another path to troubleshoot this that lets me take advantage of these drives? I did see in other posts that tools --> Diagnostics are helpful, so attaching mine. Thanks everyone for help in advance. odyssey-diagnostics-20221126-2122.zip