readonly file system - can't repair

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

readonly file system - can't repair

Postby irobot » Sun Mar 08, 2015 4:57 am

Need some help here. something got corrupted on my boot usbflash drive on my GoFlex Net. It was working fine until just now I noticed really slow response to ssh login, I enabled netconsole for kernel and got "cannot write to swap device" message repeating non stop. Shutdown the GFN, inserted the usbflash drive in a ubuntu pc, but it does not mount it. complains of read only.

fsck complains of: fsck.ext3: Read-only file system while trying to open /dev/sdc
It will not mount read-write.

here's the out put of tune2fs -l /dev/sdc1: (while inserted in ubuntu pc)

$this->bbcode_second_pass_code('', '
tune2fs 1.42 (29-Nov-2011)
Filesystem volume name: urootfs
Last mounted on: /
Filesystem UUID: 73093581-18d5-4c71-b06a-d696561f66a4
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 930240
Block count: 3714304
Reserved block count: 185715
Free blocks: 2963948
Free inodes: 863691
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 906
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8160
Inode blocks per group: 510
Filesystem created: Sat Feb 21 14:37:46 2015
Last mount time: Wed Dec 31 18:00:12 1969
Last write time: Wed Dec 31 18:00:10 1969
Mount count: 5
Maximum mount count: -1
Last checked: Sat Feb 21 14:37:46 2015
Check interval: 0 (<none>)
Lifetime writes: 7361 MB
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: b6e2b07f-9be0-44f8-9d70-3515a5889224
Journal backup: inode blocks
')

Here's netconsole kernel output:
$this->bbcode_second_pass_code('', '
[ 18.903332] console [netcon0] enabled
[ 18.907026] netconsole: network logging started
[ 18.911725] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 18.920008] Freeing unused kernel memory: 268K (c074d000 - c0790000)
[ 18.977404] systemd-udevd[61]: starting version 195
[ 19.247524] sd 2:0:0:0: [sdb] 31950720 512-byte logical blocks: (16.3 GB/15.2 GiB)
[ 19.286752] sd 2:0:0:0: [sdb] Write Protect is on
[ 19.304943] sd 2:0:0:0: [sdb] Mode Sense: 43 00 80 00
[ 19.337781] sdb: sdb1 sdb2
[ 20.305634] EXT4-fs (sdb1): mounting ext3 file system using the ext4 subsystem
[ 20.314450] EXT4-fs (sdb1): INFO: recovery required on readonly filesystem
[ 20.321453] EXT4-fs (sdb1): write access unavailable, cannot proceed

')

Is this fixable? if so how?
irobot
 
Posts: 32
Joined: Wed Oct 23, 2013 2:28 am

Re: readonly file system - can't repair

Postby moonman » Sun Mar 08, 2015 6:39 am

The drive needs to be unmouned for fsck to perform error correction.
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: readonly file system - can't repair

Postby irobot » Sun Mar 08, 2015 7:13 am

Its not mounted. When I insert the usb flash drive in my ubuntu PC it gives mount error:

Error mounting: mount: block device /dev/sdc1 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog -try dmesg | tail or so.

if I do ummount /dev/sdc1 it says its not mounted
irobot
 
Posts: 32
Joined: Wed Oct 23, 2013 2:28 am

Re: readonly file system - can't repair

Postby moonman » Sun Mar 08, 2015 10:15 am

Then your flash drive probably died. Try formatting it and reinstalling but I would just replace it, preferably by installyng on media that can take many write cycles.
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: readonly file system - can't repair

Postby hydro » Sun Mar 08, 2015 2:39 pm

$this->bbcode_second_pass_quote('irobot', '
')mount: wrong fs type, bad option, bad superblock on /dev/sdc1,

Try use one of the backup superblocks
$this->bbcode_second_pass_code('', '
e2fsck -b 32768 /dev/sdc1
')
VDR on DockStar / Pogoplug E02: http://linux.bplaced.net/
hydro
 
Posts: 210
Joined: Wed Jun 15, 2011 2:03 pm
Location: Germany

Re: readonly file system - can't repair

Postby irobot » Sun Mar 08, 2015 5:26 pm

tried e2fsck -b 32768 /dev/sdc1

no luck .
e2fsck: Read-only file system while trying to open /dev/sdc1
this was a brand new PNY usbflash. fubar'd in 4 weeks.

Luckily i have a early back up to start from. Arrghhhhh!!
irobot
 
Posts: 32
Joined: Wed Oct 23, 2013 2:28 am


Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 9 guests

cron