Welcome! Log In Create A New Profile

Advanced

Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L

Posted by schnee 
Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
February 06, 2017 05:39PM
Hi bodhi,
it is really great that you don'T let our small plug computer to become obsolete! Huge thanks for that!

I just recently installed 4.4.38 on all my pogoplugs and now they work fine. So far i used 160 GB 2.5' SATA drives as i boot completely from SATA. Some of those drives i replaced with 160 GB SSD and everything went fine. Now i received a 180 GB SSD and the trouble started:
1. If i install the 3.17 root image it boots fine and works fine on the 180GB SSD
2. if I upgrade the kernel to 4.0 it still works fine it still works fine
3. If i upgrade to 4.1 or 4.4.38 then it hangs on boot.

SSD: Intel SSD Pro 1500 Series (180GB)

the error is around the sata as i see some timeouts in the log:
[    3.070003] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[    3.087119] ata1.00: ATA-9: INTEL SSDSC2BF180A4L, LADi, max UDMA/133
[    3.093496] ata1.00: 351651888 sectors, multi 16: LBA48 NCQ (depth 0/32)
[   18.100001] ata1.00: qc timeout (cmd 0xef)
[   18.104084] sata_oxnas: resetting SATA core
[   18.460001] ata1.00: failed to set xfermode (err_mask=0x5)
[   18.969999] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   33.990005] ata1.00: qc timeout (cmd 0xef)
......

Attached the whole boot log to the message. I will try to see if i can upgrade the SSD firmware and if it helps, but otherwise i have no ide what is going wrong.



Edited 1 time(s). Last edit at 02/07/2017 02:02AM by bodhi.
Attachments:
open | download - kernel4.4.38.log (13.2 KB)
Re: Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
February 07, 2017 02:12AM
schnee,

The log showed you have not installed the new u-boot.

However, I'm not sure yet why your SSD works in older kernel but not the new one. I'll take a look to see if I can tell if the sata-oxnas driver in kernel 4.4.38 have changed something that could cause this.

You could try to boot with a USB drive using a new rootfs with with kernel 3.17, and then with 4.4.38, to see if the SSD is recognized after the system is running. That would add a hint to where I should look for the differences.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
February 07, 2017 05:19PM
bodhi,

i installed today the new uboot on my sata drive with partial success. The new uboot loads, but i still use the old SPL from warehead. The results are the same -> fine boot with 3.17, no boot with 4.4. The main difference is that now it drops to busybox, instead of a loop trying to boot. The error is get is:

[    2.853009] Freeing unused kernel memory: 228K (c080f000 - c0848000)         
Loading, please wait...                                                         
[    2.998254] udevd[94]: starting version 175                                  
Begin: Loading essential drivers ... done.                                      
Begin: Running /scripts/init-premount ... done.                                 
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Waiting for root file system ... done.                                   
Gave up waiting for root device.  Common problems:                              
 - Boot args (cat /proc/cmdline)                                                
   - Check rootdelay= (did the system wait long enough?)                        
   - Check root= (did the system wait for the right device?)                    
 - Missing modules (cat /proc/modules; ls /dev)                                 
ALERT!  /dev/sda2 does not exist.  Dropping to a shell!                         
modprobe: module i8042 not found in modules.dep                                 
modprobe: module uhci-hcd not found in modules.dep                              
modprobe: module ohci-hcd not found in modules.dep                              
                                                                                
                                                                                
BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)                        
Enter 'help' for a list of built-in commands.                                   
                                                                                
/bin/sh: can't access tty; job control turned off                               
(initramfs)
(initramfs) cd /dev                                                             
(initramfs) cat /proc/modules                                                   
(initramfs)

attached both the 3.17 and the 4.4 boot log.

I will try to test with USB soon too.
Attachments:
open | download - new3.17.log (16.5 KB)
open | download - new4.4.log (12.3 KB)
Re: Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
February 07, 2017 06:55PM
schnee,

