Welcome! Log In Create A New Profile

Advanced

Stuck at "ALERT! /dev/disk/by-label/rootfs does not exist. Dropping to a shell!"

Posted by ElMariachi 
Hello!

I have been reading dozens of sites in this great forum for weeks now, for preparing the conversion of my GoFlex Net into something useful (newest UBoot + latest possible Debian) as good as possible. My plan was following the instructions here.
The result was a disaster, where seemingly everything went wrong as it could have had.

It started with Pogoplug not offering the checkbox for enabling SSH. I tried all options multiple times, like restting cookies, enabling UPnP, another webbrowser, but this damn checkbox wouldn't appear.
After this I wrote an email to pogoplug support, asking them for help. What I got was more an insult than any help.. they just sent me the standard form, telling me I should read the forum and whatever.. same for the next two emails I wrote them..

Ok, then. I remembered that I had an USB2serial converter, from some earlier projects and made it work with my GoFlex Net. I found some instructions on how to add an start entry for dropbear.sh into the rcS script - but there was no dropbear.sh in my device. So I tried to create my own dropbear.sh, added it into rcS and finally got SSH working.

Then I updated the bootloader, like said in Jeff's original instructions. (install_uboot_mtd0.sh).
After flashing I tried booting from the USB thumb drive I had prepared - but the GoFlexNet wouldn't boot or become accessible anymore.
So my next step was trying to recover the bootloader (U-Boot).
For making this short:
-serial console didn't work anymore and just showed garbled characters.
-kwtool didn't work at all, as it would always got "xmodem bad message".
But for luck I noticed, that when I started kwtool, reset the GoFlex and enabled serial console at the same time, I could actually get working access through console again.
As I still needed to repair the bootloader I tried achieving this by updating to the most recent bootloader, following bodhi's instructions here.
I set "fw_setenv dtb_file" because I stil had the old debain from Jeff's original post on my usb drive.

From then on I couldn't boot into debian anymore, because I always get the following error:


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/disk/by-label/rootfs does not exist. Dropping to a shell!

Could you please help me?

Edit:
I removed the old Debian on my USB drive and replaced it by the most recent Debian 4.4 from bodhi. Then I added the uEnv.txt file with dtb_file='/boot/dts/kirkwood-goflexnet.dtb'.

This actually worked and it can boot into Debian again.
I'm not sure on how to continue from here, as I still got no rescue system and I don't know if the other OS I got on USB now than the original tutorial makes a difference there..

Edit2:
Ok, I just tried the "./install_rescue.sh" scripts. IT stops with saying that I had to update U-Boot to the latest version - but I think I already have the latest version.. Is this because Jeff's install rescue script is too old for knowing bhodi's current uboot?



Edited 3 time(s). Last edit at 07/28/2016 10:55AM by ElMariachi.
Re: Stuck at "ALERT! /dev/disk/by-label/rootfs does not exist. Dropping to a shell!"
July 28, 2016 12:33PM
ElMariachi,

> This actually worked and it can boot into Debian
> again.
> I'm not sure on how to continue from here, as I
> still got no rescue system and I don't know if the
> other OS I got on USB now than the original
> tutorial makes a difference there..

Sounds like you did not really have anything on the other USB, so you should continue using the new Debian 4.4 rootfs as the base from now on.

>
> Edit2:
> Ok, I just tried the "./install_rescue.sh"
> scripts. IT stops with saying that I had to update
> U-Boot to the latest version - but I think I
> already have the latest version.. Is this because
> Jeff's install rescue script is too old for
> knowing bhodi's current uboot?

True, it is old. But you still can install rescue system v2 from Jeff or v2.8 from davygravy. Either should work fine.

-bodhi
===========================
Forum Wiki
bodhi's corner
> Sounds like you did not really have anything on
> the other USB, so you should continue using the
> new Debian 4.4 rootfs as the base from now on.

Well, it had; but in the mean time I found that the images on the first USB flash had become corrupted.
No idea why, but am i not lucky?

> True, it is old. But you still can install rescue
> system v2 from Jeff or v2.8 from davygravy. Either
> should work fine.


Great! I will try those scripts instead, thank you!
Finally I got a little of this feeling that clouds might open and clear up the sky a bit more :)

PS: I noticed that I have to go back to the last Wheezy image by bodhi, because I could't get OMV installed on Jessie.



