fdisk broken? [SOLVED]

Ask questions about Arch Linux ARM. Please search before making a new topic.

fdisk broken? [SOLVED]

Postby caderoux » Wed Oct 17, 2012 1:14 am

$this->bbcode_second_pass_code('', '[root@alarm ~]# fdisk -l
fdisk: cannot open /dev/mtdblock0: Input/output error
')

This is on two different PogoPlug V4 which are up to date, one a fairly clean new installation.
Last edited by caderoux on Sun Nov 25, 2012 4:54 am, edited 1 time in total.
caderoux
 
Posts: 44
Joined: Sat Jun 30, 2012 3:46 am

Re: fdisk broken?

Postby moonman » Wed Oct 17, 2012 2:41 am

I get the same. Don't worry about it. Just do "fdisk -l /dev/sda", "fdisk -l /dev/sdb" and so on
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: fdisk broken?

Postby bodhi » Wed Oct 17, 2012 3:16 am

Agreed! I've been having these for some of the plugs, but not all. My Dockstar spits out the errors whenever I do "fdisk -l" or blkid. But my GoFlex Home does not. Same UBoot was installed on both. I've searching for a clear answer for this, but nobody seems to know. Probably because nobody cares to get to the bottom of this.
bodhi
 
Posts: 225
Joined: Sat Aug 13, 2011 10:06 am

Re: fdisk broken?

Postby Socaltom » Wed Oct 17, 2012 11:04 pm

Check error.log in /var/log. Mine recently starting spitting out lots of mtd block errors. What changed?
Tom
used to be owned by me
Pink Pogo V2, Black Pogo V3, Zyxel NAS 325 v1,
used to be Adminstrator for
Goflex net, Black V3, Black V2
Now I have a couple of raspberry pi ( 3+ and 4)
Socaltom
 
Posts: 571
Joined: Thu Apr 07, 2011 2:21 pm
Location: The left side

Re: fdisk broken?

Postby caderoux » Thu Oct 18, 2012 12:20 am

$this->bbcode_second_pass_quote('moonman', 'I') get the same. Don't worry about it. Just do "fdisk -l /dev/sda", "fdisk -l /dev/sdb" and so on


When multiple devices are added of different sizes, that doesn't really help. If this was a permanent thing, I'd be fine, but I had plugged in some USB plugs to dump some TCP logs and needed to find the correct device.

In the end, I used $this->bbcode_second_pass_code('', 'ls -l /dev/disk/by-path') to help a little (because I knew one stick had more partitions) - but fdisk shows more useful information in one shot.

You could use something like this, I guess, until the problem with fdisk is fixed:

$this->bbcode_second_pass_code('', 'ls -l /dev/disk/by-path \
| perl -ne '/^.*\/(.*)$/ && print "fdisk -l /dev/$1\n"' \
| source /dev/stdin
')
caderoux
 
Posts: 44
Joined: Sat Jun 30, 2012 3:46 am

Re: fdisk broken?

Postby Socaltom » Sat Nov 24, 2012 3:11 am

I just reinstalled using the current FS tar and low and behold, I get the same error. When I updated over the top of my previous FS I got a lot of mtd block complaining, but fdisk still worked.
Tom
used to be owned by me
Pink Pogo V2, Black Pogo V3, Zyxel NAS 325 v1,
used to be Adminstrator for
Goflex net, Black V3, Black V2
Now I have a couple of raspberry pi ( 3+ and 4)
Socaltom
 
Posts: 571
Joined: Thu Apr 07, 2011 2:21 pm
Location: The left side

Re: fdisk broken?

Postby xenoxaos » Sun Nov 25, 2012 4:46 am

I reconfigured the kernel. pacman -Syu and you should no longer get any mtdblock errors
Arch Linux ARM exists and continues to grow through community support, please donate today!
xenoxaos
Developer
 
Posts: 323
Joined: Thu Jan 06, 2011 1:45 am

Re: fdisk broken?

Postby caderoux » Sun Nov 25, 2012 4:53 am

$this->bbcode_second_pass_quote('xenoxaos', 'I') reconfigured the kernel. pacman -Syu and you should no longer get any mtdblock errors


Verified - all good.
caderoux
 
Posts: 44
Joined: Sat Jun 30, 2012 3:46 am

Re: fdisk broken? [SOLVED]

Postby moonman » Sun Nov 25, 2012 10:08 am

Just compiled the new kernel 3.6.7 with this patch:

$this->bbcode_second_pass_code('', 'pacman -U http://music4dance.mine.nu/Downloads/ArchLinuxArm/linux-kirkwood-3.6.7-0-arm.pkg.tar.xz http://music4dance.mine.nu/Downloads/ArchLinuxArm/linux-headers-kirkwood-3.6.7-0-arm.pkg.tar.xz
')
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am

Re: fdisk broken?

Postby bodhi » Sun Nov 25, 2012 12:02 pm

$this->bbcode_second_pass_quote('xenoxaos', 'I') reconfigured the kernel. pacman -Syu and you should no longer get any mtdblock errors


xenoxaos, what was the reason for this error? how did you reconfigure the kernel?

Thx
bodhi
 
Posts: 225
Joined: Sat Aug 13, 2011 10:06 am
Top

Next

Return to User Questions

Who is online

Users browsing this forum: No registered users and 3 guests