May 25, 20251 yr Hi all.First of all, I have been a Unraid user for many years, but have never had the time or interest to learn the system.I can do the basics, follow a online guide, and install Apps.System:16harddrive bay server cabinetAsus PRIME H610M-E D4i7Core™ i7-12700KIssue no. 1I was playing around with the system, and trying to get the (issue 2) to work. Then when I rebooted the system once again, it won't create the "array" as before, one drive is currently with this issue "Unmountable: wrong or no file system"All I did, taking the Sata cable to the M2 Sata hub, and when it did not work, I switched back. Now it wont build the array as previous. How can I get it to properly mount again. (ST8000VN0022-2EL112_ZA1B77RW)Issue no. 2For a while ago, i bought a M2 NVME Sata adapter.The one I purchased was from Unraid forum, that confirmed that specific model worked with the system.The Sata adapter is not detected in BIOSUnraid, do not show any of the harddrives mounted from the 16bays in the cabinet. 4 harddrives is connected trough SAS to SATA cable to the M2 Sata adapter.However, if I mount one of the harddrives with a normal SATA600 cable, it works fine.Is there any special things I need to be aware of, when it is SAS/SATA cables being used?tower-diagnostics-20250525-2109.zipThank you in advance :)
May 26, 20251 yr Community Expert Looks like there's no partition for disk4, post the output from fdisk -l /dev/sdc
May 27, 20251 yr Author root@Tower:~# fdisk -l /dev/sdcDisk /dev/sdc: 7.28 TiB, 8001563222016 bytes, 15628053168 sectorsDisk model: ST8000VN0022-2ELUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 4096 bytes / 4096 bytes
May 27, 20251 yr Community Expert Yep, partition is missing, any idea what happened there?Type sfdisk /dev/sdc, then type 64 and hit enter, then abort sfdisk by hitting CTRL + C, post the output you get.
May 27, 20251 yr Author I will try. Well. Short answer is NO.Playing around trying to figure out why the M2 SATA adapter was not working.Trying with a harddrive that I knew that worked from the array. It did not work, Then I knew that it was not the harddrive that was the issue.
May 27, 20251 yr Author Welcome to sfdisk (util-linux 2.41).Changes will remain in memory only, until you decide to write them.Be careful before using the write command.Checking that no-one is using this disk right now ... OKThe device contains 'ddf_raid_member' signature and it may be removed by a write command. See sfdisk(8) man page and --wipe option for more details.Disk /dev/sdc: 7.28 TiB, 8001563222016 bytes, 15628053168 sectorsDisk model: ST8000VN0022-2ELUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 4096 bytes / 4096 bytessfdisk is going to create a new 'dos' disk label.Use 'label: <name>' before you define a first partitionto override the default.Type 'help' to get more information.>>> 64The size of this disk is 7.3 TiB (8001563222016 bytes). DOS partition table format cannot be used on drives for volumes larger than 2199023255040 bytes for 512-byte sectors. Use GUID partition table format (GPT).Created a new DOS (MBR) disklabel with disk identifier 0xeffe791d.The device contains 'ddf_raid_member' signature and it may be removed by a write command. See sfdisk(8) man page and --wipe option for more details.Created a new partition 1 of type 'Linux' and of size 2 TiB. /dev/sdc1 : 64 4294967295 (2T) Linux/dev/sdc2:
May 28, 20251 yr Community Expert Try the same command but type 2048 instead of 64 this time, then abort again and post the output
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.