> i installed today the new uboot on my sata drive w
> ith partial success. The new uboot loads, but i st
> ill use the old SPL from warehead.

It is OK to run WarheadSE old SPL. U-boot is really more important to replace.

> I will try to test with USB soon too.

Before you do that, a couple things to make sure that were not the cause:

1. Your env is not right: rootdelay=0. Set it to 10 like you did before.

2. Verify that you run the correct version of the DTB. When running kernel 4.1 you need the DTB that comes with it, and running kernel 4.4.38 you need the later DTB version that comes with it.

ls -lart /boot/dts/ox820-pogoplug*.dtb

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
February 07, 2017 07:03PM
Also, another thing.

Did you use the new u-boot envs image? I noticed you are still using /dev/sda2 as the root device.

If you have "flashed" (i.e. put it in the SSD) the new u-boot default envs, then you would have used root=LABEL=rootfs for the root device. And the sda2 partition should be labeled rootfs.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
February 08, 2017 03:08PM
Hi bodhi,

thanks for the reminder. I indeed forgot to update the dts files. I did it now, the result is the same, but the time to get there is longer - attached the boot log. Also edited the envs to use rootfs and 10 sec delay. I flashed your envs to the ssd, but it did not work, so it started with defaults.

current uboot.env

autoload=no
baudrate=115200
bootargs=console=ttyS0,115200n8
bootcmd=run bootcmd_uenv; run dt_bootcmd_usb; reset
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
console=console=ttyS0,115200n8
devices=usb ide
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
dt_load_dtb=ext2load ide 0:2 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb
dt_load_initrd=ext2load ide 0:2 $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext2load ide 0:2 $uimage_addr /boot/uImage
dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot
dtb_addr=0x62c00000
ethact=dwmac.40400000
ethaddr=5e:2b:15:71:ec:b6
if_netconsole=ping $serverip
ipaddr=192.168.0.222
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
preboot_nc=run if_netconsole start_netconsole
serverip=192.168.0.220
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version
stderr=serial
stdin=serial
stdout=serial
uenv_import=echo importing envs ...; env import -t 0x60500000
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x60500000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
uimage_addr=0x60500000
uinitrd_addr=0x60e00000
usb_device=0:1
usb_set_bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10

Environment size: 1975/131068 bytes
Attachments:
open | download - kernel4.4.correct.dtb.log (18.8 KB)
Re: Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
February 08, 2017 03:43PM
schnee,

This time there are 2 problems: 1) the u-boot envs. 2) the SSD could not be initialized properly (which is the same as before).

1)
The bootargs was not set properly
usb_set_bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10

Should be:
usb_set_bootargs=setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10"

2)
The SATA initialization might be because a change in driver. SSD sometime is picky (HDD is never so). Some SSD could never be used for booting. In this case, apparently kernel 4.1 works, so it might be tthe difference in sata_oxnas driver between 2 kernels.

I think the best way to solve this SATA problem is either:

1. Try using another SSD or HDD to see if same symptom occurs.
2. Boot with USB and then plug in the SSD to see if it can be initialized after the system is running.

If number 2 is still not working then I'll take a look at the driver.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
February 08, 2017 06:34PM
bodhi,

corrected the bootargs, but the result is the same

Quote

2) The SATA initialization might be because a change in driver. SSD sometime is picky (HDD is never so). Some SSD could never be used for booting. In this case, apparently kernel 4.1 works, so it might be tthe difference in sata_oxnas driver between 2 kernels.

I think the best way to solve this SATA problem is either:

1. Try using another SSD or HDD to see if same symptom occurs.
2. Boot with USB and then plug in the SSD to see if it can be initialized after the system is running.

If number 2 is still not working then I'll take a look at the driver.

This SSD works with 4.0, but it does not work with 4.1 and 4.4 kernels. I tried other HDD HTS723216L9SA60 (160G) and an SSD Intel SSD 320 series 160 GB and both works fine.

