Drives are not partitioned properly in Linux Mint XFCE.

ScarletMcLearn · Post by **ScarletMcLearn** » Sat Jun 10, 2023 7:10 am

I am using Linux Mint XFCE on ASUS Vivobook, and I don't think my drives are partitioned properly.

I am sharing the screenshots below.

I have a 1 TB Drive which is partitioned as follows:
Image 1: https://pasteboard.co/3JQCyPS2t6Fg.png

Image 2: https://pasteboard.co/HvDij6UpmTll.png

I have a 128 GB Drive which is partitioned as follows:
Image 3: https://pasteboard.co/HxHvQs9SJSuG.png

I have another 1 TB Drive which is partitioned as follows:
Image 4: https://pasteboard.co/mWmZeB4ZIkLO.png

I am giving the output of the inxxxi command below:

Code: Select all

inxi -Fxxxxz
System:
  Kernel: 5.15.0-73-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
    Desktop: Xfce 4.16.0 tk: Gtk 3.24.23 info: xfce4-panel wm: xfwm 4.16.1
    vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21 Vanessa
    base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: ASUSTeK product: X542UN v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: X542UN v: 1.0 serial: <superuser required>
    UEFI: American Megatrends v: X542UN.309 date: 09/02/2019
Battery:
  ID-1: BAT0 charge: 25.1 Wh (100.0%) condition: 25.1/38.0 Wh (66.0%)
    volts: 7.6 min: 7.6 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
    status: Not charging cycles: 130
