Have an new disk in a new Maivo 4 disk DAS.

Connecting to unraid over usb, see the disk, cannot format it nor by using Unassigned Devices nor in the array itself.

Don't care about the data. Tried different PCs and different cables.

Same disk in the same box n5105-diagnostics-20241128-2214.zipworks in linux and windows.

Formatted, copied files in windows, then erased it and installed kubuntu, only unraid can't write to it for some reason.

Tried unraid 6.12.10 and 7.0.0 beta4, tried new configuration, nothing helps.

Other disks work fine in unraid.

Please help

Not familar with thoeses drives.

when kubuntu what format filesytem is the disk on.
*live boot kubunut use gpart/disk and format the disk as xfs.

otherwise you would need to use unraid wipedisk from terminal and set to a unraid useable file system
xfs,btrfs,zfs.

 

To securely wipe a disk and format it with the XFS filesystem in Unraid, follow these steps:

Warning: This process will irreversibly erase all data on the target disk. Ensure you have backed up any important data before proceeding.

1. Identify the Disk:

Open the Unraid terminal.

List all attached storage devices to determine the device identifier (e.g., /dev/sdX) of the disk you intend to wipe:

lsblk

Review the output to identify the correct disk based on size and current mount points.

 

2. Stop the Array (if the disk is part of it):

In the Unraid web interface, navigate to the Main tab.

Stop the array by clicking the Stop button.

 

3. Wipe the Disk:

View Existing Filesystem Signatures:

Before wiping, check the existing filesystem signatures on the disk:

wipefs /dev/sdX

wipefs -a /dev/sdX

To remove all filesystem signatures, use the -a option

wipefs /dev/sdX

If the output is empty, the disk has been successfully wiped.

 

Preclear?

Use the dd command to overwrite the disk with zeros, effectively wiping all data. Replace sdX with the appropriate device identifier:

dd if=/dev/zero of=/dev/sdX bs=1M status=progress

Note: This operation can be time-consuming, depending on the disk's size.

 

4. Create a New Partition Table:

After wiping, create a new GPT partition table on the disk:

parted /dev/sdX --script mklabel gpt

 

5. Create an XFS Partition:

Create a new primary partition that spans the entire disk:

parted /dev/sdX --script mkpart primary xfs 0% 100%

Format:

mkfs.xfs /dev/sdX1

Ensure you're formatting the partition (/dev/sdX1), not the entire disk.

 

6. Reassign the Disk in Unraid:

Return to the Unraid web interface.

If the disk was part of the array, reassign it to its previous slot.

Start the array. Unraid may prompt you to format the new disk; proceed as instructed.

 

Additional Considerations:

Data Destruction: The dd command used above will destroy all data on the specified disk. Double-check the device identifier to avoid accidental data loss.

Unassigned Devices: If you're working with a disk outside the array, consider using the Unassigned Devices plugin for easier management.

Preclear Plugin: For a more thorough disk preparation, use the Preclear plugin, which can test the disk's health and readiness for use in the array.

By following these steps, you can securely wipe a disk and format it with the XFS filesystem in Unraid.

Might be your drive blk size is not 512?

Look over this if so.

Thanks you both for quick response, much appreciated. I have done as per bnartino1 guidelines, only changed xfs commands with btrfs, because I use compression and skipped preclear step.

Everything got smooth untill partition creation.

 

 mkfs.btrfs /dev/sdb1

 

Got:

 

 error during mkfs: Operation not permitted

 

Reran everything again with xfs, got following errors:

 

mkfs.xfs: pwrite failed: Input/output error
libxfs_bwrite: write failed on (unknown) bno 0x746bfef00/0x100, err=5
mkfs.xfs: Releasing dirty buffer to free list!
found dirty buffer (bulk) on free list!
mkfs.xfs: pwrite failed: Input/output error
libxfs_bwrite: write failed on (unknown) bno 0x0/0x100, err=5
mkfs.xfs: Releasing dirty buffer to free list!
found dirty buffer (bulk) on free list!
mkfs.xfs: libxfs_device_zero write failed: Input/output error

 

n5105-diagnostics-20241129-0824.zip

Edited November 29, 20241 yr by sharicov

Regards block size it's ok

 

 blockdev --getbsz /dev/sdb

 

4096

Booted from kubuntu live and got error when formatting the disk with xfs and btrf (strange thing, because I can install kubuntu on that disk formatting it with no errors).

Booted to WinPE live and formated it ext4 using minitool partition wizard (no errors occured)

Booted to unraid. it shows disk as xfs for some reason and cannot format it using unraid GUI, still getting unmountable: unsupported or no file system

While formating disk changed from sdc to sdd and now unraid is in Array started - formating device state and not moving, stop array button is disabled

Also cannot stop array with command

 

 emcmd cmdStop=Stop

 

Rebooted unraid, booted into regular windows 10.

Disk manager shows disk is MBR (changed to MBR in windows before to see if it fixes GPT record error in linux and didn't switch it back), now cannot change it back in windows, getting IO error message from disk manager.

Minitool partition wizard pretends that it change it but it doesn't.

Went to Seagate SeaTools:

Short health test didn't pass, ran short fix now it's passing the health test.

Simple overwrite format failed, now running Sanitize Overwrite format. no errors yet, should take 48 hours or so, it's Seagate IronWolf Pro 16TB disk.

Seems all manipulations in linux completely messed the drive. 

 

n5105-diagnostics-20241129-0903.zip

Edited November 29, 20241 yr by sharicov

Looks like USB problems:

 

Nov 28 22:09:43 n5105 kernel: usb 4-3.1.3: reset SuperSpeed USB device number 5 using xhci_hcd
### [PREVIOUS LINE REPEATED 5 TIMES] ###
Nov 28 22:09:45 n5105 kernel: sd 2:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=2s
Nov 28 22:09:45 n5105 kernel: sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 00 40 00 00 08 00 00 00
Nov 28 22:09:45 n5105 kernel: I/O error, dev sdb, sector 64 op 0x1:(WRITE) flags 0x4800 phys_seg 256 prio class 2
Nov 28 22:09:45 n5105 kernel: md: disk1 write error, sector=0
Nov 28 22:09:45 n5105 kernel: md: disk1 write error, sector=8
Nov 28 22:09:45 n5105 kernel: md: disk1 write error, sector=16

 

USB is not recommended for array or pool devices.

Thanks for your feedback, JorgeB, I know USB is not recommended, but that's the way I use unraid, I think the problem is the disk itself, now it's not even initializing in windows. It doesn't start with PC PSU, only in USB boxes. 

Thanks everyone for your help, since I don't have another disk, will not be able to investigate further...

Windows won't see the disk as unraid uses a linux file system xfs/btrfs/zfs.

you would have to formate the disk in windos as a ntfs/vfat to use widnwos. or use paid tools to read linux file systems.

 

usb has to many power cycle states that adds disk thrashing when assinged to the unraid array it is a unsupported configuration.
*thsi may be damaged but you would need to use tools like. ubuntu live usb boot disk/gparted to check and verfy the disk.

Thanks again, I meant Disl manager in windows even before formatting.

Send the disk back to the store as faulty, Seagate tool sees it but cannot fix it.