fvdw-sl console - Formatting error on sda5

[whitnalj]

hi

I hope you can help.

trying to upgrade a 5big vs1 to 5x4tb drives.

have downloaded and installed fvdw-sl software.

selected install firmware. and selected UIMAGE- 26394-5BIG1-43-STANDALONE

all good .. until "There was an error formatting /dev/sda5. Installer will exit. Installation incomplete, disk will not boot"

which leaves me at "root@(none):"

any and all advice much appreciated!

[Jocko]

Hi whitnalj,

I created a new topic for your issue.

NB: It is better to create its topic than to spoil another one!

[whitnalj]

hi

here are the last lines of the log - does this shed any light on the problem?

Command (? for help):
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): OK; writing new GUID partition table (GPT) to /dev/sda.
The operation has completed successfully.
creating GPT partiton table succeeded
format partition 5
mke2fs 1.41.14 (22-Dec-2010)
mke2fs-ext3: No such device or address while trying to determine filesystem size
formatting sda5 failed
root@(none):/ #

[whitnalj]

hello again,

I have replaced the drive in bay 1 and have made progress beyond the formatting error.

I now get an error relating to the firmware image as per below

format partition 5
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
32128 inodes, 128456 blocks
1284 blocks (1.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67371008
16 block groups
8192 blocks per group, 8192 fragments per group
2008 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729

Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
formatting sda5 succeeded
writing kernel to partition 6
mkdir: can't create directory 'sda5': File exists
mounting sda 5 succeeded
getting kernel from tftp server
writing kernel to partition 6
3996+1 records in
3996+1 records out
2046104 bytes (2.0MB) copied, 0.634204 seconds, 3.1MB/s
writing kernel to partition 6 succeeded
Getting firmware image from tftp server
firmware disk image uploaded succesfully\n
Unpacking firmware image from archive
firmware disk image extracted succesfully\n
Adapting firmware image for 5big1\n
Transfer of firmware correction from tfp server succeeded, starting pacthing of firmware image
mkdir: can't create directory '/fvdw-sl': File exists
mounting firmware image succeeded
./
./etc/
tar: can't make dir ./etc: Input/output error
./etc/init.d/
tar: can't create directory './etc': Input/output error
tar: can't make dir ./etc/init.d: Input/output error
./etc/init.d/insert-modules
tar: can't create directory './etc/': Input/output error
tar: can't remove old file ./etc/: Input/output error
correcting firmware image for 5big1 failed
root@(none):/ #
root@(none):/ #

[fvdw]

You are still suffering from disk errors, you could give the command

Code: Select all

dmesg

after the installer script fails. I expect you will see many disk errors in the output. If that is the case then beside a bad disk it could be an unstable power supply causing disk failures, or a bad motherboard with damaged sata interface (not likely).

[simong]

Hi whitnalj,

I created a new topic for your issue.

NB: It is better to create its topic than to spoil another one!

Hi Jocko and All,

I am about to upgrade my 5big1 after my backup. Is this post suggesting that 5big1 would be able to support GPT to support a drive larger than 2T?

many thanks !

[Jocko]

Hi simong

Thank you for your posting.

No there is no change about GPT capability on a 5big1 : bootloader fails if the system disk has a gpt partition table (so sda)

[simong]

Hi simong

Thank you for your posting.

No there is no change about GPT capability on a 5big1 : bootloader fails if the system disk has a gpt partition table (so sda)

got it . thanks Jocko !

[whitnalj]

Hello,

thank you for advice and support

I ran dmesg after the installer failure and below is the end of the output

I am a novice here, but this doesnt look like hardware error?

VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 0
ata10: failed to resume link (SControl 0)
ata10: SATA link down (SStatus 0 SControl 0)
ata11: failed to resume link (SControl 0)
ata11: SATA link down (SStatus 0 SControl 0)
ata12: failed to resume link (SControl 0)
ata12: SATA link down (SStatus 0 SControl 0)
ata13: failed to resume link (SControl 0)
ata13: SATA link down (SStatus 0 SControl 0)
Freeing init memory: 888K
sda: sda1 < sda5 sda6 sda7 sda8 sda9 sda10 > sda2
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda5): using internal journal
EXT3-fs (sda5): mounted filesystem with ordered data mode
EXT3-fs: barriers not enabled
EXT3-fs (loop0): using internal journal
kjournald starting. Commit interval 5 seconds
EXT3-fs (loop0): mounted filesystem with ordered data mode
attempt to access beyond end of device
loop0: rw=32, want=262416, limit=131680
EXT3-fs error (device loop0): ext3_get_inode_loc: unable to read inode block - inode=32474, block=32801
attempt to access beyond end of device
loop0: rw=32, want=262416, limit=131680
EXT3-fs error (device loop0): ext3_get_inode_loc: unable to read inode block - inode=32474, block=32801
attempt to access beyond end of device

the last 2 lines are then repeated identically about 10 times

I am afraid i have no idea what to do next?

[Jocko]

Hi whitnalj,

As fs on sda5 is just formatted that would mean you have have an disk nearly to be dead (old age)

So I advice to use tools of your disk manufacturer to do a deep scan from a laptop.

NB: If you have another disk (even with a small size) you can try to initialize it (to check if it is not a hardware issue on your NAS)