Booting Linux Kernel 4.4.133 Oxnas (OX820) Pogo V3 from SATA

Hello,

I have followed the rootfs Instrauctions of
https://forum.doozan.com/read.php?2,16044
to transfer the Debian rootfs to an SSD..

I attached the SSD to my Pogoplug V3's SATA port and I am trying to boot now. I was hoping my uboot (U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS) would detect it and simply boot - but it does not.

I searched now, if I need to change the boot parameters and I found:
https://forum.doozan.com/read.php?2,32994

However, I find this very confusing, and it implies, that uboot is not working correctly, right?

My parameters are:

OX820> printenv
autoload=no
baudrate=115200
bootargs=console=ttyS0,115200n8
bootcmd=run dt_bootcmd_usb
bootdelay=10
console=console=ttyS0,115200n8
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 usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-classic.dtb
dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext2load usb 0:1 $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=mii0
ethaddr=00:25:31:02:AE:F5
if_netconsole=ping $serverip
ipaddr=192.168.180.19
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
ncip=192.168.180.44
preboot_nc=run if_netconsole start_netconsole
serverip=192.168.180.44
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version
stderr=serial
stdin=serial
stdout=serial
uimage_addr=0x60500000
uinitrd_addr=0x60e00000
usb_device=0:1
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10

Environment size: 1220/131068 bytes

Is there a setting I can apply, which makes uboot first check for SATA drives and then USB drives for booting?
Or a less confusing how-to?

Any help would be very appreciated.

Regards, Dieter

PS: I had more then one partition and changed that now to one ext4, only, but still:

scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command

Led:    ORANGE (Failed)

Update2: I put the SDD into an USB case, and it does not boot!

USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
** File not found /boot/uImage **
** File not found /boot/uInitrd **
** File not found /boot/dts/ox820-pogoplug-classic.dtb **
Wrong Image Format for bootm command

Led:    ORANGE (Failed)

I seem to have missed something?
Why is it searching for a dtb-file. Ithought, with my version of uboot, I should skip the generation of the dtb file?



Edited 3 time(s). Last edit at 12/01/2018 11:24AM by Dieter.

Dieter,

> I searched now, if I need to change the boot
> parameters and I found:
> https://forum.doozan.com/read.php?2,32994
>

No you don't want to follow the above instruction. It is for booting directly from SATA with uboot and rootfs are stored in the SATA disk.

> My parameters are:
>

> OX820> printenv
> autoload=no
> baudrate=115200
> bootargs=console=ttyS0,115200n8
> bootcmd=run dt_bootcmd_usb
> bootdelay=10
> console=console=ttyS0,115200n8
> 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 usb 0:1 $dtb_addr
> /boot/dts/ox820-pogoplug-classic.dtb
> dt_load_initrd=ext2load usb 0:1 $uinitrd_addr
> /boot/uInitrd
> dt_load_uimage=ext2load usb 0:1 $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=mii0
> ethaddr=00:25:31:02:AE:F5
> if_netconsole=ping $serverip
> ipaddr=192.168.180.19
> mtdids=nand0=41000000.nand
> mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
> ncip=192.168.180.44
> preboot_nc=run if_netconsole start_netconsole
> serverip=192.168.180.44
> start_netconsole=setenv ncip $serverip; setenv
> bootdelay 10; setenv stdin nc; setenv stdout nc;
> setenv stderr nc; version
> stderr=serial
> stdin=serial
> stdout=serial
> uimage_addr=0x60500000
> uinitrd_addr=0x60e00000
> usb_device=0:1
> usb_set_bootargs=setenv bootargs
> console=ttyS0,115200 root=/dev/sda1 rootdelay=10
> 
> Environment size: 1220/131068 bytes
>

Your env indicated that you have an older u-boot on NAND. And it was set up to boot with USB only.

====

With the SSD rootfs attached, power up and interrupt serial console, and

printenv
ide reset

Please post the entire serial console log.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello bodhi,

here you go:

U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS

DRAM:  128 MiB
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:
Led:    GREEN
mii0
Main Loop
Hit any key to stop autoboot:  0
autoload=no
baudrate=115200
bootargs=console=ttyS0,115200n8
bootcmd=run dt_bootcmd_usb
bootdelay=10
console=console=ttyS0,115200n8
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 usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-classic.dtb
dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext2load usb 0:1 $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=mii0
ethaddr=00:25:31:02:AE:F5
if_netconsole=ping $serverip
ipaddr=192.168.180.19
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
ncip=192.168.180.44
preboot_nc=run if_netconsole start_netconsole
serverip=192.168.180.44
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version
stderr=serial
stdin=serial
stdout=serial
uimage_addr=0x60500000
uinitrd_addr=0x60e00000
usb_device=0:1
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10