Edited 2 time(s). Last edit at 07/28/2016 07:31PM by ElMariachi.
Re: Stuck at "ALERT! /dev/disk/by-label/rootfs does not exist. Dropping to a shell!"
July 28, 2016 07:44PM
ElMariachi Wrote:
-------------------------------------------------------
> > Sounds like you did not really have anything on
> > the other USB, so you should continue using the
> > new Debian 4.4 rootfs as the base from now on.
>
> Well, it had; but in the mean time I found that
> the images on the first USB flash had become
> corrupted.
> No idea why, but am i not lucky?
>
> > True, it is old. But you still can install
> rescue
> > system v2 from Jeff or v2.8 from davygravy.
> Either
> > should work fine.
>
>
> Great! I will try those scripts instead, thank
> you!
> Finally I got a little of this feeling that clouds
> might open and clear up the sky a bit more :)
>
> PS: I noticed that I have to go back to the last
> Wheezy image by bodhi, because I could't get OMV
> installed on Jessie.

It is actually very common for the rootfs to get corrupted if the boot process was interrupted and then you have to powerdown. Anytime that happens chance is that you have to fsck it using another box.

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 07/28/2016 07:49PM by bodhi.
Hello!

I was trying t install Rescue V2.8.2 from here now: http://forum.doozan.com/read.php?4,7915

But it won't work as there actually is no mtd1 anymore. Also mtd2 isn't there.

Quote
root@debian:/tmp# dir /dev/mt*
/dev/mtd0 /dev/mtd0r


What is the reason for the missing partitions and what should I do now?

Edit:
I think I found the reason:
Quote
root@debian:/tmp# fw_printenv mtdparts
mtdparts=00:10:75:XX:XX:XX

Now I need to know why this happend. Seems like a mac adress got in the mtdparts variable for an unknown reason. Maybe my whole env settings are trash now?

I still have the initial backup of the original env
Quote
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data
)

I wondered about the mtdparts=mtdparts=" part already before.. does this actually make sense?



Edited 5 time(s). Last edit at 07/28/2016 09:05PM by ElMariachi.
Re: Stuck at "ALERT! /dev/disk/by-label/rootfs does not exist. Dropping to a shell!"
July 28, 2016 09:31PM
ElMariachi Wrote:
-------------------------------------------------------
> Hello!
>
> I was trying t install Rescue V2.8.2 from here
> now: http://forum.doozan.com/read.php?4,7915
>
> But it won't work as there actually is no mtd1
> anymore. Also mtd2 isn't there.
>
>
Quote
root@debian:/tmp# dir /dev/mt*
> /dev/mtd0 /dev/mtd0r

>
>
>
> What is the reason for the missing partitions and
> what should I do now?
>
> Edit:
> I think I found the reason:
>
Quote
root@debian:/tmp# fw_printenv mtdparts
> mtdparts=00:10:75:XX:XX:XX

>
>
> Now I need to know why this happend. Seems like a
> mac adress got in the mtdparts variable for an
> unknown reason. Maybe my whole env settings are
> trash now?
>
> I still have the initial backup of the original
> env
>
Quote
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(
> uImage),32M(rootfs),-(data

)
>
>
>
> I wondered about the mtdparts=mtdparts=" part
> already before.. does this actually make sense?

No it does not makes sense. Something went wrong. Get the output of

fw_printenv

and post here.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Stuck at "ALERT! /dev/disk/by-label/rootfs does not exist. Dropping to a shell!"
July 28, 2016 10:52PM
that is how my E02 has to be or i get an error: "variable does not star with 'mtdparts'"
I have set mtdparts to what it was in my backup
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)

And I could install the rescue system then. (Thank you feas!).
I also had a look at the other env settings, and they looked ok at the first glance:


root@debian:~# fw_printenv
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
ethact=egiga0
ethaddr=99:99:78:65:43:21
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb_addr=0x1c00000
load_initrd_addr=0x1100000
load_uimage_addr=0x800000
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
mainlineLinux=yes
mtdids=nand0=orion_nand
partition=nand0,2
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 $load_uimage_addr /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
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $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_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
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
usb_ready_retry=15
arcNumber=3089
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 3
dtb_file=/boot/dts/kirkwood-goflexnet.dtb
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_pogo=run bootcmd_rescue
rescue_installed=1
serverip=192.168.1.35
ipaddr=192.168.1.37
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
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
preboot=run preboot_nc
root@debian:~#[/i]


Also netconsole is working now. :)

But rescue system still can't boot. It seems as if it still tried to boot from USB with no drive attached:

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19 -0700)
Seagate GoFlex Net
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot:  0 
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: ide_preinit failed
Unknown command 'mmc' - try 'help'

no USB devices available

no IDE devices available
Unknown command 'mmc' - try 'help'
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: ide_preinit failed
device ide 0:1
** Bad device size - ide 0 **
device ide 1:1
** Bad device size - ide 1 **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc
Unknown command 'mmc' - try 'help'
device mmc 0:1
** Bad device mmc 0 **
device mmc 1:1
** Bad device mmc 1 **
device mmc 2:1
** Bad device mmc 2 **
device mmc 3:1
** Bad device mmc 3 **
loading uImage ...
** Bad device usb 0 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB /boot/dts/kirkwood-goflexnet.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
GoFlexNet>


