Seagate Goflex Home turned into paperweight, please help.

Hi Bodhi,
I finally got to the final stage, not knowing what exact made this happen. But I am not sure if the result of mkimage is positive because it says Signing / verified boot not supported (CONFIG_FIT_SIGNATURE undefined). Please have a look, thank you.

My username sdd1 # tar -xjf Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
My username sdd1 # cd /media/sdd1/boot
My username boot # cp -a zImage-4.4.0-kirkwood-tld-1 zImage.fdt
My username boot # cat dts/kirkwood-goflexhome.dtb >> zImage.fdt
My username boot # mv uImage uImage.orig
My username boot # mkimage -A arm -0 linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n linux-4.4.0-kirkwood-tld-1 -d zImage.fdt uImage sync
The program 'mkimage' is currently not installed. You can install it by typing:
apt install u-boot-tools
My username boot # apt install u-boot-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
u-boot-tools
0 upgraded, 1 newly installed, 0 to remove and 55 not upgraded.
Need to get 97.8 kB of archives.
After this operation, 395 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 u-boot-tools amd64 2016.01+dfsg1-2ubuntu2 [97.8 kB]
Fetched 97.8 kB in 0s (195 kB/s)
Selecting previously unselected package u-boot-tools.
(Reading database ... 201175 files and directories currently installed.)
Preparing to unpack .../u-boot-tools_2016.01+dfsg1-2ubuntu2_amd64.deb ...
Unpacking u-boot-tools (2016.01+dfsg1-2ubuntu2) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up u-boot-tools (2016.01+dfsg1-2ubuntu2) ...
My username boot # apt install u-boot-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
u-boot-tools is already the newest version (2016.01+dfsg1-2ubuntu2).
0 upgraded, 0 newly installed, 0 to remove and 55 not upgraded.
My username boot # mkimage -A arm -0 linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n linux-4.4.0-kirkwood-tld-1 -d zImage.fdt uImage sync
Usage: mkimage -l image
-l ==> list image header information
mkimage [-x] -A arch -O os -T type -C comp -a addr -e ep -n name -d data_file[:data_file...] image
-A ==> set architecture to 'arch'
-O ==> set operating system to 'os'
-T ==> set image type to 'type'
-C ==> set compression type 'comp'
-a ==> set load address to 'addr' (hex)
-e ==> set entry point to 'ep' (hex)
-n ==> set image name to 'name'
-d ==> use image data from 'datafile'
-x ==> set XIP (execute in place)
mkimage [-D dtc_options] [-f fit-image.its|-F] fit-image
-D => set all options for device tree compiler
-f => input filename for FIT source
Signing / verified boot not supported (CONFIG_FIT_SIGNATURE undefined)
mkimage -V ==> print version information and exit
Use -T to see a list of available image types

These are 2 separate commands. sync command flushes all pending writes to the all disks (to make sure that you can remove the drive after no more disk activity).

mkimage -A arm -0 linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n linux-4.4.0-kirkwood-tld-1 -d zImage.fdt uImage 
sync

And please use code tags for all commands, logs... (like I did for the 2 commands above). It is hard to read the log without code tags

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

Thank you for the patience, Bodhi.

The image was successfully created. I unmounted sdX.
I plugged the USB in the Goflex Home, with the wire connection to the router, powered it on.
The upper light flashed green for at least 20 seconds, with a mechanical sound of the drive at the beginning
Then the light died without turning solid green.
After 3 or 4 seconds, the lower light blinked white for 1/10 second then died
After another 10 seconds, the lower light blinked white again for 1/10 second then died.

I repeated 3 times. Same brick-like result after about 40 seconds.
Also tried to press the reset pin, nothing happened.

To ensure I did do everything properly, I repeated the whole process. The only thing unexpected to me is

My username # mkdir /media/sdd1
mkdir: cannot create directory ‘/media/sdd1’: File exists

Same result, the Goflex did't boot. Please see the full log below.