Environment size: 1220/131068 bytes
OX820> ide reset

Reset IDE: Bus 0: OK
  Device 0: Model: SanDisk SDSSDP128G Firm: 2.0.0  Ser#: 123651401099
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 122104.3 MB = 119.2 GB (250069680 x 512)
OX820>

I want to mention, that I am "fully equipped" here, i.e. serial console attached, and I even found an Debian 3.X USB stick which is still working.
So I could update uboot if necessary or import other env-settings.
In the end, I would like settings to do both, booting from USB and SATA, is that possible?
Thanks a lot for you support. The little Dockstar you once helped me with is working fine ever since!

Kind Regards, Dieter

Dieter,

> U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS

This u-boot is a couple versions older than the latest: uboot.2015.10-tld-2

https://forum.doozan.com/read.php?3,16017

So you should update u-boot.

You could also try to pouplate the envs with new default image uboot.2015.10-tld-2.ox820.environment.img. These default envs already set up to boot SATA rootfs and USB rootfs

devices=usb ide

However, it is best to install both new uboot.2015.10-tld-2.ox820.mtd0.img and uboot.2015.10-tld-2.ox820.environment.img to make sure that it works well.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello bodhi,

I updated uboot.

but it is not booting my ssd, yet:

Reset IDE: Bus 0: OK
  Device 0: Model: SanDisk SDSSDP128G Firm: 2.0.0  Ser#: 123651401099
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 122104.3 MB = 119.2 GB (250069680 x 512)

no USB devices available

Partition Map for IDE device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            250067632       4d50bd00-01     83
loading envs from ide 0 ...
** File not found /boot/uEnv.txt **
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide

Reset IDE: Bus 0: OK
  Device 0: Model: SanDisk SDSSDP128G Firm: 2.0.0  Ser#: 123651401099
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 122104.3 MB = 119.2 GB (250069680 x 512)
device ide 0:1
** File not found /boot/uImage **
device ide 1:1
** Bad device ide 1 **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
loading uImage ...
** Bad device usb 0 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB /boot/dts/ox820-pogoplug-pro.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command

The env looks like this:

U-Boot 2015.10-tld-2 (Oct 21 2017 - 22:00:02 -0700)
OXNAS OX820

DRAM:  128 MiB
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   dwmac.40400000
Hit any key to stop autoboot:  0
OX820>
OX820>
OX820> printenv
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm 0x60500000 0x60e00000 0x62c00000; else bootm 0x60500000 0x60e00000; fi; else if run load_dtb; then bootm 0x60500000 - 0x62c00000; else bootm 0x60500000; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide
disks=0 1 2 3
dtb_file=/boot/dts/ox820-pogoplug-pro.dtb
ethact=dwmac.40400000
ethaddr=52:3b:20:9c:11:51
if_netconsole=ping $serverip
ipaddr=192.168.0.222
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device 0x62c00000 $dtb_file
load_initrd=echo loading uInitrd ...; load $bootdev $device 0x60e00000 /boot/uInitrd
load_uimage=echo loading uImage ...; load $bootdev $device 0x60500000 /boot/uImage
mainlineLinux=yes
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 0x60500000 /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=192.168.0.220
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
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 0x60510000  $filesize
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
usb_custom_params=zswap.enabled=1
usb_ready_retry=15

Environment size: 2720/131068 bytes

Please, what is going wrong?

Renaming the dtb-file does not work, too:

loading DTB /boot/dts/ox820-pogoplug-classic.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command

Edited 2 time(s). Last edit at 12/02/2018 11:35AM by Dieter.

Dieter,

Reset IDE: Bus 0: OK
  Device 0: Model: SanDisk SDSSDP128G Firm: 2.0.0  Ser#: 123651401099
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 122104.3 MB = 119.2 GB (250069680 x 512)
device ide 0:1
** File not found /boot/uImage **

How was the rootfs on the SDD organized? is it the only partition? if there are more than 1 parttition, is the rootfs on partition 1?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello,

one partition only, ext4.

root@pogoplug:~# ls /dev/sd*
/dev/sda  /dev/sda1  /dev/sda2  /dev/sdb  /dev/sdb1
root@pogoplug:~# e2label  /dev/sdb1
rootfs
root@pogoplug:~# fdisk /dev/sdb

Command (m for help): p

