Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Tue Jan 16, 2018 4:06 pm

All times are UTC+01:00




Post new topic  Reply to topic  [ 187 posts ]  Go to page Previous 19 10 11 12 13 Next
Author Message
PostPosted: Fri Feb 27, 2009 2:45 pm 
Offline
Total Newbie

Joined: Fri Feb 27, 2009 1:20 pm
Posts: 1
Location: amsterdam
antime wrote:
I've got an LS2 running FreeLink 3.1, and I haven't been able to get a 2.6.22 kernel working. I've installed U-Boot which works, and I can boot the old 2.4.20 kernel, but booting any kind of 2.6.22 kernel (downloaded from nas-central or selfbuilt) results in a system that doesn't respond to anything. Hints on where to start looking appreciated.
[/code]


I found an easy solution for that problem: After following Endy's instructions I could boot the 2.4 stock kernel from u-boot but the 2.6 would not come alive. I suspected that the 2.6 kernel might not mount the root filesystem because of the mangled Buffalo superblock id on hda1. So I compiled the Fix_ext2_magic tool natively on my FreeLink'ed LS2, stopped all unneeded daemons, remounted the root fs readonly, ran the fix, went into u-boot and voila, 2.6.22 comes up just perfect. Meanwhile u-boot is flashed on my box, 2.6.22 is renamed to be the default kernel and Debian is upgraded to Lenny. The Linkstation is compiling a new kernel right now following the instructions from LinuxNotIncluded (which takes its time...)

Cheers :up:
Stefan

_________________
LS2 with U-Boot, Kernel 2.6.22.ls2, Debian Lenny
LSLIVE V2 davy_gravy armel rootfs, vanilla kernel 2.6.29.1, Debian Lenny


Top
   
PostPosted: Thu Mar 05, 2009 12:02 am 
Offline
Newbie

Joined: Thu Mar 01, 2007 7:43 pm
Posts: 8
davy_gravy wrote:
What bootargs, options and commands are you using it boot the 2.6 kernel? Please post... :)

None other than the ones listed in the U-Boot environment and kernel config.

Quote:
Also, any chance that it is actually booting but for some reason you are not looking at the right IP?

Well, the logs show that it's definitely booting and the watchdog daemon seems to work as the box doesn't reboot after the timeout. The machine works perfectly fine when I boot the old 2.4.20 kernel.

Quote:
Did you try a network scanner like NMAP?

Yes, and not a peep.

stefanw wrote:
So I compiled the Fix_ext2_magic tool natively on my FreeLink'ed LS2, stopped all unneeded daemons, remounted the root fs readonly, ran the fix, went into u-boot and voila, 2.6.22 comes up just perfect.

That's not the problem in my case as I fixed the magic number years ago.

Quote:
The Linkstation is compiling a new kernel right now following the instructions from LinuxNotIncluded (which takes its time...)

Tell me about it, I've probably done it a dozen times already trying to get the 2.6 kernel working. Still not as slow as the time I decided to rebuild all of Qt and KDE on a 200 MHz Pentium. After some 30 hours I decided it was a monumentally stupid idea and aborted the build.

Anyway, I got myself a Kurobox Pro to replace the LS2 so this is not really a relevant issue anymore. If someone would like to track down the problem I can run some tests, but otherwise the LS2 is destined for the back of my closet.


Top
   
PostPosted: Thu Mar 05, 2009 1:50 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
antime wrote:
...

Anyway, I got myself a Kurobox Pro to replace the LS2 so this is not really a relevant issue anymore. If someone would like to track down the problem I can run some tests, but otherwise the LS2 is destined for the back of my closet.

well, if at any time closet become garbage can, please let me know ... I'll find a good home for it... :D


Also, if you simply post your bootargs & bootcommand, that may help.

I'm thinking that the first time I tried to boot an LS2 on the 2.6. kernel I may have seen something like this... I think I may have ended up writing my own values for bootcmd and bootargs... or adjusted them...

Also, I have a 2.6.23.17 kernel with all the bells & whistles... if you are looking for just a bit of an update.

I crosscompiled it w/ OpenEmbedded.

_________________
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
   
PostPosted: Wed Jun 03, 2009 1:51 am 
Offline
Newbie
User avatar

Joined: Wed Jun 03, 2009 1:37 am
Posts: 6
So thanks to the great work that has been done here I had my LS2 running Freelink with UBoot flashed on to it. All was great until one day I found the boot partition had gone bad. Now I have a LS2 with UBoot and all partitions are wiped clean.

Is it possible to write the Freelink images to the hard drive directly from say another linux box and then reinsert the drive into the LS2?

