Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Sun May 27, 2018 2:28 pm

All times are UTC+01:00




Post new topic  Reply to topic  [ 1 post ] 
Author Message
PostPosted: Wed Sep 16, 2009 3:16 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
hi all, looking for consensus & information...

Some of the uboots on our machines cannot read ext2/3 partitions that have 256 byte inodes. This size inode became default as of version e2fsprogs-1.40.5. So when using e2fsprogs-1.40.5 or later and invoking the normal
Code:
mkfs.ext3 /dev/sda3
it results in uboot not being able to read that partition.

Whatever box you have, if possible can you please post your :

- LinkStation model
- uboot version
- uboot build date
- any other pertinent info (custom uboot, stock uboot, etc).
- and of course if it can or can't read the 256 byte inode partitions when using mkfs.ext3 from e2fsprogs-1.40.5 or later

In particular we are trying to figure out which machines are affected by this, so that any partitions that an installer might automatically create would be _readable_ by uboot.

_________________
LS1 (foonas, nfs, Tranmission & p910nd print server, Firefly for my Roku)
LS-HG500 (Lenny)
Various LS-Pros v1,v2 (unbricked w/ serial & jtag)
KuroPro, LS2 & KuroHG (foonas)
Working on davysweather.dyndns.org lately...

=> wooohooo!
wooohooo!
Unknown command 'wooohooo!' - try 'help'


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 1 post ] 

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 2 guests


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 post attachments in this forum

Search for:
Powered by phpBB® Forum Software © phpBB Limited