Maybe this is because of dtb_file=/boot/dts/kirkwood-goflexnet.dtb?
Or because of bootdev=usb?

What what I need to change it to, for making it automatically boot from USB when plugged, SATA when plugged and internal flash when nothing is plugged in?



Edited 7 time(s). Last edit at 07/28/2016 11:10PM by ElMariachi.
Re: Stuck at "ALERT! /dev/disk/by-label/rootfs does not exist. Dropping to a shell!"
July 28, 2016 11:17PM
This did not make sense:
> > mtdparts=00:10:75:XX:XX:XX"]

While this makes perfect sense:
> mtdparts=mtdparts=orion_nand:1M(u-boot),4M(
> 
> > uImage),32M(rootfs),-(data])

Your rescue system was not set up properly.

These are OK:
set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_pogo=run bootcmd_rescue
rescue_installed=1

But this was not OK:
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec

The bootcmd must have the execution of the rescue system at the end, so that when there is no disk drive that can be booted, it will fall back to the rescue system

bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset

So to set that, boot into Debian and:

fw_setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset'

-bodhi
===========================
Forum Wiki
bodhi's corner
Edit:

Just forget about it. After I had done your suggested change and I had written a lot here, it actually worked!

Thank you very much!
It's a nice community here and you where very helpful!
:)

Now I still need to move my OS from USB to an old SATA-SSD and install OMV.



Edited 8 time(s). Last edit at 07/28/2016 11:39PM by ElMariachi.
Ok, maybe the last problem now is that I can't boot from SATA.

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19 -0700)
Seagate GoFlex Net
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot:  0 
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: Bus 0: not available  Bus 1: OK 
  Device 1: Model: TS32GSSD25S-M  Firm: 101028 Ser#: 20110414418743075560
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 30533.8 MB = 29.8 GB (62533296 x 512)
Unknown command 'mmc' - try 'help'

no USB devices available


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

Part	Start Sector	Num Sectors	UUID		Type
  1	63        	7823592   	00079389-01	83
  2	7823655   	54701325  	00079389-02	82
loading envs from ide 0 ...
** Bad device ide 0 **
Unknown command 'mmc' - try 'help'
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: not available  Bus 1: OK 
  Device 1: Model: TS32GSSD25S-M  Firm: 101028 Ser#: 20110414418743075560
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 30533.8 MB = 29.8 GB (62533296 x 512)
device ide 0:1
** Bad device ide 0 **
device ide 1:1
IDE read: device 1 not ready
IDE read: device 1 not ready
 ** ext2fs_devread() read error **
** File not found /boot/uImage **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc
Unknown command 'mmc' - try 'help'
device mmc 0:1
** Bad device mmc 0 **
device mmc 1:1
** Bad device mmc 1 **
device mmc 2:1
** Bad device mmc 2 **
device mmc 3:1
** Bad device mmc 3 **
loading uImage ...
** Bad device usb 0 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB /boot/dts/kirkwood-goflexnet.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.3.2-kirkwide
   Created:      2012-10-29  22:52:12 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3627768 Bytes = 3.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK


Starting kernel ...

In Jeff's old instructions I found that he used some settings for making SATA boot work, but obviously those settings won't fit to the current situation.
fw_setenv sata_boot 'ide reset; mw 0x800000 0 1; ext2load ide 0:1 0x800000 /boot/uImage; if ext2load ide 0:1 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi'
fw_setenv sata_bootcmd 'run usb_set_bootargs; run sata_boot'
fw_setenv bootcmd 'usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run sata_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset'

The different "bootcmd" collides with my current configuration, which looks rather different, as instructed by bodhi:
rescue:~# fw_printenv bootcmd
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset



Edited 2 time(s). Last edit at 07/29/2016 04:15AM by ElMariachi.
Re: Stuck at "ALERT! /dev/disk/by-label/rootfs does not exist. Dropping to a shell!"
July 29, 2016 01:05PM
ElMariachi,

Look the section e in the u-boot installation thread:

Quote

e. Modify the following u-boot variables using fw_setenv:

.......

Then for all boxes, restore these 2 envs using the saved envs text in step c (replace xxx with the real saved values)
fw_setenv mtdparts 'xxxxxxxxx'
fw_setenv ethaddr 'xx:xx:xx:xx:xx:xx'

Note: for boxes that boot with SATA as rootfs. Please make this adjustment if your boot drive is SATA:
fw_setenv bootcmd_uenv 'run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 3'
(This will help the "ide reset" to work properly. There seems to be a bug in u-boot that if you do "ide reset" too quickly in succession, the SATA drive might have problem spinning up).

