Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 02 Sep 2014, 23:09
All times are UTC - 4
 Forum index » House Training » Users ( For the regulars )
strange disk behaviour
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [4 Posts]  
Author Message
bigearsbilly

Joined: 24 Jul 2009
Posts: 2

PostPosted: Tue 04 Aug 2009, 17:28    Post subject:  strange disk behaviour
Subject description: bsd partition seen as ext2
 

I am having some weirdness with a BSD partition.

I get this on boot up:
Quote:
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
EXT2-fs error (device sdb4): ext2_check_page: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
EXT2-fs error (device sdb4): ext2_readdir: bad page in #2
EXT2-fs error (device sdb4): ext2_readdir: bad page in #2
EXT2-fs error (device sdb4): ext2_readdir: bad page in #2
EXT2-fs error (device sdb4): ext2_readdir: bad page in #2
EXT2-fs error (device sdb4): ext2_readdir: bad page in #2
EXT2-fs error (device sdb4): ext2_readdir: bad page in #2


I have two identical hard drives and a total of 4 BSD partitions
fdisk shows them as FreeBSD.
gparted shows FreeBSD as unknown
except the one in question it shows as ext2???
I've deleted them, re fdisked, made a new fs??
still comes up weird on that one.
any ideas?




Quote:
# fdisk -l


Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 6527 52428096 a5 FreeBSD
Partition 1 does not end on cylinder boundary.
/dev/sda2 6528 13054 52428127+ bf Solaris
Partition 2 does not end on cylinder boundary.
/dev/sda3 13055 19581 52428127+ a5 FreeBSD
Partition 3 does not end on cylinder boundary.
/dev/sda4 19582 30401 86911650 83 Linux
Partition 4 does not end on cylinder boundary.

Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 261 2096451 82 Linux swap / Solaris
Partition 1 does not end on cylinder boundary.
/dev/sdb2 * 262 9398 73392952+ a5 FreeBSD
Partition 2 does not end on cylinder boundary.
/dev/sdb3 9399 15925 52428127+ 83 Linux
Partition 3 does not end on cylinder boundary.
/dev/sdb4 15926 30401 116278470 a5 FreeBSD



[/color]
[/quote]
Back to top
View user's profile Send private message 
Bruce B


Joined: 18 May 2005
Posts: 11092
Location: The Peoples Republic of California

PostPosted: Tue 04 Aug 2009, 21:24    Post subject:  

You can format a partition without changing the type ID
You can change the type ID without formatting the partition

I think they should correspond. Do they?

Also the cylinder boundary endings don't look a happy sight. What's with that?

_________________
New! Puppy Linux Links Page
Back to top
View user's profile Send private message 
bigearsbilly

Joined: 24 Jul 2009
Posts: 2

PostPosted: Wed 05 Aug 2009, 04:02    Post subject:  

It's a mystery.
why is it FreeBSD on fdisk but non on gparted?
I don't know any other way to change the ID but fdisk and then put a new fs on it.
odd.

as for the partition boundaries, dunno.
I've never had any microsoft on my computers for
about 10 years so I cannot blame them.
I generally use fdisk to partition, though maybe I was using
solaris at the time of cuting them up.

I'll have to dig around and see how puppy checks the drives, on startup
obviously not fdisk.
Back to top
View user's profile Send private message 
sindi

Joined: 16 Aug 2009
Posts: 395

PostPosted: Sat 06 Oct 2012, 14:40    Post subject: EXT2-fs error (device loop1): ext2_readdir: bad page in..
Subject description: pulp linux boot error messages
 

pulp 0.1 (2.6.21.7 kernel, based on puppy 4.2 I think).

Pulp is installed frugally on /dev/hda7. Works mostly despite errors.
Possibly related to Youtube getting 'stuck' after a while (starts over,
stops after 2 sec) and I need to restart the browser (first I clear
history). Sometimes when I switch from console to X, the top half of X
is black with a few colored streaks and I need to reboot.

Error messages at boot time:

EXT2-fs error (device loop1): ext2_check_page: bad entry in directory
#18448: unaligned directory entry - offset=0, inode=48896, rec_len=3329, name_len=84
A similr line for #18461 with other numbers for inode etc.

EXT2-fs error (device loop1): ext2_readdir: bad page in #18461 (and 48)

There is some junk in /lost+found all from 2011-04-07.

From another operating system located on another partition I ran efs2ck
and it found no problems. e2fsck /dev/hda7
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 1 [4 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Users ( For the regulars )
Jump to:  

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 vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0508s ][ Queries: 11 (0.0036s) ][ GZIP on ]