CPU:
  Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP
    smt: enabled arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB
    L3: 8 MiB
  Speed (MHz): avg: 1090 high: 1817 min/max: 400/4000 cores: 1: 900 2: 896
    3: 897 4: 1605 5: 1817 6: 1008 7: 804 8: 800 bogomips: 31999
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: ASUSTeK driver: i915 v: kernel
    ports: active: HDMI-A-2 off: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0
    chip-ID: 8086:5917 class-ID: 0300
  Device-2: NVIDIA GP108M [GeForce MX150] vendor: ASUSTeK driver: nvidia
    v: 530.41.03 pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 01:00.0
    chip-ID: 10de:1d10 class-ID: 0302
  Device-3: IMC Networks USB2.0 VGA UVC WebCam type: USB driver: uvcvideo
    bus-ID: 1-6:4 chip-ID: 13d3:5a01 class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.4 compositor: xfwm v: 4.16.1 driver:
    X: loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa gpu: i915
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3")
    s-diag: 583mm (23")
  Monitor-1: HDMI-2 mapped: HDMI-A-2 model: LG (GoldStar) 32ML600
    res: 1920x1080 hz: 60 dpi: 102 size: 480x270mm (18.9x10.6")
    diag: 551mm (21.7") modes: max: 1920x1080 min: 720x400
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
    v: 4.6 Mesa 22.2.5 direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71
    class-ID: 0403
  Device-2: Generalplus USB Audio Device type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-3:2 chip-ID: 1b3f:2008
    class-ID: 0300
  Sound Server-1: ALSA v: k5.15.0-73-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: d000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
  Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
    vendor: AzureWave driver: ath10k_pci v: kernel pcie: speed: 2.5 GT/s
    lanes: 1 bus-ID: 03:00.0 chip-ID: 168c:0042 class-ID: 0280
  IF: wlp3s0 state: up mac: <filter>
  Device-3: Realtek RTL8152 Fast Ethernet Adapter type: USB driver: r8152
    bus-ID: 1-4.4.1:8 chip-ID: 0bda:8152 class-ID: 0000 serial: <filter>
  IF: enx00e04c360976 state: up speed: 100 Mbps duplex: full mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
  Device-1: IMC Networks type: USB driver: btusb v: 0.8 bus-ID: 1-8:6
    chip-ID: 13d3:3496 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: <filter>
Drives:
  Local Storage: total: 1.96 TiB used: 239.63 GiB (12.0%)
  ID-1: /dev/sda vendor: Intel model: SSDSC2KW010T8 size: 953.87 GiB
    speed: 6.0 Gb/s type: SSD serial: <filter> rev: 0B1C scheme: GPT
  ID-2: /dev/sdb vendor: SK Hynix model: HFS128G39TND-N210A
    size: 119.24 GiB speed: 6.0 Gb/s type: SSD serial: <filter> rev: 0P10
  ID-3: /dev/sdc type: USB vendor: HGST (Hitachi) model: HTS 541010B7E610
    size: 931.51 GiB type: N/A serial: <filter> rev: 03.0 scheme: GPT
Partition:
  ID-1: / size: 937.33 GiB used: 118.77 GiB (12.7%) fs: ext4 dev: /dev/sda2
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 60.0 C pch: 54.5 C mobo: N/A
  Fan Speeds (RPM): cpu: 3600
Info:
  Processes: 331 Uptime: 1h 39m wakeups: 1 Memory: 15.51 GiB
  used: 5.27 GiB (34.0%) Init: systemd v: 249 runlevel: 5 Compilers:
  gcc: 11.3.0 alt: 11/12 Packages: 3342 apt: 3299 flatpak: 43 Shell: Bash
  v: 5.1.16 running-in: xfce4-terminal inxi: 3.3.13
scarlet2@Scarlet:~$

I wanted to confirm the following:
1. If all these partitions are appropriate / correct / working / how they should be.

2.In the 1st Drive of 1 TB (Image 1 and 2), there are 2 partitions - one of 1 TB Ext 4 (dev/sda2), and the other of 537 MB FAT (dev/sda1). What are the purpose of these partitions? And are the sizes okay? Should I change the size? If so, to what?

3. In the 2nd Drive of 128 GB (dev/sdb1), I cannot find the drive anywhere on my system. What are the purpose of these partitions? And are the sizes okay? Should I change the size? If so, to what? Is this partition appropriate / correct / working / how it should be.

Please let me know your feedback.

Thank you for your time.

Schultz · Post by **Schultz** » Sat Jun 10, 2023 7:16 am

I don't see anything out of the ordinary (except maybe for the 128 Gig partition). But, I'm not an expert.

ScarletMcLearn · Post by **ScarletMcLearn** » Sat Jun 10, 2023 7:19 am

3. In the 2nd Drive of 128 GB (dev/sdb1), I cannot find the drive anywhere on my system. What are the purpose of these partitions? And are the sizes okay? Should I change the size? If so, to what? Is this partition appropriate / correct / working / how it should be.

This is a huge red flag for me.
I cannot access this space.

I don't know what its being used for.

I am also not sure if the other ones are appropriate.

Schultz · Post by **Schultz** » Sat Jun 10, 2023 7:20 am

Yeah, I just edited my post about that. Someone with more knowledge will have to answer that. But everything else looks okay.

Post by **djph** » Sat Jun 10, 2023 7:26 am

run these commands, and post their output back here.

1. lsblk -f

2. cat /etc/fstab

ajgreeny · Post by **ajgreeny** » Sat Jun 10, 2023 7:30 am

All looks good to me too but I do note you have 3 partitions formatted to NTFS on what is your 2nd 1T disk. I presume this means you have Windows on the system somewhere. If you do not run Windows there is little point in having NTFS on disks; NTFS is a proprietary Microsoft filesystem and can not be repaired when needed using Linux.

The first 1T disk is fine; the small fat32 partition is the EFI/ESP partition, needed as you will undoubtedly be booting in UEFI mode and the larger, almost 1T partition is your Linux Mint OS partition. Do not touch those at all but leave as they are.

The 128G disk is unknown filesystem so I have no idea what that is or what you want to use it for; enlighten us please or at least show us the output of terminal command

Code: Select all

sudo fdisk -l

ScarletMcLearn · Post by **ScarletMcLearn** » Sat Jun 10, 2023 7:41 am

Thank you for your time.

All looks good to me too but I do note you have 3 partitions formatted to NTFS on what is your 2nd 1T disk. I presume this means you have Windows on the system somewhere. If you do not run Windows there is little point in having NTFS on disks; NTFS is a proprietary Microsoft filesystem and can not be repaired when needed using Linux.

- Thank you for the suggestion. I will change it later if needed, but keeping flexibility for now as its an external drive.

The first 1T disk is fine; the small fat32 partition is the EFI/ESP partition, needed as you will undoubtedly be booting in UEFI mode and the larger, almost 1T partition is your Linux Mint OS partition. Do not touch those at all but leave as they are.

- Got it! Clear. Wont modify these.

The 128G disk is unknown filesystem so I have no idea what that is or what you want to use it for; enlighten us please or at least show us the output of terminal command

- I think, not sure though, this drive was previously called Drive in my system. I just stored files and used it as an internal SSD.
- I am providing the output as requested below.

Please suggest what might be wrong or what I can do about this.

Thank you!

Code: Select all

sudo fdisk -l
[sudo] password for scarlet2:          
Disk /dev/sda: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: INTEL SSDSC2KW01
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: gpt
Disk identifier: 9D5F6309-6648-4BEA-8CDB-754971CE7C24

Device       Start        End    Sectors   Size Type
/dev/sda1     2048    1050623    1048576   512M EFI System
/dev/sda2  1050624 2000408575 1999357952 953.4G Linux filesystem


Disk /dev/sdb: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: HFS128G39TND-N21
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: CD11C153-C391-4F85-9753-DFC14BCA76C9

Device     Start       End   Sectors   Size Type
/dev/sdb1   2048 250068991 250066944 119.2G Microsoft basic data


Disk /dev/sdc: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: 541010B7E610    
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: 6BBEBCF9-25A5-458C-ACE1-0D16B5C3C2E5

Device          Start        End   Sectors   Size Type
/dev/sdc1        2048  651352063 651350016 310.6G Microsoft basic data
/dev/sdc2   651352064 1302437887 651085824 310.5G Microsoft basic data
/dev/sdc3  1302437888 1953521663 651083776 310.5G Microsoft basic data

ScarletMcLearn · Post by **ScarletMcLearn** » Sat Jun 10, 2023 10:52 am

Sorry I missed your response:

Code: Select all

lsblk -f
NAME FSTYPE FSVER LABEL   UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                           
├─sda1
│    vfat   FAT32         DD96-DBB8                             504.9M     1% /mnt/DD96-DBB8
└─sda2
     ext4   1.0           c67dfae0-7298-48f2-9e37-5efcb3d07124  770.9G    13% /
sdb                                                                           
└─sdb1
                                                                              
sdc                                                                           
├─sdc1
│    ntfs         Project C224411A24411339                                    
├─sdc2
│    ntfs         New Volume
│                         0E5CAFD55CAFB5BD                                    
└─sdc3
     ntfs         Documents
                          52CEB43ECEB41C63                      190.2G    39% /mount/Documents
sr0

Code: Select all

cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda2 during installation
UUID=c67dfae0-7298-48f2-9e37-5efcb3d07124 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
/swapfile                                 none            swap    sw              0       0
/dev/disk/by-uuid/DD96-DBB8 /mnt/DD96-DBB8 auto nosuid,nodev,nofail,x-gvfs-show 0 0
LABEL=Drive /media/scarlet/Drive auto nosuid,nodev,nofail,x-gvfs-show 0 0
LABEL=Linux\040Mint\04021.1\040Xfce\04064-bit /mnt/Linux\040Mint\04021.1\040Xfce\04064-bit auto nosuid,nodev,nofail,noauto,x-gvfs-show 0 0
LABEL=Project /mount/Project auto nosuid,nodev,nofail,x-gvfs-show,noauto 0 0
LABEL=New\040Volume /mount/New\040Volume auto nosuid,nodev,nofail,x-gvfs-show,noauto 0 0
LABEL=Documents /mount/Documents auto nosuid,nodev,nofail,x-gvfs-show,noauto 0 0

linux-rox · Post by **linux-rox** » Sat Jun 10, 2023 11:11 am

Why are you playing hide-the-ball on how sdb got to be as it is? It's your computer and the Mint installer didn't do it. FWIW, HFS is a Mac file system, so that might be what's on the drive. Also, I notice you have edited fstab to remove the standard mount for the EFI partition. Good luck with that.

ScarletMcLearn · Post by **ScarletMcLearn** » Sat Jun 10, 2023 11:33 am

linux-rox wrote: ⤴Sat Jun 10, 2023 11:11 am Why are you playing hide-the-ball on how sdb got to be as it is? It's your computer and the Mint installer didn't do it. FWIW, HFS is a Mac file system, so that might be what's on the drive. Also, I notice you have edited fstab to remove the standard mount for the EFI partition. Good luck with that.

I am sorry, but I don't know what you mean by 'hide-the ball on how sdb got to be as it is'. While I was installing, the option to automatically set partitions was not showing. I set them appropriately that time.

Due to some problems occurring, I had to upgrade the Mint XFCE version and also remove the previous user account.

Ever since then the 'Drive' disk was gone and I have this HFS drive.

I do not have any Mac device.

If you have any suggestions, please suggest.

motoryzen · Post by **motoryzen** » Sat Jun 10, 2023 11:39 am

I think, not sure though, this drive was previously called Drive in my system. I just stored files and used it as an internal SSD

If you can access that 128GB drive's contents using a Windows PC, perhaps try to find space on another drive to view and copy whatever contents you deem important, then once you confirm the copying was a success, format that 128GB drive to exFat.

This way, you can easily plug-in play deal with both Linux and Windows with that drive without any more finaggling headaches to go through

I think Scarlett meant that you at some point through settings adjustments be it terminal commands or using gnome-disks ( aka just named Disks application in the main Whisker menu - you can press windows logo button to access it just the same as the Windows start menu) and told the system to mount that 128GB drive as sdb or sdb1.

ScarletMcLearn · Post by **ScarletMcLearn** » Sat Jun 10, 2023 11:44 am

Thank you for your suggestion.

I tried formatting it as per your guideline.

But its failing.

https://pasteboard.co/2zFJApEF83Ga.png

Please suggest what I can do here.

Thank you!

Post by **djph** » Sat Jun 10, 2023 3:07 pm

That drive seems to be in quite a bad state.

Install smartmontools (if not already), and run sudo smartctl -a /dev/sdb and post the output here.

ScarletMcLearn · Post by **ScarletMcLearn** » Sat Jun 10, 2023 3:14 pm

Thank you for your time and effort.

Here is the output:

Code: Select all

sudo smartctl -a /dev/sdb
[sudo] password for scarlet2:          
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-73-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     SK hynix SATA SSDs
Device Model:     HFS128G39TND-N210A
Serial Number:    EJ77N539911807I2X
Firmware Version: 30200P10
User Capacity:    128,035,676,160 bytes [128 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    Solid State Device
Form Factor:      M.2
TRIM Command:     Available, deterministic
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Jun 11 01:11:53 2023 +06
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (  32)	The self-test routine was interrupted
					by the host with a hard or soft reset.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x19) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					No Selective Self-test supported.
SMART capabilities:            (0x0002)	Does not save SMART data before
					entering power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  10) minutes.

SMART Attributes Data Structure revision number: 0
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   166   166   006    Pre-fail  Always       -       46
  5 Retired_Block_Count     0x0032   100   100   036    Old_age   Always       -       12
  9 Power_On_Hours          0x0032   054   054   000    Old_age   Always       -       40958
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       708
100 Total_Erase_Count       0x0032   097   097   000    Old_age   Always       -       139377995
168 Min_Erase_Count         0x0032   001   001   000    Old_age   Always       -       4313
169 Max_Erase_Count         0x0032   001   001   000    Old_age   Always       -       4314
171 Program_Fail_Count      0x0032   253   253   000    Old_age   Always       -       0
172 Erase_Fail_Count        0x0032   253   253   000    Old_age   Always       -       0
174 Unexpect_Power_Loss_Ct  0x0030   100   100   000    Old_age   Offline      -       109
175 Program_Fail_Count_Chip 0x0032   253   253   000    Old_age   Always       -       0
176 Unused_Rsvd_Blk_Cnt_Tot 0x0032   253   253   000    Old_age   Always       -       0
177 Wear_Leveling_Count     0x0032   001   001   000    Old_age   Always       -       4249
178 Used_Rsvd_Blk_Cnt_Chip  0x0032   100   100   000    Old_age   Always       -       247
179 Used_Rsvd_Blk_Cnt_Tot   0x0032   100   100   000    Old_age   Always       -       541
180 Erase_Fail_Count        0x0032   100   100   000    Old_age   Always       -       2099
184 End-to-End_Error        0x0032   100   100   000    Old_age   Always       -       1604
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       2584
188 Command_Timeout         0x0032   253   253   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   035   000   000    Old_age   Always       -       35 (Min/Max 0/61)
195 Hardware_ECC_Recovered  0x0032   100   001   000    Old_age   Always       -       32192060
196 Reallocated_Event_Count 0x0032   100   100   036    Old_age   Always       -       12
198 Offline_Uncorrectable   0x0032   100   100   000    Old_age   Always       -       32
199 UDMA_CRC_Error_Count    0x0032   253   253   000    Old_age   Always       -       0
204 Soft_ECC_Correction     0x000e   100   001   000    Old_age   Always       -       29
212 Phy_Error_Count         0x0032   253   253   000    Old_age   Always       -       0
234 Unknown_SK_hynix_Attrib 0x0032   100   100   000    Old_age   Always       -       589045
241 Total_Writes_GiB        0x0032   100   100   000    Old_age   Always       -       72466
242 Total_Reads_GiB         0x0032   100   100   000    Old_age   Always       -       42590
250 Read_Retry_Count        0x0032   006   006   000    Old_age   Always       -       3811740296

SMART Error Log Version: 1
ATA Error Count: 11569 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 11569 occurred at disk power-on lifetime: 40955 hours (1706 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 88 00 08 00 40 40      06:18:22.820  READ FPDMA QUEUED
  47 00 01 30 08 00 a0 a0      06:18:22.820  READ LOG DMA EXT
  47 00 01 30 00 00 a0 a0      06:18:22.820  READ LOG DMA EXT
  47 00 01 00 00 00 a0 a0      06:18:22.820  READ LOG DMA EXT
  ef 10 02 00 00 00 a0 a0      06:18:22.820  SET FEATURES [Enable SATA feature]

Error 11568 occurred at disk power-on lifetime: 40955 hours (1706 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 18 00 08 00 40 40      06:18:22.770  READ FPDMA QUEUED
  60 08 10 f0 bf e7 40 40      06:18:22.770  READ FPDMA QUEUED
  60 08 08 80 bf e7 40 40      06:18:22.770  READ FPDMA QUEUED
  47 00 01 30 08 00 a0 a0      06:18:22.730  READ LOG DMA EXT
  47 00 01 30 00 00 a0 a0      06:18:22.730  READ LOG DMA EXT

Error 11567 occurred at disk power-on lifetime: 40955 hours (1706 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 20 00 08 00 40 40      06:18:22.670  READ FPDMA QUEUED
  47 00 01 30 08 00 a0 a0      06:18:22.670  READ LOG DMA EXT
  47 00 01 30 00 00 a0 a0      06:18:22.670  READ LOG DMA EXT
  47 00 01 00 00 00 a0 a0      06:18:22.670  READ LOG DMA EXT
  ef 10 02 00 00 00 a0 a0      06:18:22.670  SET FEATURES [Enable SATA feature]

Error 11566 occurred at disk power-on lifetime: 40955 hours (1706 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 98 00 08 00 40 40      06:18:22.620  READ FPDMA QUEUED
  ef 10 03 00 00 00 a0 a0      06:18:22.620  SET FEATURES [Enable SATA feature]
  47 00 01 30 08 00 a0 a0      06:18:22.620  READ LOG DMA EXT
  47 00 01 30 00 00 a0 a0      06:18:22.620  READ LOG DMA EXT
  47 00 01 00 00 00 a0 a0      06:18:22.620  READ LOG DMA EXT

Error 11565 occurred at disk power-on lifetime: 40955 hours (1706 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 20 00 00 08 00 40 40      06:18:22.250  READ FPDMA QUEUED
  e7 00 00 00 00 00 a0 a0      06:18:22.250  FLUSH CACHE
  47 00 01 30 08 00 a0 a0      06:18:22.200  READ LOG DMA EXT
  47 00 01 30 00 00 a0 a0      06:18:22.200  READ LOG DMA EXT
  47 00 01 00 00 00 a0 a0      06:18:22.200  READ LOG DMA EXT

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

Selective Self-tests/Logging not supported

Code: Select all

scarlet2@Scarlet:~$ sudo smartctl -a /dev/sdb1
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-73-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     SK hynix SATA SSDs
Device Model:     HFS128G39TND-N210A
Serial Number:    EJ77N539911807I2X
Firmware Version: 30200P10
User Capacity:    128,035,676,160 bytes [128 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    Solid State Device
Form Factor:      M.2
TRIM Command:     Available, deterministic
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Jun 11 01:11:59 2023 +06
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (  32)	The self-test routine was interrupted
					by the host with a hard or soft reset.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x19) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					No Selective Self-test supported.
SMART capabilities:            (0x0002)	Does not save SMART data before
					entering power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  10) minutes.

SMART Attributes Data Structure revision number: 0
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   166   166   006    Pre-fail  Always       -       46
  5 Retired_Block_Count     0x0032   100   100   036    Old_age   Always       -       12
  9 Power_On_Hours          0x0032   054   054   000    Old_age   Always       -       40958
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       708
100 Total_Erase_Count       0x0032   097   097   000    Old_age   Always       -       139377995
168 Min_Erase_Count         0x0032   001   001   000    Old_age   Always       -       4313
169 Max_Erase_Count         0x0032   001   001   000    Old_age   Always       -       4314
171 Program_Fail_Count      0x0032   253   253   000    Old_age   Always       -       0
172 Erase_Fail_Count        0x0032   253   253   000    Old_age   Always       -       0
174 Unexpect_Power_Loss_Ct  0x0030   100   100   000    Old_age   Offline      -       109
175 Program_Fail_Count_Chip 0x0032   253   253   000    Old_age   Always       -       0
176 Unused_Rsvd_Blk_Cnt_Tot 0x0032   253   253   000    Old_age   Always       -       0
177 Wear_Leveling_Count     0x0032   001   001   000    Old_age   Always       -       4249
178 Used_Rsvd_Blk_Cnt_Chip  0x0032   100   100   000    Old_age   Always       -       247
179 Used_Rsvd_Blk_Cnt_Tot   0x0032   100   100   000    Old_age   Always       -       541
180 Erase_Fail_Count        0x0032   100   100   000    Old_age   Always       -       2099
184 End-to-End_Error        0x0032   100   100   000    Old_age   Always       -       1604
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       2584
188 Command_Timeout         0x0032   253   253   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   035   000   000    Old_age   Always       -       35 (Min/Max 0/61)
195 Hardware_ECC_Recovered  0x0032   100   001   000    Old_age   Always       -       32192060
196 Reallocated_Event_Count 0x0032   100   100   036    Old_age   Always       -       12
198 Offline_Uncorrectable   0x0032   100   100   000    Old_age   Always       -       32
199 UDMA_CRC_Error_Count    0x0032   253   253   000    Old_age   Always       -       0
204 Soft_ECC_Correction     0x000e   100   001   000    Old_age   Always       -       29
212 Phy_Error_Count         0x0032   253   253   000    Old_age   Always       -       0
234 Unknown_SK_hynix_Attrib 0x0032   100   100   000    Old_age   Always       -       589045
241 Total_Writes_GiB        0x0032   100   100   000    Old_age   Always       -       72466
242 Total_Reads_GiB         0x0032   100   100   000    Old_age   Always       -       42590
250 Read_Retry_Count        0x0032   006   006   000    Old_age   Always       -       3811740296

SMART Error Log Version: 1
ATA Error Count: 11569 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 11569 occurred at disk power-on lifetime: 40955 hours (1706 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 88 00 08 00 40 40      06:18:22.820  READ FPDMA QUEUED
  47 00 01 30 08 00 a0 a0      06:18:22.820  READ LOG DMA EXT
  47 00 01 30 00 00 a0 a0      06:18:22.820  READ LOG DMA EXT
  47 00 01 00 00 00 a0 a0      06:18:22.820  READ LOG DMA EXT
  ef 10 02 00 00 00 a0 a0      06:18:22.820  SET FEATURES [Enable SATA feature]

Error 11568 occurred at disk power-on lifetime: 40955 hours (1706 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 18 00 08 00 40 40      06:18:22.770  READ FPDMA QUEUED
  60 08 10 f0 bf e7 40 40      06:18:22.770  READ FPDMA QUEUED
  60 08 08 80 bf e7 40 40      06:18:22.770  READ FPDMA QUEUED
  47 00 01 30 08 00 a0 a0      06:18:22.730  READ LOG DMA EXT
  47 00 01 30 00 00 a0 a0      06:18:22.730  READ LOG DMA EXT

Error 11567 occurred at disk power-on lifetime: 40955 hours (1706 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 20 00 08 00 40 40      06:18:22.670  READ FPDMA QUEUED
  47 00 01 30 08 00 a0 a0      06:18:22.670  READ LOG DMA EXT
  47 00 01 30 00 00 a0 a0      06:18:22.670  READ LOG DMA EXT
  47 00 01 00 00 00 a0 a0      06:18:22.670  READ LOG DMA EXT
  ef 10 02 00 00 00 a0 a0      06:18:22.670  SET FEATURES [Enable SATA feature]

Error 11566 occurred at disk power-on lifetime: 40955 hours (1706 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 98 00 08 00 40 40      06:18:22.620  READ FPDMA QUEUED
  ef 10 03 00 00 00 a0 a0      06:18:22.620  SET FEATURES [Enable SATA feature]
  47 00 01 30 08 00 a0 a0      06:18:22.620  READ LOG DMA EXT
  47 00 01 30 00 00 a0 a0      06:18:22.620  READ LOG DMA EXT
  47 00 01 00 00 00 a0 a0      06:18:22.620  READ LOG DMA EXT

Error 11565 occurred at disk power-on lifetime: 40955 hours (1706 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 20 00 00 08 00 40 40      06:18:22.250  READ FPDMA QUEUED
  e7 00 00 00 00 00 a0 a0      06:18:22.250  FLUSH CACHE
  47 00 01 30 08 00 a0 a0      06:18:22.200  READ LOG DMA EXT
  47 00 01 30 00 00 a0 a0      06:18:22.200  READ LOG DMA EXT
  47 00 01 00 00 00 a0 a0      06:18:22.200  READ LOG DMA EXT

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

Selective Self-tests/Logging not supported

ajgreeny · Post by **ajgreeny** » Sat Jun 10, 2023 3:37 pm

If the disk really is formatted to HFS, and it can only be so if you either got it already formatted that way or you, or someone else did it, check if you have the hfsplus and hfsutils packages installed. That should at least allow you to read/write and use the HFS filesystem.

Has anyone with a Mac borrowed it and used it; you did say it's an external drive, and might they have formatted it without you knowing?

ScarletMcLearn · Post by **ScarletMcLearn** » Sat Jun 10, 2023 3:42 pm

I'm sorry to confuse you, but this drive isn't external.

I installed HFSPlus.

What should I do now?

ajgreeny · Post by **ajgreeny** » Sat Jun 10, 2023 3:46 pm

ScarletMcLearn wrote: ⤴Sat Jun 10, 2023 3:42 pm I'm sorry to confuse you, but this drive isn't external.

I installed HFSPlus.

What should I do now?

Sorry, my mistake; it's your second 1T drive with hte NTFS partitions that's external; correct?.

You've installed hfsplus; what about hfsutils?

ScarletMcLearn · Post by **ScarletMcLearn** » Sat Jun 10, 2023 3:50 pm

Sorry, my mistake; it's your second 1T drive with hte NTFS partitions that's external; correct?.

Yes, you are absolutely right now.

Code: Select all

You've installed hfsplus; what about hfsutils?

I installed both. Now what should I do?

Thank you!

Post by **djph** » Sat Jun 10, 2023 4:00 pm

ScarletMcLearn wrote: ⤴Sat Jun 10, 2023 3:14 pm Thank you for your time and effort.

Here is the output:

Code: Select all

  1 Raw_Read_Error_Rate     0x000f   166   166   006    Pre-fail  Always       -       46
  9 Power_On_Hours          0x0032   054   054   000    Old_age   Always       -       40958
177 Wear_Leveling_Count     0x0032   001   001   000    Old_age   Always       -       4249
178 Used_Rsvd_Blk_Cnt_Chip  0x0032   100   100   000    Old_age   Always       -       247
179 Used_Rsvd_Blk_Cnt_Tot   0x0032   100   100   000    Old_age   Always       -       541
241 Total_Writes_GiB        0x0032   100   100   000    Old_age   Always       -       72466
250 Read_Retry_Count        0x0032   006   006   000    Old_age   Always       -       3811740296


Error 11569 occurred at disk power-on lifetime: 40955 hours (1706 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 88 00 08 00 40 40      06:18:22.820  READ FPDMA QUEUED
  47 00 01 30 08 00 a0 a0      06:18:22.820  READ LOG DMA EXT
  47 00 01 30 00 00 a0 a0      06:18:22.820  READ LOG DMA EXT
  47 00 01 00 00 00 a0 a0      06:18:22.820  READ LOG DMA EXT
  ef 10 02 00 00 00 a0 a0      06:18:22.820  SET FEATURES [Enable SATA feature]

Honestly, with over 11,000 errors logged in its ~5 year lifespan (plus the 70 TiB written) ... chances are the drive's dead --- though I can't find any real datasheets on the drive. IN GENERAL though, good drives can handle about 200-400x the drive's total capacity in TBW before failing (so your 128G drive would theoretically top out at somewhere around 50 TiB )

ScarletMcLearn · Post by **ScarletMcLearn** » Sat Jun 10, 2023 4:03 pm

I see. Thats quite unfortunate to hear.

Is there anything I can do to get it working for now?

Or is it gone for good?

Linux Mint Forums

Drives are not partitioned properly in Linux Mint XFCE.

Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.

Re: Drives are not partitioned properly in Linux Mint XFCE.