My username # dmesg | tail
[ 2598.255965] sd 4:0:0:0: [sdd] Assuming drive cache: write through
[ 2598.265590]  sdd: sdd1
[ 2598.278560] sd 4:0:0:0: [sdd] Attached SCSI removable disk
[ 2598.700746] EXT4-fs (sdd1): mounting ext3 file system using the ext4 subsystem
[ 2598.716324] EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts: (null)
[ 3533.572216]  sda: sda1
[ 3533.580580]  sda: sda1
[ 3534.041486]  sda: sda1
[ 3664.002092]  sdd:
[ 3664.353463]  sdd: sdd1
My username # fdisk dev/sdd

Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

fdisk: cannot open dev/sdd: No such file or directory
My username # fdisk /dev/sdd

Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): o
Created a new DOS disklabel with disk identifier 0x7a730a37.

Command (m for help): n
Partition type
   p   primary (0 primary, 0 extended, 4 free)
   e   extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-31711231, default 2048): 2048
Last sector, +sectors or +size{K,M,G,T,P} (2048-31711231, default 31711231): 31711231

Created a new partition 1 of type 'Linux' and of size 15.1 GiB.

Command (m for help): a
Selected partition 1
The bootable flag on partition 1 is enabled now.

Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

My username # mkfs.ext3 -L rootfs /dev/sdd1
mke2fs 1.42.13 (17-May-2015)
/dev/sdd1 contains a vfat file system labelled 'USB Stick'
Proceed anyway? (y,n) y
Creating filesystem with 3963648 4k blocks and 991232 inodes
Filesystem UUID: 36795708-b6f7-4de4-b520-1e863c73b519
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done   

My username # mkdir /media/sdd1
mkdir: cannot create directory ‘/media/sdd1’: File exists
My username # mount /dev/sdd1 /media/sdd1
My username # cd /media/sdd1
My username sdd1 # tar -xjf Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
My username sdd1 # cd /media/sdd1/boot
My username boot # cp -a zImage-4.4.0-kiirkwood-tld-1 zImage.fdt
cp: cannot stat 'zImage-4.4.0-kiirkwood-tld-1': No such file or directory
My username boot # cp -a zImage-4.4.0-kirkwood-tld-1 zImage.fdt
My username boot # cat dts/kirkwood-goflexhome.dtb >> zImage.fdt
My username boot # mv uImage uImage.orig
My username boot # mkimage -A arm -O Linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.4.0-kirkwood-tld-1 -d zImage.fdt uImage
Image Name:   Linux-4.4.0-kirkwood-tld-1
Created:      Fri Jan 13 18:46:25 2017
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    3165437 Bytes = 3091.25 kB = 3.02 MB
Load Address: 00008000
Entry Point:  00008000
My username boot # sync
My username boot # sync
My username boot #

Edited 6 time(s). Last edit at 01/13/2017 06:17PM by paperweight.

Jay,

Everything was done correctly, except one very important command:

su

You did not become root. It is the 1st thing you must do.

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

Yes, I did. That is always the first thing I do. SU then password.

paperweight Wrote:
-------------------------------------------------------
> Yes, I did. That is always the first thing I do.
> SU then password.

Did the prompt turn red? (on Mint it is red if you are root). And you could make sure that you verify before doing anything:

whoami

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

And unplug the HDD before power up the GFHome, too. The LED indicated that you have the HDD plugged in. The only drive should be attached is the USB rootfs.

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



Edited 1 time(s). Last edit at 01/14/2017 12:45AM by bodhi.

Ah, I had the HDD sitting on the base all the time.

Unplugged it, the upper light turned solid green. In Linux:

