Posts: 630
Eino
Joined: 12 Oct 2012
#1
I have found that you need to use a drive erasing tool before, the drive will except a Linux format.
On a Intel SSD. Otherwise the drive just looks bad, and won't format.

Code: Select all

System:    Host: antiX1 Kernel: 3.7.10-antix.3-486-smp i686 (32 bit) 
           Desktop: IceWM 1.3.7 Distro: antiX-13_386-full Luddite 01 June 2013
Machine:   System: Acer product: AOA110 version: 1
           Mobo: Acer model: N/A Bios: Acer version: v0.3305 date: 05/09/2008
CPU:       Single core Intel Atom CPU N270 (-HT-) cache: 512 KB flags: (pae sse sse2 sse3 ssse3) 
           Clock Speeds: 1: 800.00 MHz 2: 800.00 MHz
Graphics:  Card: Intel Mobile 945GSE Express Integrated Graphics Controller 
           X.Org: 1.12.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1024x600@60.0hz 
           GLX Renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 GLX Version: 1.4 Mesa 8.0.5
Audio:     Card: Intel NM10/ICH7 Family High Definition Audio Controller driver: snd_hda_intel 
           Sound: Advanced Linux Sound Architecture ver: k3.7.10-antix.3-486-smp
Network:   Card-1: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller driver: r8169 
           IF: eth0 state: down mac: 00:23:8b:42:e4:f7
           Card-2: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) driver: ath5k 
           IF: wlan0 state: up mac: 00:24:2b:12:a9:7d
Drives:    HDD Total Size: 8.1GB (37.0% used) 1: id: /dev/sda model: SSDPAMM0008G1 size: 8.1GB 
Partition: ID: / size: 6.4G used: 2.8G (46%) fs: ext4 ID: swap-1 size: 1.10GB used: 0.00GB (0%) fs: swap 
Sensors:   System Temperatures: cpu: 59.0C mobo: N/A 
           Fan Speeds (in rpm): cpu: N/A 
Info:      Processes: 99 Uptime: 29 min Memory: 150.3/995.8MB Client: Shell (inxi-gui) inxi: 1.9.7
Posts: 765
rust collector
Joined: 27 Dec 2011
#2
hmm, have you had that problem before? Like, every time?
Alanarchy
Posts 0
Alanarchy
#3
A Soild State Drive can wear out more quickly dependant upon your choice of file system.
Linux systems

The ext4, JFS, Btrfs and F2FS file systems include support for the discard (TRIM) function. Currently ext4 can be recommended as a safe choice. F2FS is a modern file system optimized for SSDs and other flash-based storage, but is still in experimental stage. Kernel support for the TRIM function was introduced in version 2.6.33. To make use of it, the filesystem must be mounted using the discard parameter. Linux distributions usually do not set this kind of configuration automatically during installation and thus the fstab file requires manual modification. This is because of the notion that the current Linux TRIM command implementation might not be optimal. It has been proven to cause a performance degradation instead of a performance increase under certain circumstances. The disk utilities take care of proper partition alignment.

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://en.wikipedia.org/wiki/Solid-state_drive"
linktext was:"https://en.wikipedia.org/wiki/Solid-state_drive"
====================================



========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://wiki.archlinux.org/index.php/Solid_State_Drives"
linktext was:"https://wiki.archlinux.org/index.php/Solid_State_Drives"
====================================

Cells wear out. Consumer MLC cells at mature 50nm processes can handle 10000 writes each; 35nm generally handles 5000 writes, and 25nm 3000 (smaller being higher density and cheaper). If writes are properly spread out, are not too small, and align well with cells, this translates into a lifetime write volume for the SSD that is a multiple of its capacity. Daily write volumes have to be balanced against life expectancy.
This is also worth a read cos there is a potential problem with logs.


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.reddit.com/r/archlinux/comments/rkwjm/what_should_i_keep_in_mind_when_installing_on_ssd/"
linktext was:"http://www.reddit.com/r/archlinux/comme ... ng_on_ssd/"
====================================


Then again, Elno, you probably know this already, but it might help others __{{emoticon}}__
Posts: 850
fatmac
Joined: 26 Jul 2012
#4
Likewise, I've had to zero out the boot sector of an SSD to get it seen properly.

Edit: I use noatime & relatime for my drives.
Posts: 630
Eino
Joined: 12 Oct 2012
#5
I'm using ext4 format on it so I'm safe there. I don't use it as an every day computer. So it should last awhile.
I have been reading about other people with the same problem with the Intel SSD. So I just posted what worked for me.
Posts: 325
male
Joined: 04 Nov 2011
#6
I do not know if I have understood correctly ...
here is Secure Erase with it


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://partedmagic.com/doku.php?id=news"
linktext was:"http://partedmagic.com/doku.php?id=news"
====================================


Please see the Intel SSD

Code: Select all

# hdparm -I /dev/sda
For me (not Intel)

Code: Select all

root@antiX1:/home/male# hdparm -I /dev/sda

/dev/sda:

ATA device, with non-removable media
    Model Number:       MXSSD1MNANO-60G                         
    Serial Number:      110105411           
    Firmware Revision:  VATE1702
    Transport:          Parallel, ATA8-APT
Standards:
    Used: unknown (minor revision code 0x0039) 
    Supported: 8 7 6 5 
    Likely used: 8
Configuration:
    Logical        max    current
    cylinders    16383    16383
    heads        16    16
    sectors/track    63    63
    --
    CHS current addressable sectors:   16514064
    LBA    user addressable sectors:  117440512
    LBA48  user addressable sectors:  117440512
    Logical/Physical Sector size:           512 bytes
    device size with M = 1024*1024:       57344 MBytes
    device size with M = 1000*1000:       60129 MBytes (60 GB)
    cache/buffer size  = unknown
    Nominal Media Rotation Rate: Solid State Device
Capabilities:
    LBA, IORDY(cannot be disabled)
    Standby timer values: spec'd by Standard, no device specific minimum
    R/W multiple sector transfer: Max = 16    Current = 16
    DMA: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 udma6 
         Cycle time: min=120ns recommended=120ns
    PIO: pio0 pio1 pio2 pio3 pio4 
         Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
    Enabled    Supported:
       *    SMART feature set
            Security Mode feature set
       *    Power Management feature set
            Write cache
            Look-ahead
       *    Host Protected Area feature set
       *    WRITE_BUFFER command
       *    READ_BUFFER command
       *    NOP cmd
       *    DOWNLOAD_MICROCODE
            SET_MAX security extension
       *    48-bit Address feature set
       *    Mandatory FLUSH_CACHE
       *    FLUSH_CACHE_EXT
Security: 
    Master password revision code = 65534
        supported
    not    enabled
    not    locked
        frozen
    not    expired: security count
        supported: enhanced erase
    2min for SECURITY ERASE UNIT. 2min for ENHANCED SECURITY ERASE UNIT.
HW reset results:
    CBLID- above Vih
    Device num = 0 determined by the jumper
Checksum: correct
root@antiX1:/home/male#