apandey

What do you see on windows PC end, it should also see a link down if it's point to point Have you checked the cable on another connection?

not unless it is a public share. You need access to management UI first to see what is the setup

that is not possible with unraid. Unraid needs to boot from a USB drive, so it must be plugged into the server. It is possible it is plugged directly into the USB header on the motherboard using an adapter. You should check your server physically and get familiar

If you want, you can reset root password used to login to management UI https://wiki.unraid.net/Manual/Troubleshooting#Lost_root_Password BTW, you cannot access shares as unraid root user, you will need a shares user to do that

Unraid management UI ports can be changed in Settings -> Management access if you need standard web ports free for another use case. Just remember, you will need to explicitly use port numbers when using unraid web UI once you do this

Have you created a shares user in unraid (users tab), and does your share has access to that user in share settings?

I have a issue with drives spinning up when I load my main tab. It is limited to zfs, so not sure a UD issue of zfs plugin issue (I am on 6.11.5), but I'll start with a question here My setup: I have 11 drives showing in UD. One is a standalone share used for backups, One is a unused spare drive, and the remaining 9 are a zfs pool managed by zfs master plugin. All of these drives are used for backups that only run overnight, so most of the time, these are idle. All of these seem to spin down sometime during the night after backups are finished The issue happens when I try to load my UI Main tab. The first access is very slow (1+ min), and then subsequent access is snappy fast. Looking at logs, I have narrowed it down to the 9 zfs drives spinning up when first UI access happens. Indeed, when the UI is loaded, I see the 9 zfs drives spinning and the other 2 unassigned drives as spun down. There is no other activity in syslogs during the first load pause Anyone seen this before and any comments on what might be happening?

Try Tools - > New Permissions on the affected share and see if that fixes permissions

Do you have access to that routers interface? You have to route between VLANs if the router or switch allows it, else the default behaviour is to keep them separate Routing across VLANs need one of the following: 1. A layer 3 switch 2. Router with one physical interface per VLAN 3. Router with VLAN trunking enabled You may be out of luck. Inter-VLAN routing is an advanced topics because VLAN traffic is tagged at layer 2 while routing happens at layer 3. Connecting these two is why you need a device which can see separate vlan interfaces in some way (physical or logical). Your switch does not deal with layer 3 at all, your router may not see VLAN interfaces at all

See if this discussion helps You may also want to disable smb signing if it's enabled on Mac, as that will severely affect performance

Have you removed the /mnt/user/cctv symlink pointing to /mnt/disks/cctv? That should stop the errors

Yes, it's either / or boot mode.

Do you have have enough pci lanes to give to the 10gbe card? May 4 18:07:49 Tower kernel: ixgbe 0000:03:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at 0000:02:00.0 (capable of 32.000 Gb/s with 5.0 GT/s PCIe x8 link) If the lanes are shared, try using another slot, or remove any other peripherals that share the lanes from the slot. If you think you have enough lanes, try re-seating the card

post diagnostics, maybe it will tell something

Something seems to be holding it off still. I can get 9+ gbps between a solarflare card on PC connected to a mellanox card on unraid over a DAC

You will also need to enable sharing under SMB settings found in unassigned devices plugin settings. Usually that is enough and then UD will manage samba config If you need specific instructions post in the dedicated plugin thread

If that is a capital MB/s, then sounds like reasonably good to read from a spinning drive If you want to test the raw link speed, run an iperf3 test between the PC and Unraid, preferably both ways.

As @itimpi said, unraid runs from RAM, so usage of usb drive is minimal. Unless, if you are mirroring logs to usb or explicitly have something writing into /boot, so be aware of these unusual wear scenarios As for why, unraid uses the boot drives hardware UUID to pair your licence to, and that is something provided by most USB drives

I would run a few cycles of memtest86 to rule out any basic hardware issues Then I would configure a remote syslog server if possible, or at least syslog mirror to flash if the problem happens frequently to see what gets logged leading up to the hang

I only see this mce error in logs mcelog: Kernel does not support page offline interface If this is all you have seen and there is no obvious adverse effect, it may be harmless. If a BIOS update is available, it might help There have been issues reported for 6.12 RC on breaking spindown on doing new config. There was a discussion on one of the RC threads Maybe ask in current RC thread on latest status

I have LSI 9300 16i, which is the pcie 3.0 successor to 9201

That symlink is the problem. /mnt/user needs to be fully managed by unraid, and the errors are because it is encountering a symlink which is not a shfs mount. Trying to get status of that share in expected way is failing If you want this shared, use the unassigned devices share functionality (it won't be listed under shares) or manually configure smb-extras in samba settings

Is /mnt/user/cctv linked to /mnt/disks/cctv in any way? If yes, how?

Post diagnostics when the drive is showing unassigned. Seems you drive dropped off and hence the drive letters for remaining drives changed. The cause of original drop off is what we need Drive letters are not important to unraid, it identifies drives by name and serial number. /dev/sdX are linux assigned names and not guaranteed to remain same, so if you want to specifically address drives for any use case (like VM pass through), you should use by-id instead

That seems like a layer 2 only switch, so while it will allow VLANs, it won't be able to route through them What are you using as a router? That's where you need to allow routing between the networks