[opensuse] 15.0 won't mount EFI System sdb1 partition
![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
This M.2 device I just bought turned out to be used instead of new as expected. So, I wanted to see what's on it. Booted normally to a /dev/sda filesystem, trying to mount -t vfat or -t auto just gives a generic error "wrong fstype, bad option, bad superblock, blah blah". -t auto worked just fine for NTFS sdb3. What's the secret to examining an EFI System partition when the one used for booting is already on /boot/efi/? Man mount doesn't seem to make any mention of an EFI System partition. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/28fb60f36a5c05d6e95d00be1c0c257c.jpg?s=120&d=mm&r=g)
Le 10/05/2018 à 07:46, Felix Miata a écrit :
booting is already on /boot/efi/? Man mount doesn't seem to make any mention of an EFI System partition.
what say fdisk -l ? jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
jdd@dodin.org composed on 2018-05-10 08:12 (UTC+0200):
Felix Miata composed:
booting is already on /boot/efi/? Man mount doesn't seem to make any mention of an EFI System partition.
what say
fdisk -l
Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 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 Disklabel type: gpt Disk identifier: 5A35BCBC... Device Start End Sectors Size Type /dev/sda1 2048 657407 655360 320M EFI System /dev/sda2 657408 5375999 4718592 2.3G Linux swap /dev/sda3 5376000 10078207 4702208 2.2G Linux filesystem /dev/sda4 10078208 23185407 13107200 6.3G Linux filesystem /dev/sda5 23185408 55953407 32768000 15.6G Linux filesystem /dev/sda6 55953408 70699007 14745600 7G Linux filesystem /dev/sda7 70699008 85444607 14745600 7G Linux filesystem /dev/sda8 85444608 100190207 14745600 7G Linux filesystem /dev/sda9 100190208 114935807 14745600 7G Linux filesystem Disk /dev/sdb: 238.5 GiB, 256060514304 bytes, 500118192 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 Disklabel type: gpt Disk identifier: 906907CA... Device Start End Sectors Size Type /dev/sdb1 2048 616447 614400 300M EFI System /dev/sdb2 616448 878591 262144 128M Microsoft reserved /dev/sdb3 878592 498274303 497395712 237.2G Microsoft basic data /dev/sdb4 498274304 500117503 1843200 900M Windows recovery environment -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/28fb60f36a5c05d6e95d00be1c0c257c.jpg?s=120&d=mm&r=g)
Le 10/05/2018 à 08:37, Felix Miata a écrit :
jdd@dodin.org composed on 2018-05-10 08:12 (UTC+0200):
Felix Miata composed:
booting is already on /boot/efi/? Man mount doesn't seem to make any mention of an EFI System partition.
what say
fdisk -l
Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors
Disklabel type: gpt Disk identifier: 5A35BCBC...
Device Start End Sectors Size Type /dev/sda1 2048 657407 655360 320M EFI System
if I understand well, this is the problematic disk (you said /dev/sda)?
/dev/sda2 657408 5375999 4718592 2.3G Linux swap /dev/sda3 5376000 10078207 4702208 2.2G Linux filesystem /dev/sda4 10078208 23185407 13107200 6.3G Linux filesystem /dev/sda5 23185408 55953407 32768000 15.6G Linux filesystem /dev/sda6 55953408 70699007 14745600 7G Linux filesystem /dev/sda7 70699008 85444607 14745600 7G Linux filesystem /dev/sda8 85444608 100190207 14745600 7G Linux filesystem /dev/sda9 100190208 114935807 14745600 7G Linux filesystem
lot of very small linux partitions?
Disk /dev/sdb: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Disklabel type: gpt Disk identifier: 906907CA...
Device Start End Sectors Size Type /dev/sdb1 2048 616447 614400 300M EFI System /dev/sdb2 616448 878591 262144 128M Microsoft reserved /dev/sdb3 878592 498274303 497395712 237.2G Microsoft basic data /dev/sdb4 498274304 500117503 1843200 900M Windows recovery environment
or is it that second one, that looks like a windows disk? anyway, the EFI partition (any) have to be vfat and AFAIK is mountable normally as such. My guess is that the disk was erased, that is file systems removed, but without removing partitions, so there is nothing to mount. you should ignore the partition system and copy on it what you want jdd
-- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
jdd@dodin.org composed on 2018-05-10 08:57 (UTC+0200):
Felix Miata composed:
Device Start End Sectors Size Type /dev/sda1 2048 657407 655360 320M EFI System
if I understand well, this is the problematic disk (you said /dev/sda)?
/dev/sda2 657408 5375999 4718592 2.3G Linux swap /dev/sda3 5376000 10078207 4702208 2.2G Linux filesystem /dev/sda4 10078208 23185407 13107200 6.3G Linux filesystem /dev/sda5 23185408 55953407 32768000 15.6G Linux filesystem /dev/sda6 55953408 70699007 14745600 7G Linux filesystem /dev/sda7 70699008 85444607 14745600 7G Linux filesystem /dev/sda8 85444608 100190207 14745600 7G Linux filesystem /dev/sda9 100190208 114935807 14745600 7G Linux filesystem
lot of very small linux partitions?
# df /dev/sda1 Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 327024 26596 300428 9% /boot/efi # ll /dev/sda1 total 68 drwxrwxr-x 17 root root 4096 Feb 21 22:24 . drwxrwxr-x 4 root root 4096 Dec 31 1969 .. drwxrwxr-x 2 root root 4096 Dec 18 09:00 debian drwxrwxr-x 2 root root 4096 Dec 18 09:00 debian.1712 drwxrwxr-x 2 root root 4096 Dec 17 06:53 opensuse drwxrwxr-x 2 root root 4096 Feb 15 12:14 suse-tw drwxrwxr-x 2 root root 4096 Dec 17 06:53 suse-tw.01 drwxrwxr-x 2 root root 4096 Dec 17 06:53 suse-tw.02 drwxrwxr-x 2 root root 4096 Feb 15 12:14 suse-tw.03 drwxrwxr-x 2 root root 4096 Feb 15 04:20 opensuse150 drwxrwxr-x 2 root root 4096 Dec 17 06:53 suse150.01 drwxrwxr-x 2 root root 4096 Dec 17 06:53 suse150.02 drwxrwxr-x 2 root root 4096 Feb 15 04:20 suse150.03 drwxrwxr-x 2 root root 4096 Feb 15 04:20 suse150.04 drwxrwxr-x 2 root root 4096 Feb 6 15:50 opensuse423 drwxrwxr-x 2 root root 4096 Dec 17 06:53 suse423.01 drwxrwxr-x 2 root root 4096 Feb 6 15:50 suse423.02 # df / Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda7 7248654 3478518 3393304 51% /
Disk /dev/sdb: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Disklabel type: gpt Disk identifier: 906907CA...
Device Start End Sectors Size Type /dev/sdb1 2048 616447 614400 300M EFI System /dev/sdb2 616448 878591 262144 128M Microsoft reserved /dev/sdb3 878592 498274303 497395712 237.2G Microsoft basic data /dev/sdb4 498274304 500117503 1843200 900M Windows recovery environment
or is it that second one, that looks like a windows disk?
sdb is usually a second disk. ;-) In this case, it's the "new" but obviously used M.2 card complete with a Windows 10 64-bit build 15063 installation on sdb3.
anyway, the EFI partition (any) have to be vfat and AFAIK is mountable normally as such.
My guess is that the disk was erased, that is file systems removed, but without removing partitions, so there is nothing to mount.
Could be something like that: # fsck.vfat /dev/sdb1 fsck.fat 4.1 (2017-01-24) Logical sector size is zero. 8-|
you should ignore the partition system and copy on it what you want
I'm still considering returning for refund, since I didn't intend to buy a used device for the price paid. AFAIK, the 3 year OEM warranty such Kingston device should have is probably void as to Kingston, while its Newegg Marketplace vendor I never heard of before might not even exist 3 years from now. Newegg proper has an apparently brand new Crucial for the same price. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/28fb60f36a5c05d6e95d00be1c0c257c.jpg?s=120&d=mm&r=g)
Le 10/05/2018 à 09:42, Felix Miata a écrit :
sdb is usually a second disk. ;-) In this case, it's the "new" but obviously used M.2 card complete with a Windows 10 64-bit build 15063 installation on sdb3.
anyway, the EFI partition (any) have to be vfat and AFAIK is mountable normally as such.
My guess is that the disk was erased, that is file systems removed, but without removing partitions, so there is nothing to mount.
Could be something like that:
# fsck.vfat /dev/sdb1 fsck.fat 4.1 (2017-01-24) Logical sector size is zero.
8-|
if done from windows, I have little knowledge of what happen :-(
you should ignore the partition system and copy on it what you want
I'm still considering returning for refund, since I didn't intend to buy a used device for the price paid. AFAIK, the 3 year OEM warranty such Kingston device should have is probably void as to Kingston, while its Newegg Marketplace vendor I never heard of before might not even exist 3 years from now. Newegg proper has an apparently brand new Crucial for the same price.
it's probably a client return. But you should better have a new one, for sure :-( I often buy such product, but sold as second hand and with lower price jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 2018-05-10 09:47, jdd@dodin.org wrote:
Le 10/05/2018 à 09:42, Felix Miata a écrit :
I'm still considering returning for refund, since I didn't intend to buy a used device for the price paid. AFAIK, the 3 year OEM warranty such Kingston device should have is probably void as to Kingston, while its Newegg Marketplace vendor I never heard of before might not even exist 3 years from now. Newegg proper has an apparently brand new Crucial for the same price.
it's probably a client return. But you should better have a new one, for sure :-(
Very probably.
I often buy such product, but sold as second hand and with lower price
But in this case the vendor lied. It is possible to find out how much used is that disk. Run this: Telcontar:~ # smartctl -A /dev/sde | grep -i hours 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 2986 Telcontar:~ # Mine has 2986 hours of use. Or display it all, there are interesting parameters: Telcontar:~ # smartctl -A /dev/sde smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.4.126-48-default] (SUSE RPM) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 1 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 2986 12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 287 177 Wear_Leveling_Count 0x0013 099 099 000 Pre-fail Always - 7 179 Used_Rsvd_Blk_Cnt_Tot 0x0013 100 100 010 Pre-fail Always - 0 181 Program_Fail_Cnt_Total 0x0032 100 100 010 Old_age Always - 0 182 Erase_Fail_Count_Total 0x0032 100 100 010 Old_age Always - 0 183 Runtime_Bad_Block 0x0013 100 100 010 Pre-fail Always - 0 187 Uncorrectable_Error_Cnt 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0032 073 060 000 Old_age Always - 27 195 ECC_Error_Rate 0x001a 200 200 000 Old_age Always - 0 199 CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0 235 POR_Recovery_Count 0x0012 099 099 000 Old_age Always - 13 241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 4356147880 The last tells how may sectors were written. On another SSD (actually an m2) I get others: 230 Life_Curve_Status 0x0013 100 100 000 Pre-fail Always - 100 231 SSD_Life_Left 0x0000 097 097 011 Old_age Offline - 34359738369 233 SandForce_Internal 0x0032 000 000 000 Old_age Always - 5674 234 SandForce_Internal 0x0032 000 000 000 Old_age Always - 2452 241 Lifetime_Writes_GiB 0x0032 000 000 000 Old_age Always - 2452 242 Lifetime_Reads_GiB 0x0032 000 000 000 Old_age Always - 774 244 Unknown_Attribute 0x0000 099 099 010 Old_age Offline - 2687006 -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
Carlos E. R. composed on 2018-05-10 13:05 (UTC+0200):
jdd@dodin.org wrote:
it's probably a client return. But you should better have a new one, for sure :-(
Very probably.
I often buy such product, but sold as second hand and with lower price
But in this case the vendor lied.
Actually, it reported neither new, used, refurb nor anything else about its age.
It is possible to find out how much used is that disk. Run this:
Telcontar:~ # smartctl -A /dev/sde | grep -i hours 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 2986 Telcontar:~ #
Mine has 2986 hours of use.
Or display it all, there are interesting parameters: ... 241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 4356147880 ... On another SSD (actually an m2) I get others:
230 Life_Curve_Status 0x0013 100 100 000 Pre-fail Always - 100 231 SSD_Life_Left 0x0000 097 097 011 Old_age Offline - 34359738369 233 SandForce_Internal 0x0032 000 000 000 Old_age Always - 5674 234 SandForce_Internal 0x0032 000 000 000 Old_age Always - 2452 241 Lifetime_Writes_GiB 0x0032 000 000 000 Old_age Always - 2452 242 Lifetime_Reads_GiB 0x0032 000 000 000 Old_age Always - 774 244 Unknown_Attribute 0x0000 099 099 010 Old_age Offline - 2687006
Rather less informative mine: OS version : Linux 4.12.14 env TERM=linux root on gb250 Number of disks : 2 Disk 2 L-Geo from: GPT table, likely 1-MiB cylinders (GPT guard present in MBR) Disk 2 forcing : cylinders from 31130 to 244199 Disk 2 forcing : heads from 255 to 64 Disk 2 forcing : sectors from 63 to 32 L-Geo Disk 2 Cyl : 244199 H: 64 S:32 Bps:512 Size:0x1DCF3800 = 238.5 GiB S-Geo Disk 2 Cyl : 31130 H:255 S:63 Bps:512 Size:0x1DCEF91A = 238.5 GiB BIOS Int13 limit : 1024, I13X support needed beyond : 1024.0 MiB MBR crc 8bff08f2 : 0x88bad147 = Bootcode not present. Start of sector is empty! DFSee Linux 14.12: Executing: fdisk -r- -w- Command timestamp : Thursday 2018-05-10 00:21:34 +---+--+--+-----------------+--------+--------+-----------+----------------------------------------+-----------+ |ID |ux|Dr|Type, description|Format |Related |VolumeLabel|OS2-LVM/BM / GPT / Crypt / additional in| Size MiB | +--</dev/sdb GPT disk 2>--------+--------+-----------<KINGSTON RBU-SNS>-----------------------+-----------+ |10 | | |Fsp + GPT hdr/pta|-- -- --|-- -- --|- - - - - -|Size 0x7de sectors | 1.0| |10 | 1| |EFI System (ESP)|FAT32 |MSDOS5.0|SYSTEM |EFI system partition | 300.0| |11 | 2| |MS Reserved (MSR)| |Windows | |Microsoft reserved partition | 128.0| |12 | 3| |Windows BasicData|NTFS |Win NT |Windows |Basic data partition | 242869.0| |13 | 4| |Windows Recovery |NTFS |Win NT |WinRE tools|Basic data partition | 900.0| |15 | | |Fsp + GPT pta/hdr|-- -- --|-- -- --|- - - - - -|Size 0x28f sectors | 0.320| # fdisk -l /dev/sdb Disk /dev/sdb: 238.5 GiB, 256060514304 bytes, 500118192 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 Disklabel type: gpt Disk identifier: 906907CA-E46B-4C6D-B8FA-CDC680E4F5B4 Device Start End Sectors Size Type /dev/sdb1 2048 616447 614400 300M EFI System /dev/sdb2 616448 878591 262144 128M Microsoft reserved /dev/sdb3 878592 498274303 497395712 237.2G Microsoft basic data /dev/sdb4 498274304 500117503 1843200 900M Windows recovery environment # df /dev/sdb3 Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdb3 248697852 50800036 197897816 21% /mnt # smartctl -A /dev/sdb smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.12.14-lp150.8-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0 3 Spin_Up_Time 0x0007 100 100 050 Pre-fail Always - 0 5 Reallocated_Sector_Ct 0x0013 100 100 050 Pre-fail Always - 0 7 Unknown_SSD_Attribute 0x000b 100 100 050 Pre-fail Always - 0 8 Unknown_SSD_Attribute 0x0005 100 100 050 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 11 12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 60 168 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 0 170 Unknown_Attribute 0x0003 100 100 010 Pre-fail Always - 295 173 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 1 175 Program_Fail_Count_Chip 0x0013 100 100 050 Pre-fail Always - 0 187 Reported_Uncorrect 0x0012 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0012 100 100 000 Old_age Always - 7 194 Temperature_Celsius 0x0023 070 049 020 Pre-fail Always - 30 (Min/Max 24/51) 196 Reallocated_Event_Count 0x0002 100 100 010 Old_age Always - 0 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0 199 UDMA_CRC_Error_Count 0x000b 100 100 050 Pre-fail Always - 0 218 Unknown_Attribute 0x000b 100 100 050 Pre-fail Always - 0 231 Temperature_Celsius 0x0013 100 100 000 Pre-fail Always - 100 233 Media_Wearout_Indicator 0x000b 100 100 000 Pre-fail Always - 38 240 Unknown_SSD_Attribute 0x0013 100 100 000 Pre-fail Always - 0 241 Total_LBAs_Written 0x0012 100 100 000 Old_age Always - 81 242 Total_LBAs_Read 0x0012 100 100 000 Old_age Always - 407 244 Unknown_Attribute 0x0002 100 100 000 Old_age Always - 0 245 Unknown_Attribute 0x0002 100 100 000 Old_age Always - 1 246 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 23200 # file -s /dev/sdb1 /dev/sdb1: data # fsck /dev/sdb1 fsck from util-linux 2.31.1 e2fsck 1.43.9 (8-Feb-2018) e2fsck: need terminal for interactive repairs # fsck.vfat /dev/sdb1 Logical sector size is zero. fsck.fat 4.1 (2017-01-24) A look in a binary editor at sdb1 shows nothing but nulls. Based upon smartctl it looks like the device may simply have been briefly tested, while the 21% in use on sdb3 suggests otherwise. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/28fb60f36a5c05d6e95d00be1c0c257c.jpg?s=120&d=mm&r=g)
Le 10/05/2018 à 16:13, Felix Miata a écrit :
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 11
A look in a binary editor at sdb1 shows nothing but nulls. Based upon smartctl it looks like the device may simply have been briefly tested, while the 21% in use on sdb3 suggests otherwise.
testing may simply mean verifying speed by copying random data 11 hour mean probably a labor day still not brand new... jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 2018-05-10 16:13, Felix Miata wrote:
Carlos E. R. composed on 2018-05-10 13:05 (UTC+0200):
jdd@dodin.org wrote:
it's probably a client return. But you should better have a new one, for sure :-(
Very probably.
I often buy such product, but sold as second hand and with lower price
But in this case the vendor lied.
Actually, it reported neither new, used, refurb nor anything else about its age.
He did not caught his own fingers.
DFSee Linux 14.12: Executing: fdisk -r- -w- Command timestamp : Thursday 2018-05-10 00:21:34 +---+--+--+-----------------+--------+--------+-----------+----------------------------------------+-----------+ |ID |ux|Dr|Type, description|Format |Related |VolumeLabel|OS2-LVM/BM / GPT / Crypt / additional in| Size MiB | +--</dev/sdb GPT disk 2>--------+--------+-----------<KINGSTON RBU-SNS>-----------------------+-----------+ |10 | | |Fsp + GPT hdr/pta|-- -- --|-- -- --|- - - - - -|Size 0x7de sectors | 1.0| |10 | 1| |EFI System (ESP)|FAT32 |MSDOS5.0|SYSTEM |EFI system partition | 300.0| |11 | 2| |MS Reserved (MSR)| |Windows | |Microsoft reserved partition | 128.0| |12 | 3| |Windows BasicData|NTFS |Win NT |Windows |Basic data partition | 242869.0| |13 | 4| |Windows Recovery |NTFS |Win NT |WinRE tools|Basic data partition | 900.0| |15 | | |Fsp + GPT pta/hdr|-- -- --|-- -- --|- - - - - -|Size 0x28f sectors | 0.320|
It looks like an attempted Windows installation or migration from hard disk to ssd.
Device Start End Sectors Size Type /dev/sdb1 2048 616447 614400 300M EFI System /dev/sdb2 616448 878591 262144 128M Microsoft reserved /dev/sdb3 878592 498274303 497395712 237.2G Microsoft basic data /dev/sdb4 498274304 500117503 1843200 900M Windows recovery environment
# df /dev/sdb3 Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdb3 248697852 50800036 197897816 21% /mnt
Later it says that 81 LBA blocks were written, does not match if that usage is actual usage with no holes.
# smartctl -A /dev/sdb smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.12.14-lp150.8-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0 3 Spin_Up_Time 0x0007 100 100 050 Pre-fail Always - 0 5 Reallocated_Sector_Ct 0x0013 100 100 050 Pre-fail Always - 0 7 Unknown_SSD_Attribute 0x000b 100 100 050 Pre-fail Always - 0 8 Unknown_SSD_Attribute 0x0005 100 100 050 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 11 <========== 12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 60 <========== 168 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 0 170 Unknown_Attribute 0x0003 100 100 010 Pre-fail Always - 295 173 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 1 175 Program_Fail_Count_Chip 0x0013 100 100 050 Pre-fail Always - 0 187 Reported_Uncorrect 0x0012 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0012 100 100 000 Old_age Always - 7 194 Temperature_Celsius 0x0023 070 049 020 Pre-fail Always - 30 (Min/Max 24/51) 196 Reallocated_Event_Count 0x0002 100 100 010 Old_age Always - 0 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0 199 UDMA_CRC_Error_Count 0x000b 100 100 050 Pre-fail Always - 0 218 Unknown_Attribute 0x000b 100 100 050 Pre-fail Always - 0 231 Temperature_Celsius 0x0013 100 100 000 Pre-fail Always - 100 233 Media_Wearout_Indicator 0x000b 100 100 000 Pre-fail Always - 38 240 Unknown_SSD_Attribute 0x0013 100 100 000 Pre-fail Always - 0 241 Total_LBAs_Written 0x0012 100 100 000 Old_age Always - 81 <=========== 242 Total_LBAs_Read 0x0012 100 100 000 Old_age Always - 407 244 Unknown_Attribute 0x0002 100 100 000 Old_age Always - 0 245 Unknown_Attribute 0x0002 100 100 000 Old_age Always - 1 246 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 23200
There are too many unknown attributes with SSDs :-(
# file -s /dev/sdb1 /dev/sdb1: data
# fsck /dev/sdb1 fsck from util-linux 2.31.1 e2fsck 1.43.9 (8-Feb-2018) e2fsck: need terminal for interactive repairs
can't be e2fsck.
# fsck.vfat /dev/sdb1 Logical sector size is zero. fsck.fat 4.1 (2017-01-24)
A look in a binary editor at sdb1 shows nothing but nulls.
Probably partitioned but not formatted.
Based upon smartctl it looks like the device may simply have been briefly tested, while the 21% in use on sdb3 suggests otherwise.
It may be a partially completed cloning process. The 81 LBA sectors actually written is a small figure, I wonder why. Depends on the LBA size. Is it 512 bytes, or is it perhaps 32 or 128 KB, which is the minimal write block on an SSD? I don't know. If you intend to keep and use that disk, do a full erase (not actually filling all with zeros, that's too much wear), and then partition and format yourself. Otherwise, just return it because the disk was used and he did not say so. Or ask for a lower price. Notice that new disks may have some hours of use for testing at factory, but may not be partitioned. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
Carlos E. R. composed on 2018-05-10 20:52 (UTC+0200):
He did not caught his own fingers.
?????
It looks like an attempted Windows installation or migration from hard disk to ssd.
Or brief test, begun as if it were to be a full clone.
Later it says that 81 LBA blocks were written, does not match if that usage is actual usage with no holes.
I have idea since it was an OEM pull, it was being given a short test to confirm not dead before shipping.
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 11 <========== 12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 60 <========== 241 Total_LBAs_Written 0x0012 100 100 000 Old_age Always - 81 <=========== 242 Total_LBAs_Read 0x0012 100 100 000 Old_age Always - 407 ... It may be a partially completed cloning process. ... The 81 LBA sectors actually written is a small figure, I wonder why. ... If you intend to keep and use that disk, do a full erase (not actually filling all with zeros, that's too much wear), and then partition and format yourself. Otherwise, just return it because the disk was used and he did not say so. Or ask for a lower price.
First reply from vendor after my "misleading ad" report: "We sincerely apologize that you received a brand-new OEM pull when you were expecting a retail SSD. You may certainly return it for a full refund (we will provide a return label) or you may keep the SSD and we will provide a partial refund, as our way of apologizing for all the trouble." Second reply: "We will be happy to honor the 3 year warranty: if the SSD proves defective within 3 years of purchase, just reach out to us via email or phone, and we will be happy to replace it." I accepted a 21% refund. 11 POH were low enough, probably at least half my own letting the PC just sit while not finding a man page answer to sdb1 mounting and then running this thread, not first thinking about the possibility of incomplete cloning, and investigating with a disk editor. One significant thing stopping me from proceeding to partition it is figuring out if it should have any swap allocated. Data is going on rust. I didn't really plan on getting it in the first place, never had an M.2 before, and neither paid any attention to discussions on the subject. The other delay actually installing anything is figuring out whether the M.2 ought to be HD0 instead of HD1 before configuring a RAID for data. I really don't like blingy busy GUI BIOS setup. :-( -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 2018-05-10 23:29, Felix Miata wrote:
Carlos E. R. composed on 2018-05-10 20:52 (UTC+0200):
He did not caught his own fingers.
?????
Oh. Spanish expression, then, I thought it would be more universal. Getting the fingers of oneself caught on the door hinge. Figuratively, it means the vendor was careful with his words, not claiming new, not saying it wasn't either.
It looks like an attempted Windows installation or migration from hard disk to ssd.
Or brief test, begun as if it were to be a full clone.
Later it says that 81 LBA blocks were written, does not match if that usage is actual usage with no holes.
I have idea since it was an OEM pull, it was being given a short test to confirm not dead before shipping.
Ah.
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 11 <========== 12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 60 <========== 241 Total_LBAs_Written 0x0012 100 100 000 Old_age Always - 81 <=========== 242 Total_LBAs_Read 0x0012 100 100 000 Old_age Always - 407 ... It may be a partially completed cloning process. ... The 81 LBA sectors actually written is a small figure, I wonder why. ... If you intend to keep and use that disk, do a full erase (not actually filling all with zeros, that's too much wear), and then partition and format yourself. Otherwise, just return it because the disk was used and he did not say so. Or ask for a lower price.
First reply from vendor after my "misleading ad" report: "We sincerely apologize that you received a brand-new OEM pull when you were expecting a retail SSD. You may certainly return it for a full refund (we will provide a return label) or you may keep the SSD and we will provide a partial refund, as our way of apologizing for all the trouble." Second reply: "We will be happy to honor the 3 year warranty: if the SSD proves defective within 3 years of purchase, just reach out to us via email or phone, and we will be happy to replace it."
I accepted a 21% refund. 11 POH were low enough, probably at least half my own letting the PC just sit while not finding a man page answer to sdb1 mounting and then running this thread, not first thinking about the possibility of incomplete cloning, and investigating with a disk editor.
:-)
One significant thing stopping me from proceeding to partition it is figuring out if it should have any swap allocated. Data is going on rust. I didn't really plan on getting it in the first place, never had an M.2 before, and neither paid any attention to discussions on the subject.
Having swap on sata-SSD is bliss. Gave new life to my computer, as I can not add RAM. Having it on M.2 would be bliss squared :-)
The other delay actually installing anything is figuring out whether the M.2 ought to be HD0 instead of HD1 before configuring a RAID for data. I really don't like blingy busy GUI BIOS setup. :-(
Unless you have two such disks, don't. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
![](https://seccdn.libravatar.org/avatar/28fb60f36a5c05d6e95d00be1c0c257c.jpg?s=120&d=mm&r=g)
Le 11/05/2018 à 13:03, Carlos E. R. a écrit :
Having swap on sata-SSD is bliss. Gave new life to my computer, as I can not add RAM. Having it on M.2 would be bliss squared :-)
only if the m2 is nvme pci, else it's the same as sata ssd (apart the size, me use msata) jdd
-- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 2018-05-11 13:09, jdd@dodin.org wrote:
Le 11/05/2018 à 13:03, Carlos E. R. a écrit :
Having swap on sata-SSD is bliss. Gave new life to my computer, as I can not add RAM. Having it on M.2 would be bliss squared :-)
only if the m2 is nvme pci, else it's the same as sata ssd (apart the size, me use msata)
Ah! I see. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 2018-05-10 07:46, Felix Miata wrote:
This M.2 device I just bought turned out to be used instead of new as expected. So, I wanted to see what's on it. Booted normally to a /dev/sda filesystem, trying to mount -t vfat or -t auto just gives a generic error "wrong fstype, bad option, bad superblock, blah blah". -t auto worked just fine for NTFS sdb3. What's the secret to examining an EFI System partition when the one used for booting is already on /boot/efi/? Man mount doesn't seem to make any mention of an EFI System partition.
Try "file -s /dev/sdb1", then try fsck it. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
participants (3)
-
Carlos E. R.
-
Felix Miata
-
jdd@dodin.org