Disk /dev/sdb: 128.0 GB, 128035676160 bytes
30 heads, 63 sectors/track, 132312 cylinders, total 250069680 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
Disk identifier: 0x4d50bd00

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048   250069679   125033816   83  Linux
q
root@pogoplug:~# mkdir ssd
root@pogoplug:~# mount /dev/sdb1 ssd
[  640.713607] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
root@pogoplug:~# ls ssd/boot/dts/*
ssd/boot/dts/ox820-akitio.dtb            ssd/boot/dts/ox820-pogoplug-pro.dtb
ssd/boot/dts/ox820-kd20.dtb              ssd/boot/dts/ox820-stg212.dtb
ssd/boot/dts/ox820-pogoplug-classic.dtb

Am I missing something?



Edited 1 time(s). Last edit at 12/03/2018 12:16PM by Dieter.

Dieter,

This could be the problem: with EXT4, when you format this drive, the default is delay formatting. So you need to make sure that the EXT4 file system got finished completely and saved to disk.

With only the SDD attached to the box, power up, interrupt serial console, and

ide reset
ext2ls ide 0:1 /boot

If you cannot see uImage, then the above was indeed the problem.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello Bodhi,

it seems, you are on the right track (as always ;-) ) :

U-Boot 2015.10-tld-2 (Oct 21 2017 - 22:00:02 -0700)
OXNAS OX820

DRAM:  128 MiB
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   dwmac.40400000
Hit any key to stop autoboot:  0
OX820> ide reset

Reset IDE: Bus 0: OK
  Device 0: Model: SanDisk SDSSDP128G Firm: 2.0.0  Ser#: 123651401099
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 122104.3 MB = 119.2 GB (250069680 x 512)
OX820> ext2ls ide 0:1 /boot
OX820>

But how do I make sure that the EXT4 file system got finished completely and saved to disk?
I formatted the drive with

mkfs.ext4 /dev/sdj1

and afterwards, I extracted the tar-ball on it and umounted it?!?

Regards, Dieter

PS: Does an SSD make sense, or will I have continously trouble with it, with trim etc.? I want to run FHEM, a smart home software on the Pogoplug, which does a lot of writing, maybe too much for an USB stick.



Edited 1 time(s). Last edit at 12/04/2018 01:09AM by Dieter.

Dieter,

When you format the drive with Ext4. There is a -O option to specify how you want to format the drive.

mkfs.ext4

