General NAS-Central Forums

Welcome to the NAS community
It is currently Sun Sep 24, 2017 3:53 pm

All times are UTC




Post new topic Reply to topic  [ 73 posts ]  Go to page Previous  1, 2, 3, 4, 5  Next
Author Message
PostPosted: Thu Sep 26, 2013 7:58 am 
Offline

Joined: Wed Aug 21, 2013 2:20 pm
Posts: 38
I re-imaged the hdd again with files from http://downloads.lacie.nas-central.org/Users/Mijzelf/Ethernet%20Big%20Disk/Partitions/

And I'm getting the kernel to boot but it again stopped and turned the NAS off automatically.

https://docs.google.com/file/d/0B3RJUVbE6jxWbjJnREk5b3BEUnM/edit?usp=sharing


Top
 Profile  
 
PostPosted: Thu Sep 26, 2013 8:20 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
Quote:
VFS: Cannot open root device "sda7" or unknown-block(0,0)
The kernel cannot mount sda7. Maybe it shouldn't be a raid array. Try
Code:
mke2fs /dev/sdb7
mkdir /tmp/sdb7
mount /dev/sdb7 /tmp/sdb7
cd /tmp/sdb7
tar xzf /full/path/to/sda7.tgz
cd ..
umount /tmp/sdb7
(Where sdb is your disk, of course.)


Top
 Profile  
 
PostPosted: Thu Sep 26, 2013 8:42 am 
Offline