My username # ping debian.local
PING debian.local (xxx.xxx.xx.x) 56(84) bytes of data.
64 bytes from xxx.xxx.xx.x: icmp_seq=1 ttl=64 time=3.15 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=2 ttl=64 time=8.32 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=3 ttl=64 time=1.55 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=4 ttl=64 time=2.72 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=5 ttl=64 time=1.46 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=6 ttl=64 time=3.90 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=7 ttl=64 time=2.01 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=8 ttl=64 time=1.56 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=9 ttl=64 time=1.28 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=10 ttl=64 time=1.37 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=11 ttl=64 time=1.25 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=12 ttl=64 time=1.51 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=13 ttl=64 time=2.34 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=14 ttl=64 time=1.60 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=15 ttl=64 time=2.17 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=16 ttl=64 time=1.47 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=17 ttl=64 time=2.08 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=18 ttl=64 time=1.33 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=19 ttl=64 time=1.64 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=20 ttl=64 time=1.80 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=21 ttl=64 time=3.50 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=22 ttl=64 time=1.65 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=23 ttl=64 time=1.54 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=24 ttl=64 time=1.31 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=25 ttl=64 time=1.85 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=26 ttl=64 time=1.18 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=27 ttl=64 time=1.53 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=28 ttl=64 time=1.27 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=29 ttl=64 time=2.33 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=30 ttl=64 time=2.14 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=31 ttl=64 time=7.11 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=32 ttl=64 time=1.39 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=33 ttl=64 time=2.92 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=34 ttl=64 time=1.20 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=35 ttl=64 time=1.62 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=36 ttl=64 time=1.20 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=37 ttl=64 time=1.54 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=38 ttl=64 time=1.34 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=39 ttl=64 time=1.48 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=40 ttl=64 time=4.71 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=41 ttl=64 time=2.05 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=42 ttl=64 time=1.37 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=43 ttl=64 time=1.69 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=44 ttl=64 time=1.18 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=45 ttl=64 time=1.92 ms
64 bytes from xxx.xxx.xx.x: icmp_seq=46 ttl=64 time=1.38 ms
...

I guess the Goflex Home is unbricked?



Edited 1 time(s). Last edit at 01/14/2017 02:19AM by paperweight.

Jay,

> My username # ping debian.local
> PING debian.local (xxx.xxx.xx.x) 56(84) bytes of
> data.
> 64 bytes from xxx.xxx.xx.x: icmp_seq=1 ttl=64
> time=3.15 ms
> 64 bytes from xxx.xxx.xx.x: icmp_seq=2 ttl=64
> time=8.32 ms
> 64 bytes from xxx.xxx.xx.x: icmp_seq=3 ttl=64
> time=1.55 ms
...
> I guess the Goflex Home is unbricked?

Wow! that's is a very good sign :)

Now, on Terminal, connect with SSH. The rootfs root password is root.

ssh root@debian.local

Upon connecting,

uname -a

If you can do all this, then it is unbricked!

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

I am not sure if I could do it. After I became root, the result is:

My username # ssh root@debian.local
ssh: Could not resolve hostname debian.local: Name or service not known
My username # uname -a
My Linuxbox Name 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
My username #

Update:
Out of curiosity I played with the ssh command again after a few minutes. The result is:

My Username # ssh root@debian.local
The authenticity of host 'debian.local (xxx.xxx.xx.x)' can't be established.
RSA key fingerprint is SHA256:3w8lhtM2U+2PuKpadNZsyiesUrKAO9BTgJ4k013Fxnk.
Are you sure you want to continue connecting (yes/no)? y
Please type 'yes' or 'no': yes
Warning: Permanently added 'debian.local,xxx.xxx.xx.x' (RSA) to the list of known hosts.
root@debian.local's password: 
Linux debian 4.4.0-kirkwood-tld-1 #1 PREEMPT Mon Jan 25 20:35:24 PST 2016 armv5tel

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Feb 19 20:08:26 2016 from 192.168.0.100
root@debian:~#

Edited 3 time(s). Last edit at 01/14/2017 11:22AM by paperweight.

Jay,

Congrat :) you've successfully unbricked your GFHome!

First thing is to make a back up for this USB drive. Use either Acronis on Windows, or using tar command as described here .

And then read various topics here in the Wiki thread.

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



Edited 1 time(s). Last edit at 01/14/2017 07:55PM by bodhi.

Thank you, Bodhi, for the enlightenment!
Finally the Goflex home got rescued and I got the chance to try Linux.

1) So the rootfs USB I have is similar to the USB stick with installed Linux OS?
2) The Goflex Home is now a regular NAS with some "programs" installed on the HDD previously (like the Squeeze server 5 years ago)? Or I need to install later on the USB stick?
3) I should keep the rootfs USB permanently on the Home? Remove the HDD whenever I need to restart it?

Could you recommend some easy-to-follow wikis that teache how to use a NAS with Linux and Windows?
To be honest, I don't even know how to see what is in the attached HDD :-))

Jay.



Edited 1 time(s). Last edit at 01/14/2017 10:02PM by paperweight.

Jay,

>
> 1) So the rootfs USB I have is similar to the USB
> stick with installed Linux OS?