Usage: mkfs.ext4 [-c|-l filename] [-b block-size] [-C cluster-size]
	[-i bytes-per-inode] [-I inode-size] [-J journal-options]
	[-G flex-group-size] [-N number-of-inodes] [-d root-directory]
	[-m reserved-blocks-percentage] [-o creator-os]
	[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
	[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
	[-t fs-type] [-T usage-type ] [-U UUID] [-e errors_behavior][-z undo_file]
	[-jnqvDFSV] device [blocks-count]

And following that -O you can use options to overide the default. For Ext4 the default is delalloc

delalloc
              Deferring block allocation until write-out time.

       nodelalloc
              Disable delayed allocation. Blocks are allocated when data is copied from user to page cache.

Use nodelalloc will disable the delayed allocation.

The bottom line is: When formatting a rootfs, always use nodelalloc to avoid data loss and problem with booting.

And SSD is fine to use as a main drive for Pogo V3.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

on my x84 Debian system, the option does not exist:

root@openmediavault:/tmp# mkfs.ext4 -O nodelalloc /dev/sdj1
mke2fs 1.43.4 (31-Jan-2017)
Ungültige Dateisystem-Option angegeben: nodelalloc
root@openmediavault:/tmp# cat /etc/debian_version
9.6

However, because ext4 support trim, it might be gernerally a good idea for an SSD, right?
Is there another way to fix the problem?

Dieter,

> on my x84 Debian system, the option does not
> exist.

It should be available on any Linux system. Look for a slightly different syntax such as the caret ^ (it means negate the option).

mkfs.ext4 -O ^delalloc /dev/sdj1

Read the manual.

man mkfs.ext4
man ext4

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Sorry, forgot about the man pages!

Checked them and found them in the man pages for ext4.
It seems, that delalloc and nodelalloc are mount options, not format options. I can't set them as mount options in uboot, can I?
I probably simply move to ext3 now and check if that works. Figured out, that trim should be supported, too.

Anyway, thanks a lot!

Dieter

Dieter,

> It seems, that delalloc and nodelalloc are mount
> options, not format options. I can't set them as
> mount options in uboot, can I?

Try that nodealloc during format, too. See if it takes?

u-boot does not know enough about EXT4 (the driver is more primitive), so no mount option in u-boot.

> I probably simply move to ext3 now and check if
> that works. Figured out, that trim should be
> supported, too.

EXT3 is the best format for rootfs. Especially during power outage, EXT3 rootfs will boot right backup with no problem.

EXT4 had problem with power outage in the past which has been fixed in mainline. However, without using nodealloc, the rootfs still have the potential to be corrupted during power outtage (depending what the system does during that time).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Salut bodhi,

thank you so much for your help!
I have given up working on EXT4. I moved to ext3 and now it is working!
Even the kernel update works fine, excellent!

The note 2, however is not clear to me.
It is not enough, to put

init=/bin/systemd

into the /boot/uEnv.txt, right?
do I need to add

usb_set_bootargs='setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts init=/bin/systemd'

?
Regards, Dieter

Dieter,

> The note 2, however is not clear to me.
> It is not enough, to put
>

> init=/bin/systemd
>

> into the /boot/uEnv.txt, right?

To make it temporarily booting with systemd when you have uEnv.txt (remove uEnv.txt and you will boot sysvinit). You can set the bootargs env to make it boot systemd permanently.

> do I need to add
>

> usb_set_bootargs='setenv bootargs console=$console
> root=$usb_root rootdelay=$usb_rootdelay
> rootfstype=$usb_rootfstype $mtdparts
> init=/bin/systemd'
>

> ?

No, that's the wrong env. For this new u-boot the bootargs is set with a different env.

Generally, the best approach for users is to do is to set it in uEnv.txt to try it out.

However, since you have serial console, the best approach for you to do is to set it temporarily in serial console and boot:

setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts init=/bin/systemd'
boot

After you are satisified that it works, then set it in Debian:

fw_setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts init=/bin/systemd'

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello,

it is a shame, my SSD does not feel well with the Pogo:

[107171.445283] sata_oxnas: resetting SATA core
[107171.815226] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[107171.822348] ata1.00: failed command: DATA SET MANAGEMENT
[107171.827778] ata1.00: cmd 06/01:01:00:00:00/00:00:00:00:00/a0 tag 13 dma 512 out
[107171.827778]          res 51/04:01:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[107171.843031] ata1.00: status: { DRDY ERR }
[107171.847134] ata1.00: error: { ABRT }
[107171.850785] ata1: hard resetting link
[107172.355228] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[107172.365998] ata1.00: configured for UDMA/133
[107172.370352] ata1.00: device reported invalid CHS sector 0
[107172.375897] sd 0:0:0:0: [sda] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[107172.384217] sd 0:0:0:0: [sda] tag#13 Sense Key : 0x5 [current] [descriptor]
[107172.391370] sd 0:0:0:0: [sda] tag#13 ASC=0x21 ASCQ=0x4
[107172.396692] sd 0:0:0:0: [sda] tag#13 CDB: opcode=0x93 93 08 00 00 00 00 03 e5 b0 00 00 00 08 00 00 00
[107172.405980] blk_update_request: I/O error, dev sda, sector 65384448
[107172.412382] ata1: EH complete

----------------
[107503.995417] sata_oxnas: resetting SATA core
[107504.365312] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[107504.372431] ata1.00: failed command: DATA SET MANAGEMENT
[107504.377861] ata1.00: cmd 06/01:01:00:00:00/00:00:00:00:00/a0 tag 10 dma 512 out
[107504.377861]          res 51/04:01:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[107504.393113] ata1.00: status: { DRDY ERR }
[107504.397212] ata1.00: error: { ABRT }
[107504.400867] ata1: hard resetting link
[107504.905297] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[107509.905310] ata1.00: qc timeout (cmd 0xec)
[107509.909478] sata_oxnas: resetting SATA core
[107510.265313] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[107510.271470] ata1.00: revalidation failed (errno=-5)
[107510.276469] ata1: hard resetting link
[107510.785305] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[107510.792570] ata1.00: configured for UDMA/133
[107510.796966] ata1.00: device reported invalid CHS sector 0
[107510.802462] sd 0:0:0:0: [sda] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[107510.810816] sd 0:0:0:0: [sda] tag#10 Sense Key : 0x5 [current] [descriptor]
[107510.817950] sd 0:0:0:0: [sda] tag#10 ASC=0x21 ASCQ=0x4
[107510.823244] sd 0:0:0:0: [sda] tag#10 CDB: opcode=0x93 93 08 00 00 00 00 03 e6 18 00 00 00 08 00 00 00
[107510.832537] blk_update_request: I/O error, dev sda, sector 65411072
[107510.838981] ata1: EH complete

I already changed to

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
LABEL=rootfs    /               ext3    noatime,errors=remount-ro,nodiscard 0 1

in case it is caused by trim - it does not seem so, the error comes again and again.


I think I need to move to a normal HDD - or a stick.

Dieter,

Boot with USB rootfs, and then plug in this SSD drive. See if you get the same eror.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)