Joined: Wed Aug 21, 2013 2:20 pm
Posts: 38
:( :( :(
Weird, still getting the same error:

Code:
Loading I2C based RTC driver device interface.
Found TWSI adapter with id: 0
Found I2C RTC rs5c372 @ 0x32
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "sda7" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


Top
 Profile  
 
PostPosted: Thu Sep 26, 2013 9:04 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
Hm. I should read better. The kernel doesn't detect the whole disk. Here you can see the bootlog of an EdMini V2, and it logs
Code:
Intergrated Sata device found
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
  Vendor: SAMSUNG   Model: SP2504C           Rev: VT10
  Type:   Direct-Access                      ANSI SCSI revision: 03
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sda: drive cache: write back
 sda: sda1 < sda5 sda6 sda7 sda8 sda9 > sda2
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi1, channel 0, id 0, lun 0,  type 0
On the corresponding place your bootlog only logs
Code:
Intergrated Sata device found
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
That is weird, u-boot could read that disk fine. Do you have another disk to test with? And also, I'll dive up that EDB kernel I extracted from the signed update. Maybe some bug was squashed.


Top
 Profile  
 
PostPosted: Thu Sep 26, 2013 9:42 am 
Offline

Joined: Wed Aug 21, 2013 2:20 pm
Posts: 38
So it's different after all...

Let me try I think I still have a spare 500GB hdd


Top
 Profile  
 
PostPosted: Thu Sep 26, 2013 10:41 am 
Offline

Joined: Wed Aug 21, 2013 2:20 pm
Posts: 38
No luck, still not getting any... :?

https://docs.google.com/file/d/0B3RJUVbE6jxWbUpWY2xaYXJlckE/edit?usp=sharing
U-Boot detects it:
Code:
Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
  Device 1: OK
Model: ST3500418AS                              Firm: CC34     Ser#:             9VM02P8L
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 476938.9 MB = 465.7 GB (976771055 x 512)


Loading from IDE device 1, partition 10: Name: hdb10


But Kernel cannot?
Code:
Intergrated Sata device found
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
physmap flash device: 80000 at ff800000
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040


And still getting the same error :(
Code:
VFS: Cannot open root device "sda7" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


Top
 Profile  
 
PostPosted: Thu Sep 26, 2013 10:49 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
Can you try the other sata connection?


Top
 Profile  
 
PostPosted: Thu Sep 26, 2013 11:33 am 
Offline

Joined: Wed Aug 21, 2013 2:20 pm
Posts: 38
stops...

Code:
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|  ** LOADER **
 ** MARVELL BOARD: DB-88F5182-LaCie LE

U-Boot 1.1.4 (Feb  9 2009 - 13:15:53) Marvell version: 2.4.9  LaCie : 1.00.0001

U-Boot code: 00200000 -> 0026FFF0  BSS: -> 00283280

Soc: 88F5182 A2 (DDR2)
CPU running @ 400Mhz
SysClock = 200Mhz , TClock = 166Mhz

DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  32bit width
[512kB@fff80000] Flash: 512 kB
Addresses 4M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (4M - 3M): Done

CPU : ARM926 (Rev 0)
88F5182 A2 streaming disabled

USB 0: host mode
USB 1: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Net:   egiga0 [PRIME]
POWER ON
Hit any key to stop autoboot:  0
mvEgigaInit: egiga0 mvEthPortEnable failed (error)
mvEgigaInit: egiga0 failed
Waiting for LUMP (2)
no lump receive; continuing

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
  Device 0: OK
Model: ST3500418AS                              Firm: CC34     Ser#:             9VM02P8L
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 476938.9 MB = 465.7 GB (976771055 x 512)


** Device 1 not available

** Device 1 not available
## Booting image at 00400000 ...
Bad Magic Number
mvEgigaInit: egiga0 mvEthPortEnable failed (error)
mvEgigaInit: egiga0 failed
Waiting for LUMP (0)



Top
 Profile  
 
PostPosted: Thu Sep 26, 2013 11:49 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
So u-boot insists on booting from device1? In this respect it differs from the 2Big and 5Big. These don't care, they just tkae the first kernel they can find.

Anyway, I've uploaded the kernels from update 2.2.8 here. You can write one of them directly to partition 6:
Code:
dd if=/path/to/uImage of=/dev/sdx6


Top
 Profile  
 
PostPosted: Thu Sep 26, 2013 1:52 pm 
Offline

Joined: Wed Aug 21, 2013 2:20 pm
Posts: 38
Yes, and LED will blink in red.

Thanks for the kernel. It boots now without turning off automatically bu I can't turn it off unless I unplug it. LED keeps on blinking in BLUE after booting.

Getting this:
https://docs.google.com/file/d/0B3RJUVbE6jxWSy1Sd0ZleVBLeUU/edit?usp=sharing

Code:
#### Started PatchManager ####
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
#### Running File System Check on Base Partition ###
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda9, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Error: snapshots/snaps dir not found. Should never come here
unionfs: unrecognized option 'delete'
unionfs: read_super: error while parsing options (err = -22)
mount: Mounting unionfs on /var/base failed: Invalid argument
/var/base is not a valid union.
/var/base is not a valid union.
mkdir: Cannot create directory `oldroot': Read-only file system
pivot_root: pivot_root: No such file or directory
/sbin/init: Kernel panic - not syncing: Attempted to kill init!
/sbin/init: 38: cannot open dev/console: No such file


Top
 Profile  
 
PostPosted: Thu Sep 26, 2013 3:41 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
Your link is wrong, I think.


Top
 Profile  
 
PostPosted: Fri Sep 27, 2013 12:27 am 
Offline

Joined: Wed Aug 21, 2013 2:20 pm
Posts: 38
Sorry, here's the correct one:

https://docs.google.com/file/d/0B3RJUVbE6jxWUGF6Q3NKWW41Y2c/edit?usp=sharing


Top
 Profile  
 
PostPosted: Fri Sep 27, 2013 8:14 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
Ah. Obviously this kernel is not intended for ' daily use', it has an initrd inside which contains a rootfs which only purpose is to apply the update. So the update sequence is: extract the file somewhere, put this kernel in charge, reboot. The new kernel then executes it initrd, which does the actual update, puts the old kernel back in charge (there is no other kernel available), and reboot again.

The good news is that this kernel recognizes the disk(s), so there has been some patching between the old kernel and this one. The EBD is supported by the vanilla kernel, so I build a recent one (3.10.10) for your EBD. You can test it. If it detects the disk well, you can just put some modern userland on sda7 (maybe sdb7, it could be that some strange name mangling is in effect in the old kernel, which means that using a vanilla kernel might be loaded from partition 6 of disk 1, while it expects it userland on partition 7 of disk 2. Unless you have only one disk)


Top
 Profile  
 
PostPosted: Fri Sep 27, 2013 12:45 pm 
Offline

Joined: Wed Aug 21, 2013 2:20 pm
Posts: 38
Kernel boots fine. So do I have to put in any image for sdb7?

FYI:
Code:
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|  ** LOADER **
 ** MARVELL BOARD: DB-88F5182-LaCie LE

U-Boot 1.1.4 (Feb  9 2009 - 13:15:53) Marvell version: 2.4.9  LaCie : 1.00.0001

U-Boot code: 00200000 -> 0026FFF0  BSS: -> 00283280

Soc: 88F5182 A2 (DDR2)
CPU running @ 400Mhz
SysClock = 200Mhz , TClock = 166Mhz

DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  32bit width
[512kB@fff80000] Flash: 512 kB
Addresses 4M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (4M - 3M): Done

CPU : ARM926 (Rev 0)
88F5182 A2 streaming disabled

USB 0: host mode
USB 1: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Net:   egiga0 [PRIME]
POWER ON
Hit any key to stop autoboot:  0
mvEgigaInit: egiga0 mvEthPortEnable failed (error)
mvEgigaInit: egiga0 failed
Waiting for LUMP (2)
no lump receive; continuing

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
  Device 0: OK
Model: Hitachi HDS722020ALA330                  Firm: JKAOA10D Ser#:       JK1120YAG26Y5P
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512)
  Device 1: OK
Model: Hitachi HDS722020ALA330                  Firm: JKAOA10D Ser#:       JK1120YAG275NP
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512)


Loading from IDE device 1, partition 10: Name: hdb10
  Type: U-Boot

** Bad Magic Number **

Loading from IDE device 1, partition 6: Name: hdb6
  Type: U-Boot
   Image Name:   Linux-3.10.10
   Created:      2013-09-27   7:34:05 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2202432 Bytes =  2.1 MB
   Load Address: 00008000
   Entry Point:  00008000
## Booting image at 00400000 ...
   Image Name:   Linux-3.10.10
   Created:      2013-09-27   7:34:05 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2202432 Bytes =  2.1 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK



Top
 Profile  
 
PostPosted: Fri Sep 27, 2013 12:52 pm 
Offline

Joined: Wed Aug 21, 2013 2:20 pm
Posts: 38
Does this seem to be normal? seems it halted again


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 73 posts ]  Go to page Previous  1, 2, 3, 4, 5  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group