Yes. It is a full Linux system just like the Linux Mint USB rootfs. This is my custom build Debian.

> 2) The Goflex Home is now a regular NAS with some
> "programs" installed on the HDD previously (like
> the Squeeze server 5 years ago)?

It is. However, since this rootfs is a basic rootfs, you will need to install Debian packages to make it like Squeezeplug.

> 3) I should keep the rootfs USB permanently on the
> Home? Remove the HDD whenever I need to restart
> it?

There is no need to remove the HDD, if you modify some uboot envs to point the rootfs to the USB always. The current u-boot you have on this is quite old, but it does its job very well :). At the shell prompt, execute these commands and post the output here:

dmesg
cat /proc/mtd
fw_printenv

> Could you recommend some easy-to-follow wikis that
> teache how to use a NAS with Linux and Windows?
> To be honest, I don't even know how to see what is
> in the attached HDD :-))

I don't know any tutorial for beginners. The Wiki thread I post above contains a wealth of information. You could read that to get an idea.

As I said, backup this rootfs, and then expirement. Keep making backup regularly, and when you think you screw up, just restore it to the last good one.

----

Or if you prefer a ready solution like Squeezeplug, just make a USB rootfs of that and boot back to Squeezeplug. As long as you don't change any u-boot envs, it won't brick it again (but be careful, post questions if you are not sure how to avoid that).

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

Thank you, Bodhi, for info.

1) When I backup the USB rootfs, I need to remove the USB stick. Do I need to turn off the GoflexHome from Linux terminal (because something is running on the rootfs) or just press the power button?

2) Do I need to first power off the base and then plug in and out the HDD, regardless if I have the modification (to point the rootfs to the USB always) or not? How do I know the HDD is not spinning/in use?

Update: I think I found the answer in another post of yours 4 years ago: "The Goflex Home always assigns the SATA drive sda because it was recognized first. And there is no system on sda1. " The Pogoplug system was deleted from the HDD during my last hacking attempt 5 years ago but the Home still assigns HDD for booting. By removing the HDD physically, the home is forced to boot from the USB rather than SATA

3) What boot is in the HDD? As you instructed, I had to remove the HDD to let base boot from the USB. Then why the base can't boot from HDD when there is no USB rootfs attached?

4) The Goflexhome is a headless computer but a very weak one. Do I need to have a partition on the HDD as additional memory for any packages to work?

5) How can I determine which package(s) from this page will work on this weak hardware?

6) Since I can't find the squeezebox server package,I should look for alternatives in the section of Media Streaming? The original Pogoplug software can't be restored and I want to try something that functions like a personal dropbox. Will Owncloud on Goflexhome fit the bill if I keep the Goflexhome always on? Openmediavault?



Edited 10 time(s). Last edit at 01/15/2017 03:07PM by paperweight.

paperweight Wrote:
-------------------------------------------------------
> Thank you, Bodhi, for info.
>
> 1) When I backup the USB rootfs, I need to remove
> the USB stick. Do I need to turn off the
> GoflexHome from Linux terminal (because something
> is running on the rootfs) or just press the power
> button?

Shutdown the GFHome at the Linux shell:

shutdown -h now

And observe the LED. After it has turned off, wait a few seconds before pushing the power button to release it. And then unplug the USB.

>
> 2) Do I need to first power off the base and then
> plug in and out the HDD, regardless if I have the
> modification (to point the rootfs to the USB
> always) or not? How do I know the HDD is not
> spinning/in use?
>
> Update: I think I found the answer in another post
> of yours 4 years ago: "The Goflex Home always
> assigns the SATA drive sda because it was
> recognized first. And there is no system on sda1.
> " The Pogoplug system was deleted from the HDD
> during my last hacking attempt 5 years ago but the
> Home still assigns HDD for booting. By removing
> the HDD physically, the home is forced to boot
> from the USB rather than SATA

Always shutdown the GFHome before removing the HDD.

>
> 3) What boot is in the HDD? As you instructed, I
> had to remove the HDD to let base boot from the
> USB. Then why the base can't boot from HDD when
> there is no USB rootfs attached?
>

There is nothing on the HDD that you can use for booting.

> 4) The Goflexhome is a headless computer but a
> very weak one. Do I need to have a partition on
> the HDD as additional memory for any packages to
> work?
>

You need to create a swap file so that memory can be used more effectively. Use the swap file to make it more flexible, don't use swap partition as traditonaly suggested.

> 5) How can I determine which package(s) from
> this
> page will work on this weak hardware?
>

You dont need to look at that yet. Just google for something you want to do and usually the instruction you find will show that you need to run this command at Linux shell:

apt-get install ....

> 6) Since I can't find the squeezebox server
> package,I should look for alternatives in the
> section of Media Streaming? The original Pogoplug
> software can't be restored and I want to try
> something that functions like a personal dropbox.
> Will Owncloud on Goflexhome fit the bill if I keep
> the Goflexhome always on? Openmediavault?

Everybody has own preference. But I would suggest looking into Nextcloud (formerly Owncloud).

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



Edited 1 time(s). Last edit at 01/15/2017 06:19PM by bodhi.

Thanks, Bodhi.

Are you sure it is -h that I need to shut down? When I performed that, the Linux shell (my netbook) got shut down.

paperweight Wrote:
-------------------------------------------------------
> Thanks, Bodhi.
>
> Are you sure it is -h that I need to shut down?
> When I performed that, the Linux shell (my
> netbook) got shut down.

Execute the command at the Linux shell of the GFHome (after you have connected with SSH). Not the Linux Mint shell, which will shutdown the netbook.

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

My username  # cd /media/sdd1
My username sdd1 # time tar -cjf /media/sda1/my-rootfs.tar.bz2  . &
[1] 2646
My username sdd1 # tar (child): /media/sda1/my-rootfs.tar.bz2: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now

real	0m0.019s
user	0m0.004s
sys	0m0.004s

[1]+  Exit 141                time tar -cjf /media/sda1/my-rootfs.tar.bz2 .
My username sdd1 #

I got this error message when I tried to backup in Linux. Now I am trying Acronis.

Update:
I made a sector by sector image of the rootfs with the Easeup Free. Hope that is sufficient.

When I cleaned my old desktop tower, I found the old rootfs I made 5 years ago and booted the Home with it. I tried to post the info about the build but I could only get the following with dmesg command:

177.401179] usb 1-3.3: USB disconnect, device number 7
[  197.053862] usb 1-3.3: new high-speed USB device number 8 using ehci-pci
[  197.147953] usb 1-3.3: New USB device found, idVendor=1307, idProduct=0165
[  197.147971] usb 1-3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  197.147981] usb 1-3.3: Product: USB Mass Storage Device
[  197.147989] usb 1-3.3: Manufacturer: USBest Technology
[  197.147997] usb 1-3.3: SerialNumber: 00000000002325
[  197.154202] usb-storage 1-3.3:1.0: USB Mass Storage device detected
[  197.155815] scsi host4: usb-storage 1-3.3:1.0
[  198.162958] scsi 4:0:0:0: Direct-Access     Ut165    USB2FlashStorage 0.00 PQ: 0 ANSI: 2
[  198.172469] sd 4:0:0:0: Attached scsi generic sg3 type 0
[  198.174914] sd 4:0:0:0: [sdd] 15794176 512-byte logical blocks: (8.09 GB/7.53 GiB)
[  198.176506] sd 4:0:0:0: [sdd] Write Protect is off
[  198.176523] sd 4:0:0:0: [sdd] Mode Sense: 00 00 00 00
[  198.177292] sd 4:0:0:0: [sdd] Asking for cache data failed
[  198.177305] sd 4:0:0:0: [sdd] Assuming drive cache: write through
[  198.513686]  sdd: sdd1 sdd2
[  198.527842] sd 4:0:0:0: [sdd] Attached SCSI removable disk
[  199.071387] EXT4-fs (sdd1): mounting ext3 file system using the ext4 subsystem
[  278.812796] EXT4-fs (sdd1): warning: checktime reached, running e2fsck is recommended
[  279.112168] EXT4-fs (sdd1): recovery complete
[  279.114383] EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts: (null)
[  967.022327] usb 1-3.3: USB disconnect, device number 8

Which command should I use to get the name of the build?

ssh root@debian.local
ssh root@squeezeplug

Ssh with the above two guesses can't get me root so now I can't shut it down.



Edited 1 time(s). Last edit at 01/16/2017 01:47PM by paperweight.