Increase the sleep period to make it longer if 3 is not enough.


If that still does not work then you need to troubleshoot by executing each command after interrupting serial console
run scan_disk
run set_bootargs
run bootcmd_exec
And post the output of those 3 above commands here.

-bodhi
===========================
Forum Wiki
bodhi's corner
Hello!

I tried increasing the sleep period, but it wouldn't work.

rescue:~# fw_setenv bootcmd_uenv 'run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 9'
rescue:~# fw_printenv bootcmd_uenv
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 9
rescue:~#


I am using an SSD so I think that spinup shouldn't be a problem.
So I interrupted booting and tried the commands you gave me:

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19 -0700)
Seagate GoFlex Net
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot:  9 
 0 
GoFlexNet> run scan_disk
run scan_disk
running scan_disk ...
Scan device usb
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
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: not available  Bus 1: OK 
  Device 1: Model: TS32GSSD25S-M  Firm: 101028 Ser#: 20110414418743075560
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 30533.8 MB = 29.8 GB (62533296 x 512)
device ide 0:1
** Bad device ide 0 **
device ide 1:1
IDE read: device 1 not ready
 ** ext2fs_devread() read error **
** File not found /boot/uImage **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc
Unknown command 'mmc' - try 'help'
device mmc 0:1
** Bad device mmc 0 **
device mmc 1:1
** Bad device mmc 1 **
device mmc 2:1
** Bad device mmc 2 **
device mmc 3:1
** Bad device mmc 3 **
GoFlexNet>

So it seems that problems already start there. The SSD can actually be read without any problem after booting from rescue system or USB. It's an 32GB SSD with one 5GB ext3 partition named 'rootfs' and like 20GB swap after this.

rescue:~# fdisk /dev/sda -l

Disk /dev/sda: 32.0 GB, 32017047552 bytes
255 heads, 63 sectors/track, 3892 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1         487     3911796   83  Linux
/dev/sda2             488        3892    27350662+  82  Linux swap / Solaris
rescue:~#

rescue:~# dumpe2fs /dev/sda1
dumpe2fs 1.41.12 (17-May-2010)
Filesystem volume name:   rootfs
Last mounted on:          <not available>
Filesystem UUID:          a40e220a-2f4a-4956-bd36-0de4709600d5
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype sparse_super large_file
Filesystem flags:         unsigned_directory_hash 
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              244800
Block count:              977949
Reserved block count:     48897
Free blocks:              862335
Free inodes:              231528
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      238
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8160
Inode blocks per group:   510
Filesystem created:       Fri Jul 29 10:03:00 2016
Last mount time:          Fri Jul 29 10:03:20 2016
Last write time:          Sat Jul 30 08:24:30 2016
Mount count:              1
Maximum mount count:      21
Last checked:             Fri Jul 29 10:03:00 2016
Check interval:           15552000 (6 months)
Next check after:         Wed Jan 25 10:03:00 2017
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:	          256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      2700e4cc-adca-4089-8757-b501cf7a94fb
Journal backup:           inode blocks
Journal features:         (none)
Journal size:             64M
Journal length:           16384
Journal sequence:         0x0000000b
Journal start:            0


Group 0: (Blocks 0-32767)
  Primary superblock at 0, Group descriptors at 1-1
  Reserved GDT blocks at 2-239
  Block bitmap at 240 (+240), Inode bitmap at 241 (+241)
  Inode table at 242-751 (+242)
  32010 free blocks, 8149 free inodes, 2 directories
  Free blocks: 758-32767
  Free inodes: 12-8160
Group 1: (Blocks 32768-65535)
  Backup superblock at 32768, Group descriptors at 32769-32769
  Reserved GDT blocks at 32770-33007
  Block bitmap at 33008 (+240), Inode bitmap at 33009 (+241)
  Inode table at 33010-33519 (+242)
  31599 free blocks, 7607 free inodes, 92 directories
  Free blocks: 33520-55295, 55713-65535
  Free inodes: 8714-16320
Group 2: (Blocks 65536-98303)
  Block bitmap at 65536 (+0), Inode bitmap at 65537 (+1)
  Inode table at 65538-66047 (+2)
  32255 free blocks, 8159 free inodes, 1 directories
  Free blocks: 66048-88063, 88065-98303
  Free inodes: 16322-24480
Group 3: (Blocks 98304-131071)
  Backup superblock at 98304, Group descriptors at 98305-98305
  Reserved GDT blocks at 98306-98543
  Block bitmap at 98544 (+240), Inode bitmap at 98545 (+241)
  Inode table at 98546-99055 (+242)
  32015 free blocks, 8159 free inodes, 1 directories
  Free blocks: 99056-120831, 120833-131071
  Free inodes: 24482-32640
Group 4: (Blocks 131072-163839)
  Block bitmap at 131072 (+0), Inode bitmap at 131073 (+1)
  Inode table at 131074-131583 (+2)
  32246 free blocks, 8150 free inodes, 4 directories
  Free blocks: 131584-153599, 153610-163839
  Free inodes: 32651-40800
Group 5: (Blocks 163840-196607)
  Backup superblock at 163840, Group descriptors at 163841-163841
  Reserved GDT blocks at 163842-164079
  Block bitmap at 164080 (+240), Inode bitmap at 164081 (+241)
  Inode table at 164082-164591 (+242)
  30691 free blocks, 8048 free inodes, 1 directories
  Free blocks: 164592-186367, 187693-196607
  Free inodes: 40913-48960
Group 6: (Blocks 196608-229375)
  Block bitmap at 196608 (+0), Inode bitmap at 196609 (+1)
  Inode table at 196610-197119 (+2)
  30839 free blocks, 8061 free inodes, 1 directories
  Free blocks: 197120-219135, 220553-229375
  Free inodes: 49060-57120
Group 7: (Blocks 229376-262143)
  Backup superblock at 229376, Group descriptors at 229377-229377
  Reserved GDT blocks at 229378-229615
  Block bitmap at 229616 (+240), Inode bitmap at 229617 (+241)
  Inode table at 229618-230127 (+242)
  21791 free blocks, 5726 free inodes, 175 directories
  Free blocks: 230128-251903, 262129-262143
  Free inodes: 59555-65280
Group 8: (Blocks 262144-294911)
  Block bitmap at 262144 (+0), Inode bitmap at 262145 (+1)
  Inode table at 262146-262655 (+2)
  25900 free blocks, 5726 free inodes, 338 directories
  Free blocks: 262656-284671, 291028-294911
  Free inodes: 67715-73440
Group 9: (Blocks 294912-327679)
  Backup superblock at 294912, Group descriptors at 294913-294913
  Reserved GDT blocks at 294914-295151
  Block bitmap at 295152 (+240), Inode bitmap at 295153 (+241)
  Inode table at 295154-295663 (+242)
  27379 free blocks, 5726 free inodes, 173 directories
  Free blocks: 295664-317439, 322077-327679
  Free inodes: 75875-81600
Group 10: (Blocks 327680-360447)
  Block bitmap at 327680 (+0), Inode bitmap at 327681 (+1)
  Inode table at 327682-328191 (+2)
  22504 free blocks, 6938 free inodes, 138 directories
  Free blocks: 328192-350207, 359960-360447
  Free inodes: 82823-89760
Group 11: (Blocks 360448-393215)
  Block bitmap at 360448 (+0), Inode bitmap at 360449 (+1)
  Inode table at 360450-360959 (+2)
  22090 free blocks, 6460 free inodes, 264 directories
  Free blocks: 360960-382975, 393142-393215
  Free inodes: 91461-97920
Group 12: (Blocks 393216-425983)
  Block bitmap at 393216 (+0), Inode bitmap at 393217 (+1)
  Inode table at 393218-393727 (+2)
  24773 free blocks, 7171 free inodes, 157 directories
  Free blocks: 393728-415743, 423227-425983
  Free inodes: 98910-106080
Group 13: (Blocks 425984-458751)
  Block bitmap at 425984 (+0), Inode bitmap at 425985 (+1)
  Inode table at 425986-426495 (+2)
  15855 free blocks, 8160 free inodes, 0 directories
  Free blocks: 442897-458751
  Free inodes: 106081-114240
Group 14: (Blocks 458752-491519)
  Block bitmap at 458752 (+0), Inode bitmap at 458753 (+1)
  Inode table at 458754-459263 (+2)
  26413 free blocks, 8084 free inodes, 2 directories
  Free blocks: 459264-481279, 487123-491519
  Free inodes: 114317-122400
Group 15: (Blocks 491520-524287)
  Block bitmap at 491520 (+0), Inode bitmap at 491521 (+1)
  Inode table at 491522-492031 (+2)
  32255 free blocks, 8159 free inodes, 1 directories
  Free blocks: 492032-514047, 514049-524287
  Free inodes: 122402-130560
Group 16: (Blocks 524288-557055)
  Block bitmap at 524288 (+0), Inode bitmap at 524289 (+1)
  Inode table at 524290-524799 (+2)
  32255 free blocks, 8159 free inodes, 1 directories
  Free blocks: 524800-546815, 546817-557055
  Free inodes: 130562-138720
Group 17: (Blocks 557056-589823)
  Block bitmap at 557056 (+0), Inode bitmap at 557057 (+1)
  Inode table at 557058-557567 (+2)
  32255 free blocks, 8158 free inodes, 1 directories
  Free blocks: 557568-579583, 579585-589823
  Free inodes: 138723-146880
Group 18: (Blocks 589824-622591)
  Block bitmap at 589824 (+0), Inode bitmap at 589825 (+1)
  Inode table at 589826-590335 (+2)
  32255 free blocks, 8159 free inodes, 1 directories
  Free blocks: 590336-612351, 612353-622591
  Free inodes: 146882-155040
Group 19: (Blocks 622592-655359)
  Block bitmap at 622592 (+0), Inode bitmap at 622593 (+1)
  Inode table at 622594-623103 (+2)
  32250 free blocks, 8148 free inodes, 5 directories
  Free blocks: 623104-645119, 645126-655359
  Free inodes: 155053-163200
Group 20: (Blocks 655360-688127)
  Block bitmap at 655360 (+0), Inode bitmap at 655361 (+1)
  Inode table at 655362-655871 (+2)
  22016 free blocks, 6982 free inodes, 138 directories
  Free blocks: 655872-677887
  Free inodes: 164379-171360
Group 21: (Blocks 688128-720895)
  Block bitmap at 688128 (+0), Inode bitmap at 688129 (+1)
  Inode table at 688130-688639 (+2)
  18213 free blocks, 8160 free inodes, 0 directories
  Free blocks: 702683-720895
  Free inodes: 171361-179520
Group 22: (Blocks 720896-753663)
  Block bitmap at 720896 (+0), Inode bitmap at 720897 (+1)
  Inode table at 720898-721407 (+2)
  32256 free blocks, 8160 free inodes, 0 directories
  Free blocks: 721408-753663
  Free inodes: 179521-187680
Group 23: (Blocks 753664-786431)
  Block bitmap at 753664 (+0), Inode bitmap at 753665 (+1)
  Inode table at 753666-754175 (+2)
  32256 free blocks, 8160 free inodes, 0 directories
  Free blocks: 754176-786431
  Free inodes: 187681-195840
Group 24: (Blocks 786432-819199)
  Block bitmap at 786432 (+0), Inode bitmap at 786433 (+1)
  Inode table at 786434-786943 (+2)
  32256 free blocks, 8160 free inodes, 0 directories
  Free blocks: 786944-819199
  Free inodes: 195841-204000
Group 25: (Blocks 819200-851967)
  Backup superblock at 819200, Group descriptors at 819201-819201
  Reserved GDT blocks at 819202-819439
  Block bitmap at 819440 (+240), Inode bitmap at 819441 (+241)
  Inode table at 819442-819951 (+242)
  32016 free blocks, 8160 free inodes, 0 directories
  Free blocks: 819952-851967
  Free inodes: 204001-212160
Group 26: (Blocks 851968-884735)
  Block bitmap at 851968 (+0), Inode bitmap at 851969 (+1)
  Inode table at 851970-852479 (+2)
  32256 free blocks, 8160 free inodes, 0 directories
  Free blocks: 852480-884735
  Free inodes: 212161-220320
Group 27: (Blocks 884736-917503)
  Backup superblock at 884736, Group descriptors at 884737-884737
  Reserved GDT blocks at 884738-884975
  Block bitmap at 884976 (+240), Inode bitmap at 884977 (+241)
  Inode table at 884978-885487 (+242)
  32016 free blocks, 8160 free inodes, 0 directories
  Free blocks: 885488-917503
  Free inodes: 220321-228480
Group 28: (Blocks 917504-950271)
  Block bitmap at 917504 (+0), Inode bitmap at 917505 (+1)
  Inode table at 917506-918015 (+2)
  32255 free blocks, 8159 free inodes, 1 directories
  Free blocks: 918016-940031, 940033-950271
  Free inodes: 228482-236640
Group 29: (Blocks 950272-977948)
  Block bitmap at 950272 (+0), Inode bitmap at 950273 (+1)
  Inode table at 950274-950783 (+2)
  27165 free blocks, 8160 free inodes, 0 directories
  Free blocks: 950784-977948
  Free inodes: 236641-244800
rescue:~#

Strange ist, that after rebooting and trying the run_scandisk command a seconds time I got another result:
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19 -0700)
Seagate GoFlex Net
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot:  9 
 0 
GoFlexNet> run scan_disk
run scan_disk
running scan_disk ...
Scan device usb
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
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: not available  Bus 1: OK 
  Device 1: Model: TS32GSSD25S-M  Firm: 101028 Ser#: 20110414418743075560
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 30533.8 MB = 29.8 GB (62533296 x 512)
IDE read: device 1 not ready
device ide 0:1
** Bad device ide 0 **
device ide 1:1
** No partition table - ide 1 **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc
Unknown command 'mmc' - try 'help'
device mmc 0:1
** Bad device mmc 0 **
device mmc 1:1
** Bad device mmc 1 **
device mmc 2:1
** Bad device mmc 2 **
device mmc 3:1
** Bad device mmc 3 **
GoFlexNet>