Will test with USB soon.
Re: Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
February 08, 2017 07:10PM
schnee,

> This SSD works with 4.0, but it does not work with
> 4.1 and 4.4 kernels.

> I tried other HDD HTS723216L9
> SA60 (160G) and an SSD Intel SSD 320 series 160 GB
> and both works fine.

Thanks for the correction!

This is very good info. It's proved that the Intel SSDSC2BF180A4L has some quirks that only surface in later kernel 4.1+. Especially is that 4.0 and 4.1 use the same driver (IIRC, have not doublechecked) . So that narrow down the issue quite a bit more.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 1 time(s). Last edit at 02/08/2017 09:40PM by bodhi.
Re: Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
February 13, 2017 02:56PM
I was a bit busy with some other things, so i only got back to testing today..

I made my pogo to boot from USB and attached the disk to it after it booted up. The result is the same, the drive is failing with "ata1.00: failed to set xfermode (err_mask=0x5)"

full log output on the serial console:
[   88.996234] sata_oxnas: resetting SATA core
[   89.010711] ata1: exception Emask 0x10 SAct 0x0 SErr 0x20000 action 0xe frozen
[   89.017907] ata1: SError: { PHYInt }
[   89.021539] ata1: hard resetting link
[   89.930022] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   89.946247] ata1.00: ATA-9: INTEL SSDSC2BF180A4L, LADi, max UDMA/133
[   89.952616] ata1.00: 351651888 sectors, multi 16: LBA48 NCQ (depth 0/32)
[  104.960040] ata1.00: qc timeout (cmd 0xef)
[  104.964124] sata_oxnas: resetting SATA core
[  105.320035] ata1.00: failed to set xfermode (err_mask=0x5)
[  105.325511] ata1: hard resetting link
[  105.830026] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  120.850040] ata1.00: qc timeout (cmd 0xef)
[  120.854126] sata_oxnas: resetting SATA core
[  121.210035] ata1.00: failed to set xfermode (err_mask=0x5)
[  121.215513] ata1.00: limiting speed to UDMA/133:PIO3
[  121.220523] ata1: hard resetting link
[  121.730030] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  136.750033] ata1.00: qc timeout (cmd 0xef)
[  136.754117] sata_oxnas: resetting SATA core
[  137.110039] ata1.00: failed to set xfermode (err_mask=0x5)
[  137.115507] ata1.00: disabled
[  137.118479] sata_oxnas: resetting SATA core
[  137.132956] ata1: exception Emask 0x10 SAct 0x0 SErr 0x20000 action 0xe frozen t4
[  137.140436] ata1: SError: { PHYInt }
[  137.144017] ata1: hard resetting link
[  138.050032] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  138.067128] ata1.00: ATA-9: INTEL SSDSC2BF180A4L, LADi, max UDMA/133
[  138.073500] ata1.00: 351651888 sectors, multi 16: LBA48 NCQ (depth 0/32)
[  153.080184] ata1.00: qc timeout (cmd 0xef)
[  153.084267] sata_oxnas: resetting SATA core
[  153.440038] ata1.00: failed to set xfermode (err_mask=0x5)
[  153.445514] ata1: hard resetting link
[  153.950036] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  168.970048] ata1.00: qc timeout (cmd 0xef)
[  168.974133] sata_oxnas: resetting SATA core
[  169.330048] ata1.00: failed to set xfermode (err_mask=0x5)
[  169.335526] ata1.00: limiting speed to UDMA/133:PIO3
[  169.340538] ata1: hard resetting link
[  169.850042] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  184.870049] ata1.00: qc timeout (cmd 0xef)
[  184.874129] sata_oxnas: resetting SATA core
[  185.230046] ata1.00: failed to set xfermode (err_mask=0x5)
[  185.235517] ata1.00: disabled
[  185.238487] sata_oxnas: resetting SATA core
[  185.252953] ata1: exception Emask 0x10 SAct 0x0 SErr 0x20000 action 0xe frozen t3
[  185.260431] ata1: SError: { PHYInt }
[  185.264010] ata1: hard resetting link
[  186.170048] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  186.187148] ata1.00: ATA-9: INTEL SSDSC2BF180A4L, LADi, max UDMA/133
[  186.193523] ata1.00: 351651888 sectors, multi 16: LBA48 NCQ (depth 0/32)
[  201.200056] ata1.00: qc timeout (cmd 0xef)
[  201.204142] sata_oxnas: resetting SATA core
[  201.560051] ata1.00: failed to set xfermode (err_mask=0x5)
[  201.565527] ata1: hard resetting link
[  202.070049] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  217.090068] ata1.00: qc timeout (cmd 0xef)
[  217.094151] sata_oxnas: resetting SATA core
[  217.450055] ata1.00: failed to set xfermode (err_mask=0x5)
[  217.455528] ata1.00: limiting speed to UDMA/133:PIO3
[  217.460541] ata1: hard resetting link
[  217.970050] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  232.990069] ata1.00: qc timeout (cmd 0xef)
[  232.994152] sata_oxnas: resetting SATA core
[  233.350059] ata1.00: failed to set xfermode (err_mask=0x5)
[  233.355525] ata1.00: disabled
[  233.358494] sata_oxnas: resetting SATA core
[  233.372945] ata1: exception Emask 0x10 SAct 0x0 SErr 0x20000 action 0xe frozen t2
[  233.380441] ata1: SError: { PHYInt }
[  233.384017] ata1: hard resetting link
[  234.290058] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  234.307159] ata1.00: ATA-9: INTEL SSDSC2BF180A4L, LADi, max UDMA/133
[  234.313533] ata1.00: 351651888 sectors, multi 16: LBA48 NCQ (depth 0/32)
[  249.320069] ata1.00: qc timeout (cmd 0xef)
[  249.324152] sata_oxnas: resetting SATA core
[  249.680061] ata1.00: failed to set xfermode (err_mask=0x5)
[  249.685539] ata1: hard resetting link
[  250.190246] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  265.210071] ata1.00: qc timeout (cmd 0xef)
[  265.214156] sata_oxnas: resetting SATA core
[  265.570076] ata1.00: failed to set xfermode (err_mask=0x5)
[  265.575552] ata1.00: limiting speed to UDMA/133:PIO3
[  265.580567] ata1: hard resetting link
[  266.090071] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  281.110072] ata1.00: qc timeout (cmd 0xef)
[  281.114155] sata_oxnas: resetting SATA core
[  281.470080] ata1.00: failed to set xfermode (err_mask=0x5)
[  281.475548] ata1.00: disabled
[  281.478520] sata_oxnas: resetting SATA core
[  281.492968] ata1: exception Emask 0x10 SAct 0x0 SErr 0x20000 action 0xe frozen t1
[  281.500449] ata1: SError: { PHYInt }
[  281.504028] ata1: hard resetting link
[  282.410068] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  282.427171] ata1.00: ATA-9: INTEL SSDSC2BF180A4L, LADi, max UDMA/133
[  282.433543] ata1.00: 351651888 sectors, multi 16: LBA48 NCQ (depth 0/32)
[  297.440081] ata1.00: qc timeout (cmd 0xef)
[  297.444165] sata_oxnas: resetting SATA core
[  297.800076] ata1.00: failed to set xfermode (err_mask=0x5)
[  297.805555] ata1: hard resetting link
[  298.310069] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  313.330094] ata1.00: qc timeout (cmd 0xef)
[  313.334177] sata_oxnas: resetting SATA core
[  313.690076] ata1.00: failed to set xfermode (err_mask=0x5)
[  313.695552] ata1.00: limiting speed to UDMA/133:PIO3
[  313.700567] ata1: hard resetting link
[  314.210081] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  329.230082] ata1.00: qc timeout (cmd 0xef)
[  329.234163] sata_oxnas: resetting SATA core
[  329.590085] ata1.00: failed to set xfermode (err_mask=0x5)
[  329.595558] ata1.00: disabled
[  329.598525] ata1: EH pending after 5 tries, giving up
[  329.603642] ata1: EH complete

