Yet Another cannot boot thread
Posted by dinjo
|
Re: Yet Another cannot boot thread October 28, 2013 01:37AM |
Registered: 11 years ago Posts: 93 |
|
Re: Yet Another cannot boot thread October 28, 2013 01:58AM |
Admin Registered: 13 years ago Posts: 18,554 |
No need to, you've already running my latest kernel and latest rootfs. This rootfs has kernel 3.11.1 and the apt source is wheezy (look in /etc/apt/sources.list).
So from now on, from time to time when you want to get the latest package versions, then:
apt-get update
apt-get upgrade
You don't really need to update the kernel, if you don't need the latest changes. But if you do, then watch the same thread: http://forum.doozan.com/read.php?2,12096. I'll upload newer version of the kernel whenever the Linux kernel tree has significant updates. Otherwise , you can just doing apt-get update and apt-get upgrade to all the bugs fixed from the wheezy release.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/28/2013 02:00AM by bodhi.
So from now on, from time to time when you want to get the latest package versions, then:
apt-get update
apt-get upgrade
You don't really need to update the kernel, if you don't need the latest changes. But if you do, then watch the same thread: http://forum.doozan.com/read.php?2,12096. I'll upload newer version of the kernel whenever the Linux kernel tree has significant updates. Otherwise , you can just doing apt-get update and apt-get upgrade to all the bugs fixed from the wheezy release.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/28/2013 02:00AM by bodhi.
|
Re: Yet Another cannot boot thread October 28, 2013 02:22AM |
Registered: 11 years ago Posts: 93 |
Whats the difference between flashing kernel and doing apt upgrade ? I flash kernel then do a upgrade or other way around or both are independent
The reason im asking is i wanted to run minidlna and with older kernel it does not auto updates the media content
I tried setting up netconsole nothing comes up , I haven't rebooted the device yet
Edited 3 time(s). Last edit at 10/28/2013 02:49AM by dinjo.
The reason im asking is i wanted to run minidlna and with older kernel it does not auto updates the media content
I tried setting up netconsole nothing comes up , I haven't rebooted the device yet
fw_setenv serverip 192.168.1.104 fw_setenv ipaddr 192.168.1.110 fw_setenv if_netconsole 'ping $serverip' fw_setenv start_netconsole 'setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;' fw_setenv preboot 'run if_netconsole start_netconsole'
root@debian:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:25:31:02:01:8b
inet addr:192.168.1.104
root@debian:~# nc -l -u -p 6666 &
[1] 3581
root@debian:~#
root@debian:~# nc -u 192.168.1.110 6666
Edited 3 time(s). Last edit at 10/28/2013 02:49AM by dinjo.
|
Re: Yet Another cannot boot thread October 28, 2013 03:13AM |
Admin Registered: 13 years ago Posts: 18,554 |
dinjo Wrote:
-------------------------------------------------------
> Whats the difference between flashing kernel and
> doing apt upgrade ? I flash kernel then do a
> upgrade or other way around or both are
> independent
They are independent: apt-get upgrade only updates the current packages to latest version in wheezy. So don't worry about kernel. Kernel update sometimes affect the packages upgrade, but seldomly.
>
>
> The reason im asking is i wanted to run minidlna
> and with older kernel it does not auto updates the
> media content
You'll only need an up-to-date version of minidlna, and apt-get upgrade is for that purpose. If you need even newer than what is in wheezy then more tweak to the apt sources will be needed, but I'd doubt it. (You can also update minidlna individually with apt-get install).
>
>
> I tried setting up netconsole nothing comes up , I
> haven't rebooted the device yet
>
This should be on the GoFlex Net:
This should be on the server, where you run ssh, and watch the netconsole output:
Try changing the second command to
Also, run the server side first. And then reboot the GoFlex Net.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/28/2013 03:17AM by bodhi.
-------------------------------------------------------
> Whats the difference between flashing kernel and
> doing apt upgrade ? I flash kernel then do a
> upgrade or other way around or both are
> independent
They are independent: apt-get upgrade only updates the current packages to latest version in wheezy. So don't worry about kernel. Kernel update sometimes affect the packages upgrade, but seldomly.
>
>
> The reason im asking is i wanted to run minidlna
> and with older kernel it does not auto updates the
> media content
You'll only need an up-to-date version of minidlna, and apt-get upgrade is for that purpose. If you need even newer than what is in wheezy then more tweak to the apt sources will be needed, but I'd doubt it. (You can also update minidlna individually with apt-get install).
>
>
> I tried setting up netconsole nothing comes up , I
> haven't rebooted the device yet
>
This should be on the GoFlex Net:
> fw_setenv serverip 192.168.1.104 > fw_setenv ipaddr 192.168.1.110 > fw_setenv if_netconsole 'ping $serverip' > fw_setenv start_netconsole 'setenv ncip $serverip; > setenv bootdelay 10; setenv stdin nc; setenv > stdout nc; setenv stderr nc; version;' > fw_setenv preboot 'run if_netconsole > start_netconsole' >>
This should be on the server, where you run ssh, and watch the netconsole output:
> root@debian:~# ifconfig > eth0 Link encap:Ethernet HWaddr > 00:25:31:02:01:8b > inet addr:192.168.1.104 > root@debian:~# nc -l -u -p 6666 & > [1] 3581 > root@debian:~# > root@debian:~# nc -u 192.168.1.110 6666 >
Try changing the second command to
nc -up 6666 192.168.1.110 6666
Also, run the server side first. And then reboot the GoFlex Net.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/28/2013 03:17AM by bodhi.
|
Re: Yet Another cannot boot thread October 28, 2013 03:19AM |
Registered: 11 years ago Posts: 93 |
|
Re: Yet Another cannot boot thread October 28, 2013 03:27AM |
Admin Registered: 13 years ago Posts: 18,554 |
The server side is your Pogo E02? should be 192.168.1.104
Your GoFlex Net should be 192.168.1.110 (verify it with ifconfig like you did)
Server side has to be running these 2 nc commands first. And then reboot the GoFlex Net.
And remember to backup your GoFlex Net rootfs, since you are going to modify it quite a bit with apt-get upgrade.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 10/28/2013 03:31AM by bodhi.
Your GoFlex Net should be 192.168.1.110 (verify it with ifconfig like you did)
Server side has to be running these 2 nc commands first. And then reboot the GoFlex Net.
And remember to backup your GoFlex Net rootfs, since you are going to modify it quite a bit with apt-get upgrade.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 10/28/2013 03:31AM by bodhi.
|
Re: Yet Another cannot boot thread October 28, 2013 03:32AM |
Registered: 11 years ago Posts: 93 |
Yes its my OXNAS Pogo
Pogo
GoFlexNet
Pogo
root@debian:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:25:31:02:01:8b
inet addr:192.168.1.104 Bcast:192.168.1.255 Mask:255.255.255.0
root@debian:~# ps -ef | grep nc
root 12 2 0 07:16 ? 00:00:00 [async/mgr]
root 3884 3500 0 13:51 pts/0 00:00:00 nc -l -u -p 6666
root 3979 3500 0 14:01 pts/0 00:00:00 grep nc
GoFlexNet
root@debian:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:10:75:26:7f:a8
inet addr:192.168.1.110 Bcast:192.168.1.255 Mask:255.255.255.0
|
Re: Yet Another cannot boot thread October 28, 2013 03:39AM |
Registered: 11 years ago Posts: 93 |
Booted now but i see some errors in below
I'll add my sata drive , is it recommended to use usb flash drive for boot or use SATA drive ?
Thanks bodhi for your help and most importantly patience ;-)
root@debian:~# nc -up 6666 192.168.1.110 6666
U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt
** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 219 MiB
UBI: number of good PEBs: 1751
UBI: number of bad PEBs: 1
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 1730
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2218808 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
6518131 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.11.1-kirkwood-tld-1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2218744 Bytes = 2.1 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-3.11.1-kirkwood-tld-1
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6518067 Bytes = 6.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
I'll add my sata drive , is it recommended to use usb flash drive for boot or use SATA drive ?
Thanks bodhi for your help and most importantly patience ;-)
|
Re: Yet Another cannot boot thread October 28, 2013 04:03AM |
Admin Registered: 13 years ago Posts: 18,554 |
dinjo,
Looks great :) this ubifs error is expected, can safely be ignored.
It's really depend how you use the GF Net. If you want to mount NTFS HDD so that you can unplug it and connect it on Windows, then I would boot with USB, but more setup step needed to make sure you don't wear out the USB thumb.
The safest and best way is to boot with HDD rootfs. A few uBoot envs need to change to enable that.
Therefore, netconsole is a must have: you can do alwasy modify uBoot envs in netconsole first, and then after everything works, set them for real in Debian. If you make a mistake in netconsole, as long as you don't save it, they will be gone the next boot.
However, changing only a few uBoot envs to boot SATA has minimal risk, so you should set it up in Debian. When you ready, there are posts in this forum show how to do this.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/28/2013 04:13AM by bodhi.
Looks great :) this ubifs error is expected, can safely be ignored.
It's really depend how you use the GF Net. If you want to mount NTFS HDD so that you can unplug it and connect it on Windows, then I would boot with USB, but more setup step needed to make sure you don't wear out the USB thumb.
The safest and best way is to boot with HDD rootfs. A few uBoot envs need to change to enable that.
Therefore, netconsole is a must have: you can do alwasy modify uBoot envs in netconsole first, and then after everything works, set them for real in Debian. If you make a mistake in netconsole, as long as you don't save it, they will be gone the next boot.
However, changing only a few uBoot envs to boot SATA has minimal risk, so you should set it up in Debian. When you ready, there are posts in this forum show how to do this.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/28/2013 04:13AM by bodhi.
|
Re: Yet Another cannot boot thread October 28, 2013 04:53AM |
Registered: 11 years ago Posts: 93 |
I have 500 GB ext4 drive I can convert to ext3 if ext4 is not recommended which I plan to use for boot as well as data can you link me what boot args I need to change to boot from that drive since I have netconsole now it's feels better.
Also when you said require some commands so it does not wear out usb what do you mean? Disable logging?
Also when you said require some commands so it does not wear out usb what do you mean? Disable logging?
|
Re: Yet Another cannot boot thread October 28, 2013 06:18AM |
Registered: 11 years ago Posts: 93 |
When i attach my sata drive dmesg shows below and does not automount i was able to mount manually , the problem here is my drive has sdb2 no sdb1 not sure how to make it sdb1 as i think unless its done that way i wont be able to boot I'll change the label also to rootfs
Can you verify these are the commands i need to run to boot from sata
root@debian:~# blkid /dev/sdb
root@debian:~# blkid /dev/sdb1
root@debian:~# blkid /dev/sdb2
/dev/sdb2: LABEL="Data" UUID="2ba032fc-0e7e-4563-aa0d-77a89b35cdd2" TYPE="ext4"
root@debian:~#
root@debian:~# fdisk -l /dev/sdb
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0006b6ec
Device Boot Start End Blocks Id System
/dev/sdb2 2222080 976773119 487275520 83 Linux
root@debian:~#
[ 411.176712] ata1: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
[ 411.184352] ata1: edma_err_cause=00000020 pp_flags=00000003, SError=00180000
[ 411.191642] ata1: SError: { 10B8B Dispar }
[ 411.195777] ata1: hard resetting link
[ 411.539762] ata1: SATA link down (SStatus 0 SControl F300)
[ 416.539761] ata1: hard resetting link
[ 416.889760] ata1: SATA link down (SStatus 0 SControl F300)
[ 416.895286] ata1: limiting SATA link speed to 1.5 Gbps
[ 421.889765] ata1: hard resetting link
[ 422.239759] ata1: SATA link down (SStatus 0 SControl F310)
[ 422.245283] ata1.00: disabled
[ 422.248282] ata1: EH complete
[ 422.251296] ata1.00: detaching (SCSI 1:0:0:0)
[ 422.261648] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 422.272015] sd 1:0:0:0: [sdb]
[ 422.275182] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 422.281585] sd 1:0:0:0: [sdb] Stopping disk
[ 422.285848] sd 1:0:0:0: [sdb] START_STOP FAILED
[ 422.290813] sd 1:0:0:0: [sdb]
[ 422.293973] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 425.518403] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[ 425.526101] ata1: edma_err_cause=00000010 pp_flags=00000000, dev connect
[ 425.533039] ata1: SError: { PHYRdyChg DevExch }
[ 425.537619] ata1: hard resetting link
[ 429.629767] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
[ 429.669802] ata1.00: ATA-8: ST9500325AS, 0002BSM1, max UDMA/133
[ 429.675753] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 429.739801] ata1.00: configured for UDMA/133
[ 429.744101] ata1: EH complete
[ 429.747431] scsi 1:0:0:0: Direct-Access ATA ST9500325AS 0002 PQ: 0 ANSI: 5
[ 429.765319] sd 1:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[ 429.773440] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 429.779167] sd 1:0:0:0: [sdb] Write Protect is off
[ 429.789998] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 429.790179] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 429.832708] sdb: sdb2
[ 429.841002] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 581.771450] EXT4-fs (sdb2): warning: maximal mount count reached, running e2fsck is recommended
[ 581.785067] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null)
root@debian:~# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=14627,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=12360k,mode=755)
/dev/sda1 on / type ext2 (rw,noatime,errors=remount-ro)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=24700k)
tmpfs on /tmp type tmpfs (rw,relatime)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/sdb2 on /media/mnt type ext4 (rw,relatime,data=ordered)
Can you verify these are the commands i need to run to boot from sata
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'
|
Re: Yet Another cannot boot thread October 28, 2013 07:15AM |
Registered: 11 years ago Posts: 93 |
I ran a filesystem check and there are contiguous files but i guess its not a problem in short term , does anyone knows why my sata drive is not automounting ? When i use same drive on my pogo it does not comes with any errors
Edited 2 time(s). Last edit at 10/28/2013 07:23AM by dinjo.
root@debian:~# e2fsck -f -y -v /dev/sdb2 -C 0
e2fsck 1.42.5 (29-Jul-2012)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
4711 inodes used (0.02%, out of 30457856)
740 non-contiguous files (15.7%)
5 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 116/81/1
Extent depth histogram: 3933/417/152/5
75560125 blocks used (62.03%, out of 121818880)
0 bad blocks
20 large files
4552 regular files
147 directories
0 character device files
1 block device file
0 fifos
0 links
2 symbolic links (1 fast symbolic link)
0 sockets
------------
4702 files
root@debian:~# ls -lF /dev/disk/by-label total 0 drwxr-xr-x 2 root root 80 Oct 28 16:39 ./ drwxr-xr-x 6 root root 120 Jan 1 1970 ../ lrwxrwxrwx 1 root root 10 Oct 28 17:40 Data -> ../../sdb2 lrwxrwxrwx 1 root root 10 Jan 1 1970 rootfs -> ../../sda1 root@debian:~#
[ 4246.824100] ata1: exception Emask 0x10 SAct 0x0 SErr 0x10180000 action 0x6 frozen
[ 4246.831939] ata1: edma_err_cause=00000020 pp_flags=00000003, SError=10180000
[ 4246.839029] ata1: SError: { 10B8B Dispar }
[ 4246.843448] ata1: hard resetting link
[ 4247.189762] ata1: SATA link down (SStatus 0 SControl F300)
[ 4252.189767] ata1: hard resetting link
[ 4252.539761] ata1: SATA link down (SStatus 0 SControl F300)
[ 4252.545284] ata1: limiting SATA link speed to 1.5 Gbps
[ 4254.947796] ata1: hard resetting link
[ 4259.779766] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F310)
[ 4259.879809] ata1.00: configured for UDMA/133
[ 4259.884110] ata1: EH complete
root@debian:~# tune2fs -l /dev/sdb2
tune2fs 1.42.5 (29-Jul-2012)
Filesystem volume name: Data
Last mounted on: /media/Data
Filesystem UUID: 2ba032fc-0e7e-4563-aa0d-77a89b35cdd2
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent sparse_super large_file uninit_bg
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 30457856
Block count: 121818880
Reserved block count: 6090944
Free blocks: 46258755
Free inodes: 30453145
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 994
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Sat Sep 10 13:51:51 2011
Last mount time: Mon Oct 28 16:41:47 2013
Last write time: Mon Oct 28 17:33:47 2013
Mount count: 0
Maximum mount count: 26
Last checked: Mon Oct 28 17:33:47 2013
Check interval: 15552000 (6 months)
Next check after: Sat Apr 26 17:33:47 2014
Lifetime writes: 1578 GB
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: f5642ec2-5fb6-4f43-a853-e2549d749dfc
Journal backup: inode blocks
root@debian:~#
Edited 2 time(s). Last edit at 10/28/2013 07:23AM by dinjo.
|
Re: Yet Another cannot boot thread October 28, 2013 02:02PM |
Registered: 10 years ago Posts: 7 |
I can't get netconsole to work on my E02 pogoplug for anything. I used the exact same commands (substituting the IPs) and i dont see any activity in nc on the server. One thing I noticed is that when i put in fw_setenv if_netconsole 'ping $serverip' it removes the single quotes. Is this a problem and if so, how do i force them in?
edit: nevermind i tried it from a different server (one on the same physical switch, instead of on a linked switch) and it worked. What's up with that?
Edited 2 time(s). Last edit at 10/28/2013 02:13PM by joebob2000.
edit: nevermind i tried it from a different server (one on the same physical switch, instead of on a linked switch) and it worked. What's up with that?
Edited 2 time(s). Last edit at 10/28/2013 02:13PM by joebob2000.
|
Re: Yet Another cannot boot thread October 28, 2013 10:55PM |
Registered: 11 years ago Posts: 93 |
@bodhi
Any reason why SATA drives are not automounting ?
Also I'm re-creating the partitions I have posted in correct forum
http://forums.debian.net/viewtopic.php?f=30&t=108598
Edited 1 time(s). Last edit at 10/28/2013 10:56PM by dinjo.
Any reason why SATA drives are not automounting ?
Also I'm re-creating the partitions I have posted in correct forum
http://forums.debian.net/viewtopic.php?f=30&t=108598
Edited 1 time(s). Last edit at 10/28/2013 10:56PM by dinjo.
|
Re: Yet Another cannot boot thread October 29, 2013 12:51AM |
Admin Registered: 13 years ago Posts: 18,554 |
dinjo,
This looks good for booting with USB, and SATA in this order (if the rootfs is on USB then it will boot, if not then boot SATA):
SATA is not automounting because this rootfs is a basic rootfs, which does not have packages that handle automounting, or udev rules to do that. To automount USB or HDD disk drives, it is best to add udev rules to do that. OTOH, it could get complicated really quickly. If you're going to boot with HDD then there is no need to worry, but if you boot with USB then you can do one of these:
1. add a mount command for the HDD in /etc/rc.local
or
2. add an fstab entry for the HDD.
If you intend to unplug the disk while the system is running, then it is best to just have a script to mount it in rc.local, and have another script to unmount it whenever you want to unplug it.
So the bottom line is what you want to do, then customize your system that way. So decide and then post back, someone (or I) will help.
Also, it is best to use Ext3 for the HDD that you have rootfs on it. So I would backup your HDD files and reformat it as Ext3.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/29/2013 01:04AM by bodhi.
This looks good for booting with USB, and SATA in this order (if the rootfs is on USB then it will boot, if not then boot SATA):
Can you verify these are the commands i need to run to boot from sata 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'
SATA is not automounting because this rootfs is a basic rootfs, which does not have packages that handle automounting, or udev rules to do that. To automount USB or HDD disk drives, it is best to add udev rules to do that. OTOH, it could get complicated really quickly. If you're going to boot with HDD then there is no need to worry, but if you boot with USB then you can do one of these:
1. add a mount command for the HDD in /etc/rc.local
or
2. add an fstab entry for the HDD.
If you intend to unplug the disk while the system is running, then it is best to just have a script to mount it in rc.local, and have another script to unmount it whenever you want to unplug it.
So the bottom line is what you want to do, then customize your system that way. So decide and then post back, someone (or I) will help.
Also, it is best to use Ext3 for the HDD that you have rootfs on it. So I would backup your HDD files and reformat it as Ext3.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 10/29/2013 01:04AM by bodhi.
|
Re: Yet Another cannot boot thread October 29, 2013 01:25AM |
Registered: 11 years ago Posts: 93 |
So you are saying that when I mark the SATA drive as rootfs and convert to ext3 it would boot properly ? And how do i go ahead and fix the partition table ordering I'm concerned about the start value in sdb2 i.e should i just do a move the second line to first line and change to sdb1 ?
The drive was originally a ext3 and i ran below to convert to ext4 , can it be changed to ext3 without formatting ?
Automount udev rules
root@debian:~# sfdisk -l /dev/sdb Disk /dev/sdb: 60801 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/sdb1 0 - 0 0 0 Empty /dev/sdb2 138+ 60801- 60663- 487275520 83 Linux /dev/sdb3 0 - 0 0 0 Empty /dev/sdb4 0 - 0 0 0 Empty root@debian:~#
The drive was originally a ext3 and i ran below to convert to ext4 , can it be changed to ext3 without formatting ?
tune2fs -O extents,uninit_bg,dir_index /dev/sdb1
Automount udev rules
root@debian:/etc/udev/rules.d# cat 11-media-by-label-auto-mount.rules
KERNEL!="sd[a-z]*", GOTO="media_by_label_auto_mount_end"
ACTION=="add", PROGRAM!="/sbin/blkid %N", GOTO="media_by_label_auto_mount_end"
# Do not mount devices already mounted somewhere else to avoid entries for all your local partitions in /media
ACTION=="add", PROGRAM=="/bin/grep -q ' /dev/%k ' /proc/self/mountinfo", GOTO="media_by_label_auto_mount_end"
# Open LUKS partition if necessary
PROGRAM=="/sbin/blkid -o value -s TYPE %N", RESULT=="crypto_LUKS", ENV{crypto}="mapper/", ENV{device}="/dev/mapper/%k"
ENV{crypto}=="", ENV{device}="%N"
ACTION=="add", ENV{crypto}!="", PROGRAM=="/usr/bin/xterm -display :0.0 -e 'echo Password for /dev/%k; /sbin/cryptsetup luksOpen %N %k'"
ACTION=="add", ENV{crypto}!="", TEST!="/dev/mapper/%k", GOTO="media_by_label_auto_mount_end"
# Global mount options
ACTION=="add", ENV{mount_options}="noatime"
# Filesystem-specific mount options
ACTION=="add", PROGRAM=="/sbin/blkid -o value -s TYPE %E{device}", RESULT=="vfat|ntfs", ENV{mount_options}="%E{mount_options},utf8,gid=100,umask=002"
ACTION=="add", PROGRAM=="/sbin/blkid -o value -s TYPE %E{device}", RESULT=="ext4", ENV{mount_options}="%E{mount_options},data=writeback,barrier=0,nobh,errors=remount-ro"
# Get label if present, otherwise assign one
PROGRAM=="/sbin/blkid -o value -s LABEL %E{device}", ENV{dir_name}="%c"
# Use basename to correctly handle labels such as ../mnt/foo
PROGRAM=="/usr/bin/basename '%E{dir_name}'", ENV{dir_name}="%c"
ENV{dir_name}=="", ENV{dir_name}="hd-%k"
# Mount the device
ACTION=="add", ENV{dir_name}!="", RUN+="/bin/mkdir -p '/media/%E{dir_name}'", RUN+="/bin/mount -o %E{mount_options} /dev/%E{crypto}%k '/media/%E{dir_name}'"
# Clean up after removal
ACTION=="remove", ENV{dir_name}!="", RUN+="/bin/umount -l '/media/%E{dir_name}'"
ACTION=="remove", ENV{crypto}!="", RUN+="/sbin/cryptsetup luksClose %k"
ACTION=="remove", ENV{dir_name}!="", RUN+="/bin/rmdir '/media/%E{dir_name}'"
# Exit
LABEL="media_by_label_auto_mount_end"
|
Re: Yet Another cannot boot thread October 29, 2013 02:36AM |
Admin Registered: 13 years ago Posts: 18,554 |
dinjo,
Ext3 rootfs should be very reliable. I think it is best that you move the files out and reformat. Upgrade from Ext3 to Ext4 is straight forward, but downgrade is a pain.
You udev rules is too complicated. I can't judge it easily!. You should worry about booting with HDD first, udev rules can come after.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Ext3 rootfs should be very reliable. I think it is best that you move the files out and reformat. Upgrade from Ext3 to Ext4 is straight forward, but downgrade is a pain.
You udev rules is too complicated. I can't judge it easily!. You should worry about booting with HDD first, udev rules can come after.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Yet Another cannot boot thread October 29, 2013 03:48AM |
Registered: 11 years ago Posts: 93 |
Ok I'm taking a complete back up now and would reformat what partition do you recommend .?
1 GB for rootfs ?
Rest all Data ?
Swap ? If yes how much swap file or swap partition ?
The reason I'm asking is last time when I had 2 partition it was not booting with usb.
Also in netconsole I see some people get to see details even after starting kernel mine does not shows anything after starting kernel?
Edited 2 time(s). Last edit at 10/29/2013 05:55AM by dinjo.
1 GB for rootfs ?
Rest all Data ?
Swap ? If yes how much swap file or swap partition ?
The reason I'm asking is last time when I had 2 partition it was not booting with usb.
Also in netconsole I see some people get to see details even after starting kernel mine does not shows anything after starting kernel?
Edited 2 time(s). Last edit at 10/29/2013 05:55AM by dinjo.
|
Re: Yet Another cannot boot thread October 29, 2013 06:04AM |
Registered: 11 years ago Posts: 93 |
|
Re: Yet Another cannot boot thread October 29, 2013 12:04PM |
Admin Registered: 13 years ago Posts: 18,554 |
I would use a swap file. It is much more flexible (e.g. you can turn on/off swap in /etc/rc.local).
Yes, the instruction for creating the rootfs on USB thumb drive specified one partition. That was to simplify the booting process only. You can use as many partition as you need, as long as only the rootfs partition is labeled rootfs. There are plenty of space on the HDD, so the rootfs should be large for future growth.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Yes, the instruction for creating the rootfs on USB thumb drive specified one partition. That was to simplify the booting process only. You can use as many partition as you need, as long as only the rootfs partition is labeled rootfs. There are plenty of space on the HDD, so the rootfs should be large for future growth.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Yet Another cannot boot thread October 29, 2013 10:26PM |
Registered: 11 years ago Posts: 93 |
Thanks booting from SATA drive now.I have some final questions.
1. When I issue a shutdown command the LAN light on router does not goes off
2. Why is the booting a bit slow ? My pogo boots and gets a ip much faster
3. This is something i asked before so asking again how are people able to get more information in netconsole even after kernel is loaded i.e Starting Kernel , can it be monitored by netconsole or is it Rescue System ?
4. Can i turnoff the light i.e I wanted the device to boot and after 2 minutes turn red and then switch off ?
5. Lot of packages are getting installed i remember there is something which needs to be put in some conf file which does not install any un-necessary stuff
Edited 1 time(s). Last edit at 10/29/2013 10:28PM by dinjo.
1. When I issue a shutdown command the LAN light on router does not goes off
2. Why is the booting a bit slow ? My pogo boots and gets a ip much faster
3. This is something i asked before so asking again how are people able to get more information in netconsole even after kernel is loaded i.e Starting Kernel , can it be monitored by netconsole or is it Rescue System ?
4. Can i turnoff the light i.e I wanted the device to boot and after 2 minutes turn red and then switch off ?
5. Lot of packages are getting installed i remember there is something which needs to be put in some conf file which does not install any un-necessary stuff
root@debian:~# nc -up 6666 192.168.1.110 6666
U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported
** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 219 MiB
UBI: number of good PEBs: 1751
UBI: number of bad PEBs: 1
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 1730
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
Reset IDE: Bus 0: OK Bus 1: not available
Device 0: Model: ST9500325AS Firm: 0002BSM1 Ser#: 5VEJJRX1
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
Loading file "/boot/uImage" from ide device 0:1 (hda1)
2218808 bytes read
Loading file "/boot/uInitrd" from ide device 0:1 (hda1)
6518131 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.11.1-kirkwood-tld-1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2218744 Bytes = 2.1 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-3.11.1-kirkwood-tld-1
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6518067 Bytes = 6.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
root@debian:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.11.1-kirkwood-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 PREEMPT Fri Sep 27 01:50:15 PDT 2013 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machine: Seagate GoFlex Net [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] On node 0 totalpages: 32768 [ 0.000000] free_area_init_node: node 0, pgdat c05f0c74, node_mem_map c065d000 [ 0.000000] Normal zone: 256 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 32768 pages, LIFO batch:7 [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [ 0.000000] pcpu-alloc: [0] 0 [ 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 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) [ 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: 117020K/131072K available (4192K kernel code, 309K rwdata, 1368K rodata, 187K init, 420K bss, 14052K reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 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 - 0xc05761a0 (5561 kB) [ 0.000000] .init : 0xc0577000 - 0xc05a5cdc ( 188 kB) [ 0.000000] .data : 0xc05a6000 - 0xc05f3538 ( 310 kB) [ 0.000000] .bss : 0xc05f3538 - 0xc065c5cc ( 421 kB) [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] NR_IRQS:114 [ 0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms [ 0.000000] Console: colour dummy device 80x30 [ 14.251803] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584) [ 14.341596] pid_max: default: 32768 minimum: 301 [ 14.341697] Security Framework initialized [ 14.341768] Mount-cache hash table entries: 512 [ 14.342387] Initializing cgroup subsys devices [ 14.342409] Initializing cgroup subsys freezer [ 14.342422] Initializing cgroup subsys net_cls [ 14.342433] Initializing cgroup subsys blkio [ 14.342507] CPU: Testing write buffer coherency: ok [ 14.342893] Setting up static identity map for 0xc03f6900 - 0xc03f693c [ 14.344725] devtmpfs: initialized [ 14.346981] pinctrl core: initialized pinctrl subsystem [ 14.347314] regulator-dummy: no parameters [ 14.347631] NET: Registered protocol family 16 [ 14.348049] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 14.348821] Kirkwood: MV88F6281-A1, TCLK=200000000. [ 14.348842] Feroceon L2: Enabling L2 [ 14.348881] Feroceon L2: Cache support initialised. [ 14.349208] initial MPP regs: 01111111 11113322 00001111 00100000 00000000 00000000 00000000 [ 14.349236] final MPP regs: 01111111 11113322 00001111 00000000 00000000 00000000 00000000 [ 14.352719] bio: create slab <bio-0> at 0 [ 14.353147] vgaarb: loaded [ 14.353285] usbcore: registered new interface driver usbfs [ 14.353337] usbcore: registered new interface driver hub [ 14.353436] usbcore: registered new device driver usb [ 14.354052] Switched to clocksource orion_clocksource [ 14.368497] NET: Registered protocol family 2 [ 14.369138] TCP established hash table entries: 1024 (order: 1, 8192 bytes) [ 14.369175] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [ 14.369196] TCP: Hash tables configured (established 1024 bind 1024) [ 14.369263] TCP: reno registered [ 14.369276] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 14.369301] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 14.369500] NET: Registered protocol family 1 [ 14.369809] RPC: Registered named UNIX socket transport module. [ 14.369821] RPC: Registered udp transport module. [ 14.369828] RPC: Registered tcp transport module. [ 14.369835] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 14.369846] PCI: CLS 0 bytes, default 32 [ 14.370047] Unpacking initramfs... [ 14.916528] Freeing initrd memory: 6360K (c1101000 - c1737000) [ 14.916632] NetWinder Floating Point Emulator V0.97 (double precision) [ 14.917237] audit: initializing netlink socket (disabled) [ 14.917283] type=2000 audit(0.660:1): initialized [ 14.918121] VFS: Disk quotas dquot_6.5.2 [ 14.918175] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 14.918537] NFS: Registering the id_resolver key type [ 14.918597] Key type id_resolver registered [ 14.918607] Key type id_legacy registered [ 14.918626] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 14.918789] jffs2: version 2.2. (NAND) (SUMMARY) \xffffffc2\xffffffa9 2001-2006 Red Hat, Inc. [ 14.919002] msgmni has been set to 240 [ 14.920869] alg: No test for stdrng (krng) [ 14.920960] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [ 14.920972] io scheduler noop registered [ 14.920980] io scheduler deadline registered [ 14.921002] io scheduler cfq registered (default) [ 14.921197] mv_xor mv_xor.0: Marvell shared XOR driver [ 14.954131] mv_xor mv_xor.0: Marvell XOR: ( xor cpy ) [ 14.994112] mv_xor mv_xor.0: Marvell XOR: ( xor cpy ) [ 14.994216] mv_xor mv_xor.1: Marvell shared XOR driver [ 15.034111] mv_xor mv_xor.1: Marvell XOR: ( xor cpy ) [ 15.074110] mv_xor mv_xor.1: Marvell XOR: ( xor cpy ) [ 15.074362] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 15.094917] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A [ 15.591531] console [ttyS0] enabled [ 15.596045] ONFI param page 0 valid [ 15.599550] ONFI flash detected [ 15.602712] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08AAD), 256MiB, page size: 2048, OOB size: 64 [ 15.613831] Scanning device for bad blocks [ 15.664293] Bad eraseblock 440 at 0x000003700000 [ 15.837902] 4 cmdlinepart partitions found on MTD device orion_nand [ 15.844214] Creating 4 MTD partitions on "orion_nand": [ 15.849375] 0x000000000000-0x000000100000 : "u-boot" [ 15.854602] 0x000000100000-0x000000500000 : "uImage" [ 15.859798] 0x000000500000-0x000002500000 : "rootfs" [ 15.865059] 0x000002500000-0x000010000000 : "data" [ 15.870337] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 15.876912] ehci-pci: EHCI PCI platform driver [ 15.881413] ehci-orion: EHCI orion driver [ 15.885511] orion-ehci orion-ehci.0: EHCI Host Controller [ 15.890957] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1 [ 15.899077] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000 [ 15.924085] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00 [ 15.930102] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 15.936943] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 15.944217] usb usb1: Product: EHCI Host Controller [ 15.949121] usb usb1: Manufacturer: Linux 3.11.1-kirkwood-tld-1 ehci_hcd [ 15.955866] usb usb1: SerialNumber: orion-ehci.0 [ 15.960921] hub 1-0:1.0: USB hub found [ 15.964735] hub 1-0:1.0: 1 port detected [ 15.969084] mousedev: PS/2 mouse device common for all mice [ 16.984160] rtc-mv rtc-mv: internal RTC not ticking [ 16.989157] i2c /dev entries driver [ 16.992724] cpuidle: using governor ladder [ 16.996857] cpuidle: using governor menu [ 17.001635] drop_monitor: Initializing network drop monitor service [ 17.008238] TCP: cubic registered [ 17.011573] NET: Registered protocol family 17 [ 17.016155] Key type dns_resolver registered [ 17.020879] registered taskstats version 1 [ 17.025834] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 17.032929] Freeing unused kernel memory: 184K (c0577000 - c05a5000) [ 17.104759] udevd[52]: starting version 175 [ 17.182305] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 17.278874] libphy: orion_mdio_bus: probed [ 17.343488] SCSI subsystem initialized [ 17.420663] libata version 3.00 loaded. [ 18.475151] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:10:75:26:7f:a8 [ 18.483969] sata_mv sata_mv.0: version 1.28 [ 18.484040] sata_mv sata_mv.0: cannot get optional clkdev [ 18.494582] sata_mv sata_mv.0: slots 32 ports 2 [ 18.502335] scsi0 : sata_mv [ 18.505806] scsi1 : sata_mv [ 18.509092] ata1: SATA max UDMA/133 irq 21 [ 18.513209] ata2: SATA max UDMA/133 irq 21 [ 19.024097] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F300) [ 19.104124] ata1.00: ATA-8: ST9500325AS, 0002BSM1, max UDMA/133 [ 19.110078] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 19.174128] ata1.00: configured for UDMA/133 [ 19.194439] scsi 0:0:0:0: Direct-Access ATA ST9500325AS 0002 PQ: 0 ANSI: 5 [ 19.544094] ata2: SATA link down (SStatus 0 SControl F300) [ 19.586720] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB) [ 19.595501] sd 0:0:0:0: [sda] Write Protect is off [ 19.600328] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 19.600444] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 19.675197] sda: sda1 sda2 [ 19.679874] sd 0:0:0:0: [sda] Attached SCSI disk [ 19.695032] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 30.229008] EXT2-fs (sda1): warning: mounting ext3 filesystem as ext2 [ 32.354155] udevd[244]: starting version 175 [ 32.888532] alg: hash: Test 1 failed for mv-hmac-sha1 [ 32.893617] 00000000: 0c aa 9f d5 37 c3 79 3a 91 d9 21 5f 42 2b 2c 24 [ 32.908658] 00000010: b7 c3 16 0c [ 32.915819] orion_wdt: Initial timeout 21 sec [ 38.856228] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down [ 39.478820] NET: Registered protocol family 10 [ 39.484129] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 41.201551] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled [ 41.211389] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 178.557417] kjournald starting. Commit interval 5 seconds [ 178.563002] EXT3-fs (sda2): using internal journal [ 178.568249] EXT3-fs (sda2): mounted filesystem with ordered data mode
Edited 1 time(s). Last edit at 10/29/2013 10:28PM by dinjo.
|
Re: Yet Another cannot boot thread October 30, 2013 12:45AM |
Admin Registered: 13 years ago Posts: 18,554 |
dinjo Wrote:
-------------------------------------------------------
> Thanks booting from SATA drive now.I have some
> final questions.
>
> 1. When I issue a shutdown command the LAN light
> on router does not goes off
I guess that because the GoFlex Net power is still on (it's normal). Power is not off completely on these plugs. But you've shutdowned so the only way to boot back up is to manually recycle the power.
> 3. This is something i asked before so asking
> again how are people able to get more information
> in netconsole even after kernel is loaded i.e
> Starting Kernel , can it be monitored by
> netconsole or is it Rescue System ?
See this thread for netconsole set up:
http://forum.doozan.com/read.php?2,9522
> 4. Can i turnoff the light i.e I wanted the device
> to boot and after 2 minutes turn red and then
> switch off ?
Yes, you could run 2 delayed echo commands to do this. Look in /etc/rc.local for example, the LED is turned green in there with an echo to the LED trigger file.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Thanks booting from SATA drive now.I have some
> final questions.
>
> 1. When I issue a shutdown command the LAN light
> on router does not goes off
I guess that because the GoFlex Net power is still on (it's normal). Power is not off completely on these plugs. But you've shutdowned so the only way to boot back up is to manually recycle the power.
> 3. This is something i asked before so asking
> again how are people able to get more information
> in netconsole even after kernel is loaded i.e
> Starting Kernel , can it be monitored by
> netconsole or is it Rescue System ?
See this thread for netconsole set up:
http://forum.doozan.com/read.php?2,9522
> 4. Can i turnoff the light i.e I wanted the device
> to boot and after 2 minutes turn red and then
> switch off ?
Yes, you could run 2 delayed echo commands to do this. Look in /etc/rc.local for example, the LED is turned green in there with an echo to the LED trigger file.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Yet Another cannot boot thread October 30, 2013 08:35AM |
Registered: 11 years ago Posts: 93 |
|
Re: Yet Another cannot boot thread October 30, 2013 04:21PM |
Admin Registered: 13 years ago Posts: 18,554 |
dinjo Wrote:
-------------------------------------------------------
> Thanks I'll look into your netconsole thread you
> mentioned sometime back if i do a apt-update and
> upgrade i dont need to do flash the kernel so does
> that mean i just add netconsole module command in
> conf file ?
It's in the instruction: modify the modules file, update initramfs file, and regenerate uInitrd.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Thanks I'll look into your netconsole thread you
> mentioned sometime back if i do a apt-update and
> upgrade i dont need to do flash the kernel so does
> that mean i just add netconsole module command in
> conf file ?
It's in the instruction: modify the modules file, update initramfs file, and regenerate uInitrd.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Yet Another cannot boot thread October 30, 2013 04:29PM |
Registered: 11 years ago Posts: 93 |
|
Re: Yet Another cannot boot thread October 30, 2013 11:51PM |
Admin Registered: 13 years ago Posts: 18,554 |
If apt-get upgrade caused this file to be updated: /boot/initrd.img-3.11.1-kirkwood-tld-1
then the uInitrd should be regenerated.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
then the uInitrd should be regenerated.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Yet Another cannot boot thread October 31, 2013 10:55PM |
Registered: 11 years ago Posts: 93 |
I'm getting this warnings in dmesg , and should i change the usb_rootfstype to ext3 ? currently its set to ext2 , also why does it looks at usb when I'm booting from SATA ?
root@debian:~# fw_printenv usb_rootfstype usb_rootfstype=ext2
[ 22.428392] sda: sda1 sda2 [ 22.433061] sd 0:0:0:0: [sda] Attached SCSI disk [ 22.448078] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 32.960112] EXT2-fs (sda1): warning: mounting ext3 filesystem as ext2 [ 35.146904] udevd[236]: starting version 175 [ 35.595458] alg: hash: Test 1 failed for mv-hmac-sha1 [ 35.603134] 00000000: 0c aa 9f d5 37 c3 79 3a 91 d9 21 5f 42 2b 2c 24 [ 35.615834] 00000010: b7 c3 16 0c [ 35.624173] orion_wdt: Initial timeout 21 sec
|
Re: Yet Another cannot boot thread November 01, 2013 12:00AM |
Admin Registered: 13 years ago Posts: 18,554 |
Yes, you should change your uBoot env for usbrootfs_type to ext3.
And pls post the full dmesg log.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
And pls post the full dmesg log.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Yet Another cannot boot thread November 01, 2013 01:03AM |
Registered: 11 years ago Posts: 93 |
Complete report
root@debian:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.11.1-kirkwood-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 PREEMPT Fri Sep 27 01:50:15 PDT 2013 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machine: Seagate GoFlex Net [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] On node 0 totalpages: 32768 [ 0.000000] free_area_init_node: node 0, pgdat c05f0c74, node_mem_map c065d000 [ 0.000000] Normal zone: 256 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 32768 pages, LIFO batch:7 [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [ 0.000000] pcpu-alloc: [0] 0 [ 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 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) [ 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: 117020K/131072K available (4192K kernel code, 309K rwdata, 1368K rodata, 187K init, 420K bss, 14052K reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 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 - 0xc05761a0 (5561 kB) [ 0.000000] .init : 0xc0577000 - 0xc05a5cdc ( 188 kB) [ 0.000000] .data : 0xc05a6000 - 0xc05f3538 ( 310 kB) [ 0.000000] .bss : 0xc05f3538 - 0xc065c5cc ( 421 kB) [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] NR_IRQS:114 [ 0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms [ 0.000000] Console: colour dummy device 80x30 [ 17.793460] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584) [ 17.883251] pid_max: default: 32768 minimum: 301 [ 17.883353] Security Framework initialized [ 17.883422] Mount-cache hash table entries: 512 [ 17.884038] Initializing cgroup subsys devices [ 17.884061] Initializing cgroup subsys freezer [ 17.884075] Initializing cgroup subsys net_cls [ 17.884087] Initializing cgroup subsys blkio [ 17.884160] CPU: Testing write buffer coherency: ok [ 17.884545] Setting up static identity map for 0xc03f6900 - 0xc03f693c [ 17.886378] devtmpfs: initialized [ 17.888636] pinctrl core: initialized pinctrl subsystem [ 17.888969] regulator-dummy: no parameters [ 17.889285] NET: Registered protocol family 16 [ 17.889704] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 17.890475] Kirkwood: MV88F6281-A1, TCLK=200000000. [ 17.890496] Feroceon L2: Enabling L2 [ 17.890535] Feroceon L2: Cache support initialised. [ 17.890862] initial MPP regs: 01111111 11113322 00001111 00100000 00000000 00000000 00000000 [ 17.890890] final MPP regs: 01111111 11113322 00001111 00000000 00000000 00000000 00000000 [ 17.894377] bio: create slab <bio-0> at 0 [ 17.894806] vgaarb: loaded [ 17.894942] usbcore: registered new interface driver usbfs [ 17.894995] usbcore: registered new interface driver hub [ 17.895093] usbcore: registered new device driver usb [ 17.895708] Switched to clocksource orion_clocksource [ 17.910174] NET: Registered protocol family 2 [ 17.910817] TCP established hash table entries: 1024 (order: 1, 8192 bytes) [ 17.910853] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [ 17.910873] TCP: Hash tables configured (established 1024 bind 1024) [ 17.910940] TCP: reno registered [ 17.910953] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 17.910978] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 17.911175] NET: Registered protocol family 1 [ 17.911487] RPC: Registered named UNIX socket transport module. [ 17.911498] RPC: Registered udp transport module. [ 17.911505] RPC: Registered tcp transport module. [ 17.911512] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 17.911524] PCI: CLS 0 bytes, default 32 [ 17.911724] Unpacking initramfs... [ 18.458164] Freeing initrd memory: 6360K (c1101000 - c1737000) [ 18.458267] NetWinder Floating Point Emulator V0.97 (double precision) [ 18.458871] audit: initializing netlink socket (disabled) [ 18.458917] type=2000 audit(0.660:1): initialized [ 18.459753] VFS: Disk quotas dquot_6.5.2 [ 18.459805] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 18.460168] NFS: Registering the id_resolver key type [ 18.460236] Key type id_resolver registered [ 18.460247] Key type id_legacy registered [ 18.460266] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 18.460429] jffs2: version 2.2. (NAND) (SUMMARY) \xffffffc2\xffffffa9 2001-2006 Red Hat, Inc. [ 18.460639] msgmni has been set to 240 [ 18.462508] alg: No test for stdrng (krng) [ 18.462601] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [ 18.462613] io scheduler noop registered [ 18.462621] io scheduler deadline registered [ 18.462642] io scheduler cfq registered (default) [ 18.462835] mv_xor mv_xor.0: Marvell shared XOR driver [ 18.495787] mv_xor mv_xor.0: Marvell XOR: ( xor cpy ) [ 18.535768] mv_xor mv_xor.0: Marvell XOR: ( xor cpy ) [ 18.535870] mv_xor mv_xor.1: Marvell shared XOR driver [ 18.575769] mv_xor mv_xor.1: Marvell XOR: ( xor cpy ) [ 18.615767] mv_xor mv_xor.1: Marvell XOR: ( xor cpy ) [ 18.616021] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 18.636574] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A [ 19.133164] console [ttyS0] enabled [ 19.137677] ONFI param page 0 valid [ 19.141183] ONFI flash detected [ 19.144345] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08AAD), 256MiB, page size: 2048, OOB size: 64 [ 19.155463] Scanning device for bad blocks [ 19.205918] Bad eraseblock 440 at 0x000003700000 [ 19.379525] 4 cmdlinepart partitions found on MTD device orion_nand [ 19.385838] Creating 4 MTD partitions on "orion_nand": [ 19.390999] 0x000000000000-0x000000100000 : "u-boot" [ 19.396227] 0x000000100000-0x000000500000 : "uImage" [ 19.401422] 0x000000500000-0x000002500000 : "rootfs" [ 19.406684] 0x000002500000-0x000010000000 : "data" [ 19.411961] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 19.418535] ehci-pci: EHCI PCI platform driver [ 19.423039] ehci-orion: EHCI orion driver [ 19.427137] orion-ehci orion-ehci.0: EHCI Host Controller [ 19.432582] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1 [ 19.440557] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000 [ 19.465741] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00 [ 19.471758] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 19.478601] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 19.485867] usb usb1: Product: EHCI Host Controller [ 19.490771] usb usb1: Manufacturer: Linux 3.11.1-kirkwood-tld-1 ehci_hcd [ 19.497516] usb usb1: SerialNumber: orion-ehci.0 [ 19.502571] hub 1-0:1.0: USB hub found [ 19.506377] hub 1-0:1.0: 1 port detected [ 19.510726] mousedev: PS/2 mouse device common for all mice [ 20.525816] rtc-mv rtc-mv: internal RTC not ticking [ 20.530810] i2c /dev entries driver [ 20.534383] cpuidle: using governor ladder [ 20.538516] cpuidle: using governor menu [ 20.543295] drop_monitor: Initializing network drop monitor service [ 20.549898] TCP: cubic registered [ 20.553232] NET: Registered protocol family 17 [ 20.557806] Key type dns_resolver registered [ 20.562531] registered taskstats version 1 [ 20.567494] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 20.574584] Freeing unused kernel memory: 184K (c0577000 - c05a5000) [ 20.646406] udevd[52]: starting version 175 [ 20.714888] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 20.767423] libphy: PHY orion-mdio-mii:00 not found [ 20.772353] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral [ 20.853492] SCSI subsystem initialized [ 20.891109] libphy: orion_mdio_bus: probed [ 20.987423] libata version 3.00 loaded. [ 20.989295] sata_mv sata_mv.0: version 1.28 [ 20.989370] sata_mv sata_mv.0: cannot get optional clkdev [ 20.994881] sata_mv sata_mv.0: slots 32 ports 2 [ 21.100872] scsi0 : sata_mv [ 21.135818] scsi1 : sata_mv [ 21.138810] ata1: SATA max UDMA/133 irq 21 [ 21.142922] ata2: SATA max UDMA/133 irq 21 [ 21.715770] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F300) [ 21.795773] ata1.00: ATA-8: ST9500325AS, 0002BSM1, max UDMA/133 [ 21.801720] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 21.905776] ata1.00: configured for UDMA/133 [ 21.926081] scsi 0:0:0:0: Direct-Access ATA ST9500325AS 0002 PQ: 0 ANSI: 5 [ 22.078065] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:10:75:26:7f:a8 [ 22.295749] ata2: SATA link down (SStatus 0 SControl F300) [ 22.338347] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB) [ 22.347130] sd 0:0:0:0: [sda] Write Protect is off [ 22.351955] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 22.352072] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 22.428392] sda: sda1 sda2 [ 22.433061] sd 0:0:0:0: [sda] Attached SCSI disk [ 22.448078] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 32.960112] EXT2-fs (sda1): warning: mounting ext3 filesystem as ext2 [ 35.146904] udevd[236]: starting version 175 [ 35.595458] alg: hash: Test 1 failed for mv-hmac-sha1 [ 35.603134] 00000000: 0c aa 9f d5 37 c3 79 3a 91 d9 21 5f 42 2b 2c 24 [ 35.615834] 00000010: b7 c3 16 0c [ 35.624173] orion_wdt: Initial timeout 21 sec [ 41.852880] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down [ 42.463365] NET: Registered protocol family 10 [ 42.469350] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 44.240638] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled [ 44.250470] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 56.491179] kjournald starting. Commit interval 5 seconds [ 56.496975] EXT3-fs (sda2): using internal journal [ 56.501791] EXT3-fs (sda2): mounted filesystem with ordered data mode [ 62.731510] Adding 524284k swap on /media/Data/swapfile. Priority:-1 extents:134 across:642636k root@debian:~#
|
Re: Yet Another cannot boot thread November 01, 2013 01:51AM |
Admin Registered: 13 years ago Posts: 18,554 |
Everything looks normal. Except for that Ext2/Ext3 mounting. It doesn't hurt to run it that way, but it's best to change usbrootfs_type to Ext3 to get the journal going so it will be resilient to unexpected power outage.
The HDD was assigned as /dev/sda and the rootfs partition is sda1, so it is normal too. HDD used to be assigned has hda/hda1.. , but the kernel has changed the way the HDD is mounted.
Also, since you swap file is on HDD, you can use a larger size. Swap file sized 1, 2 GB is nothing comparing to the HDD capacity, but it'll come in handy when you run things that require a lot of memory (e.g. mysql, kernel compilation). I'm using a 8GB swap file on a 500GB HDD, just in case (never got to even 100MB usage, though).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/01/2013 02:00AM by bodhi.
The HDD was assigned as /dev/sda and the rootfs partition is sda1, so it is normal too. HDD used to be assigned has hda/hda1.. , but the kernel has changed the way the HDD is mounted.
Also, since you swap file is on HDD, you can use a larger size. Swap file sized 1, 2 GB is nothing comparing to the HDD capacity, but it'll come in handy when you run things that require a lot of memory (e.g. mysql, kernel compilation). I'm using a 8GB swap file on a 500GB HDD, just in case (never got to even 100MB usage, though).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 11/01/2013 02:00AM by bodhi.
