Failed update of v2.2.3 firmware Drive don't show up anymore

braveheartbe
Posts: 16
Joined: Thu Jan 26, 2012 9:11 am

Re: Failed update of v2.2.3 firmware Drive don't show up any

Post by braveheartbe » Sat Jan 28, 2012 4:10 pm

So,
I finally got my disks inside the Mac<
"sfdisk -l gives":
Disk /dev/sda: 243201 cylinders, 255 heads, 63 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/sda: unrecognized partition table type
No partitions found

Disk /dev/sdb: 243201 cylinders, 255 heads, 63 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/sdb: unrecognized partition table type
No partitions found


"sudo cat /proc/partitions" gives:
major minor #blocks name

7 0 683116 loop0
8 0 1953514584 sda
8 16 1953514584 sdb


Ideas for the next step?
any repair command or am I good for a clean install?
Last edited by braveheartbe on Sat Jan 28, 2012 5:41 pm, edited 1 time in total.

Mijzelf
Posts: 6226
Joined: Mon Jun 16, 2008 10:45 am

Re: Failed update of v2.2.3 firmware Drive don't show up any

Post by Mijzelf » Sat Jan 28, 2012 4:43 pm

Testdisk might be able to recreate your partition table.

I wonder how this could happen, both partition tables wiped.

braveheartbe
Posts: 16
Joined: Thu Jan 26, 2012 9:11 am

Re: Failed update of v2.2.3 firmware Drive don't show up any

Post by braveheartbe » Sat Jan 28, 2012 5:33 pm

Okay,
I'm currently running testdisk
I'll keep you posted

braveheartbe
Posts: 16
Joined: Thu Jan 26, 2012 9:11 am

Re: Failed update of v2.2.3 firmware Drive don't show up any

Post by braveheartbe » Sat Jan 28, 2012 8:18 pm

A little update:
here some commands I ran and some outputs:

SDB

Linux 33 1 1 33 252 59 15872
Linux RAID 33 1 1 33 254 61 16000 [md0]
Linux 34 1 1 139 252 18 1702656
Linux RAID 34 1 1 33 254 20 1702784 [md1]
Linux 140 1 1 248 251 14 1750784

SDC
Linux 33 1 1 33 252 59 15872
Linux RAID 33 1 1 33 254 61 16000 [md0]
Linux 34 1 1 139 252 18 1702656
Linux RAID 34 1 1 33 254 20 1702784 [md1]
Linux 140 1 1 248 251 14 1750784
Linux RAID 140 1 1 248 253 16 1750912 [md2]
Linux 250 0 1 486151 252 47 7806015488

sudo cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : inactive sdb5[1](S)
875392 blocks

sudo mdadm --assemble --scan
mdadm: No arrays found in config file or automatically


Not sure what to do next...

sfdisk -l gives now:


Disk /dev/sdb: 243201 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 140 248 109 875542+ 5 Extended
/dev/sdb2 0 - 0 0 0 Empty
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty
/dev/sdb5 140+ 248 109- 875511 83 Linux

Disk /dev/sdc: 243201 cylinders, 255 heads, 63 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
/dev/sdc: unrecognized partition table type
No partitions found


Thanks for your advice

Mijzelf
Posts: 6226
Joined: Mon Jun 16, 2008 10:45 am

Re: Failed update of v2.2.3 firmware Drive don't show up any

Post by Mijzelf » Sat Jan 28, 2012 9:14 pm

braveheartbe wrote:here some commands I ran and some outputs:
SDB
Linux 33 1 1 33 252 59 15872
Linux RAID 33 1 1 33 254 61 16000
[md0]Linux 34 1 1 139 252 18 1702656
Linux RAID 34 1 1 33 254 20 1702784
[md1]Linux 140 1 1 248 251 14 1750784
I must admit that I'm not sure what the command could have been.

Somehow SDC seems to give more data than SDB, but sfdisk tells that sdc has no valid partition table, while sdb has. I cannot connect these information.

What is the goal? Do you want to rescue your data, or do you want to revive your nas?

braveheartbe
Posts: 16
Joined: Thu Jan 26, 2012 9:11 am

Re: Failed update of v2.2.3 firmware Drive don't show up any

Post by braveheartbe » Sat Jan 28, 2012 9:24 pm

Mijzelf wrote:
braveheartbe wrote:here some commands I ran and some outputs:
SDB
Linux 33 1 1 33 252 59 15872
Linux RAID 33 1 1 33 254 61 16000
[md0]Linux 34 1 1 139 252 18 1702656
Linux RAID 34 1 1 33 254 20 1702784
[md1]Linux 140 1 1 248 251 14 1750784
I must admit that I'm not sure what the command could have been.
This is the first output of sfdisk before running the deep analysis.
At this moment, if I can revive my NAS, I'll be more than happy

braveheartbe
Posts: 16
Joined: Thu Jan 26, 2012 9:11 am

Re: Failed update of v2.2.3 firmware Drive don't show up any

Post by braveheartbe » Sun Jan 29, 2012 9:08 am

I believe I've spent enough time on this.
Therefore my last action the next couple of hours will be to try an install of the default 2Big2 image.
And if unsuccessfull it's going back to LaCie next week.

Now up to a good reading before really messing the thing up! 8-)

Or should I take this opportunity to install an image with all the "extra's"?
Please be free to point me into the right direction.
Correction: after some reading: http://lacie.nas-central.org/wiki/Categ ... om_capsule
I came to the conclusion that I still am too much a newbie to perform this, at the current time :roll:
Thus, going for the standard installation

braveheartbe
Posts: 16
Joined: Thu Jan 26, 2012 9:11 am

Re: Failed update of v2.2.3 firmware Drive don't show up any

Post by braveheartbe » Sun Jan 29, 2012 9:58 am

Can anybody help me with the creation of the partitions (with fdisk or gparted?), please?
gparted doesn't give me the blocks, so I don't know what size I must give...
I already get a warning message from fdisk:
The device presents a logical sector size that is smaller than
the physical sector size. Aligning to a physical sector (or optimal
I/O) size boundary is recommended, or performance may be impacted.

What can I do to solve this?

Me giving up on this, as I am not up to the task.

Mijzelf thanks a lot for your efforts in helping me.
I'll send the device back to LaCie and will post the conclusion within 2 or 3 weeks...

Mijzelf
Posts: 6226
Joined: Mon Jun 16, 2008 10:45 am

Re: Failed update of v2.2.3 firmware Drive don't show up any

Post by Mijzelf » Sun Jan 29, 2012 11:57 am

braveheartbe wrote:The device presents a logical sector size that is smaller than the physical sector size. Aligning to a physical sector (or optimalI/O) size boundary is recommended, or performance may be impacted.
Are this the original disks? :shock:
This means it are 'Advanced format' disks, internally using sectors of 4kB, instead of the standard 512 bytes. When the partitions don't start at multiplies of 4kB, the disk internally has to compensate for that, which costs throughput. That can be ignored, but I think the difference is noticeable in a 2Big2.
Too bad the original partitiontable was damaged. I'm wondering if Lacie has taken this into account.
braveheartbe wrote:gparted doesn't give me the blocks, so I don't know what size I must give...
The exact size isn't important, as long as both disks are equal, and the sizes are just 'big enough'. 1 block is 1kB. Just create the partitions slightly bigger, to be safe. I *think* gparted will automatically do the 'advanced format' aligning, so that's no problem too.
Or should I take this opportunity to install an image with all the "extra's"?
You can't. The 'extra's' are installed on a working device, so you first have to get it working.
Mijzelf thanks a lot for your efforts in helping me.
You're welcome.
I'll send the device back to LaCie and will post the conclusion within 2 or 3 weeks...
Did Lacie already give you this term?

braveheartbe
Posts: 16
Joined: Thu Jan 26, 2012 9:11 am

Re: Failed update of v2.2.3 firmware Drive don't show up any

Post by braveheartbe » Sun Jan 29, 2012 4:04 pm

Mijzelf wrote:Are this the original disks? :shock:
This means it are 'Advanced format' disks, internally using sectors of 4kB, instead of the standard 512 bytes. When the partitions don't start at multiplies of 4kB, the disk internally has to compensate for that, which costs throughput. That can be ignored, but I think the difference is noticeable in a 2Big2.
Too bad the original partitiontable was damaged. I'm wondering if Lacie has taken this into account.
Yes, they are original disks
Mijzelf wrote:The exact size isn't important, as long as both disks are equal, and the sizes are just 'big enough'. 1 block is 1kB. Just create the partitions slightly bigger, to be safe. I *think* gparted will automatically do the 'advanced format' aligning, so that's no problem too.
What I found confusing is the different outputs between fdisk / sfdisk and gparted commands.
When creating the mbr, using this: gzip -dc /full/path/to/mbr+label.gz | dd of=/dev/sdb
gparted and fdisk would give me different output than sfdisk
So I ended up confused, not knowing which to trust...
Mijzelf wrote:Did Lacie already give you this term?
Yes, if I was to first send the device to Lacie Belgium: 2 to 3 weeks
If I am sending it directly to France: 10 days.

Post Reply