with kernel 3.17 there are no issues:
[   51.559137] ox820sata: reseting SATA core
[   51.573652] ata1: exception Emask 0x10 SAct 0x0 SErr 0x20000 action 0xe frozen
[   51.580887] ata1: SError: { PHYInt }
[   51.584465] ata1: hard resetting link
[   52.490032] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   52.507133] ata1.00: ATA-9: INTEL SSDSC2BF180A4L, LADi, max UDMA/133
[   52.513502] ata1.00: 351651888 sectors, multi 16: LBA48 NCQ (depth 0/32)
[   52.547161] ata1.00: configured for UDMA/133
[   52.551470] ata1: EH complete
[   52.554867] scsi 0:0:0:0: Direct-Access     ATA      INTEL SSDSC2BF18 LADi PQ: 0 ANSI: 5
[   52.569021] sd 0:0:0:0: [sdb] 351651888 512-byte logical blocks: (180 GB/167 GiB)
[   52.578644] sd 0:0:0:0: [sdb] Write Protect is off
[   52.583772] sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   52.602112]  sdb: sdb1 sdb2 sdb3
[   52.618211] sd 0:0:0:0: [sdb] Attached SCSI disk

Hope this helps to pinpoint the issue with the drive.

PS: i looked at intel's site and there is no firmware update for this drive (so i hope it is not a firmware issue)
Re: Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
February 14, 2017 01:45AM
schnee,