UBoot works great but I suspect I can no longer use the Freelink firmware update program.

If this is not possible does that mean I would have to find a way to reflash the original loader on to the LS2?

I am looking for the best way to get back to having a LS2 with Freelink and UBoot. Then I can move on to trying for a 2.6 kernel.

_________________
Linkstation HD-H250LAN (LS2 mipsel)


Top
   
PostPosted: Wed Jun 03, 2009 2:01 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
the answer is yes, but you might have to jump through a few hoops...

if I remember correctly, the installer by default mangles some bits when it sets up the partitions, so they aren't readable as a normal ext2/3 partition would be. If I remember correctly, you may have to run the program "fix_ext2_magic" on that partition in order to be able to mount it normally. and then untar the freelink tmpimage.gz on it.

Another option would be to tftp-boot your LS2, use mkfs.ext3 to set up your hda1 fresh, and then untar the freelink tmpimage.gz on it.

I'm thinking that foonas-em is the only tftp-boot image we have for the LS2.

EDIT:

I was in a rush to answer your post, and I now reread it...

LM12 wrote:
1. So thanks to the great work that has been done here I had my LS2 running Freelink with UBoot flashed on to it. All was great until one day I found the boot partition had gone bad. Now I have a LS2 with UBoot and all partitions are wiped clean.

2. Is it possible to write the Freelink images to the hard drive directly from say another linux box and then reinsert the drive into the LS2?

3. UBoot works great but I suspect I can no longer use the Freelink firmware update program.

4. If this is not possible does that mean I would have to find a way to reflash the original loader on to the LS2?

I am looking for the best way to get back to having a LS2 with Freelink and UBoot. Then I can move on to trying for a 2.6 kernel.

1. This is a hdd w/ no partitions on it? Just a blank drive?

2. Yes, as long as the partitions are normal ext2/3. If the partitions were created by the Buffalo LInkStation Updater, then you'd need to run the fix_ext2_magic program on it to unmangle the partitions bits.

3. That is correct, uboot makes it impossible (as far as I know) to use the LS Updater program on it. But you can still tftp-boot it with foonas-em. http://foonas.org/index.php/Foonas-em:TFTPBoot-lsmipsel

4. Uboot is so good (in my opinion) that there is no reason to go back to the original bootloader. That is just my opinion, though.

_________________
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
   
PostPosted: Wed Jun 03, 2009 8:01 am 
Offline
Newbie
User avatar

Joined: Wed Jun 03, 2009 1:37 am
Posts: 6
Thanks for the quick response davy_gravy.

I did have a blank hard drive. I figured if I am going to write the images directly I might as well size the partitions to something that made more sense for what I want to do with the LS2. I stuck the hard drive in my KUbuntu box and I now have sdb1 - 36GB, sdb2 - 2.5GB, and sdb3 - 210GB.

tmpimage.tgz was then uncompressed to sdb1 which gives the file structure you would expect to see in / . All except for /boot.

I downloaded kernel_and_modules_for_lsmipsel_dg_v1-2.6.23.17.tar.gz and copied boot to /, and moved the 2.6.23.17 modules directory into /lib/modules.

sdb1 now seems to have the system files and a kernel image. I also setenv hdfile /boot/vmlinux-2.6.23.17 in uboot, but I am missing something here as uboot reports an error.

Code:
Loading 0:1:/boot/vmlinux-2.6.23.17

** Unable to read "/boot/vmlinux-2.6.23.17" from ide 0:1 **
## Booting image at bfc40000
## No elf image at address Oxbfc40000


Perhaps I will have better ideas tomorrow. I can only take the LS2 apart so many times in a given day. :)

_________________
Linkstation HD-H250LAN (LS2 mipsel)


Top
   
PostPosted: Wed Jun 03, 2009 11:35 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
LM12 wrote:
... sdb1 - 36GB, sdb2 - 2.5GB, and sdb3 - 210GB.

tmpimage.tgz was then uncompressed to sdb1 which gives the file structure you would expect to see in / . All except for /boot.

I downloaded kernel_and_modules_for_lsmipsel_dg_v1-2.6.23.17.tar.gz and copied boot to /, and moved the 2.6.23.17 modules directory into /lib/modules.

sdb1 now seems to have the system files and a kernel image. I also setenv hdfile /boot/vmlinux-2.6.23.17 in uboot, but I am missing something here as uboot reports an error.

Code:
Loading 0:1:/boot/vmlinux-2.6.23.17

** Unable to read "/boot/vmlinux-2.6.23.17" from ide 0:1 **
## Booting image at bfc40000
## No elf image at address Oxbfc40000


Perhaps I will have better ideas tomorrow. I can only take the LS2 apart so many times in a given day. :)


Looks like you are very close.

Try this: while in the uboot console, experiment with the ext2ls command and see if it can sense what is in /boot
Code:
ext2ls ide 0:1 /boot


This command should list the contents of /boot

It may give a clue of what is going on.

I'm guessing that your fstab is set up with hda[1,2,3], right? (although your Kubuntu box listed them as sdb[1,2,3] ...?

_________________
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
   
PostPosted: Wed Jun 03, 2009 10:24 pm 
Offline
Betatester
User avatar

Joined: Thu Jul 14, 2005 4:38 pm
Posts: 941
Location: England
I think it is possible to use the foonas-em web browser (either tftp or installed on hdd) and then use that to install freelink, thus repartitioning hdd and getting it running, than install whatever kernel.


Top
   
PostPosted: Fri Jun 05, 2009 9:24 am 
Offline
Newbie
User avatar

Joined: Wed Jun 03, 2009 1:37 am
Posts: 6
ext2ls ide 0:1 /boot

In UBoot, checking for the /boot directory ( or any of the directories for that matter ) did not work.

ext2ls ide 0:1 / did work. It didn't display any directories under / , but it didn't spit back any errors either.

Just to clear my thoughts, I use ext3 for my filesystem and had partitioned the LS2 with this filesystem as well. I see we are using ext2ls; is a ext2 filesystem required?

As it is, it had no problem with / , but could not find any of the directories on ide 0:1.

_________________
Linkstation HD-H250LAN (LS2 mipsel)


Top
   
PostPosted: Fri Jun 05, 2009 12:40 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
This is odd. You may want to try running fdisk on it again, and then mkfs.ext3.

UBoot should read either ext2 or ext3 equally well.

_________________
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
   
PostPosted: Sun Jun 07, 2009 4:53 am 
Offline
Newbie
User avatar

Joined: Wed Jun 03, 2009 1:37 am
Posts: 6
fdisk

I went ahead and ran fdisk again recreating the three partitions I mentioned earlier. The boot flag is set on sdb1, and sdb2 reads as a swap partition type 82. sdb1 and sdb3 are both ext3 (83) filesystems.

I double checked the fstab file from the tmpimage.tgz that I have been uncompressing onto sdb1. It does reference the hard drives using hda, sdb just being the reference when I work on the hard drive while it's in my kubuntu box.

This all seems like I know kind of what I'm doing until I try and erase an extra copy of /lib/modules/2.6....... from the kernel download and miss type it as rm /lib ..... as root. :(

Chuck one up for not enabling your root account in KUbuntu. I should have taken a nap instead. Yes a separate /home partition saved me, but still what a stupid mistake to make.

This all goes to the reason I was reinstalling KUbuntu while the LS2 hard drive was still installed. At the end of installation the grub bootloader detects the system files on sdb1 and added a boot entry! So the partition and files seem fine while it is in the KUbuntu box, but when I put it back in the LS2, Uboot comes up but can not boot the system.

Maybe I am missing some important boot argument or something.....not sure.

Below is the information for the LS2 I got from UBoot, I just can't seem to get to the next step. I'm not quite sure what my next direction will be here.

Another thought....is there any partition size limits when using UBoot? My boot partition is 36GB as it is the / mount point.

Code:
=> boot
boot
Loading 0:1:/boot/vmlinux-2.6.23.17

** Unable to read "/boot/vmlinux-2.6.23.17" from ide 0:1 **
## Booting image at bfc40000 ...
## No elf image at address 0xbfc40000

=> ext2ls ide 0:1
ext2ls ide 0:1
=> ext2ls ide 0:1 /
ext2ls ide 0:1 /
=> ext2ls ide 0:1 /boot
ext2ls ide 0:1 /boot
** Can not find directory. **
** Error ext2fs_ls() **


==> bdinfo
bdinfo
boot_params = 0x83E4FFB0
memstart    = 0x80000000
memsize     = 0x04000000
flashstart  = 0xBFC00000
flashsize   = 0x00400000
flashoffset = 0x0002837C
ethaddr     = 00:0D:0B:74:B4:37
ip_addr     = 192.168.11.150
baudrate    = 57600 bps

=> flinfo           
flinfo             

Bank # 1: Flash chip: STMICRO M29W324DB

CFI Query Results:
Primary Vendor Command Set: 0x0002 (AMD/Fujitsu Standard)
Primary Algorithm Table at 0x0040                       
Alternate Vendor Command Set: 0x0000 (None)             
No Alternate Algorithm Table                             
Vcc Min.: 2.7 V                                         
Vcc Max.: 3.6 V                                         
Vpp Min.: 11.5 V                                         
Vpp Max.: 12.5 V                                         
Typical byte/word write timeout: 16 us                   
Maximum byte/word write timeout: 256 us                 
Full buffer write not supported                         
Typical block erase timeout: 1024 ms                     
Maximum block erase timeout: 8192 ms                     
Chip erase not supported                                 
Device size: 0x400000 bytes (4 MiB)                     
Flash Device Interface description: 0x0002               
  - x8 / x16 via BYTE# with asynchronous interface       
Max. bytes in buffer write: 1                           
Number of Erase Block Regions: 2

Actual values used by U-Boot:
Word   write timeout:      2 ms
Buffer write timeout:      2 ms
Sector erase timeout:   8192 ms

Size: 4 MiB in 71 Sectors
  Sector Start Addresses:
    BFC00000 (RO) BFC02000 (RO) BFC04000 (RO) BFC06000 (RO) BFC08000 (RO)
    BFC0A000 (RO) BFC0C000 (RO) BFC0E000 (RO) BFC10000 (RO) BFC20000 (RO)
    BFC30000 (RO) BFC40000 (RO) BFC50000 (RO) BFC60000 (RO) BFC70000 (RO)
    BFC80000 (RO) BFC90000 (RO) BFCA0000 (RO) BFCB0000 (RO) BFCC0000 (RO)
    BFCD0000 (RO) BFCE0000 (RO) BFCF0000 (RO) BFD00000 (RO) BFD10000 (RO)
    BFD20000 (RO) BFD30000 (RO) BFD40000 (RO) BFD50000 (RO) BFD60000 (RO)
    BFD70000 (RO) BFD80000 (RO) BFD90000 (RO) BFDA0000 (RO) BFDB0000 (RO)
    BFDC0000 (RO) BFDD0000 (RO) BFDE0000 (RO) BFDF0000 (RO) BFE00000 (RO)
    BFE10000 (RO) BFE20000 (RO) BFE30000 (RO) BFE40000 (RO) BFE50000 (RO)
    BFE60000 (RO) BFE70000 (RO) BFE80000 (RO) BFE90000 (RO) BFEA0000 (RO)
    BFEB0000 (RO) BFEC0000 (RO) BFED0000 (RO) BFEE0000 (RO) BFEF0000 (RO)
    BFF00000 (RO) BFF10000 (RO) BFF20000 (RO) BFF30000 (RO) BFF40000 (RO)
    BFF50000 (RO) BFF60000 (RO) BFF70000 (RO) BFF80000 (RO) BFF90000 (RO)
    BFFA0000 (RO) BFFB0000 (RO) BFFC0000 (RO) BFFD0000 (RO) BFFE0000 (RO)
    BFFF0000 (RO)

=> printenv                                                 
printenv                                                     
nfsboot=run nfsload nfsargs;bootm                           
bootdelay=10                                                 
baudrate=57600                                               
autoload=no                                                 
stdin=nc                                                     
stdout=nc                                                   
stderr=nc                                                   
ipaddr=192.168.11.150                                       
netmask=255.255.255.0                                       
serverip=192.168.11.149                                     
ncip=192.168.11.149                                         
netretry=no                                                 
nc=setenv stdin nc;setenv stdout nc;setenv stderr nc         
ser=setenv stdin serial;setenv stdout serial;setenv stderr serial
ldaddr=82000000                                                 
guaddr=81000000                                                 
hdpart=0:1                                                       
hdload=echo Loading ${hdpart}:${hdfile};ext2load ide ${hdpart} ${ldaddr} ${hdfile}
boothd=setenv bootargs root=/dev/hda1;bootm ${ldaddr}                             
hdboot=run hdload boothd                                                         
flboot=setenv bootargs root=/dev/hda1;bootm bfc40000
emboot=setenv bootargs root=/dev/ram0;bootm bfc40000
rootpath=/opt/nfsroot/mipsel
nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off
nfsload=nfs ${ldaddr} ${serverip}:${rootpath}/${nfsfile}
bootretry=30
bootcmd1=run hdboot;run flboot
bootcmd2=run flboot
bootcmd3=run emboot
ubpart=0:3
ubfile=share/u-boot/u-boot-v2-mips.flash.bin
ubload=echo Loading ${ubpart}:${ubfile};ext2load ide ${ubpart} ${ldaddr} ${ubfile}
ubsaddr=bfc00000
ubeaddr=bfc2ffff
ubflash=protect off ${ubsaddr} ${ubeaddr};era ${ubsaddr} ${ubeaddr};cp.b ${ldaddr} ${ubsaddr} ${filesize};cmp.b ${ldaddr} ${ubsaddr} ${filesize}
upgrade=run ubload ubflash
ethact=rc32434_eth
bootcmd=run bootcmd1
bootargs=root=/dev/hda1
hdfile=/boot/vmlinux-2.6.23.17

Environment size: 1382/65532 bytes


_________________
Linkstation HD-H250LAN (LS2 mipsel)


Top
   
PostPosted: Sun Jun 07, 2009 9:35 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
is this the same/original hard drive?

are you sure that there is no damage somewhere to the ide cable or header?

do you have another hdd you can try in it?

it looks/sounds to me that it is not seeing the drive?

Ohh! did you run an ide reset?

try running these and posting back the output:
Code:
ide info
ide reset

_________________
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
   
PostPosted: Mon Jun 08, 2009 2:47 am 
Offline
Newbie
User avatar

Joined: Wed Jun 03, 2009 1:37 am
Posts: 6
davy_gravy wrote:
is this the same/original hard drive?

are you sure that there is no damage somewhere to the ide cable or header?

do you have another hdd you can try in it?

it looks/sounds to me that it is not seeing the drive?

Ohh! did you run an ide reset?

try running these and posting back the output:
Code:
ide info
ide reset


This is indeed the original 250GB drive. I have not known the drive to have any problems, it is getting old though.

I do not see any damage to the ide cable or header. I may see if I have a different cable around to try.

I have another 4GB hard drive I can try, of course it is old also. But hey maybe if it works it will point to the original drive having problems.

I agree it appears to me like it can't really see the drive in some fashion. However according to the output below it can read the partition table, there is just an issue with reading off the filesystem.

I also wanted to ask about the kernel image that is specified in hdfile. I have the one called vmlinux.... set in the environment. What is the difference between the vmlinux and the vmlinuz images? I don't think this is the problem at hand as ext2ls should still give me a listing even if I was specifying the wrong image file. ext2ls continues to not see anything of the filesystem.

Code:
=> ide info
ide info   

IDE device 0: Model: SAMSUNG SP2514N  Firm: VF100-33 Ser#: 0SB81JL0551386
            Type: Hard Disk                                             
            Supports 48-bit addressing                                   
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)           
=> ide reset                                                             
ide reset

Reset IDE: Bus 0: OK Bus 1: OK
  Device 0: Model: SAMSUNG SP2514N  Firm: VF100-33 Ser#: 0SB81JL0551386
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)
=> ide device hda1
ide device hda1

IDE device 0: Model: SAMSUNG SP2514N  Firm: VF100-33 Ser#: 0SB81JL0551386
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)
... is now current device
=> ide part hda
ide part hda

Partition Map for IDE device 0  --   Partition Type: DOS

Partition     Start Sector     Num Sectors     Type
    1                   63        72003267      83
    2             72003330         5012280      82
    3             77015610       411376455      83



After this output I iisued the command to boot and it failed to read from the filesystem in the exact same way as all the prior attempts.

I am now going to try this other hard drive to see if anything changes, and give the ide cable a good looking over too. :D

_________________
Linkstation HD-H250LAN (LS2 mipsel)


Top
   
PostPosted: Mon Jun 08, 2009 3:06 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
I see you tried the two uboot commands I gave you and some more...

Did you try the ext2ls after the ide reset?

I find it strange that it showed the partition... seems counterintuitive to think it would not also give a listing of files then...

_________________
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
   
PostPosted: Mon Jun 08, 2009 3:40 am 
Offline
Newbie
User avatar

Joined: Wed Jun 03, 2009 1:37 am
Posts: 6
I did hope maybe the reset would work some magic, but it did not.

Code:
=> ide info
ide info

IDE device 0: Model: SAMSUNG SP2514N  Firm: VF100-33 Ser#: 0SB81JL0551386
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)
=> ide reset
ide reset

Reset IDE: Bus 0: OK Bus 1: OK
  Device 0: Model: SAMSUNG SP2514N  Firm: VF100-33 Ser#: 0SB81JL0551386
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)
=> ext2ls ide 0:1 /boot
ext2ls ide 0:1 /boot
** Can not find directory. **
** Error ext2fs_ls() **
=>


I am going to stick the drive back in the KUbuntu box and run e2fsck to see if it reports any problems with the filesystem.

_________________
Linkstation HD-H250LAN (LS2 mipsel)


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 187 posts ]  Go to page Previous 19 10 11 12 13 Next

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