Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Sun Jan 21, 2018 2:03 am

All times are UTC+01:00




Post new topic  Reply to topic  [ 43 posts ]  Go to page 1 2 3 Next
Author Message
PostPosted: Sun Oct 07, 2007 9:30 am 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
[I also posted this in the PPC / HG forum, but I'm not sure which one is more appropriate. I didn't get a reply there, so I'm just trying here. If anyone is offended, please just delete on of the threads.]

Hi,

I decided to reboot my HG that had been running continuously with the 2.6 kernel (I guess it's v62, that's what /boot/versionHG tells me) for some months. Unfortunately, it didn't come back on. Instead, after power on, for quite some time the LINK/ACT led is on, while the POWER led is blinking. Then, after a few minutes, the DIAG led blinks repeatedly for 6 times.

So, I removed the HD from the HG, plugged it into my PC, and mounted the drive. /boot doesn't seem to contain anything special: No *running, and there is a try_new_kernelHG file containing vmlinux.binHG. No boot.log either. In fact, the absence of the *running file is strange: It seems like the 2.6 kernel doesn't come up at all.

I have no idea how to start to fix this. My 2.4 installation on the HG has been broken since the beginning, so I cannot boot into 2.4. All I can do is mount the drive on my PC. Would manually installing the newest 2.6 kernel (v84) be a good idea? I decided not to do this yet, since I couldn't find the details on manual installation anymore. Obviously, I'm not that keen on running the webinstaller on my PC, given that the paths on my PC do not match those on the HG.

I'd appreciate any pointers on how to fix this!

Koen


Top
   
PostPosted: Sun Oct 07, 2007 3:40 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
Might be a hardware issue, probably the hard disk drive not responding fast enough. Try the most recent bootloader tarball and see if that gives. /dev/hda[13] are checked and error-free, aren't they?


Top
   
PostPosted: Sun Oct 07, 2007 5:39 pm 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
Thanks for the suggestions! I downloaded the latest bootloader, mounted the 1st HG partition on /root/hg, and ran

tar -C /root/hg -xvzf latest-bootloader.tar.gz

Unfortunately, that didn't change the HG's behaviour. I might be missing a step though. My try_new_kernelHG contains vmlinux.binHG, but vmlinux.binHG is a symlink to vmlinux.binPPC, which does not exist. Is that the way it should be?

/dev/hdc[13] (as they are called on my PC) are clean, according to e2fsck.

When booting, I noticed that first there is some activity, then the LINK/ACT LED is off for a moment, then back on with the POWER LED flashing. Probably not important, but it seems there is at least some HD activity.

Just to be sure I checked the amount of free disk space on hdc1, but that seems normal (162M).


Top
   
PostPosted: Sun Oct 07, 2007 9:27 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
Sorry, the new bootloader uses a 'wrong' symlink for your 'old' kernel. Correct this manually please and see if that gives...


Top
   
PostPosted: Mon Oct 08, 2007 4:50 pm 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
I'm not really sure which symlink I am supposed to fix, or in which way. I have System.mapHG pointing to the non-existent System.mapPPC, configHG pointing to the non-existing configPPC, versionHG pointing to the non-existing versionPPC and vmlinux.binHG pointing to the non-existent vmlinux.binPPC. Since these files (*PPC) do not exist, I have no idea how to fix this. Obviously, the old files in my /boot directory are overwritten by these symlinks. So, how can I get the right ones back? Would it be easier to manually install a new kernel (v84) instead?

Thanks!


Top
   
PostPosted: Mon Oct 08, 2007 4:57 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
v84 would be a good choice, IMHO. --

But if you copy your existing (well, backed-up, sorry for that!) kernel to /boot/vmlinux.binPPC and your System.map to /boot/System.mapPPC, everything should work.


Top
   
PostPosted: Mon Oct 08, 2007 5:52 pm 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
As they say: Oops! :oops: I guess you do not have an archive of old versions?

I'll check if I can find the tar files on my HG - not sure if the webinstaller removes the downloads. If I cannot find them, I guess I'll have to manually install v84. I assume simply untarring those four tar files (kernel, bootloader, upgradehelper, modules) will do the trick?

[update: I just noticed that there is an archive; cool! I'll try to get the right files from there for v62]

[new update: There is no v62 kernel on that page. Will try to get the v63]


Top
   
PostPosted: Mon Oct 08, 2007 7:11 pm 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
No luck. I tried v63 - no change. Tried v84 - no change. So, unless I need to do more than just untar those four files, I'm pretty much stuck. I guess I'll have to move the services to another computer. No fun...


Top
   
PostPosted: Mon Oct 08, 2007 8:06 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
Check if you've got the file /etc/default/boot_new.sh_local (cp /etc/default/boot_new.sh_local_sample /etc/default/boot_new.sh_local)


Top
   
PostPosted: Mon Oct 08, 2007 9:50 pm 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
The file was missing indeed, but fixing that didn't resolve anything. I'm rather lost... Is there any way to do a 'fresh' flash in this case (maybe first install 2.4, then 2.6)? I can afford loosing hda1 (that is, I can backup it, and restore the important files later), but I currently cannot backup all of hda3.

I appreciate all your efforts!


Top
   
PostPosted: Mon Oct 08, 2007 10:15 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
You can flash FreeLink or OpenLink, which writes the kernel to flash ROM and replaces /dev/hda1, then run the webinstaller to upgrade to 2.6. How did you lose your kernel 2.4?


Top
   
PostPosted: Tue Oct 09, 2007 7:39 am 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
Thanks, I'll try to do that. The main problem is that I'm renovating my home, so I currently do not have that much time to play around with my HG. But flashing is relatively fast, so I'll do that to find out if it's a hardware issue. As I recall, flashing FreeLink replaces the flash ROM, but installing 2.6 doesn't, so if I backup hda1, after flashing I should be able to get my system back in the current state by just restoring the backup.

I don't know how I broke 2.4. I probably removed some Debian package that's needed for 2.4 but not for 2.6. It's hard to tell on a headless system...


Top
   
PostPosted: Wed Oct 10, 2007 1:11 pm 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
What would be the safest way of flashing this HG? First I have to get it into EM mode: Would simply reformatting hda1 suffice for that? If not, how would I get there without access to a console on the box (so no echo NGNG or something like that)?

Thanks!


Top
   
PostPosted: Wed Oct 10, 2007 1:59 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
Flashing is not my playground, sorry


Top
   
PostPosted: Wed Oct 10, 2007 2:05 pm 
Offline
Newbie

Joined: Thu Aug 17, 2006 3:13 pm
Posts: 63
I'll try in a more appropriate forum. Thanks!


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 43 posts ]  Go to page 1 2 3 Next

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 3 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