I'll take a look at the SATA driver difference when I start building kernel 4.9 for this box.

4.9 is an LTS kernel so that's my current target for Popgo V3 Oxnas.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
March 22, 2017 05:27PM
Hi Bodhi,

i see that you released new kernels in the 4.4.X line. By any chance did you look into the sata driver? Does it make sense to start testing again with the problematic HDD?

Thanks

schnee
Re: Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
March 22, 2017 06:28PM
schnee,

Sorry I forgot about this! too many things on my mind, guess I should start keeping/reviewing a TODO list again :).

This kernel release was just to incorporate the latest Linux 4.4.x stable kernel series (so there is no change in any drivers). But everybody should upgrade any way.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
March 22, 2017 07:10PM
schnee,

I've just taken a peek at the SATA drivers between 2 versions that could have cause this error.

The mainline libata-core driver (common to all architecture) has changed quite a bit in dealing with SSD, and there were some changes in Intel SSDs.

I don't recall if you have tried this SSD on another box as SATA drive?

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
March 22, 2017 07:27PM
> I don't recall if you have tried this SSD on anoth
> er box as SATA drive?

Bodhi,

i used to use this SATA SSD in a laptop with ubuntu linux (12.04LTS) in the past and it worked fine. I did not try it recently though.

If i attach this as a normal SATA drive to my 14.04 Ubuntu desktop it works fine.

Schnee
Re: Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
March 22, 2017 10:20PM
schnee Wrote:
-------------------------------------------------------
> > I don't recall if you have tried this SSD on ano
> th
> > er box as SATA drive?
>
> Bodhi,
>
> i used to use this SATA SSD in a laptop with ubunt
> u linux (12.04LTS) in the past and it worked fine.
> I did not try it recently though.
>
> If i attach this as a normal SATA drive to my 14.0
> 4 Ubuntu desktop it works fine.
>
> Schnee

Those might use older kernel than 4.4.x.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Problem booting Pogo Pro 4.4.38-oxnas-tld-5 with Intel SSDSC2BF180A4L
March 23, 2017 05:20PM
I did some test today with debian:

Installed debian stable --> 3.18 kernel --> upgraded to strech --> 4.9.0.2-amd64 kernel --> reboot

The system works fine. So either the driver is fixed in 4.9 or it would work fine with any 4.X kernel in debian-amd64
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: