Rescue System Pogo V3 - Using Stock Pogo V3 OS
Posted by bodhi
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS March 05, 2016 05:03PM |
Admin Registered: 13 years ago Posts: 18,997 |
hachigo,
The envs look fine. You can create the 3.17 Debian rootfs without changing anything (just tar it). Follow the instruction (extract it to a single partition type Ext3, as root user, and label it rootfs). That's it, no further change (don't embed the DTB).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
The envs look fine. You can create the 3.17 Debian rootfs without changing anything (just tar it). Follow the instruction (extract it to a single partition type Ext3, as root user, and label it rootfs). That's it, no further change (don't embed the DTB).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS March 05, 2016 05:39PM |
Registered: 10 years ago Posts: 26 |
Hi bodhi,
Hmm. What you suggested is what I did the the very first time, but it never booted. I just tried again what you suggested and still nothing.
Just to be sure I'm not screwing anything up here's what I did.
On my ubuntu machine, I erased and reformatted my sata harddrive with fdisk. Created one 4GB primary partition. Then formatted to ext3 with the label "rootfs" using this command
I then un-tar the 3.17 Debian rootfs into that partition, issued a sync command. Powered off my PC, removed the sata drive and plugged it into the pogoplug pro and powered on the pogoplug pro.
What does " ## Error: "dt_bootcmd_usb" not defined" mean? I'm not sure what I'm doing wrong. Also I didn't mean to steal the thread. Should I post in another post?
Here is the bootup output from the serial console:
-Hachigo
Edited 1 time(s). Last edit at 03/05/2016 05:45PM by hachigo.
Hmm. What you suggested is what I did the the very first time, but it never booted. I just tried again what you suggested and still nothing.
Just to be sure I'm not screwing anything up here's what I did.
On my ubuntu machine, I erased and reformatted my sata harddrive with fdisk. Created one 4GB primary partition. Then formatted to ext3 with the label "rootfs" using this command
mke2fs -L rootfs -j /dev/sdb1
I then un-tar the 3.17 Debian rootfs into that partition, issued a sync command. Powered off my PC, removed the sata drive and plugged it into the pogoplug pro and powered on the pogoplug pro.
What does " ## Error: "dt_bootcmd_usb" not defined" mean? I'm not sure what I'm doing wrong. Also I didn't mean to steal the thread. Should I post in another post?
Here is the bootup output from the serial console:
U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12) Boot device: NAND Attempting to set PLLA to 850 MHz ... plla_ctrl0 : 0000020a plla_ctrl1 : 00330000 plla_ctrl2 : 0065008b plla_ctrl3 : 000000f1 PLLA Set U-Boot 2015.10-tld-1 (Nov 21 2015 - 01:17:59 -0800) OXNAS OX820 DRAM: 128 MiB NAND: 128 MiB In: serial Out: serial Err: serial Net: dwmac.40400000 Hit any key to stop autoboot: 0 ## Error: "dt_bootcmd_usb" not defined Loading from nand0, offset 0x200000 Image Name: Linux-2.6.31.6_SMP_820 Created: 2010-11-30 20:05:12 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2260628 Bytes = 2.2 MiB Load Address: 60008000 Entry Point: 60008000 ## Booting kernel from Legacy Image at 60500000 ... Image Name: Linux-2.6.31.6_SMP_820 Created: 2010-11-30 20:05:12 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2260628 Bytes = 2.2 MiB Load Address: 60008000 Entry Point: 60008000 Verifying Checksum ... OK Loading Kernel Image ... OK Starting kernel ... Uncompressing Linux................................................................................................................................... done, booting the kernel. [ 0.000000] Linux version 2.6.31.6_SMP_820 (bdietrich@brad-ux) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #71 SMP Tue Nov 30 12:05:09 PST 2010 [ 0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5387f [ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache [ 0.000000] Machine: Oxsemi NAS [ 0.000000] 1 memory region [ 0.000000] Ignoring unrecognised tag 0x00000000 [ 0.000000] Memory policy: ECC disabled, Data cache writealloc [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [ 0.000000] Kernel command line: root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M [ 0.000000] PID hash table entries: 512 (order: 9, 2048 bytes) [ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [ 0.000000] Memory: 128MB = 128MB total [ 0.000000] Memory: 125468KB available (3724K code, 275K data, 124K init, 0K highmem) [ 0.000000] Hierarchical RCU implementation. [ 0.000000] NR_IRQS:96 [ 0.000000] OX820_RPS_init_irq: interrupts 64 to 96 [ 0.010000] Console: colour dummy device 80x30 [ 0.010000] console [ttyS0] enabled [ 0.020000] Calibrating delay loop... 339.14 BogoMIPS (lpj=1695744) [ 0.240000] Security Framework initialized [ 0.240000] Mount-cache hash table entries: 512 [ 0.250000] CPU: Testing write buffer coherency: ok [ 0.250000] Calibrating local timer... 425.50MHz. [ 0.320000] CPU1: Booted secondary processor [ 0.420000] Calibrating delay loop... 339.14 BogoMIPS (lpj=1695744) [ 0.630000] Brought up 2 CPUs [ 0.640000] SMP: Total of 2 processors activated (678.29 BogoMIPS). [ 0.650000] NET: Registered protocol family 16 [ 0.650000] Number of DMA channels = 4, version = 4 [ 0.660000] Reserving a DMA channel for DirectRAID [ 0.660000] Allocating 389 SRAM generic DMA descriptors [ 1.170000] PCIeA version/deviceID 082510b5 [ 1.170000] PCIeB version/deviceID 082510b5 [ 4.200000] ox820_pci_preinit() PCIEB link up timeout (00001814) [ 4.200000] ox820_pcie_setup_resources() Enabling PCIe Pre-Emphasis [ 4.210000] ox820_pciea_setup_resources() resource c781b2c0 [ 4.210000] ox820_pciea_setup_resources() io: 0x4be00000 - 0x4befffff [ 4.220000] ox820_pciea_setup_resources() non-pre: 0x48000000 - 0x49ffffff [ 4.230000] ox820_pciea_setup_resources() pre: 0x4a000000 - 0x4bdfffff [ 4.230000] PCI: bus0: Fast back to back transfers disabled [ 4.240000] PCI: bus1: Fast back to back transfers enabled [ 4.250000] bio: create slab <bio-0> at 0 [ 4.260000] SCSI subsystem initialized [ 4.290000] NET: Registered protocol family 2 [ 4.290000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes) [ 4.300000] Switched to NOHz mode on CPU #0 [ 4.300000] TCP established hash table entries: 4096 (order: 3, 32768 bytes) [ 4.300000] Switched to NOHz mode on CPU #1 [ 4.310000] TCP bind hash table entries: 4096 (order: 3, 32768 bytes) [ 4.320000] TCP: Hash tables configured (established 4096 bind 4096) [ 4.320000] TCP reno registered [ 4.330000] NET: Registered protocol family 1 [ 4.330000] Create fragment cache [ 4.340000] fuse init (API version 7.12) [ 4.340000] msgmni has been set to 245 [ 4.350000] alg: No test for stdrng (krng) [ 4.350000] io scheduler noop registered [ 4.360000] io scheduler anticipatory registered [ 4.360000] io scheduler deadline registered [ 4.370000] io scheduler cfq registered (default) [ 4.390000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 4.390000] serial8250: ttyS0 at MMIO 0x44200000 (irq = 55) is a 16550A [ 4.410000] brd: module loaded [ 4.420000] loop: module loaded [ 4.420000] ox820sata: OX820 sata core. [ 4.420000] scsi0 : oxnassata [ 4.430000] scsi1 : oxnassata [ 4.430000] ata1: SATA max UDMA/133 irq 50 [ 4.440000] ata2: SATA max UDMA/133 irq 50 [ 4.440000] ox820sata: reseting SATA core [ 4.960000] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 4.960000] ata1.00: ATA-8: FUJITSU MHY2160BH, 0085000B, max UDMA/100 [ 4.970000] ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 4.980000] ata1.00: configured for UDMA/100 [ 4.980000] ox820sata: reseting SATA core [ 5.690000] ata2: SATA link down (SStatus 0 SControl 300) [ 5.690000] scsi 0:0:0:0: Direct-Access ATA FUJITSU MHY2160B 0085 PQ: 0 ANSI: 5 [ 5.700000] sd 0:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB) [ 5.710000] sd 0:0:0:0: [sda] Write Protect is off [ 5.710000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 5.720000] tun: Universal TUN/TAP device driver, 1.6 [ 5.720000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> [ 5.720000] NAND: Page read time 40ms [ 5.720000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit) [ 5.720000] Scanning device for bad blocks [ 5.780000] Creating 2 MTD partitions on "NAND 128MiB 3,3V 8-bit": [ 5.790000] 0x000000000000-0x000000e00000 : "boot" [ 5.790000] sda: [ 5.800000] 0x000000e00000-0x000008000000 : "rootfs" [ 5.800000] UBI: attaching mtd2 to ubi0 [ 5.810000] UBI: physical eraseblock size: 131072 bytes (128 KiB) [ 5.810000] UBI: logical eraseblock size: 129024 bytes [ 5.820000] UBI: smallest flash I/O unit: 2048 [ 5.820000] UBI: sub-page size: 512 [ 5.830000] UBI: VID header offset: 512 (aligned 512) [ 5.830000] UBI: data offset: 2048 [ 6.010000] sda1 [ 6.190000] UBI: attached mtd2 to ubi0 [ 6.190000] UBI: MTD device name: "rootfs" [ 6.200000] UBI: MTD device size: 114 MiB [ 6.200000] UBI: number of good PEBs: 912 [ 6.210000] UBI: number of bad PEBs: 0 [ 6.210000] UBI: max. allowed volumes: 128 [ 6.210000] UBI: wear-leveling threshold: 4096 [ 6.220000] UBI: number of internal volumes: 1 [ 6.220000] UBI: number of user volumes: 1 [ 6.230000] UBI: available PEBs: 0 [ 6.230000] UBI: total number of reserved PEBs: 912 [ 6.240000] UBI: number of PEBs reserved for bad PEB handling: 9 [ 6.240000] UBI: max/mean erase counter: 2/0 [ 6.250000] UBI: image sequence number: 0 [ 6.250000] UBI: background thread "ubi_bgt0d" started, PID 285 [ 6.260000] mice: PS/2 mouse device common for all mice [ 6.260000] TCP cubic registered [ 6.270000] NET: Registered protocol family 10 [ 6.270000] NET: Registered protocol family 17 [ 6.280000] RPC: Registered udp transport module. [ 6.280000] sd 0:0:0:0: [sda] Attached SCSI disk [ 6.290000] RPC: Registered tcp transport module. [ 6.390000] UBIFS: recovery needed [ 6.520000] UBIFS: recovery completed [ 6.530000] UBIFS: mounted UBI device 0, volume 0, name "rootfs" [ 6.530000] UBIFS: file system size: 114573312 bytes (111888 KiB, 109 MiB, 888 LEBs) [ 6.540000] UBIFS: journal size: 9033728 bytes (8822 KiB, 8 MiB, 71 LEBs) [ 6.550000] UBIFS: media format: w4/r0 (latest is w4/r0) [ 6.550000] UBIFS: default compressor: zlib [ 6.560000] UBIFS: reserved for root: 0 bytes (0 KiB) [ 6.560000] VFS: Mounted root (ubifs filesystem) on device 0:10. [ 6.570000] Freeing init memory: 124K Too many bit errors @ 0xa0000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa0800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa1000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa1800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa2000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa2800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa3000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa3800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa4000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa4800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa5000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa5800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa6000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa6800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa7000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa7800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa8000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa8800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa9000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa9800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xaa000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xaa800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xab000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xab800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xac000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xac800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xad000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xad800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xae000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xae800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xaf000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xaf800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb0000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb0800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb1000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb1800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb2000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb2800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb3000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb3800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb4000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb4800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb5000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb5800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb6000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb6800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb7000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb7800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb8000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb8800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb9000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb9800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xba000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xba800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbb000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbb800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbc000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbc800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbd000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbd800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbe000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbe800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbf000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbf800 -- Can't correct! PAGE DATA: OOB: -- Invalid CRC32 on parameters: 0x6e206369 != 0x27033e1f /etc/init.d/rcS: /tmp/ethaddr: line 1: 00000380:: not found /etc/init.d/rcS: /tmp/ethaddr: line 3: syntax error: EOF in backquote substitution
-Hachigo
Edited 1 time(s). Last edit at 03/05/2016 05:45PM by hachigo.
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS March 05, 2016 05:56PM |
Admin Registered: 13 years ago Posts: 18,997 |
hachigo,
> What does " ## Error: "dt_bootcmd_usb" not
> defined" mean? I'm not sure what I'm doing wrong.
> Also I didn't mean to steal the thread. Should I
> post in another post?
Ah! I see, I've missed that :). This is what was wrong.
In serial console:
and then
After booting into Debian, to make it permanent:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> What does " ## Error: "dt_bootcmd_usb" not
> defined" mean? I'm not sure what I'm doing wrong.
> Also I didn't mean to steal the thread. Should I
> post in another post?
Ah! I see, I've missed that :). This is what was wrong.
In serial console:
setenv bootcmd 'run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_stock; reset'
and then
boot
After booting into Debian, to make it permanent:
fw_setenv bootcmd 'run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_stock; reset'
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS March 05, 2016 06:06PM |
Registered: 10 years ago Posts: 26 |
hi bodhi,
Success!!! thank you so much! This almost makes up for the exam I bombed this past Friday...
How did you learn how to do all this stuff? lol. I gotta a lot of learning to do.
If you don't mind, I have another question that got me into this mess of trying to boot from sata in the first place.
I was wondering if there was a Rescue System like Rescue v.2.8.2 for the pro. My pogo pro doesn't boot into the stock pogo OS anymore. Is there a replacement that has more features than the stock I could just flash over? Thanks again.
-hachigo
Success!!! thank you so much! This almost makes up for the exam I bombed this past Friday...
How did you learn how to do all this stuff? lol. I gotta a lot of learning to do.
If you don't mind, I have another question that got me into this mess of trying to boot from sata in the first place.
I was wondering if there was a Rescue System like Rescue v.2.8.2 for the pro. My pogo pro doesn't boot into the stock pogo OS anymore. Is there a replacement that has more features than the stock I could just flash over? Thanks again.
-hachigo
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS March 05, 2016 06:24PM |
Admin Registered: 13 years ago Posts: 18,997 |
hachigo,
> I was wondering if there was a Rescue System like
> Rescue v.2.8.2 for the pro. My pogo pro doesn't
> boot into the stock pogo OS anymore. Is there a
> replacement that has more features than the stock
> I could just flash over? Thanks again.
It did. That was the purpose of this thread. You see a lot of errors during boot, but it did not prevent the stock kernel running.
Shutdown, pull the USB drive out, power up, watch the stock kernel booting, and you should see the stock OS command line prompt like you did before.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I was wondering if there was a Rescue System like
> Rescue v.2.8.2 for the pro. My pogo pro doesn't
> boot into the stock pogo OS anymore. Is there a
> replacement that has more features than the stock
> I could just flash over? Thanks again.
It did. That was the purpose of this thread. You see a lot of errors during boot, but it did not prevent the stock kernel running.
[ 0.000000] Linux version 2.6.31.6_SMP_820 (bdietrich@brad-ux) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #71 SMP Tue Nov 30 12:05:09 PST 2010 [ 0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5387f [ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache [ 0.000000] Machine: Oxsemi NAS
Shutdown, pull the USB drive out, power up, watch the stock kernel booting, and you should see the stock OS command line prompt like you did before.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS March 05, 2016 06:35PM |
Registered: 10 years ago Posts: 26 |
bodhi,
Oh ok. Before I was able to ssh into it and also use the netconsole, but now I can't. I guess now I can only get into the stock OS with serial cable?
I was also wondering if installing debian to the nand is still viable option. I came across this https://github.com/ingmar-k/Pogoplug_V3_Emdebian_Debian while browsing other threads on this site and google.
I'd like to be able to ssh into my bare pogoplug pro with no USB or harddrives attached.
thanks,
hachigo
Oh ok. Before I was able to ssh into it and also use the netconsole, but now I can't. I guess now I can only get into the stock OS with serial cable?
I was also wondering if installing debian to the nand is still viable option. I came across this https://github.com/ingmar-k/Pogoplug_V3_Emdebian_Debian while browsing other threads on this site and google.
I'd like to be able to ssh into my bare pogoplug pro with no USB or harddrives attached.
thanks,
hachigo
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS March 05, 2016 06:47PM |
Admin Registered: 13 years ago Posts: 18,997 |
hachigo,
> Oh ok. Before I was able to ssh into it and also
> use the netconsole, but now I can't. I guess now I
> can only get into the stock OS with serial cable?
>
Not true. It only means that your setup has some errors. Check the error about ethaddr above at the end of your log. If the installation in the 1st post was OK, then you can ssh into Pogo OS. Again, that's the goal, you must be able to ssh into it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Oh ok. Before I was able to ssh into it and also
> use the netconsole, but now I can't. I guess now I
> can only get into the stock OS with serial cable?
>
Not true. It only means that your setup has some errors. Check the error about ethaddr above at the end of your log. If the installation in the 1st post was OK, then you can ssh into Pogo OS. Again, that's the goal, you must be able to ssh into it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS March 05, 2016 07:13PM |
Registered: 10 years ago Posts: 26 |
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS April 03, 2016 01:03PM |
Registered: 8 years ago Posts: 17 |
I have installed the rescue system on my Pogoplug v3 and it works as advertised. But in rescue mode, the ethernet mac address is set to 00:30:E0:00:00:00 which is different from the mac address on the foot. Not a big problem, but it's the same on another v3 and if they were both in rescue mode, there would be a mac conflict.
Is there a way to set the rescue ethernet mac address to the address on the foot of the device? I have it set correctly in printenv. Thanks.
Is there a way to set the rescue ethernet mac address to the address on the foot of the device? I have it set correctly in printenv. Thanks.
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS April 03, 2016 03:12PM |
Registered: 8 years ago Posts: 17 |
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS April 03, 2016 03:25PM |
Admin Registered: 13 years ago Posts: 18,997 |
dexter Wrote:
-------------------------------------------------------
> I figured it out.. It's set using the mac_adr
> variable under bootcmd_stock.
Thanks dexter, did you change the bootcmd_stock to set that?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> I figured it out.. It's set using the mac_adr
> variable under bootcmd_stock.
Thanks dexter, did you change the bootcmd_stock to set that?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS April 03, 2016 10:12PM |
Registered: 8 years ago Posts: 17 |
>> I figured it out.. It's set using the mac_adr
>> variable under bootcmd_stock.
>Thanks dexter, did you change the bootcmd_stock to set that?
>-bodhi
Yes, I did change bootcmd_stock to reflect the correct mac address, but it had no effect after a reboot. The HWaddr for eth0 reported by ifconfig is still 00:30:E0:00:00:00 which is almost but not exactly the same as the mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 in the original bootcmd_stock earlier in this thread.
The "wrong" mac_adr does match the bootargs line in blparam.txt saved from before the Uboot upgrade:
bootargs=root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M poweroutage=yes
I have tried altering this part of /etc/init.d/rcS
if [ "x$ethaddr" != "x" ]; then
ifconfig eth0 hw ether $ethaddr
else
if [ "x$ceethhwaddr" != "x" ]; then
ifconfig eth0 hw ether $ceethhwaddr
but no joy. Could this be modified to fix?
>> variable under bootcmd_stock.
>Thanks dexter, did you change the bootcmd_stock to set that?
>-bodhi
Yes, I did change bootcmd_stock to reflect the correct mac address, but it had no effect after a reboot. The HWaddr for eth0 reported by ifconfig is still 00:30:E0:00:00:00 which is almost but not exactly the same as the mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 in the original bootcmd_stock earlier in this thread.
The "wrong" mac_adr does match the bootargs line in blparam.txt saved from before the Uboot upgrade:
bootargs=root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M poweroutage=yes
I have tried altering this part of /etc/init.d/rcS
if [ "x$ethaddr" != "x" ]; then
ifconfig eth0 hw ether $ethaddr
else
if [ "x$ceethhwaddr" != "x" ]; then
ifconfig eth0 hw ether $ceethhwaddr
but no joy. Could this be modified to fix?
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS April 07, 2016 01:18PM |
Admin Registered: 13 years ago Posts: 18,997 |
dexter Wrote:
-------------------------------------------------------
> >> I figured it out.. It's set using the mac_adr
> >> variable under bootcmd_stock.
>
> >Thanks dexter, did you change the bootcmd_stock
> to set that?
>
> >-bodhi
>
> Yes, I did change bootcmd_stock to reflect the
> correct mac address, but it had no effect after a
> reboot. The HWaddr for eth0 reported by ifconfig
> is still 00:30:E0:00:00:00 which is almost but not
> exactly the same as the
> mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 in the
> original bootcmd_stock earlier in this thread.
>
> The "wrong" mac_adr does match the bootargs line
> in blparam.txt saved from before the Uboot
> upgrade:
> bootargs=root=ubi0:rootfs ubi.mtd=2,512
> rootfstype=ubifs console=ttyS0,115200 elevator=cfq
> mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M
> poweroutage=yes
>
> I have tried altering this part of
> /etc/init.d/rcS
>
> if [ "x$ethaddr" != "x" ]; then
> ifconfig eth0 hw ether $ethaddr
> else
> if [ "x$ceethhwaddr" != "x" ]; then
> ifconfig eth0 hw ether $ceethhwaddr
>
> but no joy. Could this be modified to fix?
I'm not sure I remember how with stock OS.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> >> I figured it out.. It's set using the mac_adr
> >> variable under bootcmd_stock.
>
> >Thanks dexter, did you change the bootcmd_stock
> to set that?
>
> >-bodhi
>
> Yes, I did change bootcmd_stock to reflect the
> correct mac address, but it had no effect after a
> reboot. The HWaddr for eth0 reported by ifconfig
> is still 00:30:E0:00:00:00 which is almost but not
> exactly the same as the
> mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 in the
> original bootcmd_stock earlier in this thread.
>
> The "wrong" mac_adr does match the bootargs line
> in blparam.txt saved from before the Uboot
> upgrade:
> bootargs=root=ubi0:rootfs ubi.mtd=2,512
> rootfstype=ubifs console=ttyS0,115200 elevator=cfq
> mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M
> poweroutage=yes
>
> I have tried altering this part of
> /etc/init.d/rcS
>
> if [ "x$ethaddr" != "x" ]; then
> ifconfig eth0 hw ether $ethaddr
> else
> if [ "x$ceethhwaddr" != "x" ]; then
> ifconfig eth0 hw ether $ceethhwaddr
>
> but no joy. Could this be modified to fix?
I'm not sure I remember how with stock OS.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS May 13, 2016 04:21AM |
Admin Registered: 13 years ago Posts: 18,997 |
I've updated the instruction (step 2) to get rid of the NAND checksum errors during stock OS booting.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS February 04, 2017 09:03PM |
Registered: 7 years ago Posts: 12 |
I've followed these instructions to create a rescue system on both of my PogoPlug Pros -- works great!
I'm going to start fiddling with a couple PogoPlug Mobiles next week and I see that the rescue systems for Kirkwood involve replacing the stock OS. Is there a reason for that? I'm sure it's fun to do, and I get that. But is there any reason I couldn't use a similar approach to the Oxnas/PogoV3?
I figure it will work as long as the Kirkwood u-boot supports the same commands for scanning external storage and defaulting back to booting NVRAM. I'll do some more reading on the different rescue systems offered in the forum, maybe they're so cool I won't be able to resist using them ;)
I'm going to start fiddling with a couple PogoPlug Mobiles next week and I see that the rescue systems for Kirkwood involve replacing the stock OS. Is there a reason for that? I'm sure it's fun to do, and I get that. But is there any reason I couldn't use a similar approach to the Oxnas/PogoV3?
I figure it will work as long as the Kirkwood u-boot supports the same commands for scanning external storage and defaulting back to booting NVRAM. I'll do some more reading on the different rescue systems offered in the forum, maybe they're so cool I won't be able to resist using them ;)
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS February 07, 2017 04:42AM |
Admin Registered: 13 years ago Posts: 18,997 |
GeekSmith,
> I'm going to start fiddling with a couple PogoPlug
> Mobiles next week and I see that the rescue system
> s for Kirkwood involve replacing the stock OS. Is
> there a reason for that? I'm sure it's fun to do,
> and I get that. But is there any reason I couldn't
> use a similar approach to the Oxnas/PogoV3?
Yes, you could. The reason I did not bother creating envs setup for Kirkwood because Jeff's Rescue System V2 works for the small Kirkwood plugs already (Pogo V4, Mobile, E02, Dockstar, GoFlex Home/Net). And davygravy's V2.8 also supposed to work the same way.
And later, bobafetthotmail also created a OpenWrt rescue system (beta version).
In fact, I've also built a new rescue system with a modern kernel as an exercise, but did not release it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I'm going to start fiddling with a couple PogoPlug
> Mobiles next week and I see that the rescue system
> s for Kirkwood involve replacing the stock OS. Is
> there a reason for that? I'm sure it's fun to do,
> and I get that. But is there any reason I couldn't
> use a similar approach to the Oxnas/PogoV3?
Yes, you could. The reason I did not bother creating envs setup for Kirkwood because Jeff's Rescue System V2 works for the small Kirkwood plugs already (Pogo V4, Mobile, E02, Dockstar, GoFlex Home/Net). And davygravy's V2.8 also supposed to work the same way.
And later, bobafetthotmail also created a OpenWrt rescue system (beta version).
In fact, I've also built a new rescue system with a modern kernel as an exercise, but did not release it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS July 21, 2017 10:34AM |
Registered: 8 years ago Posts: 25 |
Hmm,
how can i write the entire line:
---------
---------
as ONE piece ?
In debian as well in the uboot itself i am dropped to a ">" shell when using copy and paste ..
BR
dietgert
Edited 2 time(s). Last edit at 07/21/2017 02:09PM by bodhi.
how can i write the entire line:
---------
fw_setenv bootcmd_stock 'setenv autoload n; setenv bootargs_stock "root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M"; setenv poweroutage yes; setenv boot "bootm 60500000"; setenv bootcmd_stock_fw "run set_bootargs_stock; run boot_nand"; setenv boot bootm 60500000; setenv boot_nand "run load_nand boot || run load_nand2 boot"; setenv kernflmode s; setenv load_nand2 "nboot 60500000 0 800000"; setenv load_nand "nboot 60500000 0 200000"; setenv set_bootargs_stock "setenv bootargs $bootargs_stock"; setenv mainlinelinux no; run bootcmd_stock_fw'
---------
as ONE piece ?
In debian as well in the uboot itself i am dropped to a ">" shell when using copy and paste ..
BR
dietgert
Edited 2 time(s). Last edit at 07/21/2017 02:09PM by bodhi.
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS July 21, 2017 02:12PM |
Admin Registered: 13 years ago Posts: 18,997 |
dietgert,
I've put that in a code tag so we can see if it is one line.
You can copy and paste in Debian. And then verify
In serial console, the same thing.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I've put that in a code tag so we can see if it is one line.
You can copy and paste in Debian. And then verify
fw_setenv bootcmd_stock 'setenv autoload n; setenv bootargs_stock "root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M"; setenv poweroutage yes; setenv boot "bootm 60500000"; setenv bootcmd_stock_fw "run set_bootargs_stock; run boot_nand"; setenv boot bootm 60500000; setenv boot_nand "run load_nand boot || run load_nand2 boot"; setenv kernflmode s; setenv load_nand2 "nboot 60500000 0 800000"; setenv load_nand "nboot 60500000 0 200000"; setenv set_bootargs_stock "setenv bootargs $bootargs_stock"; setenv mainlinelinux no; run bootcmd_stock_fw'
fw_printenv bootcmd_stock
In serial console, the same thing.
setenv bootcmd_stock 'setenv autoload n; setenv bootargs_stock "root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M"; setenv poweroutage yes; setenv boot "bootm 60500000"; setenv bootcmd_stock_fw "run set_bootargs_stock; run boot_nand"; setenv boot bootm 60500000; setenv boot_nand "run load_nand boot || run load_nand2 boot"; setenv kernflmode s; setenv load_nand2 "nboot 60500000 0 800000"; setenv load_nand "nboot 60500000 0 200000"; setenv set_bootargs_stock "setenv bootargs $bootargs_stock"; setenv mainlinelinux no; run bootcmd_stock_fw'
printenv bootcmd_stock
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS July 22, 2017 03:52AM |
Registered: 8 years ago Posts: 25 |
Hello Bodhi,
Thank You, it was a problem of picocom on my linux-box, after increasing backscroll-pages to 4000
it worked. I have a STG-212 box.
Changed addresses, received an error (see below).
However, when using a "run bootcmd_stock" in U-Boot, the stock system boots correctly, so this entry seems ok.
Where could the problem be located ?
BR
dietgert
Thank You, it was a problem of picocom on my linux-box, after increasing backscroll-pages to 4000
it worked. I have a STG-212 box.
Changed addresses, received an error (see below).
However, when using a "run bootcmd_stock" in U-Boot, the stock system boots correctly, so this entry seems ok.
Where could the problem be located ?
BR
dietgert
U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
Boot device: NAND
Attempting to set PLLA to 850 MHz ...
plla_ctrl0 : 0000020a
plla_ctrl1 : 00330000
plla_ctrl2 : 0065008b
plla_ctrl3 : 000000f1
PLLA Set
U-Boot 2015.10-tld-1 (Nov 21 2015 - 01:17:59 -0800)
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> env print
autoload=no
baudrate=115200
bootargs=console=ttyS0,115200n8
bootcmd=run bootcmd_uenv; run dt_bootcmd_usb; run bootcmd_stock; reset
bootcmd_stock=setenv autoload n; setenv bootargs_stock "root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M"; setenv poweroutage yes; setenv boot "bootm 61000000"; setenv bootcmd_stock_fw "run set_bootargs_stock; run boot_nand"; setenv boot bootm 61000000; setenv boot_nand "run load_nand boot || run load_nand2 boot"; setenv kernflmode s; setenv load_nand2 "nboot 61000000 0 440000"; setenv load_nand "nboot 61000000 0 440000"; setenv set_bootargs_stock "setenv bootargs $bootargs_stock"; setenv mainlinelinux no; run bootcmd_stock_fw
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=3
console=console=ttyS0,115200n8
devices=usb ide
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
dt_load_dtb=ext2load 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
dtb_file=/boot/dts/ox820-pogoplug-stg212.dtb
ethact=dwmac.40400000
ethaddr=5e:2b:15:71:ec:b6
if_netconsole=ping $serverip
ipaddr=192.168.0.222
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
preboot_nc=run if_netconsole start_netconsole
serverip=192.168.0.220
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version
stderr=serial
stdin=serial
stdout=serial
uenv_import=echo importing envs ...; env import -t 0x60500000
uenv_init_devices=setenv init_usb "usb start"; setenv init_ide "ide reset"; setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x60500000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read; fi; else if $devtype part $disknum; then run uenv_read; fi; fi
uimage_addr=0x60500000
uinitrd_addr=0x60e00000
usb_device=0:1
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
Environment size: 2672/131068 bytes
OX820>
OX820> reset
resetting ...
U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
Boot device: NAND
Attempting to set PLLA to 850 MHz ...
plla_ctrl0 : 0000020a
plla_ctrl1 : 00330000
plla_ctrl2 : 0065008b
plla_ctrl3 : 000000f1
PLLA Set
U-Boot 2015.10-tld-1 (Nov 21 2015 - 01:17:59 -0800)
OXNAS OX820
DRAM: 128 MiB
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: dwmac.40400000
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: SATA PHY not ready for device 0
ide_preinit failed
no USB devices available
no IDE devices available
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
resetting ...
OX820> run bootcmd_stock Loading from nand0, offset 0x440000 Image Name: Linux-2.6.31.14_SMP_820 Created: 2012-07-13 12:14:49 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 5242768 Bytes = 5 MiB Load Address: 60008000 Entry Point: 60008000 ## Booting kernel from Legacy Image at 61000000 ... Image Name: Linux-2.6.31.14_SMP_820 Created: 2012-07-13 12:14:49 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 5242768 Bytes = 5 MiB Load Address: 60008000 Entry Point: 60008000 Verifying Checksum ... OK Loading Kernel Image ... OK Starting kernel ... Uncompressing Linux........................................................................................................................................................................................................................................................... done, booting the kernel. Linux version 2.6.31.14_SMP_820 (root@Neo) (gcc version 4.3.2 (crosstool-NG-1.8.0) ) #2 SMP Fri Jul 13 20:14:45 CST 2012 CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5387f CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: Oxsemi NAS .......
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS July 22, 2017 04:04AM |
Admin Registered: 13 years ago Posts: 18,997 |
dietgert,
This was the problem:
There are too many "reset". The reset should only be in the bootcmd. So interrupt serial console and:
If this booted into stock OK then reboot. Interrupt serial console again and save it permanently:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
This was the problem:
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset bootcmd=run bootcmd_uenv; run dt_bootcmd_usb; run bootcmd_stock; reset
There are too many "reset". The reset should only be in the bootcmd. So interrupt serial console and:
setenv dt_bootcmd_usb 'usb start; run dt_usb_bootcmd; usb stop'and then
boot
If this booted into stock OK then reboot. Interrupt serial console again and save it permanently:
setenv dt_bootcmd_usb 'usb start; run dt_usb_bootcmd; usb stop' saveenvAfter this it will work automatically.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS July 24, 2017 01:50PM |
Registered: 8 years ago Posts: 25 |
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS July 24, 2017 11:19PM |
Admin Registered: 13 years ago Posts: 18,997 |
dietgert Wrote:
-------------------------------------------------------
> Thank You Bodhi, (once again)
>
> that was it.
> Everything is working well now!
>
> BR
> dietgert
Cool!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Thank You Bodhi, (once again)
>
> that was it.
> Everything is working well now!
>
> BR
> dietgert
Cool!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS September 17, 2017 02:29PM |
Registered: 9 years ago Posts: 6 |
Hello BODHI,
Please Help in reviving my Pogoplug Pro V3 Sata Edition
sometime ago i tried to load Debian on it,
and i think i did flashed Uboot Debian 2013.10
without usb or sata disk
it stuck with green solid LED and serial console message "## Error: "dt_bootcmd_usb" not defined"
i converted a USB Pendrive to EXT3 format and extracted Debian 3.17 rootfs on it
same did on Sata HDD but no luck , No changes in serial console messages.
please provide solution to this problem
Please Help in reviving my Pogoplug Pro V3 Sata Edition
sometime ago i tried to load Debian on it,
and i think i did flashed Uboot Debian 2013.10
without usb or sata disk
it stuck with green solid LED and serial console message "## Error: "dt_bootcmd_usb" not defined"
i converted a USB Pendrive to EXT3 format and extracted Debian 3.17 rootfs on it
same did on Sata HDD but no luck , No changes in serial console messages.
please provide solution to this problem
U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12) Boot device: NAND Attempting to set PLLA to 850 MHz ... plla_ctrl0 : 0000020a plla_ctrl1 : 00330000 plla_ctrl2 : 0065008b plla_ctrl3 : 000000f1 PLLA Set 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 Waiting for PHY auto negotiation to complete.... TIMEOUT! ENET Speed is 10 Mbps - HALF duplex connection Using mii0 device ping failed; host 192.168.1.2 is not alive Hit any key to stop autoboot: 0 ## Error: "dt_bootcmd_usb" not defined
OX820> printenv autoload=no baudrate=115200 bootargs=console=ttyS0,115200 root=/dev/sda1 rootdelay=10 bootcmd=run dt_bootcmd_usb bootdelay=10 console=console=ttyS0,115200n8 dt_bootm=bootm 0x60500000 0x60e00000 0x62c00000 dt_load_dtb=ext2load usb 0:1 0x62c00000 /boot/dts/ox820-pogoplug-pro.dtb dt_load_initrd=ext2load usb 0:1 0x60e00000 /boot/uInitrd dt_load_uimage=ext2load usb 0:1 0x60500000 /boot/uImage dt_usb_boot=run dt_load_uimage dt_usb_bootcmd=run usb_set_bootargs dtb_addr=0x62c00000 ethact=mii0 ethaddr=00:25:31:01:66:5F fileaddr=60000000 filesize=20000 if_netconsole=ping 192.168.1.2 ipaddr=192.168.1.10 iserverip=192.168.1.2 keypressed=1 mtdids=nand0=41000000.nand mtdparts=mtdparts=41000000.nand:14m(boot),-(data) netcon=echo switch to net console;setenv stderr nc;setenv stdin nc;setenv stdout nc;echo switch to net console preboot=run preboot_nc preboot_nc=run if_netconsole start_netconsole safeboot=setexpr.b keypressed '*44200005' '&' 1;if test $keypressed = 0;then run netcon;fi serialcon=echo switch to serial console;setenv stderr serial;setenv stdin serial;setenv stdout serial;echo switch to serial console serverip=192.168.1.2 stderr=serial stdin=serial stdout=serial uimage_addr=0x60500000 uinitrd_addr=0x60e00000 usb_boot=mw 0x800000 0 1 usb_bootcmd=run usb_init usb_device=0:1 usb_init=run usb_scan usb_root=/dev/sda1 usb_scan=usb_scan_done=0 usb_scan_1=usb=0:1 dev=sda1 usb_scan_2=usb=1:1 dev=sdb1 usb_scan_3=usb=2:1 dev=sdc1 usb_scan_4=usb=3:1 dev=sdd1 usb_scan_list=1 2 3 4 usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 Environment size: 1664/131068 bytes OX820>
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS September 17, 2017 04:57PM |
Admin Registered: 13 years ago Posts: 18,997 |
pritamcharan,
Your u-boot envs were quite messed up.
SInce you are running my older version u-boot, I need to find that set of default envs and post the correction. Will do that later today.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Your u-boot envs were quite messed up.
SInce you are running my older version u-boot, I need to find that set of default envs and post the correction. Will do that later today.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS September 18, 2017 12:49AM |
Admin Registered: 13 years ago Posts: 18,997 |
Power up, interrupt serial console and
Please post the entire serial console log here, if it is not booting.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
setenv dt_usb_boot 'run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm' setenv dt_usb_bootcmd 'run usb_set_bootargs; run dt_usb_boot' setenv dt_bootcmd_usb 'usb start; run dt_usb_bootcmd; usb stop; reset' printenv boot
Please post the entire serial console log here, if it is not booting.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS September 18, 2017 03:11AM |
Registered: 9 years ago Posts: 6 |
Hello Bodhi, It boots in Debian .
but after restart the changes doesnot stick.
OX820> setenv dt_usb_boot 'run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm'
OX820> setenv dt_usb_bootcmd 'run usb_set_bootargs; run dt_usb_boot'
OX820> setenv dt_bootcmd_usb 'usb start; run dt_usb_bootcmd; usb stop; reset'
OX820> printenv
OX820> boot
but after restart the changes doesnot stick.
OX820> setenv dt_usb_boot 'run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm'
OX820> setenv dt_usb_bootcmd 'run usb_set_bootargs; run dt_usb_boot'
OX820> setenv dt_bootcmd_usb 'usb start; run dt_usb_bootcmd; usb stop; reset'
OX820> printenv
autoload=no baudrate=115200 bootargs=console=ttyS0,115200 root=/dev/sda1 rootdelay=10 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 0x60500000 0x60e00000 0x62c00000 dt_load_dtb=ext2load usb 0:1 0x62c00000 /boot/dts/ox820-pogoplug-pro.dtb dt_load_initrd=ext2load usb 0:1 0x60e00000 /boot/uInitrd dt_load_uimage=ext2load usb 0:1 0x60500000 /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:01:66:5F fileaddr=60000000 filesize=20000 if_netconsole=ping 192.168.1.2 ipaddr=192.168.1.10 iserverip=192.168.1.2 keypressed=1 mtdids=nand0=41000000.nand mtdparts=mtdparts=41000000.nand:14m(boot),-(data) netcon=echo switch to net console;setenv stderr nc;setenv stdin nc;setenv stdout nc;echo switch to net console preboot=run preboot_nc preboot_nc=run if_netconsole start_netconsole safeboot=setexpr.b keypressed '*44200005' '&' 1;if test $keypressed = 0;then run netcon;fi serialcon=echo switch to serial console;setenv stderr serial;setenv stdin serial;setenv stdout serial;echo switch to serial console serverip=192.168.1.2 stderr=serial stdin=serial stdout=serial uimage_addr=0x60500000 uinitrd_addr=0x60e00000 usb_boot=mw 0x800000 0 1 usb_bootcmd=run usb_init usb_device=0:1 usb_init=run usb_scan usb_root=/dev/sda1 usb_scan=usb_scan_done=0 usb_scan_1=usb=0:1 dev=sda1 usb_scan_2=usb=1:1 dev=sdb1 usb_scan_3=usb=2:1 dev=sdc1 usb_scan_4=usb=3:1 dev=sdd1 usb_scan_list=1 2 3 4 usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 Environment size: 1796/131068 bytes
OX820> boot
(Re)start USB...
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
4102704 bytes read in 497 ms (7.9 MiB/s)
1953812 bytes read in 333 ms (5.6 MiB/s)
7029 bytes read in 238 ms (28.3 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
Image Name: Linux-3.17.0-oxnas-tld-1
Created: 2014-11-01 7:16:44 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4102640 Bytes = 3.9 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: initramfs-3.17.0-oxnas-tld-1
Created: 2014-11-01 7:18:53 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 1953748 Bytes = 1.9 MiB
Load Address: 60000000
Entry Point: 60000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
Booting using the fdt blob at 0x62c00000
Loading Kernel Image ... OK
Loading Ramdisk to 67c4b000, end 67e27fd4 ... OK
Loading Device Tree to 67c46000, end 67c4ab74 ... OK
Led: GREEN
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.17.0-oxnas-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP PREEMPT Sat Oct 25 15:59:43 PDT 2014
[ 0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5787d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Pogoplug Pro
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] DT missing boot CPU MPIDR[23:0], fall back to default cpu_logical_map
[ 0.000000] Start Ox820 platform
[ 0.000000] PERCPU: Embedded 7 pages/cpu @c7ee3000 s6592 r8192 d13888 u32768
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10
[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Memory: 119844K/131072K available (5686K kernel code, 286K rwdata, 1680K rodata, 174K init, 233K bss, 11228K reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xffe00000 (2048 kB)
[ 0.000000] vmalloc : 0xc8800000 - 0xff000000 ( 872 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc0739db0 (7368 kB)
[ 0.000000] .init : 0xc073a000 - 0xc07659c0 ( 175 kB)
[ 0.000000] .data : 0xc0766000 - 0xc07adb00 ( 287 kB)
[ 0.000000] .bss : 0xc07adb00 - 0xc07e809c ( 234 kB)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:160
[ 0.000017] sched_clock: 24 bits at 390kHz, resolution 2560ns, wraps every 42949670400ns
[ 0.000181] Console: colour dummy device 80x30
[ 0.000209] Calibrating delay loop... 339.14 BogoMIPS (lpj=1695744)
[ 0.050050] pid_max: default: 32768 minimum: 301
[ 0.050216] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.050234] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.051069] Initializing cgroup subsys net_cls
[ 0.051130] CPU: Testing write buffer coherency: ok
[ 0.051520] Setting up static identity map for 0x60567fa0 - 0x60567fd8
[ 0.110446] CPU1: Booted secondary processor
[ 0.170145] Brought up 2 CPUs
[ 0.170165] SMP: Total of 2 processors activated.
[ 0.171105] devtmpfs: initialized
[ 0.174981] prandom: seed boundary self test passed
[ 0.178900] prandom: 100 self tests passed
[ 0.178923] pinctrl core: initialized pinctrl subsystem
[ 0.181672] NET: Registered protocol family 16
[ 0.182192] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.186439] gpio-oxnas 44000000.gpio: at address c8846000
[ 0.186731] gpio-oxnas 44100000.gpio: at address c8848000
[ 0.187279] pinctrl-oxnas pinctrl: initialized OX820 pinctrl driver
[ 0.308416] oxnas-pcie 47c0: PCIe version/deviceID 0x82510b5
[ 0.308495] oxnas-pcie 47c0: link up
[ 0.308728] oxnas-pcie 47c0: PCI host bridge to bus 0000:00
[ 0.308753] pci_bus 0000:00: root bus resource [mem 0x48000000-0x49ffffff]
[ 0.308771] pci_bus 0000:00: root bus resource [mem 0x4a000000-0x4bdfffff pref]
[ 0.308787] pci_bus 0000:00: root bus resource [io 0x4be00000-0x4befffff]
[ 0.308805] pci_bus 0000:00: root bus resource [bus 00-7f]
[ 0.309232] PCI: bus0: Fast back to back transfers disabled
[ 0.309309] pci 0000:00:00.0: BAR 0: assigned [mem 0x48000000-0x4800ffff]
[ 0.309696] vgaarb: loaded
[ 0.310228] SCSI subsystem initialized
[ 0.311134] usbcore: registered new interface driver usbfs
[ 0.311247] usbcore: registered new interface driver hub
[ 0.311452] usbcore: registered new device driver usb
[ 0.311567] pps_core: LinuxPPS API ver. 1 registered
[ 0.311580] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.311644] PTP clock support registered
[ 0.313111] cfg80211: Calling CRDA to update world regulatory domain
[ 0.313566] Switched to clocksource rps_clocksource_timer
[ 0.327639] NET: Registered protocol family 2
[ 0.328768] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.328811] TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
[ 0.328847] TCP: Hash tables configured (established 1024 bind 1024)
[ 0.328934] TCP: reno registered
[ 0.328960] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.328998] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.329290] NET: Registered protocol family 1
[ 0.329766] RPC: Registered named UNIX socket transport module.
[ 0.329784] RPC: Registered udp transport module.
[ 0.329797] RPC: Registered tcp transport module.
[ 0.329807] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.330232] Unpacking initramfs...
[ 0.529843] Freeing initrd memory: 1904K (c7c4b000 - c7e27000)
[ 0.531066] futex hash table entries: 512 (order: 2, 16384 bytes)
[ 0.549319] NFS: Registering the id_resolver key type
[ 0.549383] Key type id_resolver registered
[ 0.549399] Key type id_legacy registered
[ 0.549440] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.549460] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 0.550433] fuse init (API version 7.23)
[ 0.551825] msgmni has been set to 237
[ 0.552355] Key type big_key registered
[ 0.556111] alg: No test for stdrng (krng)
[ 0.626554] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.626585] io scheduler noop registered
[ 0.626608] io scheduler deadline registered
[ 0.626964] io scheduler cfq registered (default)
[ 0.627504] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[ 0.628802] console [ttyS0] disabled
[ 0.628922] 44200000.uart: ttyS0 at MMIO 0x44200000 (irq = 55, base_baud = 390625) is a 16550A
[ 1.180032] console [ttyS0] enabled
[ 1.432238] scsi host0: sata_oxnas
[ 1.485703] ata1: SATA max UDMA/133 irq 50
[ 1.490124] ox820sata: reseting SATA core
[ 1.501163] nand: Could not find valid ONFI parameter page; aborting
[ 1.507527] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[ 1.513889] nand: Hynix NAND 128MiB 3,3V 8-bit
[ 1.518312] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[ 1.523970] Scanning device for bad blocks
[ 1.603548] Bad eraseblock 942 at 0x0000075c0000
[ 1.614645] 2 ofpart partitions found on MTD device 41000000.nand
[ 1.620725] Creating 2 MTD partitions on "41000000.nand":
[ 1.626104] 0x000000000000-0x000000e00000 : "boot"
[ 1.632325] 0x000000e00000-0x000008000000 : "data"
[ 1.639004] stmmaceth 40400000.ethernet: no reset control found
[ 1.644938] stmmac - user ID: 0x12, Synopsys ID: 0x35
[ 1.649960] Ring mode enabled
[ 1.653012] DMA HW capability register supported
[ 1.657515] Enhanced/Alternate descriptors
[ 1.661857] Enabled extended descriptors
[ 1.665840] RX Checksum Offload Engine supported (type 2)
[ 1.671306] TX Checksum insertion supported
[ 1.675548] Wake-Up On Lan supported
[ 1.679185] Enable RX Mitigation via HW Watchdog Timer
[ 1.705569] libphy: stmmac: probed
[ 1.708968] eth0: PHY ID 001cc914 at 0 IRQ POLL (stmmac-0:00) active
[ 1.715343] eth0: PHY ID 001cc914 at 3 IRQ POLL (stmmac-0:03)
[ 1.721228] PPP generic driver version 2.4.2
[ 1.725821] rt2800pci 0000:00:00.0: enabling device (0140 -> 0142)
[ 1.732200] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3090, rev 3213 detected
[ 1.743431] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0005 detected
[ 1.752363] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.758873] ehci-pci: EHCI PCI platform driver
[ 1.763735] oxnas-ehci 40200100.ehci: EHCI Host Controller
[ 1.769236] oxnas-ehci 40200100.ehci: new USB bus registered, assigned bus number 1
[ 1.777016] oxnas-ehci 40200100.ehci: irq 39, io mem 0x40200100
[ 1.800555] oxnas-ehci 40200100.ehci: USB 2.0 started, EHCI 1.00
[ 1.806801] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.813585] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.820820] usb usb1: Product: EHCI Host Controller
[ 1.825676] usb usb1: Manufacturer: Linux 3.17.0-oxnas-tld-1 ehci_hcd
[ 1.832099] usb usb1: SerialNumber: 40200100.ehci
[ 1.837629] hub 1-0:1.0: USB hub found
[ 1.841502] hub 1-0:1.0: 2 ports detected
[ 1.846126] usbcore: registered new interface driver cdc_acm
[ 1.851791] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 1.859852] usbcore: registered new interface driver cdc_wdm
[ 1.865559] ata1: SATA link down (SStatus 0 SControl 300)
[ 1.871203] usbcore: registered new interface driver usb-storage
[ 1.877424] usbcore: registered new interface driver usbserial
[ 1.883384] usbcore: registered new interface driver usbserial_generic
[ 1.889966] usbserial: USB Serial support registered for generic
[ 1.896284] mousedev: PS/2 mouse device common for all mice
[ 1.901890] i2c /dev entries driver
[ 1.906475] usbcore: registered new interface driver usbhid
[ 1.912058] usbhid: USB HID core driver
[ 1.916208] TCP: cubic registered
[ 1.920652] NET: Registered protocol family 10
[ 1.926556] sit: IPv6 over IPv4 tunneling driver
[ 1.932124] NET: Registered protocol family 17
[ 1.936727] Key type dns_resolver registered
[ 1.945510] Freeing unused kernel memory: 172K (c073a000 - c0765000)
Loading, please wait...
[ 2.072122] udevd[67]: starting version 175
[ 2.160814] usb 1-1: new high-speed USB device number 2 using oxnas-ehci
[ 2.322621] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[ 2.329303] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 2.350149] usb 1-1: Product: USB2.0 Hub
[ 2.368806] hub 1-1:1.0: USB hub found
[ 2.378280] hub 1-1:1.0: 4 ports detected
[ 2.680458] usb 1-1.4: new high-speed USB device number 3 using oxnas-ehci
[ 2.790458] usb 1-1.4: New USB device found, idVendor=1908, idProduct=0226
[ 2.797306] usb 1-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.806999] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[ 2.813783] scsi host1: usb-storage 1-1.4:1.0
[ 2.832844] usbcore: registered new interface driver uas
[ 3.811568] scsi 1:0:0:0: Direct-Access Generic Mass-Storage 1.11 PQ: 0 ANSI: 2
[ 4.475138] sd 1:0:0:0: [sda] 7626752 512-byte logical blocks: (3.90 GB/3.63 GiB)
[ 4.483507] sd 1:0:0:0: [sda] Write Protect is off
[ 4.489128] sd 1:0:0:0: [sda] No Caching mode page found
[ 4.494487] sd 1:0:0:0: [sda] Assuming drive cache: write through
[ 4.508418] sda: sda1
[ 4.522439] sd 1:0:0:0: [sda] Attached SCSI removable disk
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
[ 12.643130] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[ 12.650101] EXT4-fs (sda1): write access will be enabled during recovery
[ 14.362076] EXT4-fs (sda1): recovery complete
[ 14.454141] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.88 booting
[info] Using makefile-style concurrent boot in runlevel S.
[....] Starting the hotplug events dispatcher: udevd[ 15.979427] udevd[256]: starting version 175
. ok
[ ok ] Synthesizing the initial hotplug events...done.
[ ok ] Waiting for /dev to be fully populated...done.
[....] Activating swap...[ 17.835886] random: nonblocking pool is initialized
done.
[ 17.968391] EXT4-fs (sda1): re-mounted. Opts: (null)
[....] Checking root file system...fsck from util-linux 2.20.1
/dev/sda1 has unsupported feature(s): metadata_csum
e2fsck: Get a newer version of e2fsck!
fsck died with exit status 8
failed (code 8).
[....] An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. The fsck should be perfo[FAILin maintenance mode with the root filesystem mounted in read-only mode. ... failed!
[....] The root filesystem is currently mounted in read-only mode. A maintenance shell will now be started. After performing system maintenance, press CONTROL-D[warnerminate the maintenance shell and restart the system. ... (warning).
Give root password for maintenance
(or type Control-D to continue):
root@debian:~#
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS September 18, 2017 03:28AM |
Registered: 9 years ago Posts: 6 |
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS September 18, 2017 01:04PM |
Admin Registered: 13 years ago Posts: 18,997 |
pritamcharan,
> Bodhi i saw previous messages and found a way to
> make changes stick.
Cool!
> Now Please guide, How can i update Uboot , Kernal
> to Latest.
Take a look at the 1st post of these 2 threads:
Upgrade kernel:
http://forum.doozan.com/read.php?2,16044
Upgrade u-boot:
http://forum.doozan.com/read.php?3,16017
And ask question before doing installation if you are not sure about something.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Bodhi i saw previous messages and found a way to
> make changes stick.
Cool!
> Now Please guide, How can i update Uboot , Kernal
> to Latest.
Take a look at the 1st post of these 2 threads:
Upgrade kernel:
http://forum.doozan.com/read.php?2,16044
Quote
Updated 05 Aug 2017:
Kernel linux-4.4.79-oxnas-tld-1 package was uploaded.
Upgrade u-boot:
http://forum.doozan.com/read.php?3,16017
Quote
Updated 22 Nov 2015
I've uploaded the uboot.2015.10-tld-1 u-Boot image for Pogoplug V3 Oxnas.
Warning: netconsole does not start automatically in this version. If you don't have serial console and therefore need netconsole to see the boot progress, please use previous u-boot version (uboot.2013.10-tld-3.ox820.bodhi.tar - Updated 16 May 2014). And follow the instruction in that section.
And ask question before doing installation if you are not sure about something.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS September 21, 2017 07:18AM |
Registered: 9 years ago Posts: 6 |