The other two commands always result in:
GoFlexNet> run set_bootargs
run set_bootargs
GoFlexNet> run bootcmd_exec
run bootcmd_exec
loading uImage ...
** Bad device usb 0 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB /boot/dts/kirkwood-goflexnet.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
GoFlexNet>

OK:
While searching for the error message, that I go from the hard disk scan command, I found this thread. So I thought the reason could be an incompatibility of the SSD itself and replaced it by another old SSD I got around - and it's working!

So it seems we got compatibility problems of UBoot with some Firmwares or SSD-Controllers here. Would be nice to have a list of known well working controllers then.

My working SSD btw. is an:

ADATA SP 600 32GByte (JMicron JMF661 controller)

The NOT working (not booting) SSD is an:
Transcend TS32GSSD25S-M Revision: 28 (JMicron JMF616 controller)



Thank you for your helpful hand!

:-)



Edited 7 time(s). Last edit at 07/30/2016 03:41AM by ElMariachi.
Re: Stuck at "ALERT! /dev/disk/by-label/rootfs does not exist. Dropping to a shell!"
July 30, 2016 03:22PM
This is common. Not all SSDs work with u-boot.

But the Transcend SSD seems to be working.

Reset IDE: Bus 0: not available  Bus 1: OK 
  Device 1: Model: TS32GSSD25S-M  Firm: 101028 Ser#: 20110414418743075560
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 30533.8 MB = 29.8 GB (62533296 x 512)


It just need to be handled with extra steps, since it is apparently has quirks.

-bodhi
===========================
Forum Wiki
bodhi's corner
By extra steps you mean the workaround using USB flash?



Edited 1 time(s). Last edit at 07/30/2016 10:14PM by ElMariachi.
Re: Stuck at "ALERT! /dev/disk/by-label/rootfs does not exist. Dropping to a shell!"
July 31, 2016 02:16AM
ElMariachi Wrote:
-------------------------------------------------------
> By extra steps you mean the workaround using USB
> flash?

The SSD was initialized OK in u-boot. So to use it, probably a longer sleep period is needed. To test that, do everything manually at u-boot console. For example, wait longer after "ide reset".

-bodhi
===========================
Forum Wiki
bodhi's corner
Sorry, I don't really understand what you mean.
'The first command I use after interrupting the bootloader is
'run scan_disk'.
And just using this command already gives the error, no matter how long I wait before. I even waited two minutes once.
Also I tried increasing the sleep in this line up to 30:

fw_setenv bootcmd_uenv 'run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 30

But there always is a problem while scanning the disks:

run scan_disk
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: not available  Bus 1: OK 
  Device 1: Model: TS32GSSD25S-M  Firm: 101028 Ser#: 20110414418743075560
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 30533.8 MB = 29.8 GB (62533296 x 512)
device ide 0:1
** Bad device ide 0 **
device ide 1:1
IDE read: device 1 not ready
 ** ext2fs_devread() read error **
** File not found /boot/uImage **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **

There is no command between
Reset IDE: Bus 0: not available  Bus 1: O
and
device ide 1:1
IDE read: device 1 not ready
which I could wait with, because it's all caused by the one initial
run scan_disk
in the beginning.



Edited 5 time(s). Last edit at 07/31/2016 11:29AM by ElMariachi.
Re: Stuck at "ALERT! /dev/disk/by-label/rootfs does not exist. Dropping to a shell!"
July 31, 2016 12:46PM
Boot, Interrupt serial console and

ide reset
sleep 15
ext2ls ide 1:1 /

-bodhi
===========================
Forum Wiki
bodhi's corner
It seems to be workign like this.
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19 -0700)
Seagate GoFlex Net
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot:  9 
 0 
GoFlexNet> ide reset
ide reset

Reset IDE: Bus 0: not available  Bus 1: OK 
  Device 1: Model: TS32GSSD25S-M  Firm: 101028 Ser#: 20110414418743075560
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 30533.8 MB = 29.8 GB (62533296 x 512)
GoFlexNet> sleep 15
sleep 15
GoFlexNet> ext2ls ide 1:1 /
ext2ls ide 1:1 /
<DIR>       4096 .
<DIR>       4096 ..
<DIR>      16384 lost+found
<DIR>       4096 bin
<DIR>       4096 boot
<DIR>       4096 dev
<DIR>       4096 etc
<DIR>       4096 home
<DIR>       4096 lib
<DIR>       4096 media
<DIR>       4096 mnt
<DIR>       4096 opt
<DIR>       4096 proc
<DIR>       4096 root
<DIR>       4096 run
<DIR>       4096 sbin
<DIR>       4096 selinux
<DIR>       4096 srv
<DIR>       4096 sys
<DIR>       4096 tmp
<DIR>       4096 usr
<DIR>       4096 var
GoFlexNet>

Where would I need to store these commands for making this work for booting?
Re: Stuck at "ALERT! /dev/disk/by-label/rootfs does not exist. Dropping to a shell!"
July 31, 2016 01:26PM
> Where would I need to store these commands for
> making this work for booting?

Ah. So now you know it does work, but need some extra period to settle down. You can change your bootcmd to take out the uenv loading, just leaving the scandisk in:

setenv sleep_period 15
setenv bootcmd 'run scan_disk; sleep $sleep_period; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset'

And reduce sleep_period to a number that works well for this disk.

-bodhi
===========================
Forum Wiki
bodhi's corner
My current bootcmd string is:
run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset

Is there a reason you left
 run bootcmd_uenv; 
out?
It seems like it is for reading the uEnv.txt file, so shouldn't I better leave it in somewhere?

For now I have set it to:
run bootcmd_uenv; run scan_disk; sleep $sleep_period; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset

It seems like it's scanning the drives two times now with the long time in between, but it still doesn't work (with and without bootcmd_uenv):
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19 -0700)
Seagate GoFlex Net
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot:  0 
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: Bus 0: not available  Bus 1: OK 
  Device 1: Model: TS32GSSD25S-M  Firm: 101028 Ser#: 20110414418743075560
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 30533.8 MB = 29.8 GB (62533296 x 512)
IDE read: device 1 not ready
Unknown command 'mmc' - try 'help'

no USB devices available

no IDE devices available
Unknown command 'mmc' - try 'help'
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: not available  Bus 1: OK 
  Device 1: Model: TS32GSSD25S-M  Firm: 101028 Ser#: 20110414418743075560
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 30533.8 MB = 29.8 GB (62533296 x 512)
device ide 0:1
** Bad device ide 0 **
device ide 1:1
IDE read: device 1 not ready
 ** ext2fs_devread() read error **
** File not found /boot/uImage **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc
Unknown command 'mmc' - try 'help'
device mmc 0:1
** Bad device mmc 0 **
device mmc 1:1
** Bad device mmc 1 **
device mmc 2:1
** Bad device mmc 2 **
device mmc 3:1
** Bad device mmc 3 **
loading uImage ...
** Bad device usb 0 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB /boot/dts/kirkwood-goflexnet.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.3.2-kirkwide
   Created:      2012-10-29  22:52:12 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3627768 Bytes = 3.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK


Starting kernel ...

I tried sleep_period up to 30 seconds.

I don't really understand the loops, but wouldn't the waiting time rather have to be somewhere in 'scan_disk'?

rescue:~# fw_printenv scan_disk
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 $load_uimage_addr /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
rescue:~#



Edited 10 time(s). Last edit at 07/31/2016 03:15PM by ElMariachi.
Re: Stuck at "ALERT! /dev/disk/by-label/rootfs does not exist. Dropping to a shell!"
July 31, 2016 03:13PM
Try both cases:

2. Power up, interrupt serial console

setenv bootcmd 'run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset'
boot

2. Power up, interrupt serial console

setenv bootcmd 'run bootcmd_uenv; sleep 15; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset'
boot

-bodhi
===========================
Forum Wiki
bodhi's corner
Hello!

I tried both variants. Also I tried adding additional waiting times at other points where I thought they might help. And I increased all waiting times so high, that the final boot into the rescue system would take about 3minutes. Still it won't work. The only difference I have seen is, that the error changed between
IDE read: device 1 not ready
 ** ext2fs_devread() read error **
and something like "no partition table".
Also I have seen that using "ide reset" just sometimes works and sometimes won't, epecially when used mutiple times in a row, but i sometimes fails on it's first usage, also.

I have bought an used SSD from ebay now(same like the working one), because I need those two GoFlexNets working for a friend who wants an archive and backup system, but I still got my own old GoFlexNet which I could try on later, and it would just be nice to fix this problem anyway; be it just for knowing that the system is universal and flexible with no problem regarding the SSD's choice.



Edited 2 time(s). Last edit at 07/31/2016 09:50PM by ElMariachi.
Re: Stuck at "ALERT! /dev/disk/by-label/rootfs does not exist. Dropping to a shell!"
July 31, 2016 10:42PM
ElMariachi,

> and flexible with no problem regarding the SSD's
> choice.

In general, it works for any SATA drive, whether it is SDD or HDD. But you got one SSD that falls into the exceptional case.

So the idea is you need to find the work around for that SSD. If you can use a different SSD/HDD then you should use that, and not bother with finding a workaround.

-bodhi
===========================
Forum Wiki
bodhi's corner
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: