View unanswered posts | View active topics It is currently Wed Aug 21, 2019 8:11 pm



Reply to topic  [ 38 posts ]  Go to page Previous  1, 2, 3, 4
 SSD failure or Debian 10 Incompatible ? 
Author Message

Joined: Fri Mar 27, 2009 4:22 pm
Posts: 13
Post Re: SSD failure or Debian 10 Incompatible ?
Thanks, fred44nl.

_________________
David Walker


Thu Jul 25, 2019 5:03 pm
Profile

Joined: Fri Aug 09, 2019 6:56 am
Posts: 2
Post Re: SSD failure ?
tamir wrote:
We have additional reports about issues with Debian 10 not working well on the fitlet2.
Debian 9 seems to work fine on the fitlet2, [...]


Any news on this topic?

We have a handful of fitlet2. With Debian 9 we have no problems with any device. With Debian 10, on some devices the installation stucks. It seems that the ssd disappears.

But we have also fitlet2 devices without any problems during debian 10 installation.
One of the differences between the devices is the base board version:

Code:
Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
          Manufacturer: Compulab
          Product Name: fitlet2
          Version: 1.21


Code:
Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
          Manufacturer: Compulab
          Product Name: fitlet2
          Version: 1.2


With version 1.2 we have no problems

Regards
Marco


Fri Aug 09, 2019 7:34 am
Profile

Joined: Sat Jul 13, 2019 2:05 pm
Posts: 11
Post Re: SSD failure or Debian 10 Incompatible ?
I have :

Code:
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
   Manufacturer: Compulab
   Product Name: fitlet2
   Version: 1.1


Fri Aug 09, 2019 8:27 am
Profile

Joined: Tue Jul 24, 2018 8:37 am
Posts: 29
Post Re: SSD failure ?
same here:

Quote:
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: Compulab
Product Name: fitlet2
Version: 1.1


@Marco
did you try to remove apparmor ??


Fri Aug 09, 2019 8:34 am
Profile

Joined: Sat Jul 13, 2019 2:05 pm
Posts: 11
Post Re: SSD failure or Debian 10 Incompatible ?
tamir wrote:
1. S/N (Printed on the whiter sticker located at the bottom cover)
2. P/N (Printed on the whiter sticker located at the bottom cover)
3. Full name of the Debian ISO used to install the machine.


Quote:
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Compulab
Product Name: fitlet2
Version: N/A
Serial Number: 1180405-02737
UUID: 41752a80-52c6-11e8-b327-667b4db60500
Wake-up Type: Power Switch
SKU Number: N/A
Family: N/A

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: Compulab
Product Name: fitlet2
Version: 1.1
Serial Number: 1180212-00475
Asset Tag: N/A
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: N/A
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0


Debian 10.0 (upgraded from Debian 9)

I tested without libata.force and without apparmor : crash in less than 1 hour
With libata.force, I can resist many days without crash.


Fri Aug 09, 2019 12:47 pm
Profile

Joined: Fri Aug 09, 2019 6:56 am
Posts: 2
Post Re: SSD failure ?
fred44nl wrote:
[...]

@Marco
did you try to remove apparmor ??

There is no difference, with or wo apparmor

tamir wrote:
[...]
Please provide the following details about your system:

1. S/N (Printed on the whiter sticker located at the bottom cover)
2. P/N (Printed on the whiter sticker located at the bottom cover)
3. Full name of the Debian ISO used to install the machine.


Device A
Code:
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
   Manufacturer: Compulab
   Product Name: fitlet2
   Version: 1.2
   Serial Number: 1181105-02925

P/N: FITLET2-CE3950
Bios: default

No problems with Debian 9 and 10 during Installation

Device B
Code:
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
   Manufacturer: Compulab
   Product Name: fitlet2
   Version: 1.21
   Serial Number: 1190318-01867

P/N: FITLET2-CE3950
Bios: default

No problems with Debian 9 during installation
Debian 10 stucks

Debian 10 install iso
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-10.0.0-amd64-netinst.iso
Code:
$ md5sum debian-10.0.0-amd64-netinst.iso
f31779fcca35f5ce9833a9661a9bd5bd  debian-10.0.0-amd64-netinst.iso


What we have done:

1. start d10 installation w/wo apparmor
-> no differences

2. start d10 installation w libata.force=1.5
No problems during d10 installation on Device B

3. change ssd between Device A and B
Problem move with the ssd

SSD A
Code:
# lshw -class disk
  *-disk                   
       description: ATA Disk
       product: Maximus 256G
       physical id: 0.0.0
       bus info: scsi@0:0.0.0
       logical name: /dev/sda
       version: 7A
       serial: 201812110025
       size: 238GiB (255GB)
       capabilities: gpt-1.00 partitioned partitioned:gpt
       configuration: ansiversion=5 guid=9f2c8800-5b40-4ca0-bb0a-ecad0baae6d9 logicalsectorsize=512 sectorsize=512

Code:
# udevadm info --query=all --name=/dev/sda
P: /devices/pci0000:00/0000:00:12.0/ata1/host0/target0:0:0/0:0:0:0/block/sda
N: sda
S: disk/by-id/ata-Maximus_256G_201812110025
S: disk/by-path/pci-0000:00:12.0-ata-1
E: DEVLINKS=/dev/disk/by-path/pci-0000:00:12.0-ata-1 /dev/disk/by-id/ata-Maximus_256G_201812110025
E: DEVNAME=/dev/sda
E: DEVPATH=/devices/pci0000:00/0000:00:12.0/ata1/host0/target0:0:0/0:0:0:0/block/sda
E: DEVTYPE=disk
E: ID_ATA=1
E: ID_ATA_DOWNLOAD_MICROCODE=1
E: ID_ATA_FEATURE_SET_APM=1
E: ID_ATA_FEATURE_SET_APM_ENABLED=0
E: ID_ATA_FEATURE_SET_HPA=1
E: ID_ATA_FEATURE_SET_HPA_ENABLED=1
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
E: ID_ATA_FEATURE_SET_SECURITY=1
E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=2
E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=2
E: ID_ATA_FEATURE_SET_SECURITY_FROZEN=1
E: ID_ATA_FEATURE_SET_SMART=1
E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
E: ID_ATA_ROTATION_RATE_RPM=0
E: ID_ATA_SATA=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1
E: ID_ATA_WRITE_CACHE=1
E: ID_ATA_WRITE_CACHE_ENABLED=1
E: ID_BUS=ata
E: ID_MODEL=Maximus_256G
E: ID_MODEL_ENC=Maximus\x20256G\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_PART_TABLE_TYPE=gpt
E: ID_PART_TABLE_UUID=9f2c8800-5b40-4ca0-bb0a-ecad0baae6d9
E: ID_PATH=pci-0000:00:12.0-ata-1
E: ID_PATH_TAG=pci-0000_00_12_0-ata-1
E: ID_REVISION=Q0707A
E: ID_SERIAL=Maximus_256G_201812110025
E: ID_SERIAL_SHORT=201812110025
E: ID_TYPE=disk
E: MAJOR=8
E: MINOR=0
E: SUBSYSTEM=block
E: TAGS=:systemd:
E: USEC_INITIALIZED=2835346


SSD B
Code:
# lshw -class disk
  *-disk                   
       description: ATA Disk
       product: M2SCF-6M 256GB
       physical id: 0.0.0
       bus info: scsi@0:0.0.0
       logical name: /dev/sda
       version: 0C
       serial: 20190402017401100070
       size: 236GiB (253GB)
       capabilities: gpt-1.00 partitioned partitioned:gpt
       configuration: ansiversion=5 guid=8da419b4-552e-4c44-924f-e8f2ba6de3a5 logicalsectorsize=512 sectorsize=512

Code:
# udevadm info --query=all --name=/dev/sda
P: /devices/pci0000:00/0000:00:12.0/ata1/host0/target0:0:0/0:0:0:0/block/sda
N: sda
S: disk/by-id/ata-M2SCF-6M_256GB_20190402017401100070
S: disk/by-path/pci-0000:00:12.0-ata-1
E: DEVLINKS=/dev/disk/by-id/ata-M2SCF-6M_256GB_20190402017401100070 /dev/disk/by-path/pci-0000:00:12.0-ata-1
E: DEVNAME=/dev/sda
E: DEVPATH=/devices/pci0000:00/0000:00:12.0/ata1/host0/target0:0:0/0:0:0:0/block/sda
E: DEVTYPE=disk
E: ID_ATA=1
E: ID_ATA_DOWNLOAD_MICROCODE=1
E: ID_ATA_FEATURE_SET_APM=1
E: ID_ATA_FEATURE_SET_APM_ENABLED=0
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
E: ID_ATA_FEATURE_SET_SECURITY=1
E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=2
E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=2
E: ID_ATA_FEATURE_SET_SECURITY_FROZEN=1
E: ID_ATA_FEATURE_SET_SMART=1
E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
E: ID_ATA_ROTATION_RATE_RPM=0
E: ID_ATA_SATA=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1
E: ID_ATA_WRITE_CACHE=1
E: ID_ATA_WRITE_CACHE_ENABLED=1
E: ID_BUS=ata
E: ID_MODEL=M2SCF-6M_256GB
E: ID_MODEL_ENC=M2SCF-6M\x20256GB\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_PART_TABLE_TYPE=gpt
E: ID_PART_TABLE_UUID=8da419b4-552e-4c44-924f-e8f2ba6de3a5
E: ID_PATH=pci-0000:00:12.0-ata-1
E: ID_PATH_TAG=pci-0000_00_12_0-ata-1
E: ID_REVISION=P0810C
E: ID_SERIAL=M2SCF-6M_256GB_20190402017401100070
E: ID_SERIAL_SHORT=20190402017401100070
E: ID_TYPE=disk
E: MAJOR=8
E: MINOR=0
E: SUBSYSTEM=block
E: TAGS=:systemd:
E: USEC_INITIALIZED=3251814


Regards
Marco


Mon Aug 12, 2019 7:39 am
Profile
Site Admin

Joined: Mon Dec 25, 2017 4:21 pm
Posts: 316
Post Re: SSD failure ?
dhberlin wrote:
tamir wrote:
We have additional reports about issues with Debian 10 not working well on the fitlet2.
Debian 9 seems to work fine on the fitlet2, [...]


Any news on this topic?

We have a handful of fitlet2. With Debian 9 we have no problems with any device. With Debian 10, on some devices the installation stucks. It seems that the ssd disappears.

But we have also fitlet2 devices without any problems during debian 10 installation.
One of the differences between the devices is the base board version:

Code:
Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
          Manufacturer: Compulab
          Product Name: fitlet2
          Version: 1.21


Code:
Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
          Manufacturer: Compulab
          Product Name: fitlet2
          Version: 1.2


With version 1.2 we have no problems

Regards
Marco


Is it possible to perform same replication steps on an alternative SSD of a different brand ?

Also please refer to previous reply on this thread:

tamir wrote:
After further investigation we conclude that S.M.A.R.T is not a reliable method to monitor SSD controllers and may cause issues, possibly due to certain incompatibility of the SSD's firmware.

Nevertheless, if the fitlet2 have Linux mint installed and SSD does not function as advertised, please follow our RMA procedure to have the machine repaired - https://www.fit-pc.com/web/support/rma/


Mon Aug 12, 2019 12:44 pm
Profile

Joined: Tue Jul 24, 2018 8:37 am
Posts: 29
Post Re: SSD failure or Debian 10 Incompatible ?
now I am puzzled :?:

I have added libata.force=1.5G to /etc/default/grub
Quote:
GRUB_CMDLINE_LINUX_DEFAULT="quiet libata.force=1.5G"

I did run
Code:
sudo update-grub

I did check this in /boot/grub/grub.cfg
Quote:
linux /boot/vmlinuz-4.19.0-5-amd64 root=UUID=c13aae11-e70b-4c32-95d4-887063631a09 ro quiet libata.force=1.5G

but when I run
Code:
sudo smartctl -i /dev/sda

I get this as a result:
Quote:
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)


why don't I get "current 1.5 Gb/s ??

edit:
the problem obviously is in the fact that you must have smartmontools installed for this to work

the reason I am getting back into this, is because a few days ago the kernel was updated from 4.19.37-5+deb10u1 to 4.19.37-5+deb10u2
so, a minor update, but since then, my machine locks itself every few days.


Tue Aug 13, 2019 11:30 am
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 38 posts ]  Go to page Previous  1, 2, 3, 4

Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by STSoftware for PTF.