You are not logged in.

Pages: 1

#1 2021-07-24 03:27:20

Risu
Member
Registered: 2021-07-23
Posts: 12

[SOLVED]I cant access my partition

I use gnome disk to make my ntfs partition on dev/sda8 auto mounted each boot but when i reboot my arch the booting take longer than usual but i have no problem logging in to my user account, when i open file manager i can see my sda8 partition was there but when i try to open it i got a warning you have to be root user to mount the partition, so i mount it manually using terminal and i got this output:

[root@ArchLinux ~]# mount dev/sda8 /media/sda8
mount: /media/sda8: special device dev/sda8 does not exist.

I ran fdisk:

[root@ArchLinux ~]# fdisk -l -u /dev/sda
Ignoring extra data in partition table 8.
Ignoring extra data in partition table 8.
Ignoring extra data in partition table 8.
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: ST500LT012-9WS14
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: dos
Disk identifier: 0x9eca72f8

Device     Boot      Start        End   Sectors   Size Id Type
/dev/sda1  *          2048   50505727  50503680  24.1G 83 Linux
/dev/sda2         50505728   58505215   7999488   3.8G 82 Linux swap / Solaris
/dev/sda3         58507262  976767039 918259778 437.9G  5 Extended
/dev/sda5         58507264  163842047 105334784  50.2G 83 Linux
/dev/sda6        163844096  164376575    532480   260M 83 Linux
/dev/sda7        164378624  204800063  40421440  19.3G 83 Linux
/dev/sda8       2024287494 3004010606 979723113 467.2G 6c unknown

Partition 3 does not start on physical sector boundary.
Partition 8 does not start on physical sector boundary.

I ran cfdisk:

                                       Disk: /dev/sda
                   Size: 465.76 GiB, 500107862016 bytes, 976773168 sectors
                             Label: dos, identifier: 0x9eca72f8

    Device        Boot        Start         End     Sectors    Size  Id Type
>>  /dev/sda1     *            2048    50505727    50503680   24.1G  83 Linux
    /dev/sda2              50505728    58505215     7999488    3.8G  82 Linux swap / Solaris
    /dev/sda3              58507262   976767039   918259778  437.9G   5 Extended
    ├─/dev/sda5            58507264   163842047   105334784   50.2G  83 Linux
    ├─/dev/sda6           163844096   164376575      532480    260M  83 Linux
    ├─/dev/sda7           164378624   204800063    40421440   19.3G  83 Linux
    ├─Free space          204804096  2024287494  1819483399  867.6G
    └─/dev/sda8          2024287494  3004010606   979723113  467.2G  6c unknown
    Free space            976769024   976773167        4144      2M

How can i get the partition back and not to lose the data?
I hope my english is good smile

Last edited by Risu (2021-07-25 00:21:39)

Offline

#2 2021-07-24 04:40:25

loqs
Member
Registered: 2014-03-06
Posts: 19,009

Re: [SOLVED]I cant access my partition

mount dev/sda8 /media/sda8
mount: /media/sda8: special device dev/sda8 does not exist.

missing / at the start of dev/sda8

Offline

#3 2021-07-24 04:49:13

Risu
Member
Registered: 2021-07-23
Posts: 12

Re: [SOLVED]I cant access my partition

loqs wrote:
mount dev/sda8 /media/sda8
mount: /media/sda8: special device dev/sda8 does not exist.

missing / at the start of dev/sda8

still i got this:

[root@ArchLinux ~]# mount /dev/sda8 /media/sda8
mount: /media/sda8: special device /dev/sda8 does not exist.

Last edited by Risu (2021-07-24 04:50:24)

Offline

#4 2021-07-24 05:00:18

loqs
Member
Registered: 2014-03-06
Posts: 19,009

Re: [SOLVED]I cant access my partition

Have you run a S.M.A.R.T. self-test on the device?  If not please run one if the device supports it.
Then when the test finishes or if the devices does not support it post the output of

# smartctl -x /dev/sda

Also do you have a backup of the data you are trying to access?

Offline

#5 2021-07-24 05:13:34

Risu
Member
Registered: 2021-07-23
Posts: 12

Re: [SOLVED]I cant access my partition

loqs wrote:

Have you run a S.M.A.R.T. self-test on the device?  If not please run one if the device supports it.
Then when the test finishes or if the devices does not support it post the output of

# smartctl -x /dev/sda

Also do you have a backup of the data you are trying to access?

[root@ArchLinux ~]# smartctl -x /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.12.15-arch1-1] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Laptop HDD
Device Model:     ST500LT012-9WS142
Serial Number:    S0V01FMN
LU WWN Device Id: 5 000c50 051669f20
Firmware Version: 0001SDM1
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sat Jul 24 12:05:38 2021 WIB
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: Enabled

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

General SMART Values:
Offline data collection status:  (0x82)	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever
					been run.
Total time to complete Offline
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 102) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x1035)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR--   119   096   006    -    223949456
  3 Spin_Up_Time            PO----   099   099   000    -    0
  4 Start_Stop_Count        -O--CK   085   085   020    -    16155
  5 Reallocated_Sector_Ct   PO--CK   100   100   036    -    8
  7 Seek_Error_Rate         POSR--   081   060   030    -    8914477258
  9 Power_On_Hours          -O--CK   089   089   000    -    10305 (183 187 0)
 10 Spin_Retry_Count        PO--C-   100   100   097    -    0
 12 Power_Cycle_Count       -O--CK   094   094   020    -    6932
184 End-to-End_Error        -O--CK   100   100   099    -    0
187 Reported_Uncorrect      -O--CK   001   001   000    -    166
188 Command_Timeout         -O--CK   100   099   000    -    17194090732
189 High_Fly_Writes         -O-RCK   100   100   000    -    0
190 Airflow_Temperature_Cel -O---K   057   049   045    -    43 (Min/Max 30/43)
191 G-Sense_Error_Rate      -O--CK   100   100   000    -    82
192 Power-Off_Retract_Count -O--CK   100   100   000    -    208
193 Load_Cycle_Count        -O--CK   052   052   000    -    96616
194 Temperature_Celsius     -O---K   043   051   000    -    43 (0 25 0 0 0)
196 Reallocated_Event_Count POSR--   089   089   030    -    9920 (9645 0)
197 Current_Pending_Sector  -O--C-   100   100   000    -    0
198 Offline_Uncorrectable   ----C-   100   100   000    -    0
199 UDMA_CRC_Error_Count    -OSRCK   200   200   000    -    0
240 Head_Flying_Hours       ------   089   089   000    -    9920 (37 173 0)
241 Total_LBAs_Written      ------   100   253   000    -    252947519
242 Total_LBAs_Read         ------   100   253   000    -    1587065471
254 Free_Fall_Sensor        -O--CK   100   100   000    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      5  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x21       GPL     R/O      1  Write stream error log
0x22       GPL     R/O      1  Read stream error log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa1       GPL,SL  VS      20  Device vendor specific log
0xa2       GPL     VS    2248  Device vendor specific log
0xa8       GPL,SL  VS      65  Device vendor specific log
0xa9       GPL,SL  VS       1  Device vendor specific log
0xab       GPL     VS       1  Device vendor specific log
0xb0       GPL     VS    2864  Device vendor specific log
0xbd-0xbf  GPL     VS   65535  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
Device Error Count: 168 (device log contains only the most recent 20 errors)
	CR     = Command Register
	FEATR  = Features Register
	COUNT  = Count (was: Sector Count) Register
	LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
	LH     = LBA High (was: Cylinder High) Register    ]   LBA
	LM     = LBA Mid (was: Cylinder Low) Register      ] Register
	LL     = LBA Low (was: Sector Number) Register     ]
	DV     = Device (was: Device/Head) Register
	DC     = Device Control Register
	ER     = Error register
	ST     = Status register
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 168 [7] occurred at disk power-on lifetime: 6586 hours (274 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 00 06 94 10 00 00  Error: UNC at LBA = 0x00069410 = 431120

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 00 06 94 10 40 00     01:04:15.041  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 06 94 08 40 00     01:04:14.888  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 e0 00     01:04:14.888  READ LOG EXT
  60 00 00 00 80 00 00 00 06 94 08 40 00     01:04:12.312  READ FPDMA QUEUED
  60 00 00 00 80 00 00 00 06 8b 88 40 00     01:04:12.302  READ FPDMA QUEUED

Error 167 [6] occurred at disk power-on lifetime: 6586 hours (274 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 00 06 94 10 00 00  Error: UNC at LBA = 0x00069410 = 431120

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 80 00 00 00 06 94 08 40 00     01:04:12.312  READ FPDMA QUEUED
  60 00 00 00 80 00 00 00 06 8b 88 40 00     01:04:12.302  READ FPDMA QUEUED
  60 00 00 00 80 00 00 00 06 8b 08 40 00     01:04:12.293  READ FPDMA QUEUED
  60 00 00 00 80 00 00 01 4d 08 d0 40 00     01:04:12.288  READ FPDMA QUEUED
  60 00 00 00 80 00 00 01 4d 08 50 40 00     01:04:12.281  READ FPDMA QUEUED

Error 166 [5] occurred at disk power-on lifetime: 6586 hours (274 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 00 06 94 10 00 00  Error: UNC at LBA = 0x00069410 = 431120

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 26 00 00 00 06 9b 08 40 00     00:42:46.168  READ FPDMA QUEUED
  60 00 00 01 00 00 00 00 06 9a 08 40 00     00:42:46.168  READ FPDMA QUEUED
  60 00 00 01 00 00 00 00 06 99 08 40 00     00:42:46.168  READ FPDMA QUEUED
  60 00 00 01 00 00 00 00 06 98 08 40 00     00:42:46.167  READ FPDMA QUEUED
  60 00 00 01 00 00 00 00 06 97 08 40 00     00:42:46.167  READ FPDMA QUEUED

Error 165 [4] occurred at disk power-on lifetime: 6586 hours (274 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 00 06 94 10 00 00  Error: UNC at LBA = 0x00069410 = 431120

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 40 00 00 00 16 d3 9a 40 00     00:42:37.594  READ FPDMA QUEUED
  60 00 00 00 26 00 00 00 06 9b 08 40 00     00:42:37.592  READ FPDMA QUEUED
  60 00 00 01 00 00 00 00 06 9a 08 40 00     00:42:37.592  READ FPDMA QUEUED
  60 00 00 01 00 00 00 00 06 99 08 40 00     00:42:37.592  READ FPDMA QUEUED
  60 00 00 01 00 00 00 00 06 98 08 40 00     00:42:37.592  READ FPDMA QUEUED

Error 164 [3] occurred at disk power-on lifetime: 6586 hours (274 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 00 06 94 10 00 00  Error: UNC at LBA = 0x00069410 = 431120

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 01 00 00 00 00 06 94 08 40 00     00:42:33.750  READ FPDMA QUEUED
  60 00 00 01 00 00 00 00 06 95 08 40 00     00:42:33.750  READ FPDMA QUEUED
  60 00 00 01 00 00 00 00 06 96 08 40 00     00:42:33.750  READ FPDMA QUEUED
  61 00 00 00 10 00 00 00 12 fc 48 40 00     00:42:33.750  WRITE FPDMA QUEUED
  60 00 00 01 00 00 00 00 06 97 08 40 00     00:42:33.597  READ FPDMA QUEUED

Error 163 [2] occurred at disk power-on lifetime: 6586 hours (274 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 00 06 94 10 00 00  Error: UNC at LBA = 0x00069410 = 431120

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 01 00 00 00 00 13 03 d8 40 00     00:42:29.190  READ FPDMA QUEUED
  60 00 00 01 00 00 00 00 13 02 d8 40 00     00:42:29.190  READ FPDMA QUEUED
  60 00 00 01 00 00 00 00 13 01 d8 40 00     00:42:29.190  READ FPDMA QUEUED
  60 00 00 01 00 00 00 00 13 00 d8 40 00     00:42:29.190  READ FPDMA QUEUED
  60 00 00 00 26 00 00 00 06 9b 08 40 00     00:42:29.185  READ FPDMA QUEUED

Error 162 [1] occurred at disk power-on lifetime: 6586 hours (274 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 00 06 94 10 00 00  Error: UNC at LBA = 0x00069410 = 431120

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 7c 00 00 00 1a da 98 40 00     00:42:25.804  READ FPDMA QUEUED
  60 00 00 01 00 00 00 00 06 94 08 40 00     00:42:25.794  READ FPDMA QUEUED
  60 00 00 01 00 00 00 00 06 95 08 40 00     00:42:25.785  READ FPDMA QUEUED
  61 00 00 00 08 00 00 37 2b 4e e3 40 00     00:42:25.785  WRITE FPDMA QUEUED
  60 00 00 01 00 00 00 00 06 96 08 40 00     00:42:25.784  READ FPDMA QUEUED

Error 161 [0] occurred at disk power-on lifetime: 6586 hours (274 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 00 06 94 10 00 00  Error: UNC at LBA = 0x00069410 = 431120

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 7c 00 00 00 1a da 98 40 00     00:42:23.013  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 1a da 90 40 00     00:42:23.006  READ FPDMA QUEUED
  60 00 00 00 26 00 00 00 06 9b 08 40 00     00:42:22.994  READ FPDMA QUEUED
  60 00 00 01 00 00 00 00 06 9a 08 40 00     00:42:22.994  READ FPDMA QUEUED
  60 00 00 01 00 00 00 00 06 99 08 40 00     00:42:22.994  READ FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      8609         -
# 2  Short offline       Completed without error       00%      5410         -
# 3  Short offline       Completed without error       00%      3437         -
# 4  Short offline       Completed without error       00%      3119         -
# 5  Short offline       Completed without error       00%      2927         -
# 6  Short offline       Aborted by host               90%      2927         -
# 7  Short offline       Completed without error       00%      2823         -
# 8  Short offline       Completed without error       00%      2822         -
# 9  Extended offline    Completed without error       00%      2768         -
#10  Short offline       Completed without error       00%      2766         -
#11  Short offline       Completed without error       00%      2655         -
#12  Short offline       Completed without error       00%      2025         -
#13  Short offline       Completed without error       00%      1830         -
#14  Extended offline    Aborted by host               90%      1830         -
#15  Short offline       Completed without error       00%      1830         -
#16  Extended offline    Completed without error       00%      1829         -
#17  Short offline       Aborted by host               90%      1825         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version:                  3
SCT Version (vendor specific):       522 (0x020a)
Device State:                        Active (0)
Current Temperature:                    43 Celsius
Power Cycle Min/Max Temperature:     31/43 Celsius
Lifetime    Min/Max Temperature:     25/51 Celsius
Specified Max Operating Temperature:    39 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        30 minutes
Min/Max recommended Temperature:     14/55 Celsius
Min/Max Temperature Limit:           10/60 Celsius
Temperature History Size (Index):    128 (31)

Index    Estimated Time   Temperature Celsius
  32    2021-07-21 20:30     ?  -
  33    2021-07-21 21:00    29  **********
  34    2021-07-21 21:30    30  ***********
  35    2021-07-21 22:00    36  *****************
  36    2021-07-21 22:30    37  ******************
  37    2021-07-21 23:00    36  *****************
  38    2021-07-21 23:30    39  ********************
  39    2021-07-22 00:00    38  *******************
  40    2021-07-22 00:30    34  ***************
  41    2021-07-22 01:00     ?  -
  42    2021-07-22 01:30    37  ******************
  43    2021-07-22 02:00    38  *******************
  44    2021-07-22 02:30    41  **********************
  45    2021-07-22 03:00    41  **********************
  46    2021-07-22 03:30    42  ***********************
 ...    ..(  2 skipped).    ..  ***********************
  49    2021-07-22 05:00    42  ***********************
  50    2021-07-22 05:30    43  ************************
  51    2021-07-22 06:00    43  ************************
  52    2021-07-22 06:30    43  ************************
  53    2021-07-22 07:00    42  ***********************
  54    2021-07-22 07:30    42  ***********************
  55    2021-07-22 08:00    41  **********************
  56    2021-07-22 08:30    41  **********************
  57    2021-07-22 09:00    41  **********************
  58    2021-07-22 09:30    42  ***********************
  59    2021-07-22 10:00    41  **********************
  60    2021-07-22 10:30     ?  -
  61    2021-07-22 11:00    33  **************
  62    2021-07-22 11:30    35  ****************
  63    2021-07-22 12:00    38  *******************
  64    2021-07-22 12:30    39  ********************
  65    2021-07-22 13:00    42  ***********************
  66    2021-07-22 13:30    42  ***********************
  67    2021-07-22 14:00    41  **********************
  68    2021-07-22 14:30    40  *********************
  69    2021-07-22 15:00     ?  -
  70    2021-07-22 15:30    29  **********
  71    2021-07-22 16:00    29  **********
  72    2021-07-22 16:30    34  ***************
  73    2021-07-22 17:00    39  ********************
  74    2021-07-22 17:30    39  ********************
  75    2021-07-22 18:00    40  *********************
  76    2021-07-22 18:30     ?  -
  77    2021-07-22 19:00    33  **************
  78    2021-07-22 19:30     ?  -
  79    2021-07-22 20:00    34  ***************
  80    2021-07-22 20:30    35  ****************
  81    2021-07-22 21:00    43  ************************
  82    2021-07-22 21:30    43  ************************
  83    2021-07-22 22:00    43  ************************
  84    2021-07-22 22:30    42  ***********************
  85    2021-07-22 23:00     ?  -
  86    2021-07-22 23:30    33  **************
  87    2021-07-23 00:00    34  ***************
  88    2021-07-23 00:30    42  ***********************
  89    2021-07-23 01:00    43  ************************
  90    2021-07-23 01:30     ?  -
  91    2021-07-23 02:00    34  ***************
  92    2021-07-23 02:30     ?  -
  93    2021-07-23 03:00    34  ***************
  94    2021-07-23 03:30     ?  -
  95    2021-07-23 04:00    32  *************
  96    2021-07-23 04:30    33  **************
  97    2021-07-23 05:00    37  ******************
  98    2021-07-23 05:30    38  *******************
  99    2021-07-23 06:00    44  *************************
 100    2021-07-23 06:30    39  ********************
 101    2021-07-23 07:00    38  *******************
 102    2021-07-23 07:30    38  *******************
 103    2021-07-23 08:00    38  *******************
 104    2021-07-23 08:30    37  ******************
 105    2021-07-23 09:00    37  ******************
 106    2021-07-23 09:30    37  ******************
 107    2021-07-23 10:00     ?  -
 108    2021-07-23 10:30    28  *********
 109    2021-07-23 11:00    29  **********
 110    2021-07-23 11:30    35  ****************
 111    2021-07-23 12:00    37  ******************
 112    2021-07-23 12:30    38  *******************
 113    2021-07-23 13:00    38  *******************
 114    2021-07-23 13:30    39  ********************
 ...    ..(  3 skipped).    ..  ********************
 118    2021-07-23 15:30    39  ********************
 119    2021-07-23 16:00    40  *********************
 120    2021-07-23 16:30    40  *********************
 121    2021-07-23 17:00    40  *********************
 122    2021-07-23 17:30     ?  -
 123    2021-07-23 18:00    34  ***************
 124    2021-07-23 18:30    35  ****************
 125    2021-07-23 19:00    41  **********************
 126    2021-07-23 19:30    42  ***********************
 127    2021-07-23 20:00    42  ***********************
   0    2021-07-23 20:30     ?  -
   1    2021-07-23 21:00    34  ***************
   2    2021-07-23 21:30     ?  -
   3    2021-07-23 22:00    35  ****************
   4    2021-07-23 22:30    35  ****************
   5    2021-07-23 23:00    40  *********************
   6    2021-07-23 23:30    40  *********************
   7    2021-07-24 00:00    41  **********************
   8    2021-07-24 00:30    44  *************************
   9    2021-07-24 01:00    39  ********************
  10    2021-07-24 01:30    41  **********************
  11    2021-07-24 02:00    41  **********************
  12    2021-07-24 02:30    40  *********************
  13    2021-07-24 03:00    40  *********************
  14    2021-07-24 03:30    40  *********************
  15    2021-07-24 04:00     ?  -
  16    2021-07-24 04:30    32  *************
  17    2021-07-24 05:00    33  **************
  18    2021-07-24 05:30    38  *******************
  19    2021-07-24 06:00     ?  -
  20    2021-07-24 06:30    29  **********
  21    2021-07-24 07:00     ?  -
  22    2021-07-24 07:30    31  ************
  23    2021-07-24 08:00    31  ************
  24    2021-07-24 08:30    40  *********************
  25    2021-07-24 09:00    41  **********************
  26    2021-07-24 09:30    41  **********************
  27    2021-07-24 10:00    41  **********************
  28    2021-07-24 10:30    42  ***********************
  29    2021-07-24 11:00    42  ***********************
  30    2021-07-24 11:30    42  ***********************
  31    2021-07-24 12:00    43  ************************

SCT Error Recovery Control command not supported

Device Statistics (GP/SMART Log 0x04) not supported

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x000a  2           41  Device-to-host register FISes sent due to a COMRESET
0x0001  2            0  Command failed due to ICRC error
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS

If its the data on sda8 partition, i didnt have a backup of it

Offline

#6 2021-07-24 06:28:50

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,424

Re: [SOLVED]I cant access my partition

I use gnome disk to make my ntfs partition on dev/sda8 auto mounted each boot

Why did you use a partition manager to configure fstab? What did you *actually* do?

    ├─Free space          204804096  2024287494  1819483399  867.6G
    └─/dev/sda8          2024287494  3004010606   979723113  467.2G  6c unknown

Why is there an empty block and why does sda8 have an invalid/unspecified partition type?

  5 Reallocated_Sector_Ct   PO--CK   100   100   036    -    8
…
187 Reported_Uncorrect      -O--CK   001   001   000    -    166
…
196 Reallocated_Event_Count POSR--   089   089   030    -    9920 (9645 0)

Not re-assuring… but the last errors are ~150 run-days ago.

I assume you re-arranged the partition table and sda8 used to begin at sector 204804096 (the free space)
You can just fix the partition table (the underlying filesystems would remain untouched, ie. if there previously was no free space and you edit the partition table to make sda8 begin at it's proper location, the filesystem would magically™ re-appear.
See https://wiki.archlinux.org/title/File_r … d_PhotoRec - testdisk can find filesystem headers on the drive if you're unsure about the previous layout.

i didnt have a backup of it

I strongly recommend to copy the entire drive and experiment on the copy unless you understand what you're doing. This way, if you fuck up things even more, you at least have the master to return to and restart from.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2021-07-24 07:59:16

Risu
Member
Registered: 2021-07-23
Posts: 12

Re: [SOLVED]I cant access my partition

Why did you use a partition manager to configure fstab? What did you *actually* do?

At first i was trying to make my Linux Mint /home (/dev/sda5) partition mounted each time i boot my Arch using gnome-disk-utility and it worked but when i tried to make my ntfs partition (/dev/sda8) mounted each boot using the same way it didnt work

Why is there an empty block and why does sda8 have an invalid/unspecified partition type?

As for this i dont know why, it happens after using gnome disk to make my ntfs partition mounted each boot

Offline

#8 2021-07-24 08:03:34

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,424

Re: [SOLVED]I cant access my partition

As for this i dont know why, it happens after using gnome disk to make my ntfs partition mounted each boot

This ties into

seth wrote:

What did you *actually* do?

My best guess is that you moved the partition start position and restoring the original start sector will undo and fix your partition.
BUT:

seth wrote:

I strongly recommend to copy the entire drive and experiment on the copy unless you understand what you're doing. This way, if you fuck up things even more, you at least have the master to return to and restart from.

Use fdisk, remove the sda8 partition, create a new partition that covers the entire empty space (and assign it the NTFS type), BUT:

seth wrote:

I strongly recommend to copy the entire drive and experiment on the copy unless you understand what you're doing. This way, if you fuck up things even more, you at least have the master to return to and restart from.

Oh, and did I mention that

seth wrote:

I strongly recommend to copy the entire drive and experiment on the copy unless you understand what you're doing. This way, if you fuck up things even more, you at least have the master to return to and restart from.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2021-07-24 08:08:06

Risu
Member
Registered: 2021-07-23
Posts: 12

Re: [SOLVED]I cant access my partition

I assume you re-arranged the partition table and sda8 used to begin at sector 204804096 (the free space)
You can just fix the partition table (the underlying filesystems would remain untouched, ie. if there previously was no free space and you edit the partition table to make sda8 begin at it's proper location, the filesystem would magically™ re-appear.
See https://wiki.archlinux.org/title/File_r … d_PhotoRec - testdisk can find filesystem headers on the drive if you're unsure about the previous layout.

I use testdisk and found my ntfs partition was there, what should i do?

TestDisk 7.1, Data Recovery Utility, July 2019
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org

Disk /dev/sda - 500 GB / 465 GiB - CHS 60801 255 63
     Partition               Start        End    Size in sectors
 * Linux                    0  32 33  3143 213 14   50503680 (my linux mint partition)
 P Linux Swap            3143 213 15  3641 199 14    7999488
 P Linux                 3641 231 47 10198 177 27  105334784 (linux mint /home partition)
 L Linux                10198 209 60 10231 246 63     532480
 L Linux                10232  24 33 12748  86 10   40423424 (my arch partition)
>D HPFS - NTFS          12748  86 11 58251 138 63  731009024 (this is the sda8 ntfs partition)
 D HPFS - NTFS          57615   1  6 60800 254 63   51183022 (i dont know where this come from)









Structure: Ok.  Use Up/Down Arrow keys to select partition.
Use Left/Right Arrow keys to CHANGE partition characteristics:
*=Primary bootable  P=Primary  L=Logical  E=Extended  D=Deleted
Keys A: add partition, L: load backup, T: change type, P: list files,
     Enter: to continue
NTFS, blocksize=4096, 374 GB / 348 GiB

Last edited by Risu (2021-07-24 08:20:53)

Offline

#10 2021-07-24 08:19:11

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,424

Re: [SOLVED]I cant access my partition

Add it and fix the partition table.
To re-iterate:

seth wrote:

I strongly recommend to copy the entire drive and experiment on the copy unless you understand what you're doing. This way, if you fuck up things even more, you at least have the master to return to and restart from.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2021-07-24 08:36:24

Risu
Member
Registered: 2021-07-23
Posts: 12

Re: [SOLVED]I cant access my partition

seth wrote:

Add it and fix the partition table.

I press A: add partition and this show up, what should i do next?

Disk /dev/sda - 500 GB / 465 GiB - CHS 60801 255 63





  No partition         12748  86 11 57615   1  4  720782994







>[Cylinder]  [  Head  ]  [ Sector ]  [Cylinder]  [  Head  ]  [ Sector ]
 [  Type  ]  [  Done  ]



                            Change starting cylinder
seth wrote:

I strongly recommend to copy the entire drive and experiment on the copy unless you understand what you're doing. This way, if you fuck up things even more, you at least have the master to return to and restart from.

Yes, i already copied all the important file to another disk, but at least i want to see if i can fix it without deleting the partition

Offline

#12 2021-07-24 10:17:48

WorMzy
Administrator
From: Scotland
Registered: 2010-06-16
Posts: 13,629
Website

Re: [SOLVED]I cant access my partition

Please edit your topic title to remove the redundant cry for help.

https://wiki.archlinux.org/title/Genera … ow_to_post

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#13 2021-07-24 11:37:46

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,424

Re: [SOLVED]I cant access my partition

You do not need to use testdisk for this. The partition table is complete nonsense.
Use fdisk, remove sda8 (this dosn't delete any data, let alone on the partition because the entry is complete garbage) and create a new partition that covers the free space on the disk.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#14 2021-07-24 12:18:52

Risu
Member
Registered: 2021-07-23
Posts: 12

Re: [SOLVED]I cant access my partition

I found the solution using fdisk, i booted my Arch live usb, fdisk to /dev/sda, put it to sector mode (u) and print the table (p), i see my disk end with 6080 cylinder but sda8 ends with 6800 (dont know why it changed big_smile), then i delete the partition (d), recreate the partition (n), use the correct starting and ending sector to make it fit within the disk, finally i checked the partition table again (p) and it was in the right order, save and quit (w).
Tadaaa it took me about 10 sec and everything is back like nothing happens big_smile

Last edited by Risu (2021-07-24 12:21:22)

Offline

#15 2021-07-24 12:24:24

Risu
Member
Registered: 2021-07-23
Posts: 12

Re: [SOLVED]I cant access my partition

seth wrote:

You do not need to use testdisk for this. The partition table is complete nonsense.
Use fdisk, remove sda8 (this dosn't delete any data, let alone on the partition because the entry is complete garbage) and create a new partition that covers the free space on the disk.

Yes, i solved the problem using fdisk on Arch live usb and everything is back to normal, thank you so much for your help smile

Offline

#16 2021-07-24 14:48:55

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,424

Re: [SOLVED]I cant access my partition

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB