Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Corrupted Disk? Google-Fu fails me for lsblk -f

Featured Replies

Greetings!

I installed a 250G drive to test as a Cache device on a server. The disc 'appears' but isn't recognized in Unraid under the Main - Pool tab or in system devices and I'm not sure if that is because there is no partition created.

 

The below is what I am seeing, under System Devices and under lsblk -f:

root@unraid:~# lsblk -f
NAME   FSTYPE   FSVER LABEL  UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0  squashfs 4.0                                                  7.5G     4% /lib
loop1  squashfs 4.0                                                  7.5G     4% /usr
loop2  btrfs                 88b02e85-3c6e-48ac-9849-0c1ba46bcb21   15.4G    22% /var/lib/docker/btrfs
                                                                                 /var/lib/docker
sda                                                                              
└─sda1 xfs                   67212bab-f711-4718-a047-68fe17919120                
sdb                                                                              
└─sdb1 vfat     FAT32 UNRAID 272B-4CE1                                 7G     6% /boot
sdc                                                                              
md1p1                                                                3.6T     1% /mnt/disk1

 

The device isn't showing up under fdisk -l, probably due to the lack of partition:

root@unraid:~# sudo fdisk -l
Disk /dev/loop0: 59.3 MiB, 62177280 bytes, 121440 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop1: 334.05 MiB, 350277632 bytes, 684136 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/sda: 3.64 TiB, 4000752599040 bytes, 7813969920 sectors
Disk model: easystore 25FA  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 7CBACB44-8BC8-4320-813C-E946FCD93175

Device     Start        End    Sectors  Size Type
/dev/sda1     64 7813969886 7813969823  3.6T Linux filesystem

Disk /dev/sdb: 7.45 GiB, 8004304896 bytes, 15633408 sectors
Disk model: Cruzer          
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdb1  *     2048 15633407 15631360  7.5G  c W95 FAT32 (LBA)

Disk /dev/md1p1: 3.64 TiB, 4000752545792 bytes, 7813969816 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

 

No medium found:

root@unraid:~# sudo fdisk /dev/sdc

Welcome to fdisk (util-linux 2.38.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

fdisk: cannot open /dev/sdc: No medium found

 

If the disc is dead, that's fine. I'm just trying to not throw it away if it can be saved. It might fail healthchecks but I can run that after I can get a partition on it, if that is the case. This disc won't be used for anything beyond testing as is. Just trying to test a new setup before I undo everything I already have setup.

Edited by Trizzd
remove personal data

  • Community Expert
29 minutes ago, Trizzd said:

I'm not sure if that is because there is no partition created.

That won't matter, please post the